Re: Multiple libtool libs from same sources

[Adam C Powell IV]

Alexandre Oliva wrote:

> On Aug  2, 2000, Adam C Powell IV <[EMAIL PROTECTED]> wrote:
>
> > Adam C Powell IV wrote:
> >> Greetings,
> >>
> >> I'd like to build two libtool libs from the same sources using different
> >> CFLAGS.
>
> > Okay, I assume the lack of reply means it can't be done.
>
> IIRC, CVS automake supports libfoo_la_CFLAGS

Thank you very much, yes, that would solve the problem.  I'll look into this.

-Adam P.

Re: Multiple libtool libs from same sources

[Alexandre Oliva]

On Aug  2, 2000, Adam C Powell IV <[EMAIL PROTECTED]> wrote:

> Adam C Powell IV wrote:
>> Greetings,
>> 
>> I'd like to build two libtool libs from the same sources using different
>> CFLAGS.

> Okay, I assume the lack of reply means it can't be done.

IIRC, CVS automake supports libfoo_la_CFLAGS

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

Re: Multiple libtool libs from same sources

[Adam C Powell IV]

Adam C Powell IV wrote:

> Greetings,
>
> I'd like to build two libtool libs from the same sources using different
> CFLAGS.

Okay, I assume the lack of reply means it can't be done.

So then, how do I get automake to not kill make dist when I set
libtwo_OBJECTS?  Is there something like a reverse -Werror flag (to make
errors into warnings)?  Note that it produces a perfectly good Makefile.in,
so the error must not be fatal...

Thanks,

-Adam P.

Multiple libtool libs from same sources

[Adam C Powell IV]

Greetings,

I'd like to build two libtool libs from the same sources using different
CFLAGS.  Following the "ctags/etags" example on the info page, I did the
following:

lib_LTLIBRARIES = libtwo2.la libtwo.la
# Yes, I know _OBJECTS isn't kosher, but don't see another way to do
it...
libtwo2_la_OBJECTS = twostep2.lo overhead2.lo boundary2.lo
libtwo2_la_LDFLAGS = -version-info 0:0:0 $(BLAS_LIBS)

libtwo_la_SOURCES = twostep.c overhead.c boundary.c
libtwo_la_LDFLAGS = -version-info 0:0:0 $(BLAS_LIBS)

# This is from the automake info page, generating multiple .os from each
.c:
# (adapted for libtool :-)
twostep.lo: $(srcdir)/twostep.c twostep2.lo
 $(LTCOMPILE) $(INCLUDES) -c $<
twostep2.lo: $(srcdir)/twostep.c
 $(LTCOMPILE) $(INCLUDES) -DSHIFT=2 -c $< && mv twostep.lo twostep2.lo
&& mv twostep.o twostep2.o
overhead.lo: $(srcdir)/overhead.c overhead2.lo
 $(LTCOMPILE) $(INCLUDES) -c $<
overhead2.lo: $(srcdir)/overhead.c
 $(LTCOMPILE) $(INCLUDES) -DSHIFT=2 -c $< && mv overhead.lo overhead2.lo
&& mv overhead.o overhead2.o
boundary.lo: $(srcdir)/boundary.c boundary2.lo
 $(LTCOMPILE) $(INCLUDES) -c $<
boundary2.lo: $(srcdir)/boundary.c
 $(LTCOMPILE) $(INCLUDES) -DSHIFT=2 -c $< && mv boundary.lo boundary2.lo
&& mv boundary.o boundary2.o

The problem, of course, is that twostep2_la_OBJECTS is not kosher, but
it works, and there's no other way to generate the .lo files and have
them built into a library.  The ctags example has the .o files in LDADD;
doing that results in no .lo objects.  Putting .los into LDADD, LIBADD
or DEPENDENCIES doesn't work- it dies looking for twostep.lo.c etc.

I'd leave it as is, but make dist won't allow it.

What can I do?

-Adam P.