Quoting Bob Proulx <[EMAIL PROTECTED]>:
Dan McMahill wrote:
Ralf Wildenhues wrote:
>Just curious: what's the reason for the ordering constraint?
When static objects use inheritance, the base class must be initialized
before anything can be derived from it. At least that's what I've been
told.
Dan McMahill wrote:
> Ralf Wildenhues wrote:
> >Just curious: what's the reason for the ordering constraint?
>
> When static objects use inheritance, the base class must be initialized
> before anything can be derived from it. At least that's what I've been
> told. On this particular project,
Ralf Wildenhues wrote:
Hello Dan,
Now the problem is that the link order needs to be
src1.o src2.o src3.o src4.o src5.o
Just curious: what's the reason for the ordering constraint?
When static objects use inheritance, the base class must be initialized
before anything can be derived
Quoting Ralf Wildenhues <[EMAIL PROTECTED]>:
Hello Dan,
* Dan McMahill wrote on Tue, Nov 28, 2006 at 02:56:40PM CET:
foo_SOURCES= src1.cc src4.cc src5.cc
nodist_foo_SOURCES= src2.cc src3.cc
and some extra suffix rules that specify how src2.cc and src3.cc are
created (they are generated at bu
Hello Dan,
* Dan McMahill wrote on Tue, Nov 28, 2006 at 02:56:40PM CET:
>
> foo_SOURCES= src1.cc src4.cc src5.cc
> nodist_foo_SOURCES= src2.cc src3.cc
>
> and some extra suffix rules that specify how src2.cc and src3.cc are
> created (they are generated at build time).
>
> Now the problem is t
Hello,
I'm having some problems with getting the correct link order using automake.
I have something like:
foo_SOURCES= src1.cc src4.cc src5.cc
nodist_foo_SOURCES= src2.cc src3.cc
and some extra suffix rules that specify how src2.cc and src3.cc are
created (they are generated at build time).
