Re: Where to do post installation?

* Ralf Wildenhues wrote on Mon, Jul 07, 2008 at 07:58:01PM CEST: > You'll want to use something like > > install-data-hook: > mkdir -p $(DESTDIR)$(localstatedir)/run Erm, for portability, either $(mkdir_p) (Automake >= 1.10) or $(mkinstalldirs) (for compatibility

Re: Where to do post installation?

* Steven Woody wrote on Mon, Jul 07, 2008 at 09:17:47AM CEST: > > Thank you, understood. But, when I copy samples from automake manual > and do the following: > > install-data-hook: > mkdir -p $(DESTDIR)/var/run > > and I expect that var/run will be created under my $PREFIX. You'll want to

Re: Create a custom target

* Tavian Barnes wrote on Mon, Jul 07, 2008 at 03:39:07PM CEST: > On Sun, Jul 6, 2008 at 11:25 PM, Ralf Wildenhues wrote: > > > > EXTRA_PROGRAMS = prog > > prog_SOURCES = ... > > bench: prog$(EXEEXT) > >execute prog$(EXEEXT)... > > .PHONY: bench &g

Re: Where to do post installation?

Hello Steven, * Steven Woody wrote on Mon, Jul 07, 2008 at 07:20:44AM CEST: > > After 'make install', I want to do some post-install things such as > creating some directories, run a script etc. What is valid method in > Makefile.am to do this? Thank you. Write rules for install-exec-hook and/o

Re: Create a custom target

Hello Tavian, please don't top-post, thank you. * Tavian Barnes wrote on Sun, Jul 06, 2008 at 07:45:23PM CEST: > On Sun, Jul 6, 2008 at 1:59 AM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > > Most of the Makefile.am text is copied verbatim into the Makefile.in &g

Re: correct windres use

* Vincent Torri wrote on Sun, Jul 06, 2008 at 07:38:04PM CEST: >> Typo of mine, sorry about that. Probably you'll want a rule such as >> >> .rc.lo: >> $(LIBTOOL) $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --tag=RC --mode=compile >> $(RC) $(RCFLAGS) -c $< -o $@ > > Last question: when I use -c, windr

Re: Compiling statically

Hello Paulo, * Paulo J. Matos wrote on Thu, Jun 26, 2008 at 02:34:50PM CEST: > To compile a program fully-statically I do: > ./configure CPPFLAGS="-DNDEBUG -I../../libfileIO-0.2.3/src" > CXXFLAGS="-O3" LDFLAGS="-static-libgcc -static -Wl,-Bstatic > -L../../libfileIO-0.2.3/src" You can try somethi

Re: correct windres use

Hello Vincent * Vincent Torri wrote on Fri, Jul 04, 2008 at 03:26:48PM CEST: > On Fri, 4 Jul 2008, Ralf Wildenhues wrote: >> .rc.lo: >> $(LIBTOOL) --tag=RC --mode=compile $(WINDRES) -c $< -o $@ > > ok. I'll try that. Btw, is it $(RC) or $(WINDRES) ? Because in t

Re: Create a custom target

Hello Tavian, * Tavian Barnes wrote on Sun, Jul 06, 2008 at 07:28:30AM CEST: > Hi, guys. I have a question: how do I create a custom target, and > selectively compile some code, and run the compiled executable, when > this target is chosen? Specifically, I have a benchmarking suite for > a libra

Re: correct windres use

* Vincent Torri wrote on Fri, Jul 04, 2008 at 07:47:36AM CEST: > > 1) is it normal to have -Wl,evas_wince_gapi.o ? > 2) there are 2 -Xlinker. is it useful to add the one in module_la_LDFLAGS ? AFAIK you don't need any of that. Just list the .rc files in *_SOURCES and provide a .rc.lo rule, simila

Re: correct windres use

Hello, * Brian Dessent wrote on Fri, Jul 04, 2008 at 12:00:35AM CEST: > > B. Libtool only lets you create libtool libraries from libtool objects, > which is fair enough -- it wants control of the process. But AFAIK > libtool has no way of creating a libtool object of a resource, unless > perhaps

Re: How to install shell script?

* Harlan Stenn wrote on Mon, Jun 30, 2008 at 01:15:59PM CEST: > > On Mon, Jun 30, 2008 at 4:39 PM, Harlan Stenn <[EMAIL PROTECTED]> wrote: > > > sysconf_SCRIPTS > > > > > If I do that, 'automake' will fail and report: > > > > Makefile.am:10: `sysconfdir' is not a legitimate directory for `SCRIPT

