Asmodehn Shade wrote:
Using CMake 2.4.2 on NetBSD 4.0, my command line looks like :
Why don't you try updating to CMake 2.4.6?
Cheers,
Brandon Van Every
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Philip Lowman wrote:
> I gave some thought towards working on adding first-class RPM and DPKG
> support to CPack tonight. I was just wondering if anyone has toyed
> around with this idea as of late or if this is something that the CMake
> project would even be interested in adding. Obviously, I'm
I gave some thought towards working on adding first-class RPM and DPKG
support to CPack tonight. I was just wondering if anyone has toyed
around with this idea as of late or if this is something that the CMake
project would even be interested in adding. Obviously, I'm just talking
binary package
On 2007-03-14 19:50-0400 Jean-Sébastien Guay wrote:
I personally can't spot a major difference between the two (aside from -g
replaced by -O3 and NDEBUG being defined, which shouldn't prevent it from
linking).
I ran into a similar problem recently. I am no expert on NDEBUG, but from a
superf
Hi,
My tests for my project need to load dlls which are not in the
executable directory, but in the system path. I'm using Visual Studio 7.
I can run ctest from the command line but not using the RUN_TEST target
in Visual Studio. I found the following email from 2005 and was
wondering how peo
On 2007-03-05 12:20-0500 Bill Hoffman wrote:
Alan W. Irwin wrote:
Anyhow, with the gnatmake test, the first form of TRY_COMPILE is required,
and so far I have not been able to figure out how to avoid the infinite
TRY_COMPILE issue with that form. Thus, I would really appreciate an
answer for h
Hello,
I am new to CMake, and I imagine this must be caused by a newbie error
in the CMakeLists.txt files I'm using... My project compiles and links
fine in Debug, but in Release, it fails to link. The error I get is:
[ . snipped for brevity, only keeping errors . ]
/home/guayj/Cou
Thank you for the replies...
So I think for profiling I will
- 1) reorganise my CMakeLists.txt around so the flags are set in one place only
- 2) Add a variable to say wether or not to do some profiling, regardless of
the build type . I guess I could want to do some profiling in debug and in
rel
Bill Hoffman wrote:
Orion Poplawski wrote:
What are the issues that arise? In general with RPM packaging you
are starting with a clean freshly unpacked source tree.
It really depends on the project. There are no cmake imposed
limitations on this.
What happens in practice, is if someone'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Orion Poplawski wrote:
> Various projects using cmake state that they don't support in source
> tree builds. Is this a general case for cmake projects?
>
> We're working on packaging guidelines for cmake projects in Fedora.
> Draft is here: http://
Orion Poplawski wrote:
Various projects using cmake state that they don't support in source
tree builds. Is this a general case for cmake projects?
No, it is not a general case. CMake itself can be built either way.
We're working on packaging guidelines for cmake projects in Fedora.
Draft
Various projects using cmake state that they don't support in source
tree builds. Is this a general case for cmake projects?
We're working on packaging guidelines for cmake projects in Fedora.
Draft is here: http://fedoraproject.org/wiki/PackagingDrafts/cmake.
Currently this does an in source
Cristian Adam wrote:
I hope you will include it in the next build, so that others will benefit
from it. And, maybe scintilla and SciTE will be build using CMake ;-)
Thanks for that. I have been using SciTE lately. My experience has
been that I don't need pretty printing and so forth to wor
Hi,
I'm having problems using ADD_CUSTOM_COMMAND with filenames that share
the name but live in different paths:
MACRO(GENERATE_FROM_XML target xml)
ADD_CUSTOM_COMMAND(
OUTPUT ${CMAKE_CURRENT_SOURCE_DIR}/"${target}"
COMMAND ${JAVA_RUNTIME} ${SAXON} -o ${PROJECT_SOURCE_DIR}/${target}
14 matches
Mail list logo