<div><br></div><div>The more I use cmake, the more I find it difficult to bend in to shape to cross compile. The original design doesn't seem to be designed for anything more than windows-linux or linux-windows cross compiles.<br clear="all">
</div><div><br></div><div>Some things I'm having to currently work around by creating my own cross-compiling set of modules. My host is an amd64 linux and my target is an arm linux.</div><div><br></div><div>- You can't set CMAKE_SYSTEM_NAME to anything useful other than Linux, which of course doesn't trigger the cross-compile variable CROSS_COMPILING because the host is the same.</div>
<div>- There is no distinction between install prefixes for the target and the host. Sometimes I'd like to put various build tools on the host system at the same time as libs and binaries on the target root.</div><div>
- Debian packaging in cpack will only ever put things in /usr, regardless of cross-compiles or different CMAKE_INSTALL_PREFIX. Refer again to above comment.</div><div><br></div><div>Having some useful autotools install style variables (--prefix and --exec-prefix), someway of utilising of proper gnu tuples (e.g. arm-unknown-linux-gnueabi) would make things alot easier.</div>
<div><br></div><div>Is this planned or is this something that could use a nudge to move into a useful direction? </div><div><br></div><div>Do many other people cross-compile much with cmake?</div><br>-- <br>Phone : +82-10-5400-3296 (010-5400-3296)<br>
HomePage: <a href="http://snorriheim.dnsdojo.com/">http://snorriheim.dnsdojo.com/</a><br>Yujin Robot: <a href="http://www.yujinrobot.com/">http://www.yujinrobot.com/</a><br>Projects: <a href="http://snorriheim.dnsdojo.com/redmine/projects">http://snorriheim.dnsdojo.com/redmine/projects</a><br>