On Thu, Aug 1, 2013 at 7:07 PM, Moreland, Kenneth wrote:
> The easiest solution is to simply copy UseLATEX.cmake to your project
> and update it by hand when necessary, which is probably never. That's what
> I do.
>
> -Ken
>
> Sent from my iPad so blame autocorrect.
>
I am using a subtree merg
e LOCATION target properties (which are used by the
CreateLaunchers module) are read-only. Is there any way to solve this?
Best,
--
Sybren A. St?vel
http://stuvel.eu/
-- next part --
An HTML attachment was scrubbed...
URL:
<http://www.cmake.org/pipermail/cmake/at
On 07/31/2013 03:08 PM, Orion Poplawski wrote:
Is there a way to pass arguments to ctest via the "make check" target?
Okay, here's what's up. This recipe:
http://www.cmake.org/Wiki/CMakeEmulateMakeCheck :
add_custom_target(check COMMAND ${CMAKE_CTEST_COMMAND})
is not terribly useful in th
Patrick,
On 08/01/2013 01:41 PM, David Cole wrote:
> He's probably just looking for the generator itself in the cmake
> --help output. They are listed in the dropdown gui if you use cmake-gui...
>
> The Win64 generators are not listed explicitly in the command line
> --help output anymore, altho
On 7/31/2013 7:59 PM, Michael R. Dilworth wrote:
>> Building a 64bit version of cmake, however a 32bit version worked before
>> ~2.8.8
>> (sorry it's late...)
> You should not need a 64bit cmake. The 32 bit version should build
> 64/32 bits. I am not sure what you are looking for?
He’s
R}"
> )
>
> still creates the following line in launch-boost_test-Debug.cmd:
>
> "C:\workspace\rage\build\tests\boost_test\DEBUG\boost_test.exe"
> run_boost_tests.py
>
> but I would like to see:
>
> "C:\Python33\python.exe" run_boost_tests.py
>
>
On 7/31/2013 7:59 PM, Michael R. Dilworth wrote:
Building a 64bit version of cmake, however a 32bit version worked before ~2.8.8
(sorry it's late...)
You should not need a 64bit cmake. The 32 bit version should build
64/32 bits. I am not sure what you are looking for?
-Bill
--
Powered b
Hello,
I set up cmake to use a external project. This 3rd party library writes out a
file which contains all include paths set by this library. For the master cmake
project I need to read this information at build time into a cmake variable to
set the include directories correctly.
Is there a w
Hi list,
I'm using Visual Studio 2010 to create Python modules in C++. In order to
"run" those modules, I need to execute something like:
C:\Python33\python.exe some_script_that_uses_the_module.py
To generate the VS2010 solution we use CMake. What I'm looking for is to
configure the above comman
