2010/1/30 Iman Brouwer :
> I was also struggling to get cpack to install anywhere else but in /usr when
> creating a DEB package. The following worked for me:
>
> set( CMAKE_INSTALL_PREFIX /usr/local/or/where/ever/i/want )
> set(CPACK_SET_DESTDIR TRUE)
> include( CPack )
>
> Iman
>
> P.S. Make sure
Testing, testing 1, 2, 3
___
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 the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow
I ended up using a different approach based on ExternalProject:
include(ExternalProject)
ExternalProject_Add(c68kinc
DOWNLOAD_COMMAND ""
SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/c68k
CONFIGURE_COMMAND cmake
INSTALL_COMMAND ""
BINARY_DIR ${CMAKE_CURRENT_BINARY_DIR}/c68k
)
Settin
Hello All,
I'm a student new to cmake and I ran into a stump with compiling some code.
When I apply the cmake_policy as instructed in a previous compiling error,
no executables are generated even when the output says otherwise.
-- Generating done
-- Build files have been written to: /home/mdtom
On Fri, Jan 29, 2010 at 4:07 PM, Brian Davis wrote:
> ExternalProject_Add does not like BINARY_DIR same for multiple packages...
> Why?
>
To avoid one package's output from clobbering another package's output. For
CMake built projects, for example, the BINARY_DIR is where CMakeCache.txt
ends up.
ExternalProject_Add does not like BINARY_DIR same for multiple packages...
Why?
SET( THIRD_PARTY_PACKAGES
vtk-5.4.2
dcmtk-3.5.4
boost-cmake-1_41_0
)
foreach( PACKAGE in ${THIRD_PARTY_PACKAGES} )
ExternalProject_Add(
${PACKAGE}
DOWNLOAD_COMMAND ""
SOURCE_DI
If target_link_libraries is given the full path to an external library, then
by default CMake uses rpath on Linux so that library is found at run time
for the build tree. For PLplot I have adjusted the RPATH options so that
the install-tree rpath is similarly well determined for all our external
On Thu, Jan 28, 2010 at 5:23 PM, Brian Davis wrote:
>
> Update: currently crying uncle ... and switching to ExternalProject_Add.
> CMake and the third party libs were simply not designed for this.
>
> Question on ExternalProject_Add above:
>
>
> ExternalProject_Add(
> DOWNLOAD_COMMAND ""
> CM
I was also struggling to get cpack to install anywhere else but in /usr when
creating a DEB package. The following worked for me:
set( CMAKE_INSTALL_PREFIX /usr/local/or/where/ever/i/want )
set(CPACK_SET_DESTDIR TRUE)
include( CPack )
Iman
P.S. Make sure you have 'include( CPack )' after you set
Hi all,
I just started to browse the CTest documentation, because I wanted to
get my hands dirty to setup a nightly builds for our project. I stumbled
upon a problem that might have an easy solution, but I couldn't find it
in the docs.
Most, if not all, of our tests are started by a bash script.
Zitat von Yegor Yefremov :
Alexander Neundorf wrote:
On Thursday 28 January 2010, Hendrik Sattler wrote:
Zitat von Yegor Yefremov :
are these two statements not doubled?
+#elif defined(__GNU__) && defined(__ELF__) && defined(__ARMEL__)
+# define ABI_ID "ELF ARM"
+#elif defined(__GNU__) && de
On Thu, 2010-01-28 at 09:05 -0500, John Drescher wrote:
> On Thu, Jan 28, 2010 at 3:28 AM, Marcel Loose wrote:
> > Hi all,
> >
> > For my project, I'm working on automatic 'svn update' of (parts of)
my
> > source tree, prior to building. I was wondering whether someone else
> > might be interested
Alexander Neundorf wrote:
> On Thursday 28 January 2010, Hendrik Sattler wrote:
>> Zitat von Yegor Yefremov :
>>> are these two statements not doubled?
>>>
>>> +#elif defined(__GNU__) && defined(__ELF__) && defined(__ARMEL__)
>>> +# define ABI_ID "ELF ARM"
>>> +#elif defined(__GNU__) && defined(__E
Am Donnerstag, den 28.01.2010, 11:40 +0100 schrieb Michael Wild:
> But you'll certainly want to have a look at the _POSTFIX target
> property or the _POSTFIX variable for setting a postfix (such as "d")
> depending on the configuration.
>
> Michael
>
Yes! This tip was very helpful and solves
14 matches
Mail list logo