We are planning to put all alliance tools under autoconf / automake .... With those two tools, the multi-architecture builds are very easy with vpath variables. It's already done for ocp and ocr but it's a lot of work for the other tools .... Regards ... Christophe. On Mon, 7 Jan 2002, Art wrote: > Thanks, Olivier. > > I've sync'd up my local CVS repository with yours and > have separated the "source" from the "build" directories. > > I do not know if the "Alliance" developers are interested > in this approach, but I like it because it keeps a "pure" > source tree separate from the "build" tree which can be destroyed > and recreated anywhere without having to re-download or "clean" > the source tree. I.e., it's a way to do a "I know is is as clean > as you get distribution" vs "make clean" or "make distclean". > > I am thinking about posting the "diff -c" of the "build", "Makefile", > "configure", "configure.in" and the "mbk/Makefile", once I rebuild > the entire Alliance 4.5. This will mean that this separation is complete > and works for "make". I was thinking about doing this as a sort of "staging" > approach. Once, I'm comfortable with a few "confidence" tests, I could tell > do a "make install" which would copy my "working" files from $(BUILDDIR) > to $(PRODDIR), e.g., /usr/alliance. > > Comments appreciated. It was quite an effort, since I had to modify a > lot of Makefiles with different styles into a more generic style. > A nice side-effect is that I converted a lot of explicit make rules > to fewer, more concise implicit rules. > One bad thing is, I only tested the change with GNU make vs Unix make. > I did not change the syntax much and noticed many of the current make > files already use "my" constructs anyways. :-> > > BTW, I got the opportunity to refresh my memory on Vi macros! :-) > E.g., :map #7 /libraries.mk<CR>A<CR>sdir=$(SRCDIR)<Esc> > > :map #8 /local.mk<CR>i$(sdir)/<Esc> > :map #9 /^.c.o<CR>5cw%.o<Tab>: $(sdir)/%.c<Esc> > > > Thanks & Regards, > > Art > --