generic additionnal targets, howto?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Running automake generate a lots of 'generic' targets for each Makefile.in and this is great as you don't have to write all those target for each of your directory. Now i am faced with the following problem: As part of a check run, i want to autogenerate a list of html files in a documentation directory. I have wrote the various target in one of my Makefile.am and it now works pretty well (using check-local target). However, i'd like to have this set of rules be replicated all my source Makefile.am. To prevent manageability problems, i'd like to know if there is a way to give automake a set of rules to inject all generated Makefile.in of my projet without ressorting to an ugly manual cut and paste in all Makefile.am content. I hope i was clear in my question, should be :) mmm to be sure, base question is given a pack of lines, is there a way to tell automake to inject them in all makefile.in it generate in a given projet? Thanks for help. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFERqYsHHGOa1Q2wXwRAofqAJ40QyUM1wZlxYi1cBLRnet5vALsLACfcuCk tny+07/k+mOl0Lx1qKgqiDk= =pbHh -END PGP SIGNATURE-
passing parameters to libtool
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, am using autoconf / automake in a project. We have a problem with some static library compilation leading to us needing to pass parameters to libtool call at link time. We need to pass it the --preserve-dup-deps parameters. However, i found nowhere in automake docs how to do this. All automake docs states is that libtool is fully integrated since 1.2, but no info on how to pass additionnal parameters. Need infos on it, this is quite important, our project is currently blocked until we resolve this compilation issue. Some of our developper are waiting for this soluce :) Thanks David Delbecq -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEfJAnHHGOa1Q2wXwRAuYoAJ4nPTHu+gc44gzDQkJakPgUwb402wCgxS3Y B0odSoh7Gzg0/fTufttysCA= =e3Gl -END PGP SIGNATURE-
Re: passing parameters to libtool
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yes, great, very fast thank you, i hope we can continue getting this fast :) But does not work :/ Relevant Makefile.am section: #note all .a are here twice for compilation problems AM_LIBTOOLFLAGS= --preserve-dup-deps LDADD = ../../../server/libserver.a \ ../../../common/libcross.a \ ../../../random_maps/librandom_map.a \ ../../../socket/libsocket.a \ ../../../server/libserver.a \ ../../../common/libcross.a \ ../../../random_maps/librandom_map.a \ ../../../socket/libsocket.a \ $(LIBDL) @CHECK_LIBS@ I checked twice, i reran libtoolize -f -c mv -f ltmain.sh utils aclocal autoheader automake -a -c autoconf ./configure make and Makefile does now indeed contain a reference to AM_LIBTOOLFLAGS runtime called made by make /bin/sh ../../../libtool --tag=CC --mode=link gcc -g -O2 -o check_shop check_shop.o ../../../server/libserver.a ../../../common/libcross.a ../../../random_maps/librandom_map.a ../../../socket/libsocket.a ../../../server/libserver.a ../../../common/libcross.a ../../../random_maps/librandom_map.a ../../../socket/libsocket.a -ldl -lcheck -lcrypt -lm -lnsl You see , flag is not there! :) Another solution? Thanks David Delbecq Ralf Wildenhues a écrit : > Hi David, > > * tchize wrote on Tue, May 30, 2006 at 08:34:16PM CEST: > >> am using autoconf / automake in a project. We have a problem with >> some static library compilation leading to us needing to pass >> parameters to libtool call at link time. We need to pass it the >> --preserve-dup-deps parameters. However, i found nowhere in >> automake docs how to do this. All automake docs states is that >> libtool is fully integrated since 1.2, but no info on how to pass >> additionnal parameters. > > > Per-Makefile: AM_LIBTOOLFLAGS = --preserve-dup-deps > > or per-target with *_LIBTOOLFLAGS. > > (And yes, it is very inconsistent that this flag must be passed > before the --mode, and not after the compiler, where *LDFLAGS go. > TODO item.) > >> Need infos on it, this is quite important, our project is >> currently blocked until we resolve this compilation issue. Some >> of our developper are waiting for this soluce :) > > > Well, was that fast enough? ;-) > > (You may still have troubles getting what you want; but to help > more, we need to see more, like the corresponding Makefile.am > parts.) > > Cheers, Ralf > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEfJnfHHGOa1Q2wXwRAs0kAKC9wL16+e7bknZqpD6QOobfhpSqqACgpGn7 tmqpKP1E9cdQE8Eg43/ara4= =6XXB -END PGP SIGNATURE-
Re: passing parameters to libtool
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ralf Wildenhues a écrit : > * tchize wrote on Tue, May 30, 2006 at 09:15:43PM CEST: > >> Yes, great, very fast thank you, i hope we can continue getting >> this fast :) >> >> But does not work :/ > > > Yep, I wasn't paying attention: support for LIBTOOLFLAGS has been > added only in the CVS version of Automake, after 1.9.6. :-/ Sorry > about that. Quite surprised, nobody requested to pass parameter to libtool since 1.2? :D > > > Yeah, I guess then you'll either have to use CVS Automake, Can't ask team to switch to CVS version of automake :) > or hack you way around this. Different possibilities come to mind: > > > - write LIBTOOL = @LIBTOOL@ --preserve-dup-deps Works, though i have no idea what it means :D > > - write LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) > $(LIBTOOLFLAGS) \ --mode=link $(CCLD) $(AM_CFLAGS) $(CFLAGS) > $(AM_LDFLAGS) \ $(LDFLAGS) -o $@ Works too (and that, i undestand it :p) > > in Makefile.am (both untested; feedback appreciated). Problem solved, thank you (will go for first solution as the smallest one, would like to know what it means anyway. I guess it states libtool is libtool, but i don't really understand the notation :) > > Cheers, Ralf > > Greetings, David Delbecq -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEfJ8GHHGOa1Q2wXwRAmgkAKCM/QLXtVvZPJJI+jFxvnDATC+3wwCg7KCs gZ6f2ScmIIaDhR8nh9Tg/vo= =hIbR -END PGP SIGNATURE-
Re: passing parameters to libtool
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ralf Wildenhues a écrit : > * tchize wrote on Tue, May 30, 2006 at 09:37:43PM CEST: > >> Ralf Wildenhues a écrit : >> >>> - write LIBTOOL = @LIBTOOL@ --preserve-dup-deps >> >> Works, though i have no idea what it means :D > > > Well, for each AC_SUBSTed variable in configure.ac, Automake > generates a line of the form > > VARIABLE = @VARIABLE@ > > in Makefile.in, so that you can later use $(VARIABLE) instead of > @VARIABLE@ everywhere; and, so that you have a chance to override > the value of $(VARIABLE) -- your settings come after the one by > Automake, so they will take precedence. (There are cases where it > may not work as easily, but I can't think of one off-hand now.) > > Maybe you should add a note to that line that, once your project > can assume Automake-1.10, it should be replaced with a proper > AM_LIBTOOLFLAGS setting. > > Cheers, Ralf > > thanks for enlightments, don't worry about comment, is already there, but i bet it will still be there in 2 years considering how many time Makefiles get modified :p Thanks for all help David Delbecq -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEfKWdHHGOa1Q2wXwRAjbrAJ9dlKyjIIPAvtSdpd30IWfLz75FawCgogPM aLO72cq8vUuHNDnYzcivws8= =K8qV -END PGP SIGNATURE-
customizing build output
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I there a way to tell automake to slighlty alter the process of .c -> .o ? There are a lot of flags, but i was wondering if there was a way to replace the rules created by automake with some more user friendly one (remove echo of command and instead write 'compiling xyz.c to xyz.o') Greetings, Tchize -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEf3EwHHGOa1Q2wXwRAhY4AKDuzWaczrgTq+D9vG7fNXgdfBwX3wCeJXPP AZ0R5vMKdtYA9YChStENrzU= =uzRn -END PGP SIGNATURE-
