building limited functionality click

[Eddie Kohler]

> i want to bring up an obscure point that is a result of cross
> compiling.  i find it very relevant, most people won't!  which tools
> should be cross compiled, and which shouldn't?  e.g. say i am using

I think it is very relevant to get cross-compiling working right!

> Well, when i build, i
> want to build click-shrink to run on i386, and then run click-shrink
> to produce makefiles etc to build an ARM binary.  because i am
> building on i386.

This is weird!!...

You are going to run click-mkmindriver on the build machine.
click-install (if any) will run ONLY on the host machine.
But as for the others........................................???
You may want BOTH versions, for each tool!

Sometimes it makes sense to prepare a configuration --
click-fastclassifier, click-devirtualize, click-align -- on a fast machine
before running it on a slow machine. But these programs may compile new
elements! And those new elements should be compiled for the host
machine....even if the tool runs on the build machine....

Argh.

There is probably a nice simple answer that involves making some consistent
choices. Like a configuration option: "--enable-host-tools" or something:
that says build the tools (except mkmindriver) for cross compiling. What
do you suggest?

love,
ed