On Thursday 10 April 2008, Pau Garcia i Quiles wrote:
...
> >> Is there any description which variables with what meaning have to be
> >> adjusted?
> >
> > Yes (at least in the book, I guess also in the wiki).
>
> http://www.cmake.org/Wiki/CMake_Cross_Compiling is the place to go
Without looking a
Quoting Alexander Neundorf <[EMAIL PROTECTED]>:
On Wednesday 09 April 2008, Hendrik Sattler wrote:
Hi,
I would like to make CMake work with an embedded cross-compiler, namely
nc30.
What compiler is that ?
Google on nc30 gives this: http://www.v-four.freeserve.co.uk/vfr400.htm
I guess he me
On Wednesday 09 April 2008, Hendrik Sattler wrote:
> Hi,
>
> I would like to make CMake work with an embedded cross-compiler, namely
> nc30.
What compiler is that ?
Google on nc30 gives this: http://www.v-four.freeserve.co.uk/vfr400.htm
> Is there any description which variables with what meanin
Hi,
I would like to make CMake work with an embedded cross-compiler, namely nc30.
Is there any description which variables with what meaning have to be
adjusted?
Problems with that compiler is that the created files do not have standard
names and there is no option to change that.
Thanks for a
Alexander Neundorf wrote:
On Wednesday 09 April 2008, Andreas Pakulat wrote:
On 09.04.08 10:48:30, Mike Arthur wrote:
On Wednesday 09 April 2008 10:37:39 Andreas Pakulat wrote:
Thats because qmake is in the PATH on unix usually, I think it works
autoamtically on windows too if the Qt/bin path
On Wednesday 09 April 2008, Andreas Pakulat wrote:
> On 09.04.08 10:48:30, Mike Arthur wrote:
> > On Wednesday 09 April 2008 10:37:39 Andreas Pakulat wrote:
> > > Thats because qmake is in the PATH on unix usually, I think it works
> > > autoamtically on windows too if the Qt/bin path is listed in
Jean Lepropre wrote:
Hi Bill,
Is it the same thing if static lib is built by CMake?
No, if CMake is building the library as part of the project, you link it
by the target name of the library.
Like this:
add_library(bar STATIC ...)
add_executable(foo ...)
target_link_libraries(foo bar)
CMak
Hi Bill,
Is it the same thing if static lib is built by CMake?
Cheers,
Jean.
Message: 2
Date: Wed, 09 Apr 2008 08:35:17 -0400
From: Bill Hoffman <[EMAIL PROTECTED]>
Subject: Re: [CMake] Relinking static libs
To: Ilya Shvetsov <[EMAIL PROTECTED]>
Cc: "cmake@cmake.org"
Message-ID: <[EMAIL PROTEC
You must use a FULL path to the library or CMake will not know what
depend information to add. If you have:
add_executable(foo foo.c)
link_directories(foobar)
target_link_libraries(foo A B C)
And A, B and C are libraries in the foobar directory that are not built
by CMake, then there will be
Markus Israelsson wrote:
Hello,
Bear with me, I am new to this list.
I am currently working on generating CPack configuration files through
CMake. I am using NSIS to generate an installer for windows through
CPack. Apart from the fact that I am relatively new to cmake and cpack
it is all g
Hello,
Bear with me, I am new to this list.
I am currently working on generating CPack configuration files through
CMake. I am using NSIS to generate an installer for windows through
CPack. Apart from the fact that I am relatively new to cmake and cpack
it is all going fine. I did run into a pr
Found a possible solution: VTK doesn't copy the VTKConfig.cmake during
installation. Maybe I should post this to the VTK mailinglist...
Matthias
Matthias Riechmann schrieb:
Hi everbody,
it is possible to use a installed version of VTK 5.0 via findVTK? At the
moment I set the VTK_DIR to C
Ilya Shvetsov wrote:
On Wed, 09 Apr 2008 10:55:35 +0300, Jean Lepropre
<[EMAIL PROTECTED]> wrote:
Hi,
I have a somewhat strange problem when linking with static libraries. I
have an executable that
links to a static library. If I modify only a source (cpp) file of the
static lib, the lib is re
Hi everbody,
it is possible to use a installed version of VTK 5.0 via findVTK? At the
moment I set the VTK_DIR to C:\Programme\VTK\lib\vtk-5.0 because the
useVTK.cmake is located there but findVTK alsways calls
UseVTKConfig40.cmake which complains it cannot find any CMakeCache.txt
in the inst
> Von: Mike Arthur
> On Wednesday 09 April 2008 10:37:39 Andreas Pakulat wrote:
> > Thats because qmake is in the PATH on unix usually, I think it works
> > autoamtically on windows too if the Qt/bin path is listed in the PATH
> > environment variable.
> Is there any reason FindQT couldn't just loo
On 09.04.08 10:48:30, Mike Arthur wrote:
> On Wednesday 09 April 2008 10:37:39 Andreas Pakulat wrote:
> > Thats because qmake is in the PATH on unix usually, I think it works
> > autoamtically on windows too if the Qt/bin path is listed in the PATH
> > environment variable.
> Is there any reason Fi
On 08.04.08 16:43:30, Doug Gregor wrote:
> On Tue, Apr 8, 2008 at 5:54 AM, Andreas Pakulat <[EMAIL PROTECTED]> wrote:
> > New version uploaded.
>
> I've looked through this module a bit, and it looks like it's in great
> shape. I have a few suggestions, implemented in the attached
> FindBoost.cma
On Wednesday 09 April 2008 10:37:39 Andreas Pakulat wrote:
> Thats because qmake is in the PATH on unix usually, I think it works
> autoamtically on windows too if the Qt/bin path is listed in the PATH
> environment variable.
Is there any reason FindQT couldn't just look (by default) in the default
Hello,
I am trying to make cmake include file for libraries, so I can do for
example:
add_executable(exea a.cpp)
include(../somelib/include.cmake)
use_somelib(exea)
exea will now have proper compile flags and target_link_libraries
(as you can see, I have used the approach with target_link_li
On 09.04.08 10:56:18, Matthias Riechmann wrote:
> it seems to me that FindQT.cmake cannot properly detect the whereabouts
> of Qt on windows machines. After specifying the location of qmake.exe
> the rest of Qt is found by cmake. Using linux it works completely
> automatic.
Thats because qma
2008/4/9, Alin M Elena <[EMAIL PROTECTED]>:
> Hi,
>
> I have some questions about the cmake/cpack/macosx.
> I have read the manual of cpack/cmake +
> http://www.cmake.org/pipermail/cmake/2007-October/016890.html
> and I am still a little bit confused.
> The things are a little bit more complic
Hi everybody,
it seems to me that FindQT.cmake cannot properly detect the whereabouts
of Qt on windows machines. After specifying the location of qmake.exe
the rest of Qt is found by cmake. Using linux it works completely
automatic. I had a brief look into the file FindQT.cmake itself and it
Hi,
I have some questions about the cmake/cpack/macosx.
I have read the manual of cpack/cmake +
http://www.cmake.org/pipermail/cmake/2007-October/016890.html
and I am still a little bit confused.
The things are a little bit more complicated since I do not have access to a
macOSX and somebody else
On Wed, 09 Apr 2008 10:55:35 +0300, Jean Lepropre
<[EMAIL PROTECTED]> wrote:
Hi,
I have a somewhat strange problem when linking with static libraries. I
have an executable that
links to a static library. If I modify only a source (cpp) file of the
static lib, the lib is rebuilt and
reinstalled
Hi,
I have a somewhat strange problem when linking with static libraries. I
have an executable that
links to a static library. If I modify only a source (cpp) file of the
static lib, the lib is rebuilt and
reinstalled but the executable is not relinked to the static lib (so
changes are not refl
25 matches
Mail list logo