Re: question using VPATH'S ...

Hello Roberto, please don't top-post, thank you. * Roberto Alejandro Espí Muñoz wrote on Tue, Jul 01, 2008 at 08:37:36AM CEST: > On Mon, Jun 23, 2008 at 12:13 PM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > * Roberto Alejandro Espí Muñoz wrote on Sun, Jun 22, 2008 at

Re: question using VPATH'S ...

* Roberto Alejandro Espí Muñoz wrote on Sun, Jun 22, 2008 at 06:33:07PM CEST: > Hi , I read about the possibility of creating VPATHs so that my project > can produce multiple configured outputs in different locations ( build > tree != source tree ). I'm trying to accommodate that philosophy to

Re: Iperf build break with emake.

Hello, * Upakul Barkakaty wrote on Tue, Jun 17, 2008 at 01:41:15PM CEST: > > If I try to build iperf with standard linux make, then it builds fine. > But instead if I use Electronic Make (emake) utility, then the build breaks. > > make[4]: conftest.make: No such file or directory > make[4]:

Re: Question about testing a library.

* Schrader, Glenn wrote on Wed, Jun 18, 2008 at 10:01:00PM CEST: > > This is exactly what doesn't work. All programs other than the check_ > programs are unconditionally built by the default 'all' target. There > doesn't seem to be a clean way to defer building my tests until the > user explicitly

Re: automake on solaris

Hello Akos, * Akos Rajna wrote on Tue, Jun 17, 2008 at 01:25:51PM CEST: > > can one configure automake to use gcc instead of solaris CC? Yes. For automake-using packages: ./configure CC=gcc For the Automake package itself: it doesn't use a compiler except in some of the tests. For the latte

Re: Question about testing a library.

* Schrader, Glenn wrote on Wed, Jun 18, 2008 at 09:10:13PM CEST: > I believe that I found the answer to my poorly asked question. My > confusion started when I noticed that target lists that begin with > check_ are special in that they are only built when 'make check' is > executed. This is reasona

Re: Possible bug in check-local

Hi John, * John Calcote wrote on Mon, Jun 16, 2008 at 09:15:15PM CEST: > > check-local: cstest.exe cstest_script > cstest.exe: xfcs.dll $(cstest_sources) > ... > > cstest_script: > echo "#!/bin/sh" > cstest_script > echo "mono cstest.exe" >> cstest_script > chmod 0

Re: Why I can not overwrite CXXFLAGS values?

Hello Steven, * Steven Woody wrote on Sat, Jun 07, 2008 at 04:01:06PM CEST: > On Sat, Jun 7, 2008 at 3:38 PM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > That said, you can > > CXXFLAGS = > > AM_CXXFLAGS = $(CXXFLAGS) > > xxx_CXXFLAGS = -O0 > >

Re: Setting LDADD in Makefile.am makes _DEPENDENCIES empty

Hello Navneet, * Navneet Dalal wrote on Fri, Jun 13, 2008 at 09:13:48AM CEST: > If my makefile.am looks as following, then it automatically generates > mybinary_DEPEDENCIES and set it to ../lib/libutil.la > bin_PROGRAMS= mybinary > LDADD= ../lib//libutil.la > mybinary_SOURCES = mybinary.c

Re: Overriding FFLAGS in a clean way ?

Hello Jan, * Fugitive wrote on Thu, Jun 12, 2008 at 06:42:24PM CEST: > > Simply overriding FFLAGS in Makefile.am generates warning from Automake but > it does the trick. You can do that, in combination with 'AUTOMAKE_OPTIONS = -Wno-override', > QUESTION: Is there another way over override FFLAG

Re: Question about testing a library.

Hello Glenn, * Schrader, Glenn wrote on Thu, Jun 12, 2008 at 07:54:59PM CEST: > > I am creating a library that is built with automake. The way that I > >think< this should work is: > The problem I'm having is that the programs installcheck uses to test > the library can only be build after the '

Re: Simple "how-to" question, libtool

Hello, I've little to add to Brian's detailed reply, except that ... * Mar Loh wrote on Thu, Jun 12, 2008 at 06:07:23PM CEST: > +topdir > --+libsrcdir > --+libsrcsubdir1 > --+libsrcsubdir2 there is no need to have configure scripts in each of those directories. Just have one at the top,

