On 12/28/2010 09:10 AM, edA-qa mort-ora-y wrote:
> On 12/27/2010 09:51 PM, Michael Hertling wrote:
>> You might use the ALL option of ADD_CUSTOM_TARGET() to incorporate the
>> language target in CMake's "all" target which, in turn, is built as a
>> prerequisite of the "install" target. Alternativel
Thanks, this works nicely
Sorry for the double posting.
I waited for 30 minutes and the mail didn't appear on the list, so I
assumed it failed somehow.
-mika
Michael Wild
Sent by: cmake-boun...@cmake.org
28.12.2010 16:23
To
cmake@cmake.org
cc
Subject
Re: [CMake] add_executable created
On Mon, Dec 27, 2010 at 03:56:20PM +0100, Wojciech Migda wrote:
> I'm trying to pass information from a script executed for dashboard
> submission (ctest -S) to the underlying CMakeLists.txt which is to be
> parsed by (internally called by ctest) cmake. In other words, I'd like
> to have a system w
Yep. It works with the nightly build.
Great.
/A
On Tue, Dec 28, 2010 at 6:14 PM, Bill Hoffman wrote:
> On 12/27/2010 10:25 AM, Bill Hoffman wrote:
>
>> On 12/27/2010 10:03 AM, Anders Backman wrote:
>>
>>> Seems to be bug in CMake!
>>>
>>> I reduce the solution down to 1 project. Still fails. So
On 12/27/2010 10:25 AM, Bill Hoffman wrote:
On 12/27/2010 10:03 AM, Anders Backman wrote:
Seems to be bug in CMake!
I reduce the solution down to 1 project. Still fails. So I copied the
generated .sln file into agx.cmake.sln
More helpful would be a minimal CMakeLists.txt and instructions on h
On Fri, Dec 24, 2010 at 04:19:16AM +, luxInteg wrote:
> in an execute_process() function with ${ECHO} (/bin/echo)what does one
> set for WORKING_DIRECTORY?
1. I would use ${CMAKE_COMMAND} -E echo rather than /bin/echo.
2. I would not set WORKING_DIRECTORY unless I needed it for some rea
On Dec 28, 2010, at 9:45 AM, Micha Renner wrote:
>
>> Just a small piece of feedback. All the other Visual Studio generators are
>> "in order", ie, VS 6, VS 7, VS 8, VS 9 so it made sense to look for VS 10
>> below VS 9. Was there a specific reason for putting VS 10 above VS 6 and
>> thus "out
On 12/28/2010 9:25 AM, Micha Renner wrote:
Am Dienstag, den 28.12.2010, 08:51 -0500 schrieb David Cole:
CMAKE_SHARED_LIBRARY_PREFIX only has one "F"
Shame on me.
Nevertheless, thank you.
Useful hint...
cmake --trace
That will show all the commands including set commands for stuff like
t
On Dec 28, 2010, at 9:29 AM, John Drescher wrote:
>> Just a small piece of feedback. All the other Visual Studio generators are
>> "in order", ie, VS 6, VS 7, VS 8, VS 9 so it made sense to look for VS 10
>> below VS 9. Was there a specific reason for putting VS 10 above VS 6 and
>> thus "out
> Just a small piece of feedback. All the other Visual Studio generators are
> "in order", ie, VS 6, VS 7, VS 8, VS 9 so it made sense to look for VS 10
> below VS 9. Was there a specific reason for putting VS 10 above VS 6 and thus
> "out of order"?
The only reason I can think is that VS 10
> Just a small piece of feedback. All the other Visual Studio generators are
> "in order", ie, VS 6, VS 7, VS 8, VS 9 so it made sense to look for VS 10
> below VS 9. Was there a specific reason for putting VS 10 above VS 6 and thus
> "out of order"?
Maybe the combo box is sorted?
John
___
On Dec 27, 2010, at 6:04 PM, Bill Hoffman wrote:
> On 12/27/2010 5:46 PM, Michael Jackson wrote:
>> I have CMake 2.8.3 installed on a Windows 7 x64 system. I finally got
> around to installing VS2010 in order to try it out and when I run
> CMake-GUI there is no option for Visual Studio 2010? I wa
Am Dienstag, den 28.12.2010, 08:51 -0500 schrieb David Cole:
> CMAKE_SHARED_LIBRARY_PREFIX only has one "F"
Shame on me.
Nevertheless, thank you.
Greetings
Micha
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://w
On 12/28/2010 02:39 PM, mika.raj...@patria.fi wrote:
> Hello
>
> I'd need to get the filepath of a created executable file, so that i can
> use the filepath on a custom command.
>
> add_executable(Program ...)
>
> add_custom_command(TARGET Program POST_BUILD COMMAND ${ProgramToRun}
> ${Program
Hello
I'd need to get the filepath of a created executable file, so that i can
use the filepath on a custom command.
add_executable(Program ...)
add_custom_command(TARGET Program POST_BUILD COMMAND ${ProgramToRun}
${Program} ...)
To clarify, i'd like to run the executable "ProgramToRun" with
Hello
I'm using add_executable to create an executable file.
I'd like to extract the filepath of the created executable for a custom
command.
This causes some trouble for me because I use and must use visual studio.
The familiar problem with the build type being added as a subfolder.
However,
CMAKE_SHARED_LIBRARY_PREFIX only has one "F"
(i.e., it's not "CMAKE_SHARED_LIBRARY_PREFFIX")
On Tue, Dec 28, 2010 at 8:28 AM, Micha Renner wrote:
> Am Dienstag, den 28.12.2010, 07:46 -0500 schrieb David Cole:
> > What's the context of your question?
> >
> >
> > When processing a CMakeLists file
Am Dienstag, den 28.12.2010, 07:46 -0500 schrieb David Cole:
> What's the context of your question?
>
>
> When processing a CMakeLists file, on Linux, the typical value is
> "lib".
Aha.
The following small script...
PROJECT(T)
CMAKE_MINIMUM_REQUIRED(VERSION 2.8.3)
MESSAGE(STATUS "> CMA
What's the context of your question?
When processing a CMakeLists file, on Linux, the typical value is "lib".
There could be any number of reasons why it would be blank for you:
- you're running a cmake -P script, not processing a CMakeLists file
- some file in your project has overridden the val
Hello,
I always thought that CMAKE_SHARED_LIBRARY_PREFIX should have the value
"lib" (Linux). On my system it is blank. Is there a specific reason for
that?
Greetings
Micha
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
h
On Tue, Dec 28, 2010 at 6:00 AM, girish hilage wrote:
> Hi,
>
>Thanks for your reply.
>I have now 2 different files CTestConfig.cmake and script.cmake
>I am giving the command :
>
>ctest -S script.cmake -VV
>
>my script.cmake has following lines in it (skipped initial lines) :
Hi,
Thanks for your reply.
I have now 2 different files CTestConfig.cmake and script.cmake
I am giving the command :
ctest -S script.cmake -VV
my script.cmake has following lines in it (skipped initial lines) :
..
..
ctest_start(Nightly)
ctest_update()
ctest_config
Hi,
CTEST_UPDATE doesn't officialy operate on ClearCase views, but would it be
difficult to add support to CTEST_UPDATE just collecting config spec contents
and sending it to CDash with subsequent CTEST_SUBMIT command ? Is Update.xml
capable of containing such information as ClearCase config sp
On 12/27/2010 09:51 PM, Michael Hertling wrote:
> You might use the ALL option of ADD_CUSTOM_TARGET() to incorporate the
> language target in CMake's "all" target which, in turn, is built as a
> prerequisite of the "install" target. Alternatively, if the language
> file should be installed only if
24 matches
Mail list logo
