On Mon, 2009-01-26 at 21:39 +0100, Federico Ferri wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> sorry Mark,
> 
> I tried with synce-gvfs 0.2.1 with and without --with-gvfs-source option.
> 
> without that option it compiles fine, but with your gvfs-tree.
> when I use the option (actually with a gvfs-1.0.3 tree) it fails in
> make dist, which makes the whole build fail.
> 
> attached the two logfiles (successful and unsuccessful build)
> 
> 

It's because we're treating the gvfs source as part of our tree, so it's
using relative paths, and passing an absolute path to configure. Can you
pass a relative path ?

> regards,
> Federico Ferri
> 
> 
> Mark Ellis wrote:
> > Federico, Adam, and anyone else that intends to package gvfs,
> >
> > I've finally managed to make the build system saner, it's amazing
> > what sticks if you throw enough autofoo at something :)
> >
> > --with-gvfs-source in ./configure will now use an unbuilt gvfs tree
> >
> >
> > There are dummy files in svn for the gvfs sources which will stop
> > the build if you don't give a valid gvfs source. The build will
> > work normally if you pass the location of a valid tree.
> >
> > Given a valid tree, make dist will import the required files from
> > the gvfs tree to build the package. This package will use these
> > imported files, but you can still use the ./configure flag to force
> > it to use another gvfs source. This is what I intend to do for the
> > next release, so it will be a self contained package, but if
> > something changes you can still use it with another gvfs.
> >
> > As an unimportant aside, you can make dist from svn without giving
> > it a gvfs tree, and the package will still contain the dummy files.
> >
> >
> > Hope that make sense !
> >
> > Mark
> >
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iEYEARECAAYFAkl+H38ACgkQV/B5axfzrPt39ACgvn+tUDYdgsbsK5F+RHYryJt2
> BEAAni/TUPuOckjEJDS7EZR0Xn281PcP
> =EW6k
> -----END PGP SIGNATURE-----
> 

Attachment: signature.asc
Description: This is a digitally signed message part

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel

Reply via email to