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++)
>
-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 using the arm-200
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
On Saturday, June 13, 2015 23:26:59 tors...@robitzki.de wrote:
Hi Alex,
Am 13.06.2015 um 22:18 schrieb Alexander Neundorf a.neundorf-w...@gmx.net:
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
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 object
Hi Alex,
Am 13.06.2015 um 22:18 schrieb Alexander Neundorf a.neundorf-w...@gmx.net:
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
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.
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 the
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
On 2012-10-15 21:46-0700 Daniel Russel wrote:
On Oct 15, 2012, at 9:35 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca 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
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
On Oct 15, 2012, at 9:35 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca 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
On Tue, Oct 2, 2012 at 2:48 AM, Xavier Besseron xavier.besse...@uni.lu 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
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 xavier.besse...@uni.lu
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
On Tue, Oct 2, 2012 at 4:22 PM, David Cole david.c...@kitware.com wrote:
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 xavier.besse...@uni.lu
wrote:
Hi,
I was able to build win64 executable on my
On Tue, Oct 2, 2012 at 1:09 PM, Arindam Mukherjee
arindam.muker...@gmail.com wrote:
On Tue, Oct 2, 2012 at 4:22 PM, David Cole david.c...@kitware.com 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
On Mon, Oct 1, 2012 at 4:35 PM, Arindam Mukherjee
arindam.muker...@gmail.com 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
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 correctly.
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.
...
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:
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,
2011/9/19 Martin Kupke martin.ku...@novero.com:
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
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
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
2011/9/19 Martin Kupke martin.ku...@novero.com
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
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 2011 à
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
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)
On Wednesday 27 July 2011, 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 is a
2011/7/27 r.cze...@esa-grimma.de:
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,
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 is
On Wed, Feb 23, 2011 at 11:28 AM, Alexander Neundorf
a.neundorf-w...@gmx.net 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 .
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 suffix, so
On Mon, Feb 21, 2011 at 2:14 AM, Schmid Alexander a.sch...@de.ccv.eu 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
-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
/
TRY_COMPILE
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
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.
# this one
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.
# this one
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 specified
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.
# this one is important
SET( CMAKE_SYSTEM_NAME Generic )
# this one not
-
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,
I am working
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 with nmake
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 nmake
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 using
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_ROOT_PATH
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 for eCos from
Hi Justin,
On Tuesday 14 December 2010, Justin Holewinski wrote:
On Tue, Dec 14, 2010 at 4:45 AM, Johan Björk p...@spotify.com 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
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
Hi,
On 10 January 2011 17:00, Emmanuel Blot eblot...@gmail.com 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
Hi,
(CCing the list.)
2011/1/10 Emmanuel Blot eblot...@gmail.com:
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
The docs say that the signature is
CMAKE_FORCE_C_COMPILER(compiler compiler-id)
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
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
On Tue, Dec 14, 2010 at 4:45 AM, Johan Björk p...@spotify.com 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
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 (mandatory)
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
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}-compiler.cmake
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: Re: [CMake] cross-compiling / host
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 native
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
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 a project where
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 build tree
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 and
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 various build tools
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 d.ston...@gmail.com wrote:
The more I use cmake, the more I find it difficult to bend in to shape to
cross
2010/1/4 David Cole david.c...@kitware.com
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 -
On Monday 04 January 2010, Daniel Stonier wrote:
2010/1/4 David Cole david.c...@kitware.com
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
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 Linux
. Or at least doesn't hurt.
...phsiii
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Alexander Neundorf
Sent: Monday, January 04, 2010 1:16 PM
To: cmake@cmake.org
Subject: Re: [CMake] Cross Compiling
Hi,
On Monday 04 January 2010, Daniel
Hello Alexander,
On Oct 19, 2009, at 23:18 PM, Alexander Neundorf wrote:
I set CMAKE_SYSTEM to Linux, even added SET(APPLE 0) but
install_name option is still generating.
You should set CMAKE_SYSTEM_NAME, not CMAKE_SYSTEM to Linux.
If you
really set CMAKE_SYSTEM instead of
Zitat von Vladimir Lebedev-Schmidthof vlebe...@envionsoftware.com:
On Oct 19, 2009, at 23:18 PM, Alexander Neundorf wrote:
I set CMAKE_SYSTEM to Linux, even added SET(APPLE 0) but
install_name option is still generating.
You should set CMAKE_SYSTEM_NAME, not CMAKE_SYSTEM to Linux. If you
Hello Hendrik,
On Oct 20, 2009, at 15:56 PM, Hendrik Sattler wrote:
I tried. Setting CMAKE_SYSTEM_NAME to Linux does not seem to
affect
CMAKE_SYSTEM
WHERE are you try to set this? Setting this in a CMakeLists.txt file
will not work. Did you read the wiki page[1] about cross-compiling?
Zitat von Vladimir Lebedev-Schmidthof vlebe...@envionsoftware.com:
I tried having toochain.cmake file in the same dir as CMakeLists.txt
using
cmake -DCMAKE_TOOLCHAIN_FILE=./toolchain.cmake .
does not seem to even read that file. I tried to state full path, move
the file away, no luck.
Since
Hello Hendrik,
On Oct 20, 2009, at 17:50 PM, Hendrik Sattler wrote:
Zitat von Vladimir Lebedev-Schmidthof vlebe...@envionsoftware.com:
I tried having toochain.cmake file in the same dir as CMakeLists.txt
using
cmake -DCMAKE_TOOLCHAIN_FILE=./toolchain.cmake .
does not seem to even read
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
On Monday 19 October 2009, Vladimir Lebedev-Schmidthof wrote:
Hello everyone,
Two compiling platforms - Linux and OS X.
Same project, same cmake (2.6.4), same target (Linux/ARM).
Sources compiles well (GNU C/C++) but linking is different.
Everything is fine on Linux.
comparing make
Alexander Neundorf wrote:
On Sunday 20 September 2009, Harald Kipp wrote:
Alexander Neundorf wrote:
On Sunday 20 September 2009, Harald Kipp wrote:
add_library(nutfs STATIC basename dirent dirname)
I would recommend to use the full filename, i.e. including the suffix. So
probably
On Monday 21 September 2009, Harald Kipp wrote:
Alexander Neundorf wrote:
On Sunday 20 September 2009, Harald Kipp wrote:
Alexander Neundorf wrote:
On Sunday 20 September 2009, Harald Kipp wrote:
add_library(nutfs STATIC basename dirent dirname)
I would recommend to use the full
On Sunday 20 September 2009, Harald Kipp wrote:
Hi all,
I'm considering CMake for our Ethernut project
http://www.ethernut.de
In a first step I tried to build a simple library for an arm-elf target.
I tried to follow
http://www.itk.org/Wiki/CMake_Cross_Compiling
as well as
Alexander Neundorf wrote:
On Sunday 20 September 2009, Harald Kipp wrote:
My subdir CMakeLists:
--- C:\ethernut-4.9.6\nut\fs\CMakeLists.txt ---
add_library(nutfs STATIC basename dirent dirname)
This command means that you want to build a library called nutfs from the
source files
On Sunday 20 September 2009, Harald Kipp wrote:
Alexander Neundorf wrote:
On Sunday 20 September 2009, Harald Kipp wrote:
My subdir CMakeLists:
--- C:\ethernut-4.9.6\nut\fs\CMakeLists.txt ---
add_library(nutfs STATIC basename dirent dirname)
This command means that you want to build
On Friday 19 June 2009, Hendrik Sattler wrote:
Hi,
FindQt4 seems to _completely_ fail for cross-compiling as it depends on
running qmake. As it finds the hosts qmake executable, all it gets is wrong
information.
yes, it queries qmake, and since qmake must run on the build host, this will
Am Freitag 19 Juni 2009 21:13:14 schrieb Clinton Stimpson:
To cross-compile Qt apps, you still need to be able to run at least uic,
moc, and maybe other tools.
I've done it before (way back when cross-compiling support was first
added to cmake).
What I did was compile Qt for the target
On Fri, Jun 19, 2009 at 09:00:24PM +0200, Hendrik Sattler wrote:
FindQt4 seems to _completely_ fail for cross-compiling as it depends on
running qmake. As it finds the hosts qmake executable, all it gets is wrong
information.
Not sure I understand the problem but you can use
To cross-compile Qt apps, you still need to be able to run at least uic,
moc, and maybe other tools.
I've done it before (way back when cross-compiling support was first
added to cmake).
What I did was compile Qt for the target platform, and again for the
native platform using the same
I've been using QNX and cmake together for a few weeks, and I've yet to
have the problem that you indicated. In my QNX toolchain file I use the
line:
SET( CMAKE_AR
${QNX_HOST}/usr/bin/ntox86-ar${HOST_EXECUTABLE_SUFFIX} CACHE PATH QNX
ar Program )
-kito
Thanks for the help, that has
I've been using QNX and cmake together for a few weeks, and I've yet to
have the problem that you indicated. In my QNX toolchain file I use the
line:
SET( CMAKE_AR
${QNX_HOST}/usr/bin/ntox86-ar${HOST_EXECUTABLE_SUFFIX} CACHE PATH
QNX ar Program )
-kito
Message: 5
Date: Wed, 25 Mar 2009
On Wednesday 17 September 2008, Simon Barner wrote:
Dear CMake users list,
I am currently development a CMake cross build platform
definition to support Microchips C18 C compiler[1].
I encountered the problem that C18's linker does not like '/' as
path delimiter which is why I need some
Hi,
does anybody have a clue on this? Or should I re-state
my question?
Thanks,
Simon
I am currently development a CMake cross build platform
definition to support Microchips C18 C compiler[1].
I encountered the problem that C18's linker does not like '/' as
path delimiter which is why I
On Monday 25 August 2008, Phil Smith wrote:
I'm back on this, after a week at a conference and a week of vacation.
I have the GET_FILENAME_COMPONENT call working, and it returns what I'd
expect (c:/progra~1/dignus), but the FIND_PROGRAM resolves the path with
blanks (c:/Program
${PLINK_EXECUTABLE} contains spaces...
Maybe you need escaped quotes:
SET(CMAKE_CXX_LINK_EXECUTABLE \${PLINK_EXECUTABLE}\
\ around the executable variable reference...?
On Wed, Sep 3, 2008 at 6:04 PM, Alexander Neundorf
[EMAIL PROTECTED]wrote:
On Monday 25 August 2008, Phil Smith wrote:
@cmake.org
Subject: Re: [CMake] Cross-compiling for z/OS -- linker question
On Monday 25 August 2008, Phil Smith wrote:
I'm back on this, after a week at a conference and a week of vacation.
I have the GET_FILENAME_COMPONENT call working, and it returns what I'd
expect (c:/progra~1/dignus
as-is?
...phsiii
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander
Neundorf
Sent: Saturday, August 09, 2008 8:10 AM
To: cmake@cmake.org
Subject: Re: [CMake] Cross-compiling for z/OS -- linker question
and zosport.cmake contains (comments/whitespace
and zosport.cmake contains (comments/whitespace stripped):
SET(CMAKE_SYSTEM_NAME ZOS)
SET(CMAKE_C_COMPILER c:/progra~1/dignus/cc.bat -fasciiout)
SET(CMAKE_CXX_COMPILER c:/progra~1/dignus/cxx.bat -fasciiout)
SET(CMAKE_CXX_LINK_EXECUTABLE c:/progra~1/dignus/plink.exe \-
Well, the initial tests for the compiler should work without the
CMakeForceCompiler stuff. If this works, then CMakeC[XX]CompilerId.c.in cmake
should be able to detect that it's the Dignus compiler, and set
CMAKE_C_COMPILER_ID to Dignus. Once this is works, it then tries to load
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2008 5:32 PM
To: Phil Smith
Cc: cmake@cmake.org
Subject: Re: [CMake] Cross-compiling for z/OS -- linker question
On Tuesday 05 August 2008, Phil Smith wrote:
Re the link command, thanks:
SET(CMAKE_C_LINK_EXECUTABLE c:/progra~1/dignus
On Wednesday 06 August 2008, Phil Smith wrote:
OK, once I get it working for real, I'll do this.
:-)
But I think I confused you. ZOS is the OS (really z/OS). System z is the
hardware platform. Dignus is the compiler.
So shouldn't the files be named Systemz-Dignus-C.cmake etc.?
No, it's
Hi,
On Tuesday 05 August 2008, Phil Smith wrote:
Next issue: linking. I have a toolchain file now that looks like this:
# Tell CMAKE the target system name
SET(CMAKE_SYSTEM_NAME ZOS)
# Specify the cross-compilers
: Tuesday, August 05, 2008 3:57 PM
To: cmake@cmake.org
Cc: Phil Smith
Subject: Re: [CMake] Cross-compiling for z/OS -- linker question
Hi,
On Tuesday 05 August 2008, Phil Smith wrote:
Next issue: linking. I have a toolchain file now that looks like
On Tuesday 05 August 2008, Phil Smith wrote:
Re the link command, thanks:
SET(CMAKE_C_LINK_EXECUTABLE c:/progra~1/dignus/linkit.bat -o
./TARGET OBJECTS) seems to be working much better!
As for the ForceCompiler stuff, I think I understand what you're getting
at, but am reluctant to
The CVS version does, yes.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Josef Karthauser
Sent: 30 November 2007 09:54
To: Jesse Corrington; Salvatore Iovene
Cc: cmake@cmake.org; [EMAIL PROTECTED]
Subject: RE: [CMake] cross compiling
Did I miss
1 - 100 of 110 matches
Mail list logo
