Hi there:
I am new to cmake and I am using Kdevelop, actually , I am new to linux.
In my project, there are some ice slice files which must be custom parsed
and generate some cpp/h files.
So I use the command below to tell cmake to call slice2cpp to generate the
cpp/h files.
But every times I
On 5. May, 2010, at 10:20 , suds wrote:
Hi there:
I am new to cmake and I am using Kdevelop, actually , I am new to linux.
In my project, there are some ice slice files which must be custom parsed
and generate some cpp/h files.
So I use the command below to tell cmake to call slice2cpp to
On 5/4/2010 6:26 PM, Rene Salmon wrote:
Set environment variables to choose your compiler:
$ rm -rf build
$ mkdir build
$ cd build
$ export CC=xlc CXX=xlC FC=xlf
$ cmake ..
OK. That works. Thanks. But I guess that brings up another question.
I have this in my CMakeLists.txt
Hi,
CMake was not really designed to do that. The idea of a cross platform
build system is that it should not force a compiler choice from the
build files. CMake has an order of picking compilers, if there is more
than one on the system, it is going to pick the wrong one some of the
On 5/5/2010 9:19 AM, Rene Salmon wrote:
Excellent point. I thought about that right after I hit send to my email.
The whole reason we are looking at Cmake is so that we give our users more
flexibility for building our software and not the other way around. I will
remove those lines from the
On 05/04/2010 07:19 PM, Mike Ladwig wrote:
The clean build tree seems to have been the problem. Looks as if I needed
to start clean every time I tried a new configuration approach. Much
thanks!
Typically, if FIND_PACKAGE() succeeds in locating a package the results
are cached, and if you
No, no way to hint, they can specify that on the command line.
cmake -DCMAKE_CXX_COMPILER=CC
The environment vars do not be around during the build, only the first
time that you run cmake.
So, you can do this:
CXX=CC cmake ../source
Ok Thanks.
Rene
Usually you can get away with deleting just the cached variables that a find
module create (i.e. ZLIB_LIBRARY, etc.). Boost is one of the few modules
where this doesn't always work because it creates internal cached variables
that don't show up in the cache editor.
On Wed, May 5, 2010 at 9:57
Hello cmakers!
I am developing a C++ library and I am testing CMake with Cpack with the
bundle generator for mac osx (BTW, great work! Very easy to use!). I have
successfully generated a .dmg that has a .pkg. I managed to install the
libraries and headers that are included with my library.
Hi, I'm new to cmake.
I asked at #cmake how to prefix a string to a list of paths.
I got the reply that I should use a foreach loop which worked.
Can I abstract this pattern using a macro such as this?
# prefix and suffix each element of list by ${prefix}elemnt${suffix}
macro(PREFIXSUFFIX
Rene Salmon wrote:
The above seems to somewhat work with ccmake as I can do a configure and
then a generate. I guess it does not work with cmake. How do I pick
compilers using the CMakeLists.txt file rather than setting environment
variables.
FYI, CMake is designed to let users choose their
Hi,
On 5/5/10 4:00 PM, David Ojeda wrote:
Hello cmakers!
I am developing a C++ library and I am testing CMake with Cpack with the
bundle generator for mac osx (BTW, great work! Very easy to use!). I
have successfully generated a .dmg that has a .pkg. I managed to install
the libraries and
On 5. May, 2010, at 16:14 , Marc Weber wrote:
Hi, I'm new to cmake.
I asked at #cmake how to prefix a string to a list of paths.
I got the reply that I should use a foreach loop which worked.
Can I abstract this pattern using a macro such as this?
# prefix and suffix each element
On 2010-05-05 10:22, Michael Wild wrote:
# prefix and suffix elements
foreach(l ${list_name})
list(APPEND ${list_name}_TMP ${prefix}${l}${suffix} )
endforeach()
You also have an error in your foreach, it should be:
foreach(l ${${list_name}})
--
Ben.
On 5. May, 2010, at 16:29 , Benoit Thomas wrote:
On 2010-05-05 10:22, Michael Wild wrote:
# prefix and suffix elements
foreach(l ${list_name})
list(APPEND ${list_name}_TMP ${prefix}${l}${suffix} )
endforeach()
You also have an error in your foreach, it should be:
On 5. May, 2010, at 16:22 , Werner Smekal wrote:
Hi,
On 5/5/10 4:00 PM, David Ojeda wrote:
Hello cmakers!
I am developing a C++ library and I am testing CMake with Cpack with the
bundle generator for mac osx (BTW, great work! Very easy to use!). I
have successfully generated a .dmg
I tried just listing the single step, and for some reason (probably my
fault) it didn't work.
I did get this working, but I had to add two things to keep tcl and tk
from breaking fixup_bundle -- I had to make the Tcl/Tk SO libraries
writable, and I needed to delete tclsh and wish, because
On 05/05/2010 04:00 PM, Philip Lowman wrote:
Usually you can get away with deleting just the cached variables that a find
module create (i.e. ZLIB_LIBRARY, etc.). Boost is one of the few modules
where this doesn't always work because it creates internal cached variables
that don't show up in
foreach(l IN LISTS ${list_name})
I got that lesson now - Thanks to you all. Everything works as expected.
Marc Weber
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please
As stated in my previous post, I have a script, named runTest.cmake, which
works on linux but fails on Windows with:
The process cannot access the file because it is being used by another
process
This script calls execute_process() with an executable to capture the output
for a comparison
On Tue, May 4, 2010 at 5:47 PM, Bill Hoffman bill.hoffman at
kitware.com wrote:
On 4/22/2010 3:47 PM, Gustavo Sverzut Barbieri wrote:
As we never attempted to do any sort of CMake generator, not even
looking the existing, I'd like to know the expected effort to write
one for Tup from you guys.
On 5/5/2010 3:39 PM, Mike Shal wrote:
On Tue, May 4, 2010 at 5:47 PM, Bill Hoffmanbill.hoffman at
kitware.com wrote:
On 4/22/2010 3:47 PM, Gustavo Sverzut Barbieri wrote:
As we never attempted to do any sort of CMake generator, not even
looking the existing, I'd like to know the expected
On Wed, 05 May 2010 16:08:14 -0400, Bill Hoffman bill.hoff...@kitware.com
wrote:
Not sure yet, perhaps none of it. It would have to build custom
commands and targets. Basically, support for code generators like
swig/moc/lex/yacc. I guess the auto-depend stuff in tup would work for
Hello,
I used to build my own CMake binaries under Linux and Windows, but I got
tired of having to install compatible versions of third-party libraries
such as Qt, so I've been downloading the prebuilt binaries instead. On
the Linux side, I gave up on Red Hat/EPEL and RPMforge distributions,
On Wed, May 5, 2010 at 4:41 PM, Eskandar Ensafi ens...@spacecomputer.comwrote:
Is there any good reason why 64-bit binaries are not provided for all
supported operating systems?
Is constrained resources a good reason...?
:-)
___
Powered by
Well it turns out the problem was in the execute_process script. I had the :
OUTPUT_FILE ${TEST_OUTPUT}
ERROR_FILE ${TEST_OUTPUT}
both going to one file - Windows couldn't handle that. Changing that allowed
the command to actually execute,
NOW, I have to deal with the CRLF issue
On 5/5/10 3:41 PM, Eskandar Ensafi wrote:
Hello,
I used to build my own CMake binaries under Linux and Windows, but I
got tired of having to install compatible versions of third-party
libraries such as Qt, so I've been downloading the prebuilt binaries
instead. On the Linux side, I gave up
On 5/5/10, Bill Hoffman bill.hoff...@kitware.com wrote:
On 5/5/2010 3:39 PM, Mike Shal wrote:
On Tue, May 4, 2010 at 5:47 PM, Bill Hoffmanbill.hoffman at
kitware.com wrote:
On 4/22/2010 3:47 PM, Gustavo Sverzut Barbieri wrote:
As we never attempted to do any sort of CMake
On 5/5/10, Jed Brown j...@59a2.org wrote:
Having just experimented with tup recently, test suites are a potential
issue. As I understand it, tup will always build everything rather than
stopping, for example, with the shared library or a select executable.
It would be a problem if
Thank you very much, Michael. It works
-邮件原件-
发件人: Michael Wild [mailto:them...@gmail.com]
发送时间: 2010年5月5日 20:06
收件人: suds
抄送: cmake@cmake.org
主题: Re: [CMake] I can use add_custom_command in cmake
On 5. May, 2010, at 10:20 , suds wrote:
Hi there:
I am new to cmake and I am using
I am using ExternalProject_add on windows 7 and I am having difficulty
passing in some arguments. I have mocked up an example showing my
problem. To summarise:
When I pass a path e.g. D:/somehere/cool through with the CMAKE_ARGS
args I get out just D:.
has anyone else come across this?
I tried to run linux binary but always get the following message:
Error running cmake::LoadCache(). Aborting.
Exactly how are you installing the binary?
I simply downloaded the binary files and ran ccmake. Did I miss
anything else before running ccmake?
Thanks,
Zhuang
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via ea62d6973b657041021f00c67726cf476acd2424 (commit)
from
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 0457d5315166892d6975ddf9829db7ecffb0499c (commit)
from
34 matches
Mail list logo
