Re: [CMake] How to find/run external host executables when using cross compiling

2013-12-09 Thread Eric Wing
On 12/4/13, Eric Wing wrote: > I'm currently trying to port a rather large, complex project to > Android. It has an existing CMake project so I'm trying to leverage > that. I've taken and enhanced one of the Android-CMake toolchains I've > found. > > This particular project I'm porting has unfortu

Re: [CMake] Windows XP + CMake + VS2013

2013-12-09 Thread Andrey Upadyshev
Hi Stefan, You should add CMake command option *-T vc120_xp* BR, Andrey Upadyshev On Sun, Dec 8, 2013 at 7:22 PM, Stefan Fendt wrote: > Hi, > > I'm using CMake 2.8.12 together with MSVC 2013 and need to produce a > binary which is (still) compatible with Windows XP SP3. > If I'm right, then I

[CMake] Building Matlab MEX files - a solution?

2013-12-09 Thread Williams, Norman K
I've been working on a project which requires building. After coming up with a brittle, overcomplicated way to use Matlab's MEX script to compile mex files, it occurred to me that I could simplify things by using the output of the MEX script. To that end, I wrote this. It seems to work great on Li

Re: [CMake] Proper behaviour and use of CMAKE_INSTALL_* variables

2013-12-09 Thread Mojca Miklavec
On Mon, Dec 9, 2013 at 4:52 PM, Andreas Pakulat wrote: > Hi, > > On Mon, Dec 9, 2013 at 3:50 PM, Mojca Miklavec wrote: >> >> Dear list members, >> >> I often like or need to install two versions of the same software. >> Ideally the software should put its files by default to >> $prefix/include/

Re: [CMake] Proper behaviour and use of CMAKE_INSTALL_* variables

2013-12-09 Thread Andreas Pakulat
Hi, On Mon, Dec 9, 2013 at 3:50 PM, Mojca Miklavec < mojca.miklavec.li...@gmail.com> wrote: > Dear list members, > > I often like or need to install two versions of the same software. > Ideally the software should put its files by default to > $prefix/include/$NAME/*.h > $prefix/lib/$NAME

[CMake] Proper behaviour and use of CMAKE_INSTALL_* variables

2013-12-09 Thread Mojca Miklavec
Dear list members, I often like or need to install two versions of the same software. Ideally the software should put its files by default to $prefix/include/$NAME/*.h $prefix/lib/$NAME/*.dylib ... ($prefix => $CMAKE_INSTALL_PREFIX) and in order to be able to install multiple versions

Re: [CMake] 32/64 bit flag - solved

2013-12-09 Thread pellegrini
On 12/9/2013 2:34 PM, Eric Noulard wrote: 2013/12/9 pellegrini : Thanks Eric for the hint. I read some time ago some stuffs about the CMAKE_SIZEOF_VOID_P variable but unfortunately, in the present case, the problem is a bit different. It can be for example that on a 64 bit machine, I would li

Re: [CMake] 32/64 bit flag

2013-12-09 Thread Eric Noulard
2013/12/9 pellegrini : >> >> > Thanks Eric for the hint. > I read some time ago some stuffs about the CMAKE_SIZEOF_VOID_P variable but > unfortunately, in the present case, > the problem is a bit different. It can be for example that on a 64 bit > machine, I would like to use the 32 bit > ifort ve

Re: [CMake] 32/64 bit flag

2013-12-09 Thread pellegrini
On 12/9/2013 1:26 PM, Eric Noulard wrote: 2013/12/9 pellegrini : Dear CMakers, I have to build cmake files for a Fortran project using ifort compiler on Windows, linux and macos platform. That project will be linked to Winteracter Fortran library whose installation paths are different depending

Re: [CMake] 32/64 bit flag

2013-12-09 Thread Eric Noulard
2013/12/9 pellegrini : > Dear CMakers, > > I have to build cmake files for a Fortran project using ifort compiler on > Windows, linux and macos platform. > That project will be linked to Winteracter Fortran library whose > installation paths are different depending on the 32 > or 64 bit versions. I

[CMake] 32/64 bit flag

2013-12-09 Thread pellegrini
Dear CMakers, I have to build cmake files for a Fortran project using ifort compiler on Windows, linux and macos platform. That project will be linked to Winteracter Fortran library whose installation paths are different depending on the 32 or 64 bit versions. Is there a way to automatically de

Re: [CMake] [CMAKE] Getting compilation date through CMake

2013-12-09 Thread Jon Haitz Legarreta
Thanks for the tip Jakub. BTW, I just realized that the [OUTPUT_STRIP_TRAILING_WHITESPACE] option of EXECUTE_PROCESS has the same effect of the regex I wrote to strip the trailing linebreaks. Regards, JON HAITZ On 9 December 2013 09:46, Jakub Zakrzewski wrote: > Hi, > I only wanted to warn

Re: [CMake] [CMAKE] Getting compilation date through CMake

2013-12-09 Thread Jakub Zakrzewski
Hi, I only wanted to warn you, that windows "date" command output is locale-specific, so you may get into trouble if you want to use it as anything else than a string literal. From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of Jon Haitz Legarreta Sent: Montag, 9. Dezemb

Re: [CMake] [CMAKE] Getting compilation date through CMake

2013-12-09 Thread Jon Haitz Legarreta
BTW, just for other newbies, I think my mistake was that I took another external command example literally: EXECUTE_PROCESS( COMMAND svnversion -nc "${sourceDir}" OUTPUT_VARIABLE _out_svnversion ) Now I guess the above works (without invoking the command prompt) because a FindSubversion.cma