On Thu, Sep 06, 2007 at 12:57:56AM -0400, Simon Ruggier wrote:
If you build the gui as a standalone package, in a script perhaps, you
should still be able to build it with no extra -I flags. The above
change only affects the build of the main library (specifically, the
src directory), and the
On Tue, Sep 04, 2007 at 10:01:41PM -0400, Simon Ruggier wrote:
Ok, I've fixed the inaccurate help string, removed the extra build
dep, and made the make dist warning into an error :)
Patch applied, thanks!
This change introduced something that I didn't notice the first time:
---
On 9/5/07, Chris Frey [EMAIL PROTECTED] wrote:
On Tue, Sep 04, 2007 at 10:01:41PM -0400, Simon Ruggier wrote:
Ok, I've fixed the inaccurate help string, removed the extra build
dep, and made the make dist warning into an error :)
Patch applied, thanks!
This change introduced something
On 9/4/07, Chris Frey [EMAIL PROTECTED] wrote:
Thanks for the patch! I've taken a look at it, and there are a couple
things I'm not keen on. If you send me a patch that addresses these
issues, I'll probably apply it. :-) You've fixed a number of configure
problems and made it more robust,
Here, test this out - everything should work the same, except that
there are --enable-gui and --enable-opensync flags that will configure
those directories and include them in all the recursive targets. I
also fixed all the Makefiles so that make dist generates a tarball
similar to the release
On Sun, Sep 02, 2007 at 12:08:59AM -0400, Simon Ruggier wrote:
Is it intentional that the gui and opensync plugin directories need to
be manually built? I can fix the build system and update Debian
packaging to automate this if it makes sense.
Yes, this was intentional. The more subprojects
On 9/2/07, Chris Frey [EMAIL PROTECTED] wrote:
It can be automated with a script, and I could drop a build-all style
script in the root directory if this is a major problem.
How about building them conditionally with a configure flag like
--enable-opensync?
On Sun, Sep 02, 2007 at 12:32:09PM -0400, Simon Ruggier wrote:
On 9/2/07, Chris Frey [EMAIL PROTECTED] wrote:
It can be automated with a script, and I could drop a build-all style
script in the root directory if this is a major problem.
How about building them conditionally with a
On 9/2/07, Chris Frey [EMAIL PROTECTED] wrote:
The advantage to keeping them separate is that they can be split into
separate source tarballs someday if needed. Not that it's likely, but
might be handy someday.
Are there real advantages to having things in one configure setup?
I don't
On Sun, Sep 02, 2007 at 01:29:35PM -0400, Simon Ruggier wrote:
I have good news :) It's possible to have the best of both worlds with
the AC_CONFIG_SUBDIRS macro, which will recursively call configure in
the subdirectories. It looks like I can add this without breaking any
of the above use
10 matches
Mail list logo