Re: [gnu.org #364322] Automake small patch

Hello, * Deborah Nicholson via RT wrote on Wed, Jun 11, 2008 at 11:36:38PM CEST: > I maintain the directory, but not the projects. I'm cc'ing the official > Automake email address so they can incorporate your patch. Thank you. > > [EMAIL PROTECTED] - Mon Jun 09 23:52:05 2008]: > > > > I tired

Re: Makefile.in's in build tree

Hello, * Kamaljit Singh wrote on Fri, Jun 13, 2008 at 12:17:12AM CEST: > I maintain my build tree separate to src tree which has all the > Makefile.am's. Is it possible that all generated files (including > the Makefile.in's and the various cache) be in the build tree ? No, sorry. The Mak

Re: Extra_dist cannot hold two long lists?

* A117 wrote on Wed, Jun 11, 2008 at 08:15:13AM CEST: > problem is, stdafx.* and targetver.* etc. should not go into this library, > since they are to be used by VC project only. > I guess they have to go to EXTRA_DIST. Yes you can put them in EXTRA_DIST (which will do nothing except put them in t

Re: Extra_dist cannot hold two long lists?

* bonami wrote on Wed, Jun 11, 2008 at 07:32:47AM CEST: > > A line in Makefile.am, > EXTRA_DIST = tinystr.cpp tinyxml.cpp tinyxmlerror.cpp tinyxmlparser.cpp > dllmain.cpp ezcomm.aps ezcommon.rc ezcommon.vcproj icon.ico resource.h > stdafx.cpp stdafx.h #targetver.h test.xml tinyxml.txt > > If I un

Re: A global _CFLAGS assigment?

* Steven Woody wrote on Fri, Jun 06, 2008 at 08:34:05PM CEST: > Before received your post, I tried > _CFLAGS = @AM_CFLAGS@ -additional-flags ... > but failed, but > _CFLAGS = @CXXFLAGS@ -additional-flags ... (Is that mixup of C and C++-specific flag names a typo in your mail?) > will

Re: Why I can not overwrite CXXFLAGS values?

Hello Steven, * Steven Woody wrote on Fri, Jun 06, 2008 at 08:54:59PM CEST: > In my system, the default CXXFLAGS is '-g -O2'. But, for a particular > program, I need -O0 and without -g. I tried something like: > bin_PROGRAS = xxx > xxx_CXXFLAGS = -O0 > in Makefile.am. But, the final CXXFLAG

Re: Mixing C and C++?

* Erik de Castro Lopo wrote on Sat, Jun 07, 2008 at 12:13:36AM CEST: > Organization: Erik Conspiracy Secret Labs LOL! It's been several years since I last read about the Eric conspiracy. > Olly Betts wrote: > > > You'd written "test_sources = ..." which has no special meaning to > > automake.

Re: install-exec-hook question

* Maynard Johnson wrote on Wed, Jun 04, 2008 at 08:21:37PM CEST: > I have a need to run some post-install commands that may print a message > that the user must see (so it must be near the end of the output). You have a graph of Makefile.am vertices connected by directed edges, SUBDIRS entries. E

Re: A global _CFLAGS assigment?

* Steven Woody wrote on Fri, Jun 06, 2008 at 06:44:46PM CEST: > On Sat, Jun 7, 2008 at 12:22 AM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > > (you can also AC_SUBST([AM_CFLAGS], [...]) from within configure.ac) > The big problem may be, the AM_CFLAGS will disappe

Re: How to define a `prefix' other than the default vaule?

* Steven Woody wrote on Fri, Jun 06, 2008 at 06:22:40PM CEST: > > I want all my stuff by default installed in /usr/local/mypkg unless > user specified another 'preflex' value when run 'configure' script. > How can I? Thank you.

Re: A global _CFLAGS assigment?

Hello Steven, * Steven Woody wrote on Fri, Jun 06, 2008 at 06:17:30PM CEST: > > My project tree have many Makefile.am in a recursive directory tree > and I want every Makefile.am has a line some thing like xxx_CFLAGS = > -Wall. What's the way to do that? You see, there are many different > xxx_

Re: Mixing C and C++?

* Erik de Castro Lopo wrote on Fri, Jun 06, 2008 at 01:49:15PM CEST: > http://www.mega-nerd.com/tmp/amtest-0.1.tar.gz > gcc -g -O2 -o amtest amtest.o > amtest.o: In function `main': > /tmp/amtest-0.1/amtest.c:10: undefined reference to `cpp_test' > > For some reason, the automa

Re: Mixing C and C++?

Hi Erik, * Erik de Castro Lopo wrote on Fri, Jun 06, 2008 at 11:25:45AM CEST: > > I have an project that uses automake, autoconf and libtool and for one > of the generated binaries, I'm trying to mix C and C++, but automake is > giving me the following error: > > tests/Makefile.am: object `c

Re: preprocessor output target

* Jason Roscoe wrote on Thu, Jun 05, 2008 at 09:00:16PM CEST: > What is the equivalent to: > > rm init.o && make init.o > > when using libtool? rm init.lo && make init.lo will possible recreate init.o, .libs/init.o, and init.lo. The latter is merely a small helper script. BTW, you should note th

Re: preprocessor output target

Hi Jason, * Jason Roscoe wrote on Thu, Jun 05, 2008 at 04:13:31PM CEST: > I apologize if this is not the correct list It's dead on. In addition to Stepan's answer: > The main reason is that I want to be able to see the headers > that are being included and where they are getting pulled from.

Re: Building things a little differently?

* John Calcote wrote on Mon, Jun 02, 2008 at 09:57:12PM CEST: > Ralf Wildenhues wrote: > > Automake has no builtin rules for moc files. So you need to take this > > up with whoever provides those rules. FWIW, in one package this is what > > we use: > > I was wonderin

Re: extending automake

Hello Bob, * Bob Rossi wrote on Tue, Jun 03, 2008 at 05:58:59PM CEST: > Another example I just ran across on the mingw.org site, >windres -o resfile.o resfile.rc >gcc -o hello hello.o resfile.o -mwindows > Often people want to put resources into there program. They would > greatly benefit

Re: Advice on the project structure for a library

* Jef Driesen wrote on Tue, Jun 03, 2008 at 12:31:29PM CEST: >>> CFLAGS=-I${includedir} >>> #include >>> >>> or >>> >>> CFLAGS=-I${includedir}/libfoo >>> #include [...] >> It's purely a matter of preference. You're right to segregate the >> headers, but a project shouldn't mandate one #include

Re: Building things a little differently?

Hello Bobby, * Bobby Dill wrote on Mon, Jun 02, 2008 at 12:55:11AM CEST: > When I build a library there is a hidden directory called .libs generated. Yes. That is done by libtool, because it may produce several files with the same name, and uses this private subdirectory as a means to avoid file

Re: Mac OS X: mkinstalldirs

Hello Michael, * Michael Witten wrote on Sun, May 18, 2008 at 05:59:26AM CEST: > The mkinstalldirs script does not work on Mac OS X (Leopard); > > Mac OS X's mkdir does not have --version and it seems to be > thread-safe. Unfortunately, the AC_PROG_MKDIR_P macro from Autoconf is not sharp in its

Re: directory names with blanks break automake builds

* Peter Simons wrote on Sun, May 18, 2008 at 02:36:58PM CEST: > Ralf Wildenhues writes: > > > Well, at least white space in targets and dependencies is forbidden > > with make. > > Whitespace can be quoted with '\'. At least in GNU Make, the following > sn

Re: Automake TESTS question

* John Calcote wrote on Fri, May 16, 2008 at 11:00:40PM CEST: > EXTRA_DIST = greptest.sh > TESTS = greptest.sh > > But this requires me to: > > 1) Actually HAVE a one-line script file called "greptest.sh" as part of > my package. > > 2) Use the EXTRA_DIST line. Why is this? Can't Automake tell f

