On Oct 21, 2009, at 7:44 AM, Bill Hoffman wrote:
Bill Spotz wrote:
Hi,
I am a Trilinos developer, so I recently upgraded to CMake version
2.8
so that I could test the Trilinos release 10 tarball.
I am seeing certain unit tests fail that were working before (in the
Trilinos release 10 repos
The current CMake 2.8.0 system does not allow custom commands created with
add_custom_command() to do different things based on the build
configuration.
I propose adding a new keyword to the add_custom_command CMake directive
called CONFIG:
add_custom_command(OUTPUT output1 [output2 ...]
COMMA
2009/11/27 James C. Sutherland :
> Is there a way in CMake to determine the number of shared-memory cores on a
> system?
I don't know but I discover recently a tiny tool call hwloc
which may help for that:
http://www.open-mpi.org/projects/hwloc/
It is [unfortunately] using autotools :-) but cla
Classification: UNCLASSIFIED
Caveats: NONE
I am attempting to make a Find_Package command more user friendly but am
running into problems. The package I am trying to include in my project is
Xdmf.
Currently, a user must point to /lib/XdmfCMake in
order to successfully find XDMFConfig.cmake.
Is there a way in CMake to determine the number of shared-memory cores on a
system?
___
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 th
Dear all,
Two options in my project will influence the libraries/paths search: a
32/64 bits compilation switch and a static/shared third-party libraries
link switch. These options are stored in the cache so that the user can
modify them.
Modifying one of these cache variable should obviously inf
Hi Alan,
Thanks for your elaborate reply. I had taken a look at the work-around
scripts that were upload for issue #9220 by you and Greg. They look
quite rigorous. I've come up with a much simplier but probably less
robust work-around.
# Work-around for CMake issue 0009220
if(DEFINED CMAKE_Fortra
Dear cmake users,
I ma stuck with some dependencies problem and I can not figure out why
my cmake project behave like that :
make BaseDoxygen
-> 100% built
make BaseJar :
-> make[2]: *** No rule to make target « BaseDoxygen » ...
make[1]: ***
I do not understand how make succeed to make target
Hi Alex,
I've written a very small work-around for my problem.
I noted that 'enable_language(Fortran)' sets the compiler to
CMAKE_Fortran_COMPILER-NOTFOUND, whereas 'enable_language(Fortran
OPTIONAL) sets it to the empty string. So what I do now is check whether
CMAKE_Fortran_COMPILER is defined
I have to mention that implementing a patching facility in CMake would
probably be a considerable effort. Perhaps http://www.xmailserver.org/xdiff-lib.html
could be of use there. This library would also allow to implement '-
E diff', although I'm not sure whether that would be useful at all...
10 matches
Mail list logo