Hi,
I'm using CMake 2.8.10.2 with the "Unix Makefiles" generator on Windows
and cross-compiling for Linux using GCC. I have Cygwin in the path for
make/sh/etc.
To cross compile I have the following items set:
CMAKE_SYSTEM_NAME:STRING=Linux
CMAKE_CXX_COMPILER:STRING=
CMAKE_C_COMPILER:STRING=
Th
On Tuesday 05 February 2013, David Narvaez wrote:
> On Tue, Feb 5, 2013 at 3:29 PM, Alexander Neundorf
>
> wrote:
> > What exactly are you building ?
> > Is LIB_INSTALL_DIR preset somewhere ?
>
> The software in question is GammaRay, see
>
> https://github.com/KDAB/GammaRay/blob/master/CMakeLis
On Tue, Feb 5, 2013 at 3:29 PM, Alexander Neundorf
wrote:
> What exactly are you building ?
> Is LIB_INSTALL_DIR preset somewhere ?
The software in question is GammaRay, see
https://github.com/KDAB/GammaRay/blob/master/CMakeLists.txt#L124
where it sets the LIB_INSTALL_DIR variable (thus avoidin
On Tuesday 05 February 2013, David Narvaez wrote:
> On Tue, Feb 5, 2013 at 1:15 PM, Alexander Neundorf
>
> wrote:
> > I know this was the case at some point in I think the frameworks branch
> > of kdelibs, but this was wrong, and I think it has been fixed.
> > Or where did you see this ?
>
> I'm
-Original Message-
From: Alexander Neundorf
To: David Cole
Cc: cmake
Sent: Tue, Feb 5, 2013 2:50 pm
Subject: Re: [CMake] When should I use add_subdirectory and when
ExternalProject?
On Tuesday 05 February 2013, David Cole wrote:
> -Original Message-
> From: Alexander
On Tue, Feb 5, 2013 at 1:15 PM, Alexander Neundorf
wrote:
> I know this was the case at some point in I think the frameworks branch of
> kdelibs, but this was wrong, and I think it has been fixed.
> Or where did you see this ?
I'm currently using KDE 4.10 RC 2 and, as far as I understand (I'm not
On Tuesday 05 February 2013, David Cole wrote:
> -Original Message-
> From: Alexander Neundorf
> To: cmake
> Sent: Tue, Feb 5, 2013 1:09 pm
> Subject: Re: [CMake] When should I use add_subdirectory and when
> ExternalProject?
>
> On Monday 04 February 2013, David Cole wrote:
> > The Open
That's it. Thank you very much Alex :-)
D.
--
View this message in context:
http://cmake.3232098.n2.nabble.com/Compatibility-between-cmake-based-directives-and-autoconf-based-directives-tp7583105p7583121.html
Sent from the CMake mailing list archive at Nabble.com.
--
Powered by www.kitware.com
-Original Message-
From: Alexander Neundorf
To: cmake
Sent: Tue, Feb 5, 2013 1:09 pm
Subject: Re: [CMake] When should I use add_subdirectory and when
ExternalProject?
On Monday 04 February 2013, David Cole wrote:
> The OpenChemistry project ( https://github.com/OpenChemistry/
Hi Alex,
You could probably pass the CMAKE_INSTALL_PREFIX option.
For example:
https://github.com/Slicer/Slicer/blob/master/SuperBuild/External_DCMTK.cmake#L44
Hth
Jc
On Tue, Feb 5, 2013 at 1:10 PM, Alexander Neundorf
wrote:
> On Monday 04 February 2013, David Cole wrote:
> > The OpenChemistry
On Tuesday 05 February 2013, DRypl wrote:
> Is there a way how to avoid problems with different declarations of
> directives depending whether
> using autoconf (for a library) and cmake (for my application using that
> library). For example autoconf
> declares "#define HAVE_UNISTD_H 1" while cmake
On Tuesday 05 February 2013, David Narvaez wrote:
> Hi all,
>
> I found code that sets LIB_INSTALL_DIR to a relative path ("lib" or
> "lib64"), then later calls FindKDE4Internal.cmake where
> CMAKE_INSTALL_RPATH is set to LIB_INSTALL_DIR and ultimatelysets the
> rpath of a library to something con
On Monday 04 February 2013, David Cole wrote:
> The OpenChemistry project ( https://github.com/OpenChemistry/openchemistry
> ) is a very good example of a SuperBuild project that builds all of its
> external dependencies via ExternalProject, and then all of its git
> submodules ("internal dependenc
Hi,
does anybody know the new release date for CMake 2.8.11?
In Mantis the date was scheduled for 2013-01-30.
Thanks in advance
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check t
Few pointers talking about the issue:
- http://yourmacguy.wordpress.com/2009/08/24/boot-snow-leopard-64-bit/
- http://arstechnica.com/apple/2009/08/mac-os-x-10-6/5/
Hth
Jc
On Tue, Feb 5, 2013 at 11:00 AM, Sean McBride wrote:
> On Tue, 5 Feb 2013 09:22:35 -0600, Kent Williams said:
>
> >And
On Tue, 5 Feb 2013 09:22:35 -0600, Kent Williams said:
>And the reason it says i386 is that CPACK_SYSTEM_NAME defaults to the
>output of uname -p which on OS X 10.7.5 is 'i386'
>
>So CMake is behaving as documented, and OS X is wrong ;-) Quelle Surprise!
OS X returns 'i386' for 'uname -p' deliber
Hi all,
I've been fighting against this error for the last two hours.
When I try to setup a cmake-based project which builds some protobuf
related stuff, something strange happens.
My sample cmake directives follow:
find_package(Protobuf REQUIRED)
include_direc
I meant that when I build cmake and then ran 'make package' it cmake out
i386, even though by default it only generates 64-bit binaries.
Jean-Christophe pointed out that on Kitware's builds they override this
with a better CPACK_SYSTEM_NAME.
And the reason it says i386 is that CPACK_SYSTEM_NAME d
What do you mean by "it's wrong"?
It's a universal binary with x86_64 being one of them.
On Feb 5, 2013, at 10:04 AM, Jean-Christophe Fillion-Robin
wrote:
> Hi Kent,
>
> Probably because the CPACK_SYSTEM_NAME is explicitly specified. See
> http://cmake.org/gitweb?p=cmake.git;a=blob;f=Utili
Hi Kent,
Probably because the CPACK_SYSTEM_NAME is explicitly specified. See
http://cmake.org/gitweb?p=cmake.git;a=blob;f=Utilities/Release/dashmacmini5_release.cmake;h=36b095287e80d26ed1b684b6c1a69d9bda1963ba;hb=HEAD#l19
Hth
Jc
On Tue, Feb 5, 2013 at 9:47 AM, Kent Williams wrote:
> Building o
Building on OS X 10.7.5 with XCode 4.5.2
Compiling with default compiler Apple clang version 4.1
(tags/Apple/clang-421.11.66)
The packages available for download on cmake.org are named
http://www.cmake.org/files/v2.8/cmake-2.8.10.2-Darwin64-universal.dmg
My question is this: how is the architectu
I was looking for documentation in the CMake manual for
CMAKE_OSX_ARCHITECTURES. This is a list of architectures, the possible
choices are:
i386;x86_64;ppc;ppc64
But this is not mentioned in the CMake documentation. Shouldn't it be?
--
Powered by www.kitware.com
Visit other Kitware open-sourc
Hi,
when i run cpack, then it breaks after the first error.
Is there a way (For NMake for example) to run "nmake /I" to ignore exit codes
and build as much as possible?
Thanks in advance
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensour
Is there a way how to avoid problems with different declarations of
directives depending whether
using autoconf (for a library) and cmake (for my application using that
library). For example autoconf
declares "#define HAVE_UNISTD_H 1" while cmake declares "#define
HAVE_UNISTD_H".
Using #cmakedefine
Hi all,
I found code that sets LIB_INSTALL_DIR to a relative path ("lib" or
"lib64"), then later calls FindKDE4Internal.cmake where
CMAKE_INSTALL_RPATH is set to LIB_INSTALL_DIR and ultimatelysets the
rpath of a library to something containing the relative path "lib".
Was that relative path meant
Hey there,
I am working on a project with CMake and OpenCV (CUDA and QT too, but that
is another story).
I am trying to get the "FIND_PACKAGE (OpenCV REQUIRED)" line working, but
unfortunately this line is not exactly working.
Although I pointed "OpenCV_DIR" to "H:/opencv/build/x86/vc10/lib"
(man
26 matches
Mail list logo
