Hi Jeff & Miles, Thank you both for your helpful replies.
The dependency issue that Jeff raised is not a problem for us, since we have a script to determine Fortran 90 dependencies. I'm not sure that it will work to have a separate library of the user-added code, since we don't know ahead of time what dependencies there will be between existing code and the user-added code. Your other suggestions are helpful. We'll give this some more thought. Thanks again, Bill On Jan 13, 2012, at 1:32 AM, Miles Bader wrote: > "Daily, Jeff A" <[email protected]> writes: >> Yes, all sources must be listed, AFAIK. You could write your own build >> rules and targets for these files, which would be copied by automake into >> your eventual Makefile, but that somewhat defeats the purpose of using a >> build tool if you're writing many of the rules yourself. > > Er, what? I think automake actually does a pretty good job of making > custom rules painless and useful... > > Even if you use some custom rules for a few files in a Makefile.am, > automake can still do about 99% of the heavy-lifting for a project. > > Typically my approach is to put all the "funny" stuff in its own > library, and have the "normal" automake targets (99% of them) depend on > that, with a few custom rules to dispatch the building of "libfunny.a" > to its own Makefile or something (which can be generated separately by > configure if necessary). > > -Miles > > -- > /\ /\ > (^.^) > (")") > *This is the cute kitty virus, please copy this into your sig so it can > spread.
