Cairo should support building in a directory separate from the source directory. For example, GTK's autogen.sh can be run from a separate directory, where all build-related files will end up: [gtk+-bld]$ /home/fitzsim/sources/gtk+/autogen.sh --prefix=/home/fitzsim/install Cairo's configury should also support this form of operation. It means that build files don't clutter up the source directory, so e.g. grep doesn't search through .o files. Also, it means you can clear out the build files simply by just rm -rf builddir. JHBuild assumes this mode of operation by default.
Is there a bug here? I believe that "make distcheck" does a non-srcdir build and we've used that for every snapshot for a long time. Or is it autogen.sh in particular that has a problem? Either way, we'll need more specifics about what the problem is before we can fix anthing.
Ah, OK. I should have been clearer. Likely just autogen.sh is the problem. I'm working with JHBuild, which assumes that autogen.sh is runnable from the build directory. For example, GTK's autogen.sh changes to the source directory if it's not being run from there already, runs the autotools, changes back to the build directory and runs configure from there.
2005-08-21 Owen Taylor <otaylor@redhat.com> * autogen.sh: When invoked as, say, ../autogen.sh, switch to the sourcedir to run the auto*. Based on corresponding code in GTK+'s autogen.sh. (#3402, Thomas Fitzsimmons) Ran into an issue with the non-srcdir build when gtk-doc wasn't disabled, filed as #4170.
Move bugs against "cvs" version to "0.9.3" so we can remove the "cvs" version.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.