Re: Modules and GnuCash (was: MacIntel trunk build failure)

2007-02-15 Thread Derek Atkins
Hi, Quoting David Hampton <[EMAIL PROTECTED]>: > On Thu, 2007-02-15 at 12:43 -0500, Peter McAlpine wrote: > >> And so I pose this question: is GnuCash to have a modular design or >> not? If yes, then the modules need to be ripped apart and made to use >> a strict interface. If no, then the GNCMod

Re: Modules and GnuCash (was: MacIntel trunk build failure)

2007-02-15 Thread Josh Sled
On Thu, 2007-02-15 at 12:43 -0500, Peter McAlpine wrote: > And so I pose this question: is GnuCash to have a modular design or > not? If yes, then the modules need to be ripped apart and made to use > a strict interface. If no, then the GNCModule code should be ripped > out and everything should (g

Re: Modules and GnuCash (was: MacIntel trunk build failure)

2007-02-15 Thread David Hampton
On Thu, 2007-02-15 at 12:43 -0500, Peter McAlpine wrote: > And so I pose this question: is GnuCash to have a modular design or > not? If yes, then the modules need to be ripped apart and made to use > a strict interface. If no, then the GNCModule code should be ripped > out and everything should (

Modules and GnuCash (was: MacIntel trunk build failure)

2007-02-15 Thread Peter McAlpine
After some investigation it's seems to me that it would be a good idea to set a clear direction for how GnuCash uses modules. Here is the problem I see exists now: Upon program initialization the modules are loaded (as GModule's), but throughout the core code and the module code GnuCash is directl

Re: MacIntel trunk build failure

2007-02-13 Thread Derek Atkins
I suspect that src/register/register-core and src/register/register-gnome should both be turned into LIBRARIES. I haven't looked at the patch to see what else might want to be a library instead of a module. -derek Quoting Christian Stimming <[EMAIL PROTECTED]>: > -BEGIN PGP SIGNED MESSAGE--

Re: MacIntel trunk build failure

2007-02-13 Thread Christian Stimming
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter McAlpine schrieb: > While I certainly don't claim to be an expert on the autotools, I > couldn't grasp why the modules' shared libraries should want to > (statically) link against each other, so I removed the offending > libraries from the Makefi

Re: MacIntel trunk build failure

2007-02-12 Thread Peter McAlpine
You're correct: our errors are the same. I skipped reading over your entire thread because the error you pasted on your first post didn't match my own. I spent some time over the last couple days investigating this. A number of modules are telling libtool (in their respective Makefile.am'

Re: MacIntel trunk build failure

2007-02-11 Thread Jeff Carneal
Hey Peter, You didn't include all the output, but this looks suspiciously like what I encountered under the thread 'libtool problem on OS X'. I documented there my efforts to try forcing OS X to use gnu libtool, but I still can't get it to work. Really wishing I had some experience with

MacIntel trunk build failure

2007-02-10 Thread Peter McAlpine
Hello, I'm having trouble building trunk on my MacIntel. I can build 2.0.4 source fine. ... gcc -dynamiclib ${wl}-flat_namespace ${wl}-undefined ${wl}suppress - o .libs/libgncmod-register-gnome.dylib .libs/gncmod-register- gnome.o .libs/combocell-gnome.o .libs/datecell-gnome.o .libs/ formu