by Dmit » Fri, 03 May 2002 02:06:44
done.
I still don't sure but I think that prerequsites defined in this way
doesn't calculated and thus the your target will not build when it
should be.
What can be done is:
====================
TARGETS_LIST = a.b c.d d.e f.g
SRCDIR = some_path
$(TARGETS_LIST):
DEPS.d: $(TARGETS_LIST)
for file in $(TARGETS_LISTS) do \
create line of form "DEPS.d x.y: x y"
and append it to DEPS.d
done
include DEPS.d
Dmitry
1. Makefile, targets and generated prerequisites?
I have a situation that I cannot solve.
Having a series of targets that should build the same way (ie the same
rule) but for which I cannot use static patterns, default rules, etc.
how do I do it?
## Suppose the list is:
TARGETS_LIST = a.b c.d d.e f.g
SRCDIR = some_path
## Where a.b depends on $(SRCDIR)/a and $(SRCDIR)/b and so on
## Can I write something like the following (first prerequisites takes
the name, the second the extension)?
$(TARGETS_LIST): $(SRCDIR)/$(basename $2) \
calculated?
Is there a simpler or saner way of doing this?
Thanks,
JF
2. Setup computer for small lan
3. Makefiles targets and "generated" prerequisites
5. sed/awk - generating Makefiles (Re: awk processing of Makefile macros)
7. kconfig: Generate prerequisites
8. Fast FPS60 Video Capture Card
9. add checkstack Makefile target
10. 'tags' target in makefile broken
11. what is the target "<built-in>" in a makefile?
12. Including a Makefile depending on the target
13. How to determine automatically in makefile the cpu target