Problem solved -- in what may have been an Emacs mishap, the entire
CMakeLists.txt got included twice. The post-2.4 CMake pickiness
caught the problem, but not knowing that I'd somehow duplicated the
entire contents of the file, I was faced with utterly baffling error
messages. I even thought when
>
> Don't do this on line 175: (just delete the line)
> BUILD_COMMAND ${CMAKE_BUILD_TOOL}
>
> Instead, just let cmake compute the BUILD_COMMAND for you...
>
> The default build command for ExternalProject_Add for cmake-built projects
> is something like:
> cmake --build . --config Release
>
>
>
It
Don't do this on line 175: (just delete the line)
BUILD_COMMAND ${CMAKE_BUILD_TOOL}
Instead, just let cmake compute the BUILD_COMMAND for you...
The default build command for ExternalProject_Add for cmake-built projects
is something like:
cmake --build . --config Release
HTH,
David
On Tue, Au
ental
Using HTTP submit method
Drop site:
http://subversion.sanjose.telcontar.com/cdash/submit.php?project=langlib
Uploaded:
/home/builduser/dds4.5.2/Common/langlib/build__/Testing/20100824-1715/Bu
ild.xml
Uploaded:
/home/builduser/dds4.5.2/Common/langlib/build__/Testing/20100824
Hi,
I'm using ExternalProject_Add to build a native-only part of my project.
When used with Visual Studio, the build step only opens a new Visual
Studio instance and doesn't automatically start building... in fact, it
doesn't even choose the solution file.
Is there any way to automatically open a
What is in the add_subdirectory call on line 139 of CMakeLists.txt?
CMakeLists.txt:139 (add_subdirectory):
On Tue, Aug 24, 2010 at 3:57 PM, kent williams wrote:
> I have a CMakeLists.txt file that builds a bunch of prerequisite
> library, and then my application I'm working on.
>
> This is
I have a CMakeLists.txt file that builds a bunch of prerequisite
library, and then my application I'm working on.
This is done all with External_Project macros. Once everything I need
is built, I build my code as an external project:
set(proj BRAINSTracerQT)
ExternalProject_Add(${proj}
URL fil
Thanks David. I'll stick to the add_test( NAME ... COMMAND ... ) syntax then.
I tried the script to force CTEST_CONFIGURATION_TYPE to be set, but it
didn't seem to do anything here. When I tried to debug it, the regular
'message(..)' command didn't seem to print, even with ctest -VV. Also,
when i
Hi Brad,
I have tested this version today, but the problem still exist!
Best regards,
Claus
On 23.08.2010, at 14:13, Brad King wrote:
On 08/21/2010 03:31 AM, Claus Klein wrote:
can you please check if this may related also to this BUG:
http://cmake.org/Bug/view.php?id=11153
It happens on W
On Tuesday 24 August 2010, norulez wrote:
> Hello,
>
> Is there a way to cleanup cdash? I mean to remove warnings and errors for
> the last 24 hours if these are corrected?
They will be removed with the next nightly build which has the fixes...
Alex
___
>
> The problem shows up between 2.6.4 and 2.8.0.
>
>
>
> *2.6.4:*
>
> Submit files (using http)
>
>Send to track: Experimental
>
>Using HTTP submit method
>
>Drop site:
> http://subversion.sanjose.telcontar.com/cdash/submit.php?proje
using http)
Send to track: Experimental
Using HTTP submit method
Drop site:
http://subversion.sanjose.telcontar.com/cdash/submit.php?project=langlib
Uploaded:
/home/builduser/dds4.5.2/Common/langlib/build__/Testing/20100824-1715/Bu
ild.xml
Uploaded:
/home/builduser/dds4.5.2/Comm
>. I guess those 32.lib libraries are 64 bit, even though the names suggest
>otherwise (yay for Microsoft).
>
I did not know that. Sorry. I admit, I have not looked at the lib
names on my 64 bit builds.
John
___
Powered by www.kitware.com
Visit other K
Ah, my mistake. The Microsoft Win 2003 SP1 x64 platform SDK has been installed
on the machine, and the LIB variable has been updated; 32.lib libraries are
now found in C:\Program Files\Microsoft Platform SDK\Lib\AMD64. I guess those
32.lib libraries are 64 bit, even though the names suggest othe
> True :)
>
> As I said, I'm just replicating the current Make system, in which those same
> 32 bit libs are used -- and it works. CMake even adds some extra 32 bit libs
> to the command line; I think they are added in Windows-icl.cmake
> (CMAKE_C_STANDARD_LIBRARIES_INIT). So I'd say it should a
On Tue, Aug 24, 2010 at 9:57 AM, Oenen, Jodi van
wrote:
> Hi,
>
> We are migrating an 'old' Make project into the CMake world, and I am
> encountering a problem during the link phase of one of our executables: the
> linker cannot open a boost library.
>
> I am using CMake 2.8.2 on WinXP x64, Boo
CoSMo Software is currently looking for collaborators to join the
team. We are seeking talented individuals right now!
About CoSMo
The CoSMo Company design and develop leading edge, high quality
software in the fields of complex systems. Our solutions can be
applied to systems biology modeling,
Hi,
We are migrating an 'old' Make project into the CMake world, and I am
encountering a problem during the link phase of one of our executables: the
linker cannot open a boost library.
I am using CMake 2.8.2 on WinXP x64, Boost regex library 1.33.1, with Intel
C++/Fortran 9.1 compilers (icl/i
Hello,
Is there a way to cleanup cdash? I mean to remove warnings and errors for the
last 24 hours if these are corrected?
Best Regards
NoRulez
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensour
I would be interested to learn how. Because of similar issues we got rid of a
shell script on Win64 because UnxUtil zsh.exe doesn't run from the 64bit
cmd.exe.
Also, when in a 64bit VS shell, I now need to run the 32bit nmake.exe because
otherwise my 32bit flex.exe will crash. I have tried dire
On 24. Aug, 2010, at 10:21 , Diablo 666 wrote:
>
> Hi,
>
> is there a way to use the CMAKE_*_POSTFIX variables for libraries which are
> not targets of the current project? I'd like to avoid the "optimized Foo
> debug FooD" construct. (Actually, linking against other targets of the
> current
Hi,
is there a way to use the CMAKE_*_POSTFIX variables for libraries which are not
targets of the current project? I'd like to avoid the "optimized Foo debug
FooD" construct. (Actually, linking against other targets of the current
project works well with only "Foo")
Best regards.
Andreas
22 matches
Mail list logo