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.

On Aug 1, 2013, at 10:45 AM, "Zaak Beekman" 
<[email protected]<mailto:[email protected]>> wrote:

Hi,
I am using the UseLATEX package, and I was wondering if there was a way to 
automatically download the UseLATEX.cmake file to be included in the 
CMakeLists.txt file. I was thinking of using the ExternalProject module, 
however, I'm not sure this will work.

When is the external project downloaded? Is this a bad idea? (I'm pretty sure 
it is...)

I think this is probably a bad idea and that I should probably just Fork the 
UseLATEX github git repository, or just the UseLATEX.cmake file, but if anyone 
has any insight, it would be much appreciated.

Izaak Beekman
===================================
(301)244-9367
Princeton University Doctoral Candidate
Mechanical and Aerospace Engineering
[email protected]<mailto:[email protected]>

UMD-CP Visiting Graduate Student
Aerospace Engineering
[email protected]<mailto:[email protected]>
[email protected]<mailto:[email protected]>


On Thu, Aug 1, 2013 at 12:00 PM, 
<[email protected]<mailto:[email protected]>> wrote:
Send CMake mailing list submissions to
        [email protected]<mailto:[email protected]>

To subscribe or unsubscribe via the World Wide Web, visit
        http://www.cmake.org/mailman/listinfo/cmake
or, via email, send a message with subject or body 'help' to
        [email protected]<mailto:[email protected]>

You can reach the person managing the list at
        [email protected]<mailto:[email protected]>

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CMake digest..."


Today's Topics:

   1. Custom launcher command for VS2010 (Sybren A. St?vel)
   2. read file content to a variable at build-time (Rothbauer, Stefan)
   3. Re: 2.8.11.2, Visual Studio 9 2008 Win64? (Bill Hoffman)


----------------------------------------------------------------------

Message: 1
Date: Thu, 1 Aug 2013 12:09:53 +0200
From: Sybren A. St?vel <[email protected]<mailto:[email protected]>>
Subject: [CMake] Custom launcher command for VS2010
To: [email protected]<mailto:[email protected]>
Message-ID:
        
<CAAAfPCDzCJDAdC8KfrCX47cRzA9ep4ZT6wibR=bfrcsjcwv...@mail.gmail.com<mailto:bfrcsjcwv%[email protected]>>
Content-Type: text/plain; charset="utf-8"

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 command in the Debug settings. I tried using the
CreateLaunchers script from https://github.com/rpavlik/cmake-modules, but
unfortunately that doesn't allow me to override the executable command.

For example, our unit tests are compiled into an executable, but still need
to be run via a Python script to set up the environment correctly.
Unfortunately the following in my CMake project definition:


set_target_properties(${PROJECTNAME}
    PROPERTIES
    LOCATION "${PYTHON_EXECUTABLE}"
    LOCATION_DEBUG "${PYTHON_EXECUTABLE}"
    LOCATION_RELEASE "${PYTHON_EXECUTABLE}"
    LOCATION_RELWITHDEBINFO "${PYTHON_EXECUTABLE}"
)

create_default_target_launcher(${PROJECTNAME}
    ARGS "run_boost_tests.py"
    WORKING_DIRECTORY "${RAGE_SCRIPTS_DIR}"
)

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

Apparently the 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/attachments/20130801/8b79b095/attachment-0001.htm>

------------------------------

Message: 2
Date: Thu, 1 Aug 2013 14:07:31 +0000
From: "Rothbauer, Stefan" 
<[email protected]<mailto:[email protected]>>
Subject: [CMake] read file content to a variable at build-time
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Message-ID:
        
<13b93ffb94978c46804a139a3e45e44c013...@defthw99ei1msx.ww902.siemens.net<mailto:13b93ffb94978c46804a139a3e45e44c013...@defthw99ei1msx.ww902.siemens.net>>

Content-Type: text/plain; charset="iso-8859-1"

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 way to do this?
I checked into External_Project_Add_Step but couldn?t find a solution.
I can?t use FILE(READ.) either since the file with include paths is generated 
when cmake configures the 3rd party library.
Execute_Process (cat .) can?t be used because the context switch destroys the 
information.

Thanks for any hints!

Best regards,

Stefan


------------------------------

Message: 3
Date: Thu, 01 Aug 2013 10:49:57 -0400
From: Bill Hoffman <[email protected]<mailto:[email protected]>>
Subject: Re: [CMake] 2.8.11.2, Visual Studio 9 2008 Win64?
To: [email protected]<mailto:[email protected]>
Message-ID: <[email protected]<mailto:[email protected]>>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

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



------------------------------

_______________________________________________
CMake mailing list
[email protected]<mailto:[email protected]>
http://www.cmake.org/mailman/listinfo/cmake

End of CMake Digest, Vol 112, Issue 2
*************************************

--

Powered by www.kitware.com<http://www.kitware.com>

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to