Re: directory names with blanks break automake builds

* Peter Simons wrote on Sun, May 18, 2008 at 01:29:47PM CEST: > Bob Proulx writes: > > > This leads to 'make' not being designed to handle filenames with > > whitespace and of course automake tries to produce portable make > > configurations. > > I don't know what limitation you refer to. Can

Re: directory names with blanks break automake builds

Hi Peter, * Peter Simons wrote on Sat, May 17, 2008 at 06:07:39PM CEST: > I just ran across an interesting problem with automake 1.10. Just unpack > any other build into a directory called, say "/tmp/test automake", and > run it. In my particular case, the makefiles failed to call the local > copy

Re: Disable make distcheck --help and --version checks

Hi Brendon, * Brendon Costa wrote on Wed, May 07, 2008 at 09:20:27AM CEST: > The subject says it all. I have a "special" example project that i would > like to ensure when i use the distcheck target it does NOT check that > some or all of the installed applications provide --help or --version.

Re: packaging release and debug builds in the same RPM package

Hello Olivier, * Olivier Langlois wrote on Mon, May 05, 2008 at 11:52:47PM CEST: > Now that I am able to build these 2 versions of my libs into separate > subdirectories, I would like to suffix the library names with 'd'. > Suggestions on how to express this in automake files are welcome. Also >

