Hi all.
I am currently trying to create a more tidy CMakeLists.txt script for
a simulation code I'm working on. The target platforms are mac and
linux desktops (for development) and HPC [0] servers (all linux or, in
some hypothetical future, unix systems). On HPC servers, it is very
common to
Hi all.
I am currently trying to create a more tidy CMakeLists.txt script for
a simulation code I'm working on. The target platforms are mac and
linux desktops (for development) and HPC [0] servers (all linux or, in
some hypothetical future, unix systems). For the desktop/laptop case,
it's mostly
Am Samstag, 19. Mai 2012, 14:42:49 schrieb Paul Anton Letnes:
Hi all.
I am currently trying to create a more tidy CMakeLists.txt script for
a simulation code I'm working on. The target platforms are mac and
linux desktops (for development) and HPC [0] servers (all linux or, in
some
Greetings,
I am trying to compile lapack -3.4.1 with cmake.
lapack-3.4.1/TESTING/CMakeLists.txt has these lines at the end:-
#
execute_process(COMMAND ${CMAKE_COMMAND} -E copy
${LAPACK_SOURCE_DIR}/lapack_testing.py ${LAPACK_BINARY_DIR})
add_test(
NAME LAPACK_Test_Summary
2012/5/19 Rolf Eike Beer e...@sf-mail.de:
Am Samstag, 19. Mai 2012, 14:42:49 schrieb Paul Anton Letnes:
Hi all.
I am currently trying to create a more tidy CMakeLists.txt script for
a simulation code I'm working on. The target platforms are mac and
linux desktops (for development) and HPC
and other libraries I'm using (hdf5,
mkl, ...) share the same fate. Previously I've just hand-added all
sorts of include_directories and link_directories but I'm getting fed
link_directories() is surely not the solution you need. In fact, it
usually
creates only more problems.
I
Hi,
On Sat, May 19, 2012 at 3:44 PM, Rolf Eike Beer e...@sf-mail.de wrote:
But to have some useful information: set CMAKE_PREFIX_PATH to the path
where the libraries can be found without the lib/ or include/ suffix,
CMake will add them itself.
So if you have fftw2 in
On 2012-05-19 15:24+0100 luxInteg wrote:
Greetings,
I am trying to compile lapack -3.4.1 with cmake.
lapack-3.4.1/TESTING/CMakeLists.txt has these lines at the end:-
#
execute_process(COMMAND ${CMAKE_COMMAND} -E copy
${LAPACK_SOURCE_DIR}/lapack_testing.py
Hi,
I must in some case define a fresh set of include directories. AFAIK,
INCLUDE_DIRECTORIES either appends or prepends. How can I remove a
certain directory, or alternatively, query and clear the entries?
Thanks
Dominik
--
Powered by www.kitware.com
Visit other Kitware open-source projects
Sorry, I forgot to add, I need the same thing with link_directories.
Thanks
Dominik
On Sat, May 19, 2012 at 7:56 PM, Dominik Szczerba domi...@itis.ethz.ch wrote:
Hi,
I must in some case define a fresh set of include directories. AFAIK,
INCLUDE_DIRECTORIES either appends or prepends. How can
Hello Eric,
hello David,
sorry for the long response time.
I noticed that the custom CPackConfig is not necessary if I use variable names
beginning with CPACK_. So first I removed the custom file.
Then the main problem...
I don't use a changed NSIS.template.in file from the CMake installation.
Am Samstag, 19. Mai 2012, 20:01:55 schrieb Dominik Szczerba:
Sorry, I forgot to add, I need the same thing with link_directories.
That is easy. Don't use link_directories. Ever. Pass absolute paths to
target_link_libraries().
signature.asc
Description: This is a digitally signed message part.
CPack does a make install and puts your install tree underneath
_CPack_Packages.
THEN, it calls NSIS with the *.nsi script, and packages that up into an
installer.
There is nothing in the *.nsi file that copies anything into
_CPack_Packages. That happens before makensis is ever called.
Please
Sorry, but the project is a commercial application.
Did you mean this site? http://www.cmake.org/cmake/help/cmake_tutorial.html#s7
But there must something in the original *.nsi file, because if I use the
original file then the files get copied (Without changing the CMakeLists.txt
file)
On
Hello Paul,
I don't know about your specific find_package file for FFTW, but we do use
modules together with CMake, so I'll add my thoughts:
As Eric already said, the modules command alters your environment. CMake
doesn't know about shell modules, but most find_package commands provide some
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 120f2b3..6f45c4f 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -2,5 +2,5 @@
SET(CMake_VERSION_MAJOR 2)
SET(CMake_VERSION_MINOR 8)
SET(CMake_VERSION_PATCH 8)
-SET(CMake_VERSION_TWEAK 20120519
16 matches
Mail list logo