I forgot to reply to all.
The gist is that I did override the output directories in some
sub-modules. I.e. setting CMAKE_*_OUTPUT_DIRECTORY is really all I
need.
- Hauke
On Wed, May 4, 2011 at 6:26 PM, Michael Jackson
wrote:
> Are you talking about the actual library/DLL that you are creating o
On Wed, May 4, 2011 at 12:25 PM, Michael Jackson
wrote:
> Funny, I did the same thing using pure CMake code because I couldn't figure
> out batch files.
>
BTW, I started from your example of your macro to create my macro. Thanks.
John
___
Powered by w
Are you talking about the actual library/DLL that you are creating or some 3rd
party library that your built library depends on? If you do this:
# -- Setup output Directories -
SET (CMAKE_LIBRARY_OUTPUT_DIRECTORY
${PROJECT_BINARY_DIR}/Bin
CACHE PATH
"Single D
Funny, I did the same thing using pure CMake code because I couldn't figure out
batch files.
#
#-- Copy all the dependent DLLs into the current build directory so that the
test
#-- can run.
MACRO (CMP_COPY_DEPENDENT_LIBRARIES
> I am curious whether there is a common way of dealing with unit tests
> when the actual project to be tested is a DLL? The issue I am facing
> is a common Windows issue where the required DLL is not found in the
> path.
>
> I tried to put all binaries in the same directory by modifying
> CMAKE_*_
Hi,
I am curious whether there is a common way of dealing with unit tests
when the actual project to be tested is a DLL? The issue I am facing
is a common Windows issue where the required DLL is not found in the
path.
I tried to put all binaries in the same directory by modifying
CMAKE_*_OUTPUT_D
