Alexander Neundorf schrieb:
...
So indeed a relative CMAKE_INSTALL_PREFIX is interpreted relative to the build
dir.
Do you think this should be handled differently ?
Then c:/usr would have to be translated at some point to /c:/usr if cross
compiling on some UNIX.
Would this make sense ?
On Thursday 07 January 2010, Claus Klein wrote:
Hi
i want to install a cross compiled (build host is a MAC OS X) project
to a temporary state dir to get an archive to distribute the binaries.
The target is win32 (mingw), compiled to be installed at c:/usr as
CMAKE_INSTALL_PREFIX.
This
Hi all,
now I got it:
There are 3 different problems:
1.) never use an absolute DESTINATION path with INSTALL commands!
###XXX### INSTALL( FILES cmake/FindLibSmi.cmake DESTINATION $
{CMAKE_ROOT}/Modules )
2.) never use an absolute source Path!
###XXX### INSTALL( FILES
On Fri, Jan 8, 2010 at 12:37 AM, Claus Klein claus.kl...@arcormail.dewrote:
On 08.01.2010, at 02:25, Alexander Neundorf wrote:
On Thursday 07 January 2010, Claus Klein wrote:
Hi
i want to install a cross compiled (build host is a MAC OS X) project
to a temporary state dir to get an
Hi David,
Yes, this works fine when I change the CMAKE_INSTALL_PREFIX at
CMakeCache.txt, sure.
There is only one fault: the config files will be rebuild with the
wrong path before install :-((
At least, I know 2 packages, NetSnmp and LibSmi, they has to be
compiled with fix absolute
On 08.01.2010, at 02:25, Alexander Neundorf wrote:
On Thursday 07 January 2010, Claus Klein wrote:
Hi
i want to install a cross compiled (build host is a MAC OS X) project
to a temporary state dir to get an archive to distribute the
binaries.
The target is win32 (mingw), compiled to be
Hi
i want to install a cross compiled (build host is a MAC OS X) project
to a temporary state dir to get an archive to distribute the binaries.
The target is win32 (mingw), compiled to be installed at c:/usr as
CMAKE_INSTALL_PREFIX.
This prefix is used while compile the binaries, so I can't
