[asterisk-dev] Trickiness building svn-trunk as cross-compile

[Brian Capouch]

I'm working on keeping svn-trunk built-up against the openWRT kamikaze 
build system.  Both are changing constantly, so there's always fun to be 
had.

I'm trying to rig things so that I can complete the build without having 
to manually munge (or, hopefully, even patch) the distribution build files.

I'm stuck on one little matter, and have thought myself into an addle on 
it.  Perhaps someone else will see a way out.

The menuselect process needs to be built to run on the host machine, 
whereas everything else has to run on the target.

So what I do is have my build script duck into the menuselect directory 
right after running ./configure, and do a make with --host and --build 
both set to the host architecture.  Then I back out and run "make 
menuselect" at the toplevel.  This works splendidly.

I then do a "make all" in the toplevel.

That's where the bits hit the fan.

all: calls _all: which calls cleantest, which sees the recently-built 
code in menuselect and removes it, then goes in there and starts 
building it to run on the target platform.  BANG!!

The only workaround I have been able to figure out is to remove the 
cleantest target from make all.  That has an aroma to it I'm not too 
fond of.

I wonder what would be the correct fix?

Thanks.

B.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.