On 10/17/2012 08:05 PM, Totte Karlsson wrote:
>
> On 10/16/2012 12:49 AM, Michael Wild wrote:
>> This will always work:
>>
>> add_executable(frobnicate frobnicate.c)
>>
>> add_custom_command(OUTPUT ${resultFile}
>>COMMAND frobnicate ${resultFileFolder}
>>WORKING_DIRECTORY ${PROJECT_SOURCE_
Hi all,
I have a library project with some assocaited tests.
The library is build in myproject/src directory, while tests are built
in myproject/tests directory.
Everything builds fine under MSVC2010, resulting DLL is stored in
myproject/src/Debug.
However, if I try to run the test, it com
Interestingly it only does this for C/C++ but does not do it for Fortran source
files (at least in my project when I just tested it) even though -S is a valid
option for Intel and GNU Fortran compilers.
Any possibility that could be corrected?
Tim
- Original Message -
From: "Bill Hoffm
> CMake has targets to do that. If you type make help you can see them. It
> should be something like this:
>
> make Assembly.s
>
> -Bill
Ah, so easy. Thanks Bill!
David
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
On 10/18/2012 9:47 PM, David Doria wrote:
I am trying to produce the .s file that "g++ -S file.cpp" would
produce, but on a CMake target (because I want the include path that
I've setup through CMake, etc.)
Consider a simple demo:
PROJECT(Assembly)
ADD_EXECUTABLE(Assembly Assembly.cpp ) # this
I am trying to produce the .s file that "g++ -S file.cpp" would
produce, but on a CMake target (because I want the include path that
I've setup through CMake, etc.)
Consider a simple demo:
PROJECT(Assembly)
ADD_EXECUTABLE(Assembly Assembly.cpp ) # this produces an 'Assembly' executable
I tried t
Just fix the documentation, please.
--
Dave Abrahams
BoostPro Computing Software DevelopmentTraining
http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware
Hi,
I have to execute an extra install command only if the component is selected,
searching for a solution I found this
(http://public.kitware.com/Bug/view.php?id=12592) Someone with the same problem
already created a patch do give CPACK_NSIS_EXTRA_INSTALL_COMMANDS a component
based version, a
Hi.
OK, I smiled too soon (too little coffee, I guess).
add_test(NAME ut COMMAND ${CMAKE_COMMAND} -E environment)
doesn't do what I want. Don't know, why, I thought it runs my test, so just
ignore previous response.
Equivalent of this works:
cmake_minimum_required(VERSION 2.8)
project(t1)