I think autotools has a concept of disallowing symlinks as it seems symlinks
can't be done in a portable way, and the goal of autotools is making
projects portable.
Well, if the autotools user feels like using symlinks, then it must be
expected to break portability wherever you take your autoc
Re: automake with fortran
But even then, do src/Makefile.am is happy with any order of the source
file or you have to keep the order manually?
On Thu, 2013-07-25 at 14:11 -0300, Fabrício Zimmerer Murta wrote:
I implemented GNU Build System on a fortran project I work with..
I've created a
I implemented GNU Build System on a fortran project I work with..
I've created a 'Makefile.am' inside src/ (src/Makefile.am) thus my
PACKAGE_ROOT/Makefile.am has a 'SUBDIRS=src'.
This will make 'GNU Make' to chdir into src/ dir and the created modules
works just fine. I think this 'subdirs' a
would it be too naive of my part to think that you could leave everything on
the GNUbuild/ directory and pointing to ../src?
I like to have the configure script on the root of the package and I assume
this organization you want would be of a specific package not meant to
follow general 'open s
ng library or linking
directly
On 2012-09-11 15:41 -0300, Fabrício Zimmerer Murta wrote:
Is that supposed not to work?
(“LIBRARY_BUILD” AM_CONDITIONAL set accordingly on configre.ac)
Makefile.am:
if LIBRARY_BUILD
lib_LTLIBRARIRES = libprog.la
libprog_la_SOURCES = a.c b.c d.c
else !LIBRARY_BU
Is that supposed not to work?
(“LIBRARY_BUILD” AM_CONDITIONAL set accordingly on configre.ac)
Makefile.am:
if LIBRARY_BUILD
lib_LTLIBRARIRES = libprog.la
libprog_la_SOURCES = a.c b.c d.c
else !LIBRARY_BUILD
bin_PROGRAMS = driver
driver_SOURCES = a.c b.c d.c driver.c
endif !LIBRARY_BUILD
if LIBRA
If I read
http://www.gnu.org/software/autoconf/manual/autoconf.html#Specifying-Target-Triplets,
I read:
If using gfortran or g77 (the GNU Fortran compilers), then set the shell
variable GFC to ‘yes’. If the output variable FCFLAGS was not already set in
the environment, then set it to -g -02 fo
From: Fabrício Zimmerer Murta
Sent: Saturday, June 16, 2012 3:50 AM
To: Automake List
Subject: BUG: AC_PROG_FC does not define GCF when compiler is gfortran
If I read
http://www.gnu.org/software/autoconf/manual/autoconf.html#Specifying-Target-Triplets,
I read:
If using gfortran or g77 (the GNU
Hello,
I am unable to use automatic dependency tracking as I have been doing a
project in Fortran 90. My problem is: when I change include/config.h, src/*.F90
which have the include/ file “included” are not recompiled (as would be
expected). I wonder if it would be okay just to add to the M
That's really what I was looking for. Thank you very much for your time!
--
From:
Sent: Tuesday, December 06, 2011 2:05 AM
To:
Subject: Re: Directions on compiling the right files
In other words, there will be new .c files that should be com
Hello,
I am a bit lost here. We recently started a project using GNU Build
System in order to make our package installable everywhere without mysteries
of package-specific builds.
Now I am facing a problem I will try to explain with an easier to
understand example.
Suppose I am making
"I certainly don't have the cycles, but I wish I could inspire someone to
write a Fortran dependency analysis module for Automake!"
Agreed!
I've just started a fortran 90 project and I mean to have the GNU build
system on it. There were two major problems I encountered:
- Must make manual rules
12 matches
Mail list logo
