Michiel Soede wrote:
- non-recursive make, is that the same as just making one big make
file that will always build
everything? So I would loose the ability to build (for example) only
one application, or library?
You can always issue `make foo' if you wanna build `foo' only.
- isn't there
Hi John,
Thanks for the fast reply (my mailtool messed up the line-feeds I guess,
sorry about that).
You were right about the wrong order in SUBDIRS = apps comps (that was a
type).
Your answers raised some new questions to me:
- non-recursive make, is that the same as just making one big mak
Hi Michiel,
On 8/4/2009 10:01 AM, Michiel Soede wrote:
Hi,
I have a problem with dependencies to libraries in my build structure.the
directory structure in my project is as follows (roughly):
configure.acmakefile.amapps/ makefile.am app1/
main.cc ma
Hi,
automake requires aclocal.m4 to be present in the current directory.
this is not the case for me, I have one master aclocal.m4 and a few
subprojects, each with its own Makefile.am and configure.in.
this means that for automake to run, I have to create a temp symlynk for
aclocal.m4 and then the
Hi,
I have a problem with dependencies to libraries in my build structure.the
directory structure in my project is as follows (roughly):
configure.acmakefile.amapps/ makefile.am app1/
main.cc makefile.am comps/ makefile.am
comp1
