Re: naming convention for object files.

2012-10-12 Thread Nicolas Bock
Hi Miles, thanks for the explanation. I had never hear of the SHORTNAME attribute before, this is good to know. nick On Thu, Oct 11, 2012 at 9:20 PM, Miles Bader wrote: > Nicolas Bock writes: >> libsomething_la_CPPFLAGS = -I../../ > ... >> the naming changed from a.F90 -> libsomething_la-a.lo

Re: naming convention for object files.

2012-10-11 Thread Miles Bader
Nicolas Bock writes: > libsomething_la_CPPFLAGS = -I../../ ... > the naming changed from a.F90 -> libsomething_la-a.lo to a.F90 -> > a.lo. Very strange. It's an annoying, but documented, effect of using per-library CFLAGS: when you do that, automake decides that it must generate unique object fil

Re: naming convention for object files.

2012-10-11 Thread Nicolas Bock
Hello list, I found the reason for the difference in naming: In the second library I had lib_LTLIBRARIES = libsomething.la libsomething_la_CPPFLAGS = -I../../ when I changed that to AM_CPPFLAGS = -I../../ the naming changed from a.F90 -> libsomething_la-a.lo to a.F90 -> a.lo. Very strange. n

naming convention for object files.

2012-10-11 Thread Nicolas Bock
Hello list, I am using libtool to compile a library of a bunch of F90 files. Those files have various dependencies between them and since automake is not capable of tracking those for Fortran I have to by hand add lines like a.lo : b.lo c.lo to Makefile.am. Unfortunately automake's naming conven