On Saturday 19 May 2012, Johannes Zarl wrote:
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
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
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
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
