Hello,
I have a problem with cross-compiling that i don't know how to solve
even after days of searching.
The situation is :
- Project compiled on ARM platform directly, works fine.
- Cross-compiled, final executable linking fails because of a transitive
library not found.
I am using a few
Hi,
I want to compile a program for Android. I work on Windows 10. Because I
recently reinstalled my OS everything isn't older than two month. I
Installed everything using Qt's, Android Studio's (and for Windows
Visual Studio's) installers/SDK Manager, to prevent mistakes I might
have made.
I
Gunter, Walter E wrote:
> I setup the Main CMakeLists.txt to cross_compile using an arm toolchain:
>
> cmake_minimum_required(VERSION 3.2)
>
> project(enterprise CXX)
>
> set(CMAKE_SYSTEM_NAME Linux)
> set(CMAKE_CXX_COMPILER
> /opt/toolchains/arm-2008q3/bin/arm-none-linux-gnueabi-g++)
> set(CMAK
I am referencing some includes that are part of my embedded device toolchain,
#include
If I have setup the cross compile directory correctly, does it know about these
or do I need to make it known?
if so, what’ the best approach?
Current Main CMakeLists.txt
cmake_minimum_required(VERSION 3.2)
clude <
-Original Message-
From: Rolf Eike Beer [mailto:e...@sf-mail.de]
Sent: Thursday, September 15, 2016 12:06 PM
To: cmake@cmake.org
Cc: Gunter, Walter E
Subject: Re: [CMake] cross-compiling for arm
Am Donnerstag, 15. September 2016, 15:48:02 schrieb Gunter, Walter E:
> I am us
Am Donnerstag, 15. September 2016, 15:48:02 schrieb Gunter, Walter E:
> I am using the arm-2008q3 toolchain and having some issues with compiling.
> Doing a c++ compile for RT Linux,
> I have setup the following in my main CMakeLists.txt
Use a toolchain file. project() will scan for the compiler a
I am using the arm-2008q3 toolchain and having some issues with compiling.
Doing a c++ compile for RT Linux,
I have setup the following in my main CMakeLists.txt
arm-none-linux-gnueabi-g++
cmake_minimum_required(VERSION 3.2)
project(enterprise CXX)
set(CMAKE_SYSTEM_NAME Linux)
set(CMAKE_CXX_COM
Hello,
I'm using CMake 3.2.2 on Solaris 10 x86. I've built a toolchain to
cross compile for SPARC, which is working fine for software with GNU
autotools.
But now I'm trying to compile Synergy, which is based on CMake, and I
have lots of troubles with double declarations:
[sepp@synergy /home/sepp/
On Saturday, June 13, 2015 23:26:59 tors...@robitzki.de wrote:
> Hi Alex,
>
> Am 13.06.2015 um 22:18 schrieb Alexander Neundorf :
> > On Friday, May 29, 2015 11:14:06 tors...@robitzki.de wrote:
> …
>
> >> I saw that there is a file Platform/Generic-SDCC-C.cmake, while searching
> >> for a way to
Hi Alex,
Am 13.06.2015 um 22:18 schrieb Alexander Neundorf :
> On Friday, May 29, 2015 11:14:06 tors...@robitzki.de wrote:
…
>> I saw that there is a file Platform/Generic-SDCC-C.cmake, while searching
>> for a way to force cmake to use this file, I found a makro
>> CMAKE_FORCE_C_COMPILER that let
On Friday, May 29, 2015 11:14:06 tors...@robitzki.de wrote:
> Hello,
> I was looking for some resources on how to configure cmake to use the small
> device c compiler (sdcc). I tried a little bit and found that cmake assumed
> that the object file extension would be .obj. But sdcc uses .rel for obj
Hello,
I was looking for some resources on how to configure cmake to use the small
device c compiler (sdcc). I tried a little bit and found that cmake assumed
that the object file extension would be .obj. But sdcc uses .rel for object
files. I’ve searched a lot in the web and the cmake sources,
Hello I am new to cmake,
I have two question´s concerning cross compiling with gnu compilers
1) First Question: Can anyone explain me, why a toolchain file is called twice when cross compiling? I use the current cmake version 3.2.2.
I use this toolchain file as an example...
# the
I understand the cross-compile process reasonably well. I also have a
fairly good feel for ExternalProject_Add, What I'm trying to do is combine
these ideas but, I am confused about one general issue.
While I am cross-compiling the Linux kernel, I discover that the kernel
requires zlib. So, I add
On Fri 06 Dec 2013 01:04:35 AM CET, Stephen Kelly wrote:
Bogdan Cristea wrote:
SET(CMAKE_FIND_ROOT_PATH
/home/bogdan/dev/src/tizenbuildtools/emulator/GBS-ROOT/local/BUILD-
ROOTS/scratch.i586.0)
This is not passed as --sysroot. However, cmake master supports a
CMAKE_SYSROOT variable.
http:/
Bogdan Cristea wrote:
> SET(CMAKE_FIND_ROOT_PATH
> /home/bogdan/dev/src/tizenbuildtools/emulator/GBS-ROOT/local/BUILD-
ROOTS/scratch.i586.0)
This is not passed as --sysroot. However, cmake master supports a
CMAKE_SYSROOT variable.
http://www.cmake.org/cmake/help/git-master/variable/CMAKE_SYSRO
Hi
I am trying to write a toolchain cmake script in order to crosscompile a
cpp program for Tizen emulator. Here is the cmake script I am using:
SET(CMAKE_SYSTEM_NAME Linux)
SET(CMAKE_SYSTEM_VERSION 1)
SET(CMAKE_C_COMPILER
/home/bogdan/tizen-sdk/tools/i386-linux-gnueabi-gcc-4.5/bin/i386-linux
Stephen Kelly wrote
>You might consider trying my cross-compiling-toolchain-variables branch in
>the git repo.
Thanks but I really want to understand what I can do to get my version
(2.8.0) to work.
Is there some CMAKE_ variable I should be setting in my toolchain file to
point the linker at th
Jack Smith wrote:
> Hello,
>
> I'm confused by an issue that I am having with a project I have recently
> joined.
You might consider trying my cross-compiling-toolchain-variables branch in
the git repo.
Thanks,
Steve.
--
Powered by www.kitware.com
Please keep messages on-topic and check t
Hello,
I'm confused by an issue that I am having with a project I have recently
joined.
We are cross compiling for ARM on linux.
I have the cross compiler toolchain installed at /CC_TOOLCHAIN
I set CMAKE_SYSROOT_PATH appropriately, then do this in my toolchain file:
set(CMAKE_FIND_ROOT_PATH "$
On Monday 27 May 2013, BILODEAU Andre wrote:
> Hello
>
> I am presently installing makefiles for cross-compiling by using cmake
> 2.8.10.2 and I have to deal with the following issues:
>
> 1- The toolchain, Wind River C compiler (formerly Diab) is not
> mentioned into modules such as "CMakeD
Hello
I am presently installing makefiles for cross-compiling by using cmake 2.8.10.2
and I have to deal with the following issues:
1- The toolchain, Wind River C compiler (formerly Diab) is not mentioned
into modules such as "CMakeDetermineCompilerId.cmake), and the compiler is not
ident
On 2012-10-15 21:46-0700 Daniel Russel wrote:
On Oct 15, 2012, at 9:35 PM, "Alan W. Irwin" wrote:
On 2012-10-15 21:02-0700 Daniel Russel wrote:
I'm trying to get cross compilation of a simple library working to
build a windows library on a linux box using the visual studio
compilers.
I d
On Oct 15, 2012, at 9:35 PM, "Alan W. Irwin" wrote:
> On 2012-10-15 21:02-0700 Daniel Russel wrote:
>
>> I'm trying to get cross compilation of a simple library working to
> build a windows library on a linux box using the visual studio
> compilers.
>
> I don't get it. How can visual studio c
On 2012-10-15 21:02-0700 Daniel Russel wrote:
I'm trying to get cross compilation of a simple library working to
build a windows library on a linux box using the visual studio
compilers.
I don't get it. How can visual studio compilers execute properly on Linux?
Don't they need to be run on a
I'm trying to get cross compilation of a simple library working to build a
windows library on a linux box using the visual studio compilers. So far the
farthest I've gotten is with:
./cmake-2.8.9-Linux-i386/bin/cmake ../rmf -DCMAKE_SYSTEM_NAME=Windows
-DCMAKE_C_COMPILER=/usr/bin/cl -DCMAKE_CXX_
On Tue, Oct 2, 2012 at 1:09 PM, Arindam Mukherjee
wrote:
> On Tue, Oct 2, 2012 at 4:22 PM, David Cole wrote:
>>
>>
>> cmake -G "Visual Studio 9 2008 Win32" src_dir
>>
>> will not work. There is no such generator. Leave out the " Win32" for this
>> case... it is implied.
>>
>>
>
> How would it be
On Tue, Oct 2, 2012 at 4:22 PM, David Cole wrote:
> On Tue, Oct 2, 2012 at 5:30 AM, Arindam Mukherjee
> wrote:
>>
>> On Tue, Oct 2, 2012 at 2:48 AM, Xavier Besseron
>> wrote:
>> > Hi,
>> >
>> > I was able to build win64 executable on my 32-bit Windows.
>> >
>> > First, I had to make the "full in
On Tue, Oct 2, 2012 at 5:30 AM, Arindam Mukherjee <
arindam.muker...@gmail.com> wrote:
> On Tue, Oct 2, 2012 at 2:48 AM, Xavier Besseron
> wrote:
> > Hi,
> >
> > I was able to build win64 executable on my 32-bit Windows.
> >
> > First, I had to make the "full installation" of VS 2008 (the "defaul
On Tue, Oct 2, 2012 at 2:48 AM, Xavier Besseron wrote:
> Hi,
>
> I was able to build win64 executable on my 32-bit Windows.
>
> First, I had to make the "full installation" of VS 2008 (the "default
> installation" did not provide the win64 compiler in my case). Then, I
> had to select the "Visual
Hi,
I was able to build win64 executable on my 32-bit Windows.
First, I had to make the "full installation" of VS 2008 (the "default
installation" did not provide the win64 compiler in my case). Then, I
had to select the "Visual Studio 9 2008 Win64" generator in CMake. And
the project built corre
On Mon, Oct 1, 2012 at 4:35 PM, Arindam Mukherjee
wrote:
> Hi,
>
> I have a Windows XP build setup with Visual Studio 2008 SP1 and
> Windows SDK 6. I have set up a CMake project for a source base that is
> built on Linux, Solaris, AIX and Windows. So far I have managed to get
> the Windows 32-bit
Svenskmand wrote:
> Hello :)
>
> I am one of the developers of OpenDungeons a FOSS RTS game inspired by
> Dungeon Keeper. I am trying to cross-compile our game on Ubuntu 12.04 for
> Windows (XP, Vista and 7), but I have run into some trouble.
>
> I following these guides:
> http://www.cmake.org/W
On Wednesday 18 July 2012, Svenskmand wrote:
> Hello :)
>
> I am one of the developers of OpenDungeons a FOSS RTS game inspired by
> Dungeon Keeper. I am trying to cross-compile our game on Ubuntu 12.04 for
> Windows (XP, Vista and 7), but I have run into some trouble.
...
> SVN/mediaSource/ODLinu
Hello :)
I am one of the developers of OpenDungeons a FOSS RTS game inspired by
Dungeon Keeper. I am trying to cross-compile our game on Ubuntu 12.04 for
Windows (XP, Vista and 7), but I have run into some trouble.
I following these guides:
http://www.cmake.org/Wiki/CMake_Cross_Compiling
http://w
2011/11/9 Thomas Walwyn :
> Hi All,
>
>
>
> I’m brand-new to cmake, and have run into a problem cross compiling for an
> Intel embedded platform:
>
>
>
> Make complains about missing file 'curl/curl.h' when compiling against an
> Intel SDK for linux. 'curl/curl.h' resides in the cross-compile toolc
Hi All,
I'm brand-new to cmake, and have run into a problem cross compiling for an
Intel embedded platform:
Make complains about missing file 'curl/curl.h' when compiling against an Intel
SDK for linux. 'curl/curl.h' resides in the cross-compile toolchain under
[toolchain-folder]/include/curl/
Hi Alex,
sorry for sending mails in HTML format (hopefully the mail client is now
configured correctly).
You'll find my answers to your comments below.
On 20.09.11 05:29, Alexander Neundorf wrote:
Hi,
can you please adjust your mail client so it doesn't send HTML mails ?
On Monday, Septembe
Hi,
can you please adjust your mail client so it doesn't send HTML mails ?
On Monday, September 19, 2011 04:57:32 PM Martin Kupke wrote:
> That's a hint, I changed my toolchain file "toolchain_ppc.cmake" to the
> following: INCLUDE(CMakeForceCompiler)
> set(CMAKE_SYSTEM_NAME "Discovery")
>
>
That's a hint, I changed my toolchain file "toolchain_ppc.cmake" to
the following:
INCLUDE(CMakeForceCompiler)
set(CMAKE_SYSTEM_NAME "Discovery")
if(CMAKE_CROSSCOMPILING)
message("Cross Compiling")
endif(CMAKE_CROSSCOMPILING)
# which compilers to use
You can use the following commands to know what are compilers used in
the CMakeLists.txt:
message("C compiler: " ${CMAKE_C_COMPILER})
message("C++ compiler: " ${CMAKE_CXX_COMPILER})
Moreover, you can set them:
set(CMAKE_CXX_COMPILER ...)
regards
Benjamin JEANTY-RUARD
Le lundi 19 septembre 201
2011/9/19 Martin Kupke
>
> My problem (the error) already occurs in the toolchain file, this means
> before the CMakeLists.txt is read. So far it is total independent of the
> entries in the CMakeLists.txt!
>
> I have added the line:
> message ("Mein CMakeLists.txt File")
> in top of my CMakeLis
My problem (the error) already occurs in the toolchain file, this
means before the CMakeLists.txt is read. So far it is total
independent of the entries in the CMakeLists.txt!
I have added the line:
message ("Mein CMakeLists.txt File")
in top of my CMakeLists.txt
If adding the parameter -G "NMake Makefiles" to my command line,
then the output is different...but still errors:
* snip output *
Cross Compiling
-- The C compiler identification is unknown
-- The CXX compiler identification is
2011/9/19 Martin Kupke :
> I'm using CMake in version 2.8.5 and just want to cross compile with a
> decicated Compiler / Linker set on my Windows machine. Of course I've read
> the FAQ and the Tutorial, afterwards I started trying to use CMake on a DOS
> (cmd.exe) command line interface with CMakeL
I'm using CMake in version 2.8.5 and just want to cross compile with a
decicated Compiler / Linker set on my Windows machine. Of course I've
read the FAQ and the Tutorial, afterwards I started trying to use CMake
on a DOS (cmd.exe) command line interface with CMakeLists.txt and a
toolchain file
I'm trying to compile code for an ARM processor on an x86-64 Ubuntu
machine. I'm using scratchbox, compiling programes with the standard
autoconf/configure scripts work fine so the cross compiler works.
When I use Cmake I runinto problems, the following is my arm_cross.cmake
file
INCLUDE(CM
On 07/27/2011 04:28 PM, r.cze...@esa-grimma.de wrote:
> Hi all,
>
> I tried to cross-compile an internal application for windows on a linux
> machine,
> but failed, because cmake at some point re-start the configure process,
> and
> drops the CMAKE_SYSTEM_NAME variable along that way. Attached i
ng that way. Attached is a
> minimal CMakeLists.txt, which reproduces the problem.
>
> Is there a way to avoid the reconfiguration?
Did you try to use a toolchain file as described in the cmake cross compiling
wiki page ?
http://www.vtk.org/Wiki/CMake_Cross_Compiling
It even has a separa
2011/7/27 :
> Hi all,
>
> I tried to cross-compile an internal application for windows on a linux
> machine,
> but failed, because cmake at some point re-start the configure process, and
> drops the CMAKE_SYSTEM_NAME variable along that way. Attached is a
> minimal CMakeLists.txt, which reproduces
Hi all,
I tried to cross-compile an internal application for windows on a linux
machine,
but failed, because cmake at some point re-start the configure process,
and
drops the CMAKE_SYSTEM_NAME variable along that way. Attached is a
minimal CMakeLists.txt, which reproduces the problem.
Is there
Hi.
I'm currently facing problems with rpath and cross compiling.
I build a program (deployer-gnulinux) that need and external lib in a non
standard path (lib/orocos/gnulinux/plugins).
Somewhere in the CMake procedure, there is a call to find_library with
"PATH_SUFFIXES orocos/gnulinux/plugins
On Wed, Feb 23, 2011 at 11:28 AM, Alexander Neundorf
wrote:
> On Wednesday 23 February 2011, Schmid Alexander wrote:
>> > This suffix should be set by the platform file.
>> > Modules/CMakeSystemSpecificInformation.cmake includes
>> > CMakeGenericSystem.cmake, which sets it to "". That's what you s
On Wednesday 23 February 2011, Schmid Alexander wrote:
> > This suffix should be set by the platform file.
> > Modules/CMakeSystemSpecificInformation.cmake includes
> > CMakeGenericSystem.cmake, which sets it to "". That's what you see.
> >
> > Then it includes Platform/${CMAKE_SYSTEM_NAME}, which
> This suffix should be set by the platform file.
> Modules/CMakeSystemSpecificInformation.cmake includes
> CMakeGenericSystem.cmake, which sets it to "". That's what you see.
>
> Then it includes Platform/${CMAKE_SYSTEM_NAME}, which is
> Platform/Generic.cmake. This file does not change the suffi
On Monday 21 February 2011, Schmid Alexander wrote:
...
> I did some tests and from my point of view you are right - I do not have to
> set it at all. But, nevertheless, the problem stays.
> The crosscompiling toolchain produces binary files with .out suffix, and
> for me it seems that the the TRY_
> -Ursprüngliche Nachricht-
> Von: David Cole [mailto:david.c...@kitware.com]
> Gesendet: Montag, 21. Februar 2011 13:41
> An: Schmid Alexander
> Cc: a.neundorf-w...@gmx.net; cmake@cmake.org
> Betreff: Re: [CMake] Cross-compiling: Cmake compiler and ABI check don´t work
On Mon, Feb 21, 2011 at 2:14 AM, Schmid Alexander wrote:
> On Friday 18 February 2011, Schmid Alexander wrote:
>> Hi,
>>
>> of course, I´d like to have you think further about it, so here you go...
>
> ;-)
>
>> This is the toolchain file I use.
>> The specialty about is that I want to use the ARMC
On Friday 18 February 2011, Schmid Alexander wrote:
> Hi,
>
> of course, I´d like to have you think further about it, so here you go...
;-)
> This is the toolchain file I use.
> The specialty about is that I want to use the ARMCC as compiler and an
> SDK-provided linker tool for linking.
>
> # th
On Friday 18 February 2011, Schmid Alexander wrote:
> Hi,
>
> of course, I´d like to have you think further about it, so here you go...
;-)
> This is the toolchain file I use.
> The specialty about is that I want to use the ARMCC as compiler and an
> SDK-provided linker tool for linking.
>
> # th
4 100
84072 Au i.d. Hallertau www.ccv-deutschland.de
www.ccv.eu
a.sch...@de.ccv.eu
HRB 177321 - Registergericht München
Geschäftsführung:
On Thursday 17 February 2011, Schmid Alexander wrote:
> Hi,
>
> is it possible that the ABI check won´t work anyway for cross-compiling
> scenarios?
It should.
> Anyway, I don´t think that the toolchain file is messed up, because the
> first part of CMake´s detection flow uses the settings I spec
-
Von: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net]
Gesendet: Dienstag, 15. Februar 2011 22:49
An: cmake@cmake.org
Cc: Schmid Alexander
Betreff: Re: [CMake] Cross-compiling: Cmake compiler and ABI check don´t work
Hi,
On Friday 11 February 2011, Schmid Alexander wrote:
> Hi,
>
>
Hi,
On Friday 11 February 2011, Schmid Alexander wrote:
> Hi,
>
>
>
> I am working with CMake 2.8.3 and trying to set up a cross-compiling
> toolchain for an ARMCC that runs on a Windows system.
>
>
>
> What I´ve done up to now is that I set up a toolchain file that I am using
> in combination wit
> > On Friday 11 February 2011, Schmid Alexander wrote:
> > Hi,
> >
> >
> >
> > I am working with CMake 2.8.3 and trying to set up a cross-compiling
> > toolchain for an ARMCC that runs on a Windows system.
> >
> >
> >
> > What I´ve done up to now is that I set up a toolchain file that I am using
>
On Friday 11 February 2011, Schmid Alexander wrote:
> Hi,
>
>
>
> I am working with CMake 2.8.3 and trying to set up a cross-compiling
> toolchain for an ARMCC that runs on a Windows system.
>
>
>
> What I´ve done up to now is that I set up a toolchain file that I am using
> in combination with nma
Hi,
I am working with CMake 2.8.3 and trying to set up a cross-compiling toolchain
for an ARMCC that runs on a Windows system.
What I´ve done up to now is that I set up a toolchain file that I am using in
combination with nmake makefiles.
This file defines:
SET( CMAKE_C_COMPILER "$
On Monday 07 February 2011, Emmanuel Blot wrote:
> >> FWIW: I found why I use CMAKE_FORCE_C_COMPILER rather than the simpler
> >> CMAKE_C_COMPILER command:
> >> I build projects for eCos from outside the eCos tree directory, and
> >> CMake has some trouble finding the eCos header files when simply
>> FWIW: I found why I use CMAKE_FORCE_C_COMPILER rather than the simpler
>> CMAKE_C_COMPILER command:
>> I build projects for eCos from outside the eCos tree directory, and
>> CMake has some trouble finding the eCos header files when simply using
>> CMAKE_C_COMPILER. It complains about CMAKE_FIND_
Hi Justin,
On Tuesday 14 December 2010, Justin Holewinski wrote:
> On Tue, Dec 14, 2010 at 4:45 AM, Johan Björk wrote:
> > Hi Justin,
> >
> > I'm very unsure if this is the correct solution, but it worked for me. I
> > haven't been able to find any good documentation stating how the
> > CMakeCach
On Monday 10 January 2011, Emmanuel Blot wrote:
> >> INCLUDE (CMakeForceCompiler)
> >> CMAKE_FORCE_C_COMPILER (arm-eabi-gcc-4.5.2 GNU 4)
> >
> > I haven't used that one before.
>
> FWIW: I found why I use CMAKE_FORCE_C_COMPILER rather than the simpler
> CMAKE_C_COMPILER command:
> I build projects
>> INCLUDE (CMakeForceCompiler)
>> CMAKE_FORCE_C_COMPILER (arm-eabi-gcc-4.5.2 GNU 4)
>
> I haven't used that one before.
FWIW: I found why I use CMAKE_FORCE_C_COMPILER rather than the simpler
CMAKE_C_COMPILER command:
I build projects for eCos from outside the eCos tree directory, and
CMake has so
> The docs say that the signature is
> CMAKE_FORCE_C_COMPILER( )
> so maybe something bad happens when you give it that extra
> argument "4"? Try without "4"?
Actually, it changes nothing.
*but* if I remove the specific version number for the compiler, i.e. I define
FIND_PROGRAM (xcc ${XTOOL
Hi,
(CCing the list.)
2011/1/10 Emmanuel Blot :
>> When I cross compile I do "set(CMAKE_C_COMPILER arm-linux-gcc)"
>> in a toolchain file and CMake automatically finds ranlib (and other
>> toolchain utilities) using the prefix from the C compiler. How do you
>> setup CMake for cross-compilation?
Hi,
On 10 January 2011 17:00, Emmanuel Blot wrote:
> Hello,
>
> Using the ADD_LIBRARY command for a static library (.a), how to tell
> CMake to use the ranlib tool for the target, not the default one for
> the host?
>
> I'm getting the following warning message:
>
> cd watchdog && /usr/local/Cell
> I'm getting the following warning message:
>From http://www.cmake.org/pipermail/cmake/2010-September/039705.html,
it seems on my development environment that _CMAKE_TOOLCHAIN_PREFIX is
left empty.
If I force this variable to the expected value (arm-eabi-), the proper
tools are detected and invo
Hello,
Using the ADD_LIBRARY command for a static library (.a), how to tell
CMake to use the ranlib tool for the target, not the default one for
the host?
I'm getting the following warning message:
cd watchdog && /usr/local/Cellar/cmake/2.8.3/bin/cmake -E
cmake_link_script CMakeFiles/nd_watchdog
On Tue, Dec 14, 2010 at 4:45 AM, Johan Björk wrote:
> Hi Justin,
>
> I'm very unsure if this is the correct solution, but it worked for me. I
> haven't been able to find any good documentation stating how the CMakeCache
> interacts with other parts of CMake.
>
> My assumption is that since CMAKE_
Hi Justin,
I'm very unsure if this is the correct solution, but it worked for me. I
haven't been able to find any good documentation stating how the CMakeCache
interacts with other parts of CMake.
My assumption is that since CMAKE_C{XX}_FLAGS is supposed to allow the user
to set optional compilat
I am experiencing a cross-compiling issue that I believe is related to how
toolchain files interact with the configure-time compiler checks. For
reference, I am targeting the iOS 4.2 SDK. I have a toolchain file that
sets CMAKE_C_FLAGS, CMAKE_CXX_FLAGS, CMAKE_C_LINK_FLAGS, and
CMAKE_CXX_LINK_FLAG
On Friday 02 July 2010, Kishore wrote:
> On Thursday 01 Jul 2010 8:13:56 pm Kishore wrote:
> > In the CMake wiki (http://www.cmake.org/Wiki/CMake_Cross_Compiling) it
> > says clearly that the platform module are included in the following
> > order;
> >
> > Platform/${CMAKE_SYSTEM_NAME}.cmake (manda
On Thursday 22 July 2010, Hassan Mansouri wrote:
> Hi,
> I am trying to do cross-compiling with CMake for IAR compiler (ARM).
> My main problem with the current CMake 2.8.2 is the complain about -c
> option from IAR compiler. IAR compiler does not accept -c as input C file
> and the sysntax is CC
Hi,
I am trying to do cross-compiling with CMake for IAR compiler (ARM).
My main problem with the current CMake 2.8.2 is the complain about -c option
from IAR compiler. IAR compiler does not accept -c as input C file and the
sysntax is CC .c [options]. How can I tell CMake not to put -c when
On Thursday 01 Jul 2010 8:13:56 pm Kishore wrote:
> In the CMake wiki (http://www.cmake.org/Wiki/CMake_Cross_Compiling) it says
> clearly that the platform module are included in the following order;
>
> Platform/${CMAKE_SYSTEM_NAME}.cmake (mandatory)
> Platform/${CMAKE_SYSTEM_NAME}-.cmake (option
In the CMake wiki (http://www.cmake.org/Wiki/CMake_Cross_Compiling) it says
clearly that the platform module are included in the following order;
Platform/${CMAKE_SYSTEM_NAME}.cmake (mandatory)
Platform/${CMAKE_SYSTEM_NAME}-.cmake (optional)
Platform/${CMAKE_SYSTEM_NAME}--${CMAKE_SYSTEM_PROCESS
On Monday 07 June 2010, Aeschbacher, Fabrice wrote:
> Thank you for responding
>
> Actually, I noticed that putting following line in the CMakeLists.txt of
> the tool that should not be cross-compiled also works:
>
> SET(CMAKE_C_COMPILER "gcc")
>
> The only drawback I found until now is that the na
tup (which is for us a minor issue)
Best regards,
Fabrice Aeschbacher
> -Ursprüngliche Nachricht-
> Von: Michael Wild [mailto:them...@gmail.com]
> Gesendet: Donnerstag, 3. Juni 2010 14:15
> An: Alexander Neundorf
> Cc: cmake@cmake.org; Aeschbacher, Fabrice
> Betreff:
On 3. Jun, 2010, at 14:09 , Alexander Neundorf wrote:
> On Wednesday 02 June 2010, Aeschbacher, Fabrice wrote:
>> [Sorry if this message is posted twice, but first was before I subscribed
>> to the list, so I'm not sure it was not rejected]
>>
>>
>> Hi,
>>
>> [using cmake 2.8.1]
>>
>> I have
On Wednesday 02 June 2010, Aeschbacher, Fabrice wrote:
> [Sorry if this message is posted twice, but first was before I subscribed
> to the list, so I'm not sure it was not rejected]
>
>
> Hi,
>
> [using cmake 2.8.1]
>
> I have a project where almost every sub-dirs should be cross-compiled
> (arm-l
[Sorry if this message is posted twice, but first was before I subscribed to
the list, so I'm not sure it was not rejected]
Hi,
[using cmake 2.8.1]
I have a project where almost every sub-dirs should be cross-compiled
(arm-linux-gnuueabi-gcc), but one directory containing a tool which must be
On 5. Jan, 2010, at 19:55 , Alexander Neundorf wrote:
> On Tuesday 05 January 2010, Michael Wild wrote:
>> On 4. Jan, 2010, at 19:15 , Alexander Neundorf wrote:
>> [snip]
>>
- There is no distinction between install prefixes for the target and
the host. Sometimes I'd like to put variou
On Tuesday 05 January 2010, Michael Wild wrote:
> On 4. Jan, 2010, at 19:15 , Alexander Neundorf wrote:
> [snip]
>
> >> - 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
On 4. Jan, 2010, at 19:15 , Alexander Neundorf wrote:
[snip]
>
>> - 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.
>
> In CMake one buil
DIALECT)
Our IBM_ZOS.cmake (in the Platform\ directory under the above):
INCLUDE(Platform/UnixPaths)
HTH. Or at least doesn't hurt.
...phsiii
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Alexander Neundorf
Se
Hi,
On Monday 04 January 2010, Daniel Stonier wrote:
> 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.
No. It is tested for
* x86 Lin
On Monday 04 January 2010, Daniel Stonier wrote:
> 2010/1/4 David Cole
>
> > Are you following the directions here?
> > http://www.cmake.org/Wiki/CMake_Cross_Compiling
> >
> > Or trying to cross compile some other way...?
> >
> >
> > Yes, that's where I got started - been using that for quite a wh
2010/1/4 David Cole
> Are you following the directions here?
> http://www.cmake.org/Wiki/CMake_Cross_Compiling
>
> Or trying to cross compile some other way...?
>
>
> Yes, that's where I got started - been using that for quite a while. Just
noticed some loose ends recently. Note - if I follow tha
Are you following the directions here?
http://www.cmake.org/Wiki/CMake_Cross_Compiling
Or trying to cross compile some other way...?
On Mon, Jan 4, 2010 at 3:00 AM, Daniel Stonier wrote:
>
> The more I use cmake, the more I find it difficult to bend in to shape to
> cross compile. The original
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.
Some things I'm having to currently work around by creating my own
cross-compiling set of m
Vladimir Lebedev-Schmidthof wrote:
No I didn't. I just did and all compiled and linked successfully.
Sorry for stupid questions then, I will remember to clean
cmake-generated files in future.
Thank you very much.
--
You should use out of source builds in the future... :)
-Bill
_
1 - 100 of 159 matches
Mail list logo