Re: Trying to improve our dependency tracking

Hello James, * James Willenbring wrote on Thu, May 01, 2008 at 10:51:11PM CEST: > When I add > > myexe_DEPENDENCIES = $(PACKAGEA_DEPENDENCIES) > > $(PACKAGEA_DEPENDENCIES) is not resolved before dependencies are checked. > Despite the fact that I put the include directive at the top of the > Mak

Re: extending automake

* Bob Rossi wrote on Wed, Apr 30, 2008 at 02:59:11PM CEST: > You busy or thing the idea is no good? Busy. If you want to help, there are still unaddressed questions from (even if the above notation is not adopted, it

Re: flag question

* Bob Friesenhahn wrote on Fri, Apr 25, 2008 at 11:32:34PM CEST: > On Fri, 25 Apr 2008, NightStrike wrote: >> >> Is there a configure test to see if -Wall works? > > These options only work with GCC. If the compiler is GCC you can use > them, otherwise skip them. FWIW, icc supports -Wall, too.

Re: extending automake

* Bob Rossi wrote on Fri, Apr 25, 2008 at 03:41:20AM CEST: > On Sat, Apr 19, 2008 at 01:22:29PM -0400, Bob Rossi wrote: > > They generate files during build time, and modify BUILT_SOURCES... > > > > In fact, think of the bison or flex extension (adding .y or .l files to > > the _SOURCES variable)

Re: Dynamic AC_OUPUT

Hi Gary, * Gary Kramlich wrote on Wed, Apr 23, 2008 at 01:58:02PM CEST: > Ralf Wildenhues wrote: >> * Gary Kramlich wrote on Wed, Apr 23, 2008 at 03:08:38AM CEST: >> >>> This python script also determines what directories should have >>> makefiles created and

Re: CPPFLAGS for LIBOBJS

* Russ Allbery wrote on Wed, Apr 23, 2008 at 10:51:11PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > Yes, they don't get per-target preprocessor or compile flags. That > > doesn't work, because then they would have to be renamed: $(LIBOBJS) > &g

Re: CPPFLAGS for LIBOBJS

* Ralf Wildenhues wrote on Wed, Apr 23, 2008 at 09:57:46PM CEST: > * Russ Allbery wrote on Wed, Apr 23, 2008 at 02:16:34AM CEST: > > > If I add: > > > > > > portable_libportable_a_CPPFLAGS = $(KRB5_LDFLAGS) $(KAFS_LDFLAGS) > > > > Er, obviously that

Re: CPPFLAGS for LIBOBJS

Hi Russ, * Russ Allbery wrote on Wed, Apr 23, 2008 at 02:16:34AM CEST: > > If I add: > > > > portable_libportable_a_CPPFLAGS = $(KRB5_LDFLAGS) $(KAFS_LDFLAGS) > > Er, obviously that should be KRB5_CPPFLAGS and KAFS_CPPFLAGS. Sorry about > the confusion. Should it also be libportable_a_CPPFLAGS

Re: Dynamic AC_OUPUT

Hello Gary, * Gary Kramlich wrote on Wed, Apr 23, 2008 at 03:08:38AM CEST: > This python script also determines what directories should have > makefiles created and so on. I've gotten far enough to trick configure > into outputting all of the make files. (This is done by appending the > director

Re: order of execution of the install-exec-hook rule

Apologies for mangled accents. Thanks for the translations (though my French isn't that bad yet). If you want to save yourself work translating to others, do 'LC_ALL make ...'. * Vincent Torri wrote on Tue, Apr 22, 2008 at 07:36:41PM CEST: > > make INSTALL_PROGRAM="/bin/sh > /home/torri/tmp/cv

Re: order of execution of the install-exec-hook rule

Hi Vincent, * Vincent Torri wrote on Tue, Apr 22, 2008 at 03:17:02PM CEST: > > i want to use install-exec-hook to move a file. I install it with > install-strip. > > I would like to know if the install-exec-hook rule is called after > install-strip. Yes. The install-exec-hook recipe is execu

Re: extending automake

* Brian Dessent wrote on Sat, Apr 19, 2008 at 04:45:54PM CEST: > Ralf Wildenhues wrote: > > > Do you mean that, given that keyword, all rules of the form > > target1 target2 : prereq ... > > command ... > > > > should be rewritten to be a multipl

Re: extending automake

* Brian Dessent wrote on Sat, Apr 19, 2008 at 03:59:19PM CEST: > Ralf Wildenhues wrote: > > <http://thread.gmane.org/gmane.comp.sysutils.automake.general/8916/focus=8924> > > The MULTITARGETS and foo_{TARGETS,SOURCES,COMMAND} syntax that you came > up with is certainly i

Re: extending automake

* Brian Dessent wrote on Sat, Apr 19, 2008 at 02:42:57PM CEST: > > That brings up the next logical point, can anyone comment on the > feasibility of some kind of generalized "tool X reads A and outputs Y > and Z" construct to help solve the "tools generating multiple outputs" > case without having

Re: extending automake

Hi Bob, Brian, * Brian Dessent wrote on Sat, Apr 19, 2008 at 06:23:59AM CEST: > Method B, not GNU make specific, using a single witness stamp along the > lines of what is suggested in the manual: [...] > pyxml-stamp: $(PYXMLFILES) > @rm -f pyxml-tmp > @touch pyxml-tmp > (set -e;

Re: precompiled headers

* Brian Dessent wrote on Fri, Apr 18, 2008 at 11:28:07AM CEST: > BUILT_SOURCES = myheader.hh.gch > %.hh.gch: %.hh > $(CXX) -c $< [...] The rule is a good start, but likely lacking dependency information. > But honestly the above is just a random stab at how to start, you'd be > much better

Re: '#####' comment handling in aclocal

Hi Peter, * Peter Simons wrote on Sat, Apr 12, 2008 at 01:20:51PM CEST: > > It appears that aclocal strips those "# ..." comments while > copying the macros into the generated aclocal.m4 file. > > I was wondering whether this behavior is intentional and, > assuming that it is, what the ratio

Re: Report to stdout like Linux kernel compilation does

* NightStrike wrote on Sat, Apr 12, 2008 at 04:12:24AM CEST: > On Fri, Apr 11, 2008 at 5:28 PM, Ralf Wildenhues wrote: > > I can't understand why people do edit-compile-test cycles without having > > compiler output be post-processed by their editor. It works with all >

Re: Report to stdout like Linux kernel compilation does

* John Calcote wrote on Fri, Apr 11, 2008 at 11:18:48PM CEST: > Anyway, what I meant was that my > development cycles are fairly short - I might not get around to > checking for warnings (by redirecting stdout to /dev/null) for a few > days, so I might let a few warnings go for a week (or less), if

Re: Report to stdout like Linux kernel compilation does

* Robert J. Hansen wrote on Fri, Apr 11, 2008 at 06:36:56PM CEST: > Bob Proulx wrote: >> To give you a different perspective, I *hate* that format because it >> hides problems and *makes debugging harder*. I want to see exactly >> the command that was executed. I want to see the entire command.

Re: parallel make help

Hi Bob, * Bob Rossi wrote on Thu, Apr 10, 2008 at 03:28:56PM CEST: > I currently have my project setup so that each subdirectory has a > Makefile.am. I've noticed that when I do 'make -j4' that it does 1 > directory at a time, then links a little library or makes a program. > > If I moved everyth

Re: Problem mixing .cpp and .cxx in _SOURCES.

Hello Jeroen, * Jeroen N. Witmond [Bahco] wrote on Mon, Apr 07, 2008 at 09:19:26PM CEST: > > problem_SOURCES = main.cpp problem.cxx > > # When a file problem.cpp is present, this file is compiled. File > # problem.cxx in problem_SOURCES is ignored. Can you work around it by either - removing pr

Re: ``install -C'' / unnecessarily updating time stamps

Hi Thomas, * Thomas Schwinge wrote on Sun, Apr 06, 2008 at 08:12:49PM CEST: > On Mon, Dec 25, 2006 at 09:23:15PM -0800, Paul Eggert wrote: > > > > I installed the following to Automake install-sh to implement > > "install-sh -C", which is the second part of that patch. > However now there is ano

Re: pattern rules

* Ralf Hemmecke wrote on Mon, Mar 31, 2008 at 11:39:49AM CEST: > I am not new to open software development, just new to the Autotools. > And I am well aware that input from novices is often very useful to > improve the software, but there must be active developers who take care > and help wit

Re: Automake and literate programming

Hello Ralf, * Ralf Hemmecke wrote on Mon, Mar 31, 2008 at 10:22:25AM CEST: > > Until now I have the impression, that I have to do everything by hand, > ie. that Automake doesn't give me much help in the build process. > It also seems that Libtool cannot help me at all. Any ideas? Both statemen

Re: pattern rules

* Ralf Hemmecke wrote on Mon, Mar 31, 2008 at 09:53:42AM CEST: > On 03/27/2008 06:21 PM, Ralf Wildenhues wrote: > >> What you can do is use -Wno-portability only for those Makefile.am files >> for which you need it, by enabling it in those files only: >> AUTOMAKE_OPTION

Re: install mingwm10.dll

* Bob Rossi wrote on Fri, Mar 28, 2008 at 12:47:25AM CET: > > I want to copy /c/mingw/bin/mingwm10.dll to my bin dir yes. After I do > the make install, I will then use something like NSIS to take the > install dir and make some sort of installation package for windows. > > > Why in the world wou

Re: install mingwm10.dll

Hi Bob, * Bob Rossi wrote on Thu, Mar 27, 2008 at 06:55:26PM CET: > On Wed, Mar 26, 2008 at 03:28:26PM -0400, Bob Rossi wrote: > > > > I want to install mingwm10.dll, since my program requires it. I'm trying > > to figure out the best way to do this. The dll lives in /c/mingw/bin. > > > > Would

Re: Are dependency lists statically defined?

Hello John, * John Calcote wrote on Thu, Mar 27, 2008 at 03:03:25PM CET: > > include_HEADERS = file1.h file2.h ... fileN.h > > But very often, these lists will contain shell expansions, like this: > > if ENABLED_ADDED_FUNCTIONALITY_A > added_functionality_a = fileX.h fileY.h > endif > > incl

Re: pattern rules

* Ralf Hemmecke wrote on Thu, Mar 27, 2008 at 01:31:36PM CET: > > -W CATEGORY > --warnings=category > Output warnings falling in category. category can be one of: > ... > portability > portability issues (e.g., use of make features that are > known to be not portable) >

Re: pattern rules

* Ralf Hemmecke wrote on Thu, Mar 27, 2008 at 12:05:34PM CET: > > Makefile.am:8: `%'-style pattern rules are a GNU make extension > autoreconf: automake failed with exit status: 1 > Is there something wrong with > > AM_INIT_AUTOMAKE([-Wall -Werror]) As of Automake 1.10, -Wall includes -Wportabili

Re: pattern rules

Hello Ralf, * Ralf Hemmecke wrote on Wed, Mar 26, 2008 at 10:49:35AM CET: > > pattern rules are forbidden by automake, but I have the following problem. They are not forbidden. They are unportable to non-GNU make, and automake may not fully understand them, but other than that, there is no probl

Re: A new Autotools book

Hello John, * John Calcote wrote on Tue, Mar 25, 2008 at 07:07:56PM CET: > Sorry for the list spam, No problem, but could we continue this discussion on one list only, say, the autoconf one, for lack of a better choice? Thanks. Reply-To and Mail-Followup-To set. > http://www.freesoftwaremagazin

Re: traces output order

On Fri, March 21, 2008 13:20, Eric Blake wrote: > I think I see a way around the problem. Use the nesting level, which is > also part of the trace. For example, autoconf --trace=_AM_COND_IF:'$n-$d' > can tell you that _AM_COND_IF-2 was probably invoked unquoted within > _AM_COND_IF-1. For more a

Re: Questions on 'make dist'

* NightStrike wrote on Wed, Mar 19, 2008 at 07:02:17PM CET: > On 3/11/08, Bob Friesenhahn <[EMAIL PROTECTED]> wrote: > > On Tue, 11 Mar 2008, NightStrike wrote: > > > > > > I had intended to do everything with non-recursive make, but as you > > > pointed out once, non-recursive is also considered h

Re: make dist trouble

Hello Stefan, * Klett, Stefan wrote on Fri, Mar 14, 2008 at 11:09:11AM CET: > This time I don't know how to deal with the following error message: > > { test ! -d libgeneva-0.5 || { find libgeneva-0.5 -type d ! -perm -200 > -exec chmod u+w {} ';' && rm -fr libgeneva-0.5 ; }; } > test -d libgene

Re: defining multiple targets

Hello Stefan, * steve_k wrote on Tue, Mar 11, 2008 at 02:20:25PM CET: > Could somebody of you explain to me how to > define multiple targets in one configure.ac Makefile.am ? I got it compiling > everything with SUBDIRS - but now it was requested that i should make the > testcases ( in tests/Testc

Re: stamp-h.in

* Brian Dessent wrote on Wed, Mar 12, 2008 at 07:56:37PM CET: > Ralf Wildenhues wrote: > > > This is what I found using "git -Sstamp-h.in": > > However, automake still makes use of "stamp-h" witness files, it's just > that they are created and delet

Re: stamp-h.in

Hello John, * John Calcote wrote on Wed, Mar 12, 2008 at 06:55:40PM CET: > Can someone please tell me what is the high-level purpose of the > stamp-h.in file (and those files generated from it)? I understand > it's a timestamp file - what I want to know is what it's used for by > automake. And, f

Re: Questions on 'make dist'

* NightStrike wrote on Mon, Mar 10, 2008 at 03:42:52PM CET: > Our project is laid out like this: > > /trunk/ > /trunk/mingw-w64-crt/ > /trunk/mingw-w64-doc/ > /trunk/mingw-w64-headers/ > What is the best way to handle this situation to remove the need to > manually tar up the trunk? Move the (to

Re: problem with fortran sources in recent automake.

Hello Dan, * Dan McMahill wrote on Mon, Mar 10, 2008 at 01:49:54PM CET: > > I'm trying to debug a piece of open-source 3rd party software. It mixes > c++ and fortran and has a Makefile.am fragment that looks like: > > foo_SOURCES= src/file1.cpp src/file2.cpp src/file3.F src/file4.F > > The c++

Re: Shared without libtool

On Sat, March 8, 2008 01:33, NightStrike wrote: > On 3/7/08, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> On Sat, March 8, 2008 01:23, NightStrike wrote: >> >> > Does automake support building shared libraries without using >> >> >libtool? >>

Re: Shared without libtool

On Sat, March 8, 2008 01:23, NightStrike wrote: > On 3/7/08, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> On Sat, March 8, 2008 01:11, NightStrike wrote: >> > Does automake support building shared libraries without using libtool? >> >> The question is: why? &g

Re: Shared without libtool

On Sat, March 8, 2008 01:11, NightStrike wrote: > Does automake support building shared libraries without using libtool? The question is: why? There is no special support, but there is no special impediment, either. Cheers, Ralf

Re: -lm -lz

Hi Stefan, Bob, * Bob Proulx wrote on Thu, Mar 06, 2008 at 05:21:05PM CET: > Stefan Bienert wrote: > > after an hour of searching, how am I supposed to invoke "-lm -lz" into > > my compilation? The documentation states something about using "LIBS" as > > a variable, autoconf also speaks of "LIBS

Re: Checking versions and defining macros

Hello Jason, let's please limit replies to the autoconf list, thanks. * Jason Curl wrote on Wed, Mar 05, 2008 at 06:47:04AM CET: > > To achieve my goals, I've borrowed some of the internals of the auto* > tools (and libtool). I'd like to somehow check the version of the > autotools during "au

Re: substitution vs expansion in Makefile.am

* John Calcote wrote on Tue, Mar 04, 2008 at 11:34:54PM CET: > >registrarTest_SOURCES = registrar.c\ > @top_srcdir@/common/mySleep.c Hmm, putting variables in *_SOURCES is problematic as the dependency tracking code in m4/depout.m4 is really dumb and may do the wrong thing. $(top_srcdir

Re: substitution vs expansion in Makefile.am

Hi John, * John Calcote wrote on Tue, Mar 04, 2008 at 10:38:50PM CET: > Newbie question here: Is it better to do this in a Makefile.am: > >install-exec-hook: >$(mkdir_p) $(DESTDIR)@syslogdir@ > > or this: > >install-exec-hook: > $(mkdir_p) $(DESTDIR)$(syslogdir) >

Re: Extending default suffix rules.

* Remco Bras wrote on Sun, Mar 02, 2008 at 03:39:57PM CET: > Op Sunday 02 March 2008 15:20:42 schreef Ralf Wildenhues: > > Your rule is dangerous. If the user interrupts make at the time the > > convertors.sh script has run but the backup hasn't been restored yet, > >

Re: Extending default suffix rules.

* Remco Bras wrote on Sun, Mar 02, 2008 at 03:10:58PM CET: > Op Sunday 02 March 2008 10:42:04 schreef Ralf Wildenhues: > > * Remco Bras wrote on Fri, Feb 29, 2008 at 11:37:01PM CET: > > > as part of my work on GNU RPGE, I've had to 'extend' the automake suffix >

<    5   6   7   8   9   10   11   12   13   14   >