Re: Running initial code when in library

2006-05-25 Thread Paulo Matos
Paul Pluzhnikov wrote: > "Paulo Matos" <[EMAIL PROTECTED]> writes: > > > Why is it of my doing? Because I'm trying a design pattern which is not > > so common after all? > > No, it's because you choose to build your design with autotools, > which appear not to be flexible enough to do so without s

Re: Running initial code when in library

2006-05-25 Thread Paul Pluzhnikov
"Paulo Matos" <[EMAIL PROTECTED]> writes: > Why is it of my doing? Because I'm trying a design pattern which is not > so common after all? No, it's because you choose to build your design with autotools, which appear not to be flexible enough to do so without special hacks. Cheers, -- In order

Re: Running initial code when in library

2006-05-25 Thread Paulo Matos
Paul Pluzhnikov wrote: > "Paulo Matos" <[EMAIL PROTECTED]> writes: > > > Isn't this a normal > > problem: an interface with some libraries using the interface. The core > > creates and destroys the object of the libraries through the interface. > > No, I don't believe this is a widely-used design

Re: Running initial code when in library

2006-05-24 Thread Paul Pluzhnikov
"Paulo Matos" <[EMAIL PROTECTED]> writes: > Isn't this a normal > problem: an interface with some libraries using the interface. The core > creates and destroys the object of the libraries through the interface. No, I don't believe this is a widely-used design pattern, at least not with static li

Re: Running initial code when in library

2006-05-24 Thread Paulo Matos
Paul Pluzhnikov wrote: > > I have no other solution than using --whole-archive to linker right now, > > You do have other solutions, e.g. explicitly list objects that must > be linked in, and the linker will do the right thing (pulling in > only necessary parts of the libraries). > Unfortunately

Re: Running initial code when in library

2006-05-24 Thread Paul Pluzhnikov
"Paulo Matos" <[EMAIL PROTECTED]> writes: > I didn't know the linker was going to search for unused objects and if > not used it would not include them. Nice to know. All linkers I know (even the MS ones) work that way, and (AFAICT) always did. > I don't understand why this works this way. It's

Re: Running initial code when in library

2006-05-24 Thread Paulo Matos
Paul Pluzhnikov wrote: > > GNU-ld specific solution (assuming you really do want all of > libbf libot and libfm to be included in the executable): > > > /bin/sh ../libtool --tag=CXX --mode=link g++ -ggdb -Wall -std=c++98 ... > > esatcluster.o extsat.o esatlogger.o > -Wl,--whole-archive > > ../l

Re: Running initial code when in library

2006-05-23 Thread Paul Pluzhnikov
"Paulo Matos" <[EMAIL PROTECTED]> writes: > Your guess is correct. I thought so :) > Verbose output from linker is wierd: Nothing weird about it ... > After the .o files: > attempt to open ../lib/bf/src/.libs/libbf.a succeeded > attempt to open ../lib/ot/src/.libs/libot.a succeeded > attempt

Re: Running initial code when in library

2006-05-23 Thread Paulo Matos
Paul Pluzhnikov wrote: > "Paulo Matos" <[EMAIL PROTECTED]> writes: > > > Any ideas on how can I know if the code is linked as shared or as > > static? > > What's the link command line? > > Add to it '-Wl,--verbose' and you'll see which libraries the linker > is actually using. > > You can also eas

Re: Running initial code when in library

2006-05-23 Thread Paul Pluzhnikov
"Paulo Matos" <[EMAIL PROTECTED]> writes: > Any ideas on how can I know if the code is linked as shared or as > static? What's the link command line? Add to it '-Wl,--verbose' and you'll see which libraries the linker is actually using. You can also easily verify my guess (that the objects you

Re: Running initial code when in library

2006-05-23 Thread Paulo Matos
Paul Pluzhnikov wrote: > "Paulo Matos" <[EMAIL PROTECTED]> writes: > > > I have singleton and everything should work fine but it is not: > > In that case, two possibilities come to mind: > - you didn't build your exe correctly (always link C++ code with 'g++') > - the code containing global 'proxy

Re: Running initial code when in library

2006-05-23 Thread Paul Pluzhnikov
"Paulo Matos" <[EMAIL PROTECTED]> writes: > I have singleton and everything should work fine but it is not: In that case, two possibilities come to mind: - you didn't build your exe correctly (always link C++ code with 'g++') - the code containing global 'proxy p;' objects isn't actually linked

Re: Running initial code when in library

2006-05-23 Thread Paulo Matos
Paul Pluzhnikov wrote: > "Paulo Matos" <[EMAIL PROTECTED]> writes: > > > Problem is that sometimes (I know this is not > > usual in current software but I really need this) I need to pack all > > the software and plugins into one big piece of code so I link every > > plugin statically to the core.

Re: Running initial code when in library

2006-05-23 Thread Paul Pluzhnikov
"Paulo Matos" <[EMAIL PROTECTED]> writes: > Problem is that sometimes (I know this is not > usual in current software but I really need this) I need to pack all > the software and plugins into one big piece of code so I link every > plugin statically to the core. This should work just fine. You s