RE: Compiling deja-dup

RE: Compiling deja-dup

[Maarten Jacobs]

Hello all,

I have a noob question for direction. I thought it would be an interesting project to attempt to compile deja-dup under Cygwin. (So far I have not been successful finding out if this was done successfully before, or not).

However - it appears I have trouble getting my environment set up to allow it to compile. When I try to compile deja-dup, it complains about not having the "libpeas" package. I couldn't find "libpeas" using the cygwinsetup, so I downloaded the source for that.

Well, libpeas won't compile because it can't find "gobject-introspection". I installed everything I could find from setup related to "gobject-introspection", still no luck.

So I tried compiling gobject-introspection from source - again no luck as it fails with a pretty cryptic error.

(I can replicate all the variosu different errors I come across if anybody's interested).

The long and short of my question is: is there a way for me to make sure that all my build dependencies are met, without having to actually go through the compilation process?

Thanks,

Maarten 		 	   		  
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Compiling deja-dup

[Larry Hall (Cygwin)]

On 4/29/2013 5:22 PM, Maarten Jacobs wrote:
> The long and short of my question is: is there a way for me to make sure
> that all my build dependencies are met, without having to actually go
> through the compilation process?

Many packages list their dependencies on the project site.  That's one
way.  Another is to look at the packaging script for other targets.  There's
probably allot of overlap.  In this particular case, you can grab
Yaakov's port (<http://sourceware.org/cygwinports/>) and either use
it directly or peek inside his cygport script to get some help.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

RE: Compiling deja-dup

[Maarten Jacobs]

Thanks! Helpful hints. After posting initially I progressed a little further. I'm starting on my own "cheat sheet" but wanted to share a few observations that may be of use to someone who travels the same road I'm going down.

1. Make sure your path does not include " ". Some of the packages I tried to compile from source failed with funny errors eluding to "Files/Windows" (obviously "Program Files/Windows") - once I updated my Path to not include references to "Program Files" those errors went away.
2. cygport is a good tool - use it. As it turns out it helps - but I still had to do significant sleuthing manually to make things compile.
3. Most of the source I worked with came from ftp://cygwin.org/pub/cygwinports/release-2/GNOME, as it turned out a very good source of CygWin packages - including a few that not appear on Cygwin's setup (such as libpeas that I have not been able to find)
4. cygport generally does a good job job of setting up, compiling and installing, but I found a few cases where cygport did not correctly install a package. I had to manually install a compiled package (notably for libpeas and libnotify). In those cases one wants to cd to <package>/build and run 'make install'.
5. A number of my problems were caused by the fact that I was building my source on a network drive (as my home directory happens to be located on a share). My experience shows that building on the local machine works a lot better. I think it has something to do with symbolic links not working right on network shares (or is that just Samba network shares?)
6. Eventually I learned that "configure" does not at all like my pkg-config. In the process of doing its thing, configure would unset $PKG_CONFIG, so it would bomb out eventually with an error like "your pkg-config script cannot be found or is too old". I worked around this by exporting the necessary compiler flags (think $DUP_CFLAGS, $DUP_LIBS, etc.) prior to running configure. (I used pkg-config to actually set those environment variables).
7. All of the above eventually led me to be able to actually compile deja-dup!
8. I decided to use 'make install" to install deja-dup... Which may explain why it's complaining about not being able to find certain DLLs when I try to run it.
   8a. Still need to try "cygport install" to see if that helps any...
9. I did get deja-dup to run if I execute it from a location that contains the necessary DLLs... It seems to run fine.

NET: I got it to work (happy!), I learned a lot (happy!). I also have a version of deja-dup that runs under windows... Now for testing to see if it actually does what it's supposed to do (create and maintain backups).
If anybody believes this compiled version of deja-dup would be share worthy I'm happy to do so.---------------------------------------- 		 	   		  
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

RE: Compiling deja-dup

[Maarten Jacobs]

Larry, thanks for your responses...

 > 1. Make sure your path does not include " ". Some of the packages I
 > tried to compile from source failed with funny errors eluding to "Files/Windows"
 > (obviously "Program Files/Windows") - once I updated my Path to not include
 > references to "Program Files" those errors went away.

 I assume you meant "Program Files" in your opening statement. Your solution
 works. The alternative is to quote the internal paths with spaces or
 otherwise escape the spaces.

>> Actually the error specifically states "Files/Windows". It took me a turn to figure out it was complaining about my path. I did try escaping the spaces in $PATH with a \ but that didn't have the desired effect... So I decided to update PATH to not have any spaces.

 > 3. Most of the source I worked with came from
 > ftp://cygwin.org/pub/cygwinports/release-2/GNOME, as it turned out a very
 > good source of CygWin packages - including a few that not appear on Cygwin's
 > setup (such as libpeas that I have not been able to find)

 More than "a few" packages in Cygwin Ports are not in the official
 distribution. :-) They can all be installed with 'setup.exe' if you add the
 path to the Cygwin Ports repository to 'setup.exe' though.

>> Can you explain this a bit more - I'm not sure how to "add the path to setup.exe". I tried using the above URL from setup.exe - but it didn't give me an option to install deja-dup directly. 

 > 5. A number of my problems were caused by the fact that I was building
 > my source on a network drive (as my home directory happens to be located on a
 > share). My experience shows that building on the local machine works a lot
 > better. I think it has something to do with symbolic links not working right
 > on network shares (or is that just Samba network shares?)

 Permissions are more problematic on your typical network share. If you can
 avoid them, that makes things easier, yes.

 > If anybody believes this compiled version of deja-dup would be share
 > worthy I'm happy to do so.----------------------------------------

 Is it really different from the one on Cygwin Ports? Regardless, if you
 want to provide it as an official package for Cygwin, read through
 <http://cygwin.com/setup.html> and in your ITA/ITP, just ask Yaakov if
 he minds you picking up this package and its dependencies from him.

>> Hmm. It probably isn't - however (as I indicated above) I've not been able to figure out how I would go about installing it "directly" - i.e. without first downloading the source from Cygwin Ports and compiling/installing. Perhaps there's another trick I'm not aware of. 		 	   		  
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple