Hi,
I think it would be more usefull if the Module section in the cmake(1) man page
would be sorted.
ck
--- cmake-2.4.5/Source/kwsys/Directory.cxx.org 2006-12-04 17:04:05.0 +0100
+++ cmake-2.4.5/Source/kwsys/Directory.cxx 2007-01-10 22:47:44.0 +0100
@@ -139,6 +139,10 @@
this
Hi,
I would like to execute a command exactly one time during each build for
any, some or all targets, it this possible in an easy way?
I fiddled with the ADD_CUSTOM_TARGET and ADD_CUSTOM_COMMAND commands but was
unable to do so.
For instance when I used ADD_CUSTOM_TARGET(dummy ALL echo FOO), th
On Wednesday 10 January 2007 20:22, Bill Hoffman wrote:
> Claus Klein wrote:
> >
> > thanks for quick anser.
> >
> > If it works with:
> > cmake -DSIZEOF_SIZE_T=4 ..
> > it is ok for me.
> >
> > But my real intention is:
> >
> > It ist possible to prevent test which use TRY_RUN()?
> >
> > That was
Claus Klein wrote:
thanks for quick anser.
If it works with:
cmake -DSIZEOF_SIZE_T=4 ..
it is ok for me.
But my real intention is:
It ist possible to prevent test which use TRY_RUN()?
That was the most often problem with configure, why continue this with cmake?
While crosscompiling, sure!
On Wednesday 10 January 2007 17:00, Bill Hoffman wrote:
> Claus Klein wrote:
> > Hallo,
> >
> > the following Modules use TRY_RUN, which must fail while crosscompile:
> >
> > CheckTypeSize.cmake:TRY_RUN(${VARIABLE} HAVE_${VARIABLE}
> > FindThreads.cmake:TRY_RUN(THREADS_PTHREAD_ARG
> >
Claus Klein wrote:
Hallo,
the following Modules use TRY_RUN, which must fail while crosscompile:
[EMAIL PROTECTED]:~/downloads/cmake-2.4.5/Modules> grep TRY_RUN *.cmake
# OK CheckCSourceRuns.cmake:TRY_RUN(${VAR} ${VAR}_COMPILED
# OK CheckCXXSourceRuns.cmake:TRY_RUN(${VAR} ${VAR}_COMPILE
Hallo,
the following Modules use TRY_RUN, which must fail while crosscompile:
[EMAIL PROTECTED]:~/downloads/cmake-2.4.5/Modules> grep TRY_RUN *.cmake
# OK CheckCSourceRuns.cmake:TRY_RUN(${VAR} ${VAR}_COMPILED
# OK CheckCXXSourceRuns.cmake:TRY_RUN(${VAR} ${VAR}_COMPILED
CheckTypeSize.cmake
David Cole wrote:
CMake uses the "language" of the source files compiled for an
executable to determine what variable to use for the link stage... So,
in the normal C++ case, CMAKE_CXX_LINK_EXECUTABLE would be used.
In the general case, where an executable is built solely with
"language" sour
Hello David,
thank you for your explanation. I have gone for the
SET(CMAKE_RC_LINK_EXECUTABLE "${CMAKE_CXX_LINK_EXECUTABLE}")
solution, which works nicely.
Best regards,
Gerhard
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/li
CMake uses the "language" of the source files compiled for an executable to
determine what variable to use for the link stage... So, in the normal C++
case, CMAKE_CXX_LINK_EXECUTABLE would be used.
In the general case, where an executable is built solely with "language"
source files, the variable
Hello there,
using CMake 2.4.5 on Windows, I'm trying to build a resource-only executable
(required for Windows Installer setup authoring).
My source directory contains an icon resource "test.ico", a resource script
"test.rc" and a "CMakeLists.txt" file:
--
Hello everybody,
I have a project which I need to build either with Visual Studio 6 or nmake.
Unfortunately there are two dynamic libs which depend on each other. I know
that this is not good, but I have to live with it at the moment.
My question: I there a way in cmake to create the two lib-
Hi,
now that I've got my cont. build basically working, it seems the warning
exceptions as defined in ${CMAKE_SOURCE_DIR}/CTestCustom.ctest are ignored
(it's an in-source build).
Looking at the code I found that there is also CTestCustom.cmake.
Which one is used in which case ?
Do I have to expl
13 matches
Mail list logo
