On 2006-09-08 13:59-0400 William A. Hoffman wrote:

As a CMake developer I think it would be much easier to do it with
two makefiles.  As far as I can tell there are two modes of cross compiling.

1. The whole project is being built for some other architecture.

2. The project has some targets that need to be built local and some
that need to be built for some other architecture.

[...]
For 2, two build trees will not be that hard to manage, with of course a top
level makefile that can go into both trees, local first then target.   If
you
use an executable from the build tree via its cmake target name it will be
easy to tell where to find the correct executable.

I have no expertise in cross-compiling, but I am trying to follow this thread
anyway to learn something.

Your last paragraph that I quoted above seems to imply a single cmake
invocation would prepare both a build tree for the local architecture and a
build tree for the different architecture. If that interpretation of what
you said is correct, then that seems over-complicated to me.  Instead, I
would think that if somebody wants to build for both a local and different
architecture, why not simply have two completely independent build trees
with two completely independent invocations of cmake?  One invocation would
have appropriate options for the local architecture (as for cmake now), and
one would have appropriate options for the different architecture (as in 1).
Neither invocation would know about the other.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the Yorick front-end to PLplot (yplot.sf.net); the
Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to