Hi Rolf,
Can you update to a CMake based on 'next' and try the commit I made this
morning on a QNX machine? (based on your patch, thank you for that...)
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=680ca4baab85cbc1be98bcfd81b7e4402ffa8d84
We are supposed to have a continuous and a nightly
FYI:
The output that you see, both directly from ProcessorCount.cmake, and
indirectly from the tools that it calls to try to determine the processor
count, will be eliminated shortly (over the next few days)... but for now...
it is being left in for dashboard diagnostics so that I can see what is
Am Montag, 8. November 2010 schrieb David Cole:
Hi Rolf,
Can you update to a CMake based on 'next' and try the commit I made this
morning on a QNX machine? (based on your patch, thank you for that...)
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=680ca4baab85cbc1be98bcfd
Am Montag, 8. November 2010 schrieb David Cole:
Hi Rolf,
Can you update to a CMake based on 'next' and try the commit I made this
morning on a QNX machine? (based on your patch, thank you for that...)
Still needs some tweak, as the output is:
getconf: Can't find _NPROCESSORS_ONLN
On 11/8/2010 1:55 PM, Rolf Eike Beer wrote:
Am Montag, 8. November 2010 schrieb David Cole:
Hi Rolf,
Can you update to a CMake based on 'next' and try the commit I made this
morning on a QNX machine? (based on your patch, thank you for that...)
Still needs some tweak, as the output is:
Am Montag, 8. November 2010 schrieb David Cole:
I'm leaving that output in there on purpose to see what happens on all of
our dashboard machines. I will not eliminate this extraneous output until
later.
But, don't worry, this will not be merged to master until all the
extraneous output is
On 11/8/2010 3:30 PM, Rolf Eike Beer wrote:
Am Montag, 8. November 2010 schrieb Bill Hoffman:
On 11/8/2010 1:55 PM, Rolf Eike Beer wrote:
Am Montag, 8. November 2010 schrieb David Cole:
Hi Rolf,
Can you update to a CMake based on 'next' and try the commit I made this
morning on a QNX
1. cmake:mex problem
According to the webpage (http://www.cmake.org/Wiki/CMake:MatlabMex)
we can tell CMake (patched version) to treat the mex build script as the
project's compiler which can be done by the command (CC=mex CXX=mex cmake
/path/to/project/source).
For the examples they provided, it
Greetings,
I am learning cmake. I would like to know if there are ways to beautify the
compiler output when using cmake. In brioef how to seperate and label the
making
of libraries,
of documentation and
of executables
in clearly defined segments of the compiler spew.
advice would
-gergap.ascolab.com
Build name: Linux-
Determine Nightly Start Time
Specified time: 00:00:00 EDT
Create new tag: 20101108-0400 - Nightly
Updating the repository: /home/gergap/work/helloworld/src
Cannot find UpdateCommand configuration key.
Configure project
Each . represents 1024 bytes
Create new tag: 20101108-0400 - Nightly
Updating the repository: /home/gergap/work/helloworld/src
Cannot find UpdateCommand configuration key.
Configure project
Each . represents 1024 bytes of output
. Size of output: 0K
Build project
Each symbol represents 1024 bytes of output
Friday I upgraded my windows VS2008 and IVF111 machines to cmake 2.8.3. Over
the weekend they all failed to configure with fortran :
-- Check for working Fortran compiler using: Visual Studio 9 2008 -- broken
CMake Error at C:/Program Files/CMake
Hi,
in our company we have a robust cmake-based build system which utilizes TI DSP
cgtools compiler. Aside from that we are developing gcc-based unit tests
(CxxTest coupled with CMake/CTest/CDash combo). We are considering merging the
latter into the former, but we kind of don't even know how
When using ifort on windows I do the following
a) Make sure cmake is launched from inside a cmd prompt with the
ifort-vars.bat set so that the ifort compiler is on the path etc etc
b) always use nmake makefiles to do the initial configure and detection
c) once the project is
On Saturday 06 November 2010 23:08:29 Eric Noulard wrote:
I think you cannot use **the same** file properties on a source file
and expect CMake will compile the file twice for the same target.
If you want to compile the same source file twice with different compile
flags **FOR THE SAME
2010/11/8 luxInteg lux-in...@btconnect.com:
On Saturday 06 November 2010 23:08:29 Eric Noulard wrote:
I think you cannot use **the same** file properties on a source file
and expect CMake will compile the file twice for the same target.
If you want to compile the same source file twice with
This did work before the update - and reinstalling cmake 2.8.2 worked. BTW, I
uninstalled and deleted the CMake Program Files folder to make sure there was
no interference between versions. I now believe this to be a CMake 2.8.3
problem. I'll be glad to help debug this if someone can provide
-gergap.ascolab.com http://lt-gergap.ascolab.com
Build name: Linux-
Determine Nightly Start Time
Specified time: 00:00:00 EDT
Create new tag: 20101108-0400 - Nightly
Updating the repository: /home/gergap/work/helloworld/src
Cannot find UpdateCommand configuration key
On 11/8/2010 1:15 PM, Allen D Byrne wrote:
This did work before the update - and reinstalling cmake 2.8.2 worked. BTW, I
uninstalled and deleted the CMake Program Files folder to make sure there was
no interference between versions. I now believe this to be a CMake 2.8.3
problem. I'll be glad
On Monday 08 November 2010, Russell L. Carter wrote:
On 11/07/2010 01:49 AM, Michael Hertling wrote:
On 11/07/2010 02:07 AM, Russell L. Carter wrote:
Hi there,
Happy cmake user here. I want to retrieve the leaf name of
the directory property PARENT_DIRECTORY. This is really
a more
On Monday 08 November 2010, Wojciech Migda wrote:
Hi,
in our company we have a robust cmake-based build system which utilizes TI
DSP cgtools compiler. Aside from that we are developing gcc-based unit
tests (CxxTest coupled with CMake/CTest/CDash combo). We are considering
merging the latter
On 11/08/2010 12:59 PM, Alexander Neundorf wrote:
To get the last component of a path, use
get_filename_component(... NAME)
To get the parent directory, use
get_filename_component(... PATH)
When you need to generate a unique name from a path, you could use the
STRING() command to
Bill,
The projects do differ in the VFFortranCompilerTool option of the project
file
DEBUG:
AdditionalOptions= /W1 /libs:dll /threads /dbglibs instead of
AdditionalOptions= /dbglibs
RELEASE:
AdditionalOptions= /W1 /libs:dll /threads instead of
and
DEBUG:
RELEASE:
SuppressStartupBanner=true
Greetings,
I am a complete beginner to CMake, so my problem might be trivial.
Nevertheless I did not find a solution yet.
I am running Windows XP in a virtual machine on a linux host system.
Having CMake 2.6.4 installed I tried to run CMakeLists.txt from a
project I downloaded.
My problem
On Mon, Nov 8, 2010 at 4:09 PM, Stormwind Developer
stormwind@googlemail.com wrote:
Greetings,
I am a complete beginner to CMake, so my problem might be trivial.
Nevertheless I did not find a solution yet.
I am running Windows XP in a virtual machine on a linux host system. Having
CMake
Hi list,
I tried to add ctest to my project and did this by adding ENABLE_TESTING() and
several ADD_TEST(...) to my CMakeLists.txt file.
The tests are run on executables, which are built inside a dedicated test
directory in my project root and the execs show up in my Makefile.
After reading
On Monday 08 November 2010 18:10:01 Eric Noulard wrote:
2010/11/8 luxInteg lux-in...@btconnect.com:
On Saturday 06 November 2010 23:08:29 Eric Noulard wrote:
I think you cannot use **the same** file properties on a source file
and expect CMake will compile the file twice for the same
Am Montag, 8. November 2010 schrieb Stormwind Developer:
Greetings,
I am a complete beginner to CMake, so my problem might be trivial.
Nevertheless I did not find a solution yet.
I am running Windows XP in a virtual machine on a linux host system.
Having CMake 2.6.4 installed I tried to
On Nov 8, 2010, at 4:39 PM, Rolf Eike Beer wrote:
Am Montag, 8. November 2010 schrieb Stormwind Developer:
Greetings,
I am a complete beginner to CMake, so my problem might be trivial.
Nevertheless I did not find a solution yet.
I am running Windows XP in a virtual machine on a linux host
On 11/08/2010 10:03 PM, Jochen Issing wrote:
Hi list,
I tried to add ctest to my project and did this by adding ENABLE_TESTING()
and several ADD_TEST(...) to my CMakeLists.txt file.
The tests are run on executables, which are built inside a dedicated test
directory in my project root and
On 2010-11-09 02:52+0100 Michael Hertling wrote:
On 11/08/2010 10:03 PM, Jochen Issing wrote:
Hi list,
I tried to add ctest to my project and did this by adding ENABLE_TESTING() and
several ADD_TEST(...) to my CMakeLists.txt file.
The tests are run on executables, which are built inside a
On Monday 08 November 2010 22:21:54 luxInteg wrote:
---
set(RUN oddone.o file2.c file3.c )
LIST CONTAINS(file2.c file3.c ${RUN})
IF (contains )
(--compile file2.c and file3.c into oddone.o )
endif (contains)
-
advice on whether lists of othrwise is
2010/11/8 luxInteg lux-in...@btconnect.com:
If you manipulate list have a look at the CMake builtin LIST command.
I had a look at lists on this page
http://www.cmake.org/Wiki/CMakeMacroListOperations
You should reallty use **builtin** list
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, next has been updated
via 20ae1b5b8908f183b389361e76efc693af9af03e (commit)
via
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, next has been updated
via 9c6907c1d921cfd1f87cf0ece3fc85a901ef27d1 (commit)
via
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, next has been updated
via 78c1abde46641d7a02e19bd8b5f1e72f295dbf5d (commit)
via
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, next has been updated
via 9d841b5b8b47c378ee49eec0ce41e503d9cd05b3 (commit)
via
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 bbb3d81d383737f4111f7303b36c23c537aaf17a (commit)
from
38 matches
Mail list logo
