Thanks everybody for the answers. I finally got it working more or
less to my satisfaction by writing it manually.
Mike, I grabbed some of your install stuff. Thanks for that.
J Decker, thanks for reminding me about CMAKE_CFG_INTDIR. I knew about
it, but it's easy to forget. (That's why I didn't
My way of dealing with this problem is similar to other people here:
1. I have a separate Python post-build script designed to be driven
through command line.
This script read somewhere the list of direct binary dependencies of
the target[1] and copy them in the
output directory. The
On Mon, May 26, 2014 at 8:04 AM, Klaim - Joël Lamotte mjkl...@gmail.com wrote:
- Why can't I use the install command from CMake? My understanding is that
it's used to install the application in the system
Not really. It's to massage the installed files into their final form --
but not
On Mon, May 26, 2014 at 5:08 PM, Dan Kegel d...@kegel.com wrote:
On Mon, May 26, 2014 at 8:04 AM, Klaim - Joël Lamotte mjkl...@gmail.com
wrote:
- Why can't I use the install command from CMake? My understanding is
that
it's used to install the application in the system
Not really. It's
On Mon, May 26, 2014 at 8:04 AM, Klaim - Joël Lamotte mjkl...@gmail.comwrote:
My way of dealing with this problem is similar to other people here:
1. I have a separate Python post-build script designed to be driven
through command line.
This script read somewhere the list of direct
Hi Eric,
This can be solved using a launcher.
When adding tests, you could use the following syntax:
add_test(
NAME NameOfTest
COMMAND ${TheProject_LAUNCH_COMMAND} $TARGET_FILE:NameOfTarget
--arg1 ...
)
where
TheProject_LAUNCH_COMMAND is a variable pointing to a
You can add the directory containing the 3rd party DLLs to the global
PATH environment variable, I bet.
As for how to ship the Microsoft DLLs,
http://msdn.microsoft.com/en-us/library/ms235299.aspx
might be a good place to start reading?
- Dan
--
Powered by www.kitware.com
Please keep messages
On 5/23/14, Dan Kegel d...@kegel.com wrote:
You can add the directory containing the 3rd party DLLs to the global
PATH environment variable, I bet.
So I'm looking for a CMake way to deal with this. I don't want to
change the system environment. My stuff is highly distributed among
lots of
On Fri, May 23, 2014 at 4:38 PM, Eric Wing ewmail...@gmail.com wrote:
On 5/23/14, Dan Kegel d...@kegel.com wrote:
You can add the directory containing the 3rd party DLLs to the global
PATH environment variable, I bet.
... I just want a
work-out-of-the-box solution with CMake doing local
On 5/23/14, Dan Kegel d...@kegel.com wrote:
On Fri, May 23, 2014 at 4:38 PM, Eric Wing ewmail...@gmail.com wrote:
On 5/23/14, Dan Kegel d...@kegel.com wrote:
You can add the directory containing the 3rd party DLLs to the global
PATH environment variable, I bet.
... I just want a
INCLUDE(InstallRequiredSystemLibraries)
INSTALL( FILES ${CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS} DESTINATION
${BINARY_OUTPUT_DIR} )
but that doesn't cover third party libraries; which should be in the path
anyway.
Oh; but that's install... so I don't use projects to run, I set the debug
properties of
Eric,
For my project I ran into the same problems
(http://www.github.com/dream3d/DREAM3D) and I chose to solve the issues by
having CMake setup custom build rules to copy the DLLs into the appropriate
Debug or Release directory for what I am building. I do this because simply
adding the
12 matches
Mail list logo
