been there. done that. the problem is that you end up wasting one person's time with build-related issues. not many people understand make very well. and parameterizing make variables -- which i was attempting to allude to --- does not help matters.
when i was knee deep in this dreck, i don't remember gnu make having target-local variables. i had to do it through other subterfuge, including VPATH and friends. - erik > I just did it over the last two weeks. Cross compiles 2.5 platfroms > (SPUs are strange), with tests and debug targets. Not too bad if you > are willing to let *one* person hold the per-directory included- > makefiles in order. It makes a huge difference (both things, the > full dependency tree, and the one person thing). > But the code is a little rude - your world winds up with too many > parameterized make variables: $($(TARGETOS)$(DIR)BUILDDIR). And you > have to use GNU make's target-local variables to remember that state. > It ain't pretty. > > Is there a better solution? > > Paul >
