libtool : No rule to make target with LDADD

Hello, I am designing the compilation system of Scilab using the autotools. It was using a system of included Makefile to perform the compile. I migrated everything using auto* & libtools. I build all the libs without problems. Now, I am stucking with the linkage of the binary with the built lib

Re: libtool : No rule to make target with LDADD

I forgot to say that I am using : automake 1.9.6-4 autoconf 2.60-1 libtool 1.5.22-4 Cheers, Sylvestre > Hello, > > I am designing the compilation system of Scilab using the autotools. > It was using a system of included Makefile to perform the compile. I > migrated everything using auto* & libtoo

Change a flag for a specific file

Hello, A quick question, I would like to be able to change one compilation flag for one file. I have a few fortran files which don't work (but can be compiled) with the optimisation flag (-O). Thus, I would like to disable the -O flag just fort those files. Is it possible to do that with automake

Re: Change a flag for a specific file

> > A quick question, I would like to be able to change one compilation flag > > for one file. > > I have a few fortran files which don't work (but can be compiled) with > > the optimisation flag (-O). > > You can use per-target flags for this, if you have to. > (I say "if you have to", because in

Re: libtool : No rule to make target with LDADD

> Sorry for the delay. No worries ! [...] > scilex_LDADD = routines/libscilab.la > > and make sure that it gets built before the program. If > routines/libscilab.la is built from the same Makefile.am, that should > happen automatically, given that you do _not_ have set > scilex_DEPENDENCIES.

Re: Change a flag for a specific file

> If it is even important to you to have _only_ one file compiled with > this flag, say bar.f, while all the others do not get this flag, you > could make the compilation of bar.f special by putting it in a (not > installed) library. For example: > bin_PROGRAMS = foo > foo_SOURCES = foo.f >

Re: Change a flag for a specific file

Le mardi 22 août 2006 à 13:31 +0200, Ralf Wildenhues a écrit : > It would be helpful if you did not omit the name and date of the quoted > part (makes searching for context much easier), thanks. Sorry for this > * Sylvestre Ledru wrote on Tue, Aug 22, 2006 at 12:50:40PM CEST: > >

Weird problem with LIBADD

Hello, I have a problem with LIBADD in one of my Makefile.am. I am building a library thanks to libtool with C and Fortran sources (nothing really eccentric here). lib_LTLIBRARIES = libcore.la libcore_la_SOURCES = $(CORE_C_SOURCES) $(CORE_FORTRAN_SOURCES) $(GATEWAY_C_SOURCES) $(GATEWAY_FORTRAN_S

Re: Weird problem with LIBADD

> ... is shorter (and more precisely) written as follows: ... > > libcore_la_LIBADD = \ > $(top_builddir)/libs/blas/libblas.la \ > $(top_builddir)/libs/lapack/liblapack.la \ > $(top_builddir)/libs/MALLOC/libmalloc.la \ > $(top_builddir)/modules/cacsd/libcacsd.la \ > $(top_builddir)/modules/differ

Re: Change a flag for a specific file

Le lundi 07 août 2006 à 15:39 +0200, Ralf Wildenhues a écrit : > * Sylvestre Ledru wrote on Mon, Aug 07, 2006 at 03:17:56PM CEST: > > > If it is even important to you to have _only_ one file compiled with > this flag, say bar.f, while all the others do not get this flag, you &

Re: Change a flag for a specific file

Le mercredi 11 octobre 2006 à 16:46 +0200, Ralf Wildenhues a écrit : > * Sylvestre Ledru wrote on Wed, Oct 11, 2006 at 04:35:49PM CEST: > > > > Here is what I did : > > noinst_LTLIBRARIES = libdummy-lapack.la > > libdummy_lapack_la_SOURCES = dlamch.f > >

Re: Best means to override CXXFLAGS locally

Hello Ralf & Akim, Le dimanche 22 octobre 2006 à 13:46 +0200, Ralf Wildenhues a écrit : > Hello Akim, > > * Akim Demaille wrote on Sun, Oct 22, 2006 at 01:10:02PM CEST: > > >What would be the cleanest means to handle this exception? > > > > Here is what I did: > > I think it's much better to do

"dynamic" makefile

Hello, I am trying to create a dynamic compilation system. In theoric, it is not difficult but I don't know if it is possible to do it. I would like to able to : * launch a ./configure in order to retrieve basic informations about the computer * with the informations retrieved by the ./configure

Re: "dynamic" makefile

Le jeudi 30 novembre 2006 à 13:13 +0100, Ralf Wildenhues a écrit : > Hello Sylvestre, > > * Sylvestre Ledru wrote on Thu, Nov 30, 2006 at 11:23:42AM CET: > > > > I am trying to create a dynamic compilation system. In theoric, it is > > not difficult but I don't

Re: "dynamic" makefile

Le jeudi 30 novembre 2006 à 15:45 +0100, Ralf Wildenhues a écrit : > * Sylvestre Ledru wrote on Thu, Nov 30, 2006 at 03:02:21PM CET: > > > > I would like to generate a Makefile which will work with source files > > provided in the command line (parameters) instead of provid

How to handle data/script files in a VPATH build ?

Hello, I am trying to enable the VPATH path build of a software. The whole compilation process is fine but I am stuck at the end of the process. I need to call a script to finish the build process. This script will be run against data files. In my Makefile.am, I have: all-local: macros macros:

Re: How to handle data/script files in a VPATH build ?

Hello, Sorry for the delay, I missed your answer. Le mercredi 03 février 2010 à 11:27 -0500, Peter Johansson a écrit : > Hello Sylvestre, > > Sylvestre Ledru wrote: > > In my Makefile.am, I have: > > all-local: macros > > macros: $(top_builddir)/bin/myscript

Re: How to handle data/script files in a VPATH build ?

Hello Ralf, As usual, thanks for your answer. Le samedi 06 février 2010 à 18:56 +0100, Ralf Wildenhues a écrit : > Hello Sylvestre, > > * Sylvestre Ledru wrote on Sat, Feb 06, 2010 at 06:49:38PM CET: > > Le mercredi 03 février 2010 à 11:27 -0500, Peter Johansson a écrit : &