Hi,
I add required libraries to my project with
TARGET_LINK_LIBRARIES(target /path/to/library)
I then generate Xcode projects, but they give me a warning that
/path/to/Debug (or /path/to/Release) doesn't exist in the linker flag
-L/path/to/{Debug,Release} (and fail because there are alongside
li
I have reproduced this by executing these two lines in a cygwin shell:
export PATH=/bin:$PATH
cmake --version
with cmake 2.4.7
It does not occur with cmake 2.4.3 or cmake 2.4.6
It probably occurs because cmake expects a directory structure of:
bin
doc
man
share
(There are no doc, man and share d
Wheeler, Frederick W (GE, Research) wrote:
David,
/bin is before /usr/bin in my path. My .bashrc file was created so
long ago, and changed so many times that it is impossible to know why
this is so.
I think there is something to all of this.
The other day on a Mac, with a PATH issue,
David,
/bin is before /usr/bin in my path. My .bashrc file was created so long
ago, and changed so many times that it is impossible to know why this is
so.
I think the bigger issue here is that it is not forbidden to put /bin
before /usr/bin in your path. For whatever reason, I'm sure a lot o
On 10/8/07, Wheeler, Frederick W (GE, Research) <[EMAIL PROTECTED]> wrote:
> CMake List:
>
> Amitha and I figured out that I can run cygwin cmake if and only if I
> use the full /usr/bin/cmake path. Neither /bin/cmake or cmake work.
> This is good enough for me. I just want to report this odd beh
H
Well my cygwin PATH starts with:
/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin
Why would the cmake in your "/bin" be chosen over the one in "/usr/bin"...?
What happens when you type:
which cmake
What is the value of your PATH environment variable and how did it get that
way...?
On 10
It looks like the exact same cmake is in both /bin and /usr/bin
% md5sum /bin/cmake.exe /usr/bin/cmake.exe
af465bc5ad9e6157a4898c476bfe62a3 */bin/cmake.exe
af465bc5ad9e6157a4898c476bfe62a3 */usr/bin/cmake.exe
This would be expected given how cygwin sets up these directories:
http://cygwin.co
Sounds like the cmake located at "/bin/cmake" is stale/old, but it's in your
path before the one from /usr/bin...
How did the one at "/bin/cmake" get there?
Maybe just deleting the cmake-related files under /bin and just using the
officially installed ones in /usr/bin is the solution?
On 10/8/0
Sylvain Benner wrote:
What about the debug/optimized flags for TARGET_LINK_LIBARIES()? Do
these work right now by taking advantage of the fact that Debug,
Release, MinSizeRel, and RelWithDebInfo are hardcoded?
We had to "upgrade" the cmTarget sources to add the new configuration
type and then
Does CMake allow for statements like
IF((var1 OR var2) AND (var3 OR var4))
or any similar syntax? When I try it in CMake 2.4.7, I get parse errors.
SET(istrue "yadda")
SET(isfalse "FALSE")
IF((istrue AND istrue) OR (isfalse AND isfalse))
MESSAGE("it works")
ELSE((istrue AND istrue) OR (isfalse
CMake List:
Amitha and I figured out that I can run cygwin cmake if and only if I
use the full /usr/bin/cmake path. Neither /bin/cmake or cmake work.
This is good enough for me. I just want to report this odd behavior.
Fred
% cmake --version
CMake Error: Could not find CMAKE_ROOT !!!
CMake ha
BTW you don't need the ARGS keyword in EXEC_PROGRAM,
ADD_CUSTOM_COMMAND, or ADD_CUSTOM_TARGET. It's correct but archaic.
ARGS is not needed with EXECUTE_PROCESS, not EXEC_PROGRAM ; )
--Sylvain
___
CMake mailing list
CMake@cmake.org
http://www.
In the mean time I'm doing,
EXEC_PROGRAM(${CMAKE_COMMAND} ${CONFIG_SUBDIR}/${CONFIG}
ARGS -G "NMake Makefiles" -DCMAKE_BUILD_TYPE=${CONFIG}
-DBUILD_SUBTREE=1
${CMAKE_HOME_DIRECTORY}
)
However that doesn't work because the double quotes aren't escaped. How
do I escape q
On 10/8/07, Josef Karthauser <[EMAIL PROTECTED]> wrote:
>
> EXEC_PROGRAM(${CMAKE_COMMAND} ${CONFIG_SUBDIR}/${CONFIG}
> ARGS -G "NMake Makefiles" -DCMAKE_BUILD_TYPE=${CONFIG}
> -DBUILD_SUBTREE=1
> ${CMAKE_HOME_DIRECTORY}
> )
>
> However that doesn't work because the double qu
However that doesn't work because the double quotes aren't escaped. How
do I escape quotes in cmake?
Like in any other strings -> \"
SET(foo "\"Hello\"") will set foo with the value "Hello".
--Sylvain
___
CMake mailing list
CMake@cmake.org
ht
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
Behalf
> Of Josef Karthauser
> Sent: 08 October 2007 16:36
> To: cmake@cmake.org
> Subject: [CMake] Calling cmake from within cmake.
>
> I want to recursively call cmake from a cmakelists.txt file to create
> bui
To whom it may concern:
Here is an example for building a Qt 3 widget as a lib (with CMake taking
care of all the moc and uic nonsense). You will only need the .ui file
(which you can create in the Qt Designer) and the following CMakeLists.txt:
# # # # # # # # # # # # # # # # # # # # # # # # # #
What about the debug/optimized flags for TARGET_LINK_LIBARIES()? Do
these work right now by taking advantage of the fact that Debug,
Release, MinSizeRel, and RelWithDebInfo are hardcoded?
Also, judging by code in cmLocalVisualStudio7Generator.cxx any custom
build solutions that you would adde
Josef Karthauser wrote:
>>> Is this a bug or a feature, does anyone know? If I rip out the
>> checks in cmGlobalVisualStudio7Generator:: GenerateConfigurations is
>> anything going to break?
>>>
>> If you rip out this I think you'll have an error with TRY_COMPILE. (be
>> aware to delete your CMake
I want to recursively call cmake from a cmakelists.txt file to create
build directories for other projects. I'm sure I saw something in the
docs that suggested a neat way of doing it that didn't involve executing
cmake explicitly as an external command, but I can't find it now I look
again. Can a
Paul Dean wrote:
Is it possible to exclude ALL_BUILD and ZERO_CHECK for the project?
It is technically possible to remove ALL_BUILD by hacking the c++. It
is not possible to
remove ZERO_CHECK as it provides functionality
I am trying to get CMake to run my CppUnit tests automatically after
building from within Visual Studio .NET 2003.
Looking at
http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_generate_an_executable.2C_t
hen_use_the_executable_to_generate_a_file.3F,
I thought this would do the trick (the example is sim
Is it possible to exclude ALL_BUILD and ZERO_CHECK for the project?
_
Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare!
http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews__
If I am understanding you correct, you would like a CMake file in
each of the subdirectories that lists the source files in that
subdirectory that should be included in the build? Try the following:
In your top level CMakeLists.txt file--
SET (PROJECT_SOURCE_DIR ${CMAKE_CURRENT_SOURC
My project is a shared library. I just moved the
project over to CMake from autotools. The sources for
the target is divided up into several
subdirectories(which also contain sources in
subdirectories). I need to be able to build all the
sources recursively and have them all linked into the
same ta
25 matches
Mail list logo
