Re: Passing options to the linker

2006-05-24 Thread Paulo J. Matos
On 24/05/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: * Ralf Wildenhues wrote on Wed, May 24, 2006 at 05:40:43PM CEST: > * Paulo J. Matos wrote: > > > This is needed due to some conclusions I referred in: > > http://groups.google.com/group/gnu.g++.help/browse_frm/thread/46517713685155f0/ > > H

Re: Non-recursive makefiles

2006-05-24 Thread Olly Betts
On Wed, May 24, 2006 at 01:57:15PM +0200, Ralf Wildenhues wrote: > * Olly Betts wrote on Wed, May 24, 2006 at 12:24:53PM CEST: > > * Generally, it would be useful for the manual to go into a bit more > > detail about how to approach all this. > > Agreed. I'm sure Alexandre will gladly accept co

Re: Passing options to the linker

2006-05-24 Thread Paulo J. Matos
On 24/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote: On 24/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote: > No, it is still not working. If we concentrate ourselves only in the > first situations where I want the libraries to be all linked > statically I have for the core: > bin_PROGRAMS = ex

Re: Non-recursive makefiles

2006-05-24 Thread Morrison
On Wed, 2006-05-24 at 13:57 +0200, Ralf Wildenhues wrote: [snip..] - Non-recursive makefiles are suitable for projects of mediocre complexity. For complex projects the price of flat Makefile is high and often doesn't pay off. Hear hear! After spending a fair bit of time considering the non

Re: Passing options to the linker

2006-05-24 Thread Paulo J. Matos
On 24/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote: No, it is still not working. If we concentrate ourselves only in the first situations where I want the libraries to be all linked statically I have for the core: bin_PROGRAMS = extsat extsat_SOURCES = esatmathcluster.cc ... extsat_LDFLAGS=-ex

Re: Passing options to the linker

2006-05-24 Thread Paulo J. Matos
On 24/05/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: * Ralf Wildenhues wrote on Wed, May 24, 2006 at 05:40:43PM CEST: > * Paulo J. Matos wrote: > > > This is needed due to some conclusions I referred in: > > http://groups.google.com/group/gnu.g++.help/browse_frm/thread/46517713685155f0/ > > H

Re: Passing options to the linker

2006-05-24 Thread Paulo J. Matos
On 24/05/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: Hi Paulo, * Paulo J. Matos wrote on Wed, May 24, 2006 at 05:34:50PM CEST: > > I'd like to know what's the best way to pass some options to the linker? > I'd like to add -Wl,--whole-archive to the linker before the libraries > I want to link

Re: Passing options to the linker

2006-05-24 Thread Ralf Wildenhues
* Ralf Wildenhues wrote on Wed, May 24, 2006 at 05:40:43PM CEST: > * Paulo J. Matos wrote: > > > This is needed due to some conclusions I referred in: > > http://groups.google.com/group/gnu.g++.help/browse_frm/thread/46517713685155f0/ > > Hmm, that looks very fishy: Never mind. Please try putti

Re: Non-recursive makefiles

2006-05-24 Thread Ralf Corsepius
On Wed, 2006-05-24 at 17:01 +0200, Ralf Wildenhues wrote: > * Ralf Corsepius wrote on Wed, May 24, 2006 at 04:34:02PM CEST: > It often helps a lot to have fewer Makefiles than one per directory, > especially in parts of a source tree where they are rather simple. > > > - subdir makefile.am-fragme

Re: Passing options to the linker

2006-05-24 Thread Ralf Wildenhues
Hi Paulo, * Paulo J. Matos wrote on Wed, May 24, 2006 at 05:34:50PM CEST: > > I'd like to know what's the best way to pass some options to the linker? > I'd like to add -Wl,--whole-archive to the linker before the libraries > I want to link, which are listed in LIBADD. Any ideas on how to do > th

Passing options to the linker

2006-05-24 Thread Paulo J. Matos
Hi all, I'd like to know what's the best way to pass some options to the linker? I'd like to add -Wl,--whole-archive to the linker before the libraries I want to link, which are listed in LIBADD. Any ideas on how to do this? This is needed due to some conclusions I referred in: http://groups.goo

Re: Non-recursive makefiles

2006-05-24 Thread Ralf Wildenhues
* Ralf Corsepius wrote on Wed, May 24, 2006 at 04:34:02PM CEST: > > - Non-recursive makefiles are suitable for projects of mediocre > complexity. For complex projects the price of flat Makefile is high and > often doesn't pay off. Yes, agreed as well, but I think nobody is suggesting that you have

Re: Non-recursive makefiles

2006-05-24 Thread Ralf Corsepius
On Wed, 2006-05-24 at 13:57 +0200, Ralf Wildenhues wrote: > Hi Olly, > > * Olly Betts wrote on Wed, May 24, 2006 at 12:24:53PM CEST: > > I've been looking at the feasibility of converting a project (Xapian) > > using autoconf+automake+libtool to using non-recursive makefiles. > > > I'm fairly c

Re: Non-recursive makefiles

2006-05-24 Thread Bob Friesenhahn
On Wed, 24 May 2006, Olly Betts wrote: * I'm not sure what to call the Makefile.am snippets in the subdirectories. I looked at GraphicsMagick which was suggested to be Likewise. :-) harder to maintain. It'd be really handy to have a way to automatically prepend the directory that the cu

Re: Non-recursive makefiles

2006-05-24 Thread Ralf Wildenhues
Hi Olly, * Olly Betts wrote on Wed, May 24, 2006 at 12:24:53PM CEST: > I've been looking at the feasibility of converting a project (Xapian) > using autoconf+automake+libtool to using non-recursive makefiles. > I'm fairly convinced it'll be an improvement overall, but there are a > few issues I

Non-recursive makefiles

2006-05-24 Thread Olly Betts
I've been looking at the feasibility of converting a project (Xapian) using autoconf+automake+libtool to using non-recursive makefiles. Currently each subdirectory produces a libtool convenience library and these are linked into the main installable library. There are a few convenience librarie