ake@cmake.org
Subject: Re: [CMake] is it worth using cmake to cross-compile for embedded arm
device?
to gcc you can pass --sysroot which will bias it's internal referenced includes
and libraries
On Wed, Oct 19, 2016 at 9:57 AM, Gunter, Walter E
mailto:walter.gun...@dematic.com>> wrote:
PATH
>
> CMAKE_FIND_ROOT_PATH
>
> Should they be the same reference location?
>
>
> This is the folder structure at the /opt/toolchains/arm-2008q3/
> bin/arm-none-linux-gnueabi
>
> /bin
>
> /include
>
> /lib
>
> /libc
>
>
>
> Thoughts?
>
om: dfloge...@gmail.com [mailto:dfloge...@gmail.com] On Behalf Of Dave
Flogeras
Sent: Friday, September 16, 2016 5:43 PM
To: Gunter, Walter E
Subject: Re: [CMake] is it worth using cmake to cross-compile for embedded arm
device?
I personally use cmake with multiple cross toolchains successfully.
On 17.09.2016 00:11, Gunter, Walter E wrote:
> Okay…that made a huge difference.
Just a silly question: Where have been the commands that you now have
moved to the toolchain file? Before or after project()?
For project() triggers the process of finding the compiler etc. and I'm
not sure wether i
Re: [CMake] is it worth using cmake to cross-compile for embedded arm
device?
I personally use cmake with multiple cross toolchains successfully. I guess it
depends on what you are trying to achieve. I prefer it because I can use the
same CMakeLists.txt to build natively on linux/mac/windows,
Gunter, Walter E wrote:
> I am having some troubles getting cmake setup and wonder if cmake is the
> right tool.
> Thoughts? Suggestions?
Yes, it is. I do it basically every day. Read my advise and properly set up a
toolchain file, that is very likely the missing magic.
https://cmake.org/cmake/h
