Yes, that's exactly it. I'll try to add something to the wiki.
On Wed, Jan 11, 2012 at 6:01 AM, Eric Noulard wrote:
> 2012/1/11 Robert Dailey :
>> He probably just uses a project.vcproj.user file, and uses the
>> configure_file() command on it to fill in command arguments, environment
>> variable
2012/1/11 Robert Dailey :
> He probably just uses a project.vcproj.user file, and uses the
> configure_file() command on it to fill in command arguments, environment
> variables, etc etc.
>
> I've done this before and it works fantastically, although I have never
> tried it to force the EXE to sear
He probably just uses a project.vcproj.user file, and uses the
configure_file() command on it to fill in command arguments, environment
variables, etc etc.
I've done this before and it works fantastically, although I have never
tried it to force the EXE to search for my DLL files without copying t
On Tue, Jan 10, 2012 at 3:17 PM, Ben Medina wrote:
> I'd guess the performance of fixup_bundle will be a big pitfall if
> you're planning on doing this after every build.
>
One other approach is not making it a post build step but a custom
target that the user can build only when needed. This cus
I am VERY interested in how you did this. Did you have CMake write a file for
you? Do you have some code to share by any chance?
Thanks
--
Mike Jackson
On Jan 10, 2012, at 3:17 PM, Ben Medina wrote:
> I'd guess the performance of fixup_bundle will be a big pitfall if
> you're planning on doin
I'd guess the performance of fixup_bundle will be a big pitfall if
you're planning on doing this after every build.
An entirely different approach is to configure a Visual Studio .user
file to set the PATH environment variable (not setting it globally;
just for debugging your app from within VS).
2012/1/9 Hauke Heibel :
> 2012/1/9 Michael Stürmer :
>> Awesome! Sometimes you just need to know what's already available to solve
>> your problems in a very elegant way. I'll have a look at these bundles and
>> probably switch to them instead of maintaining my own stuff!
>
> When looking at the
2012/1/9 Michael Stürmer :
> Awesome! Sometimes you just need to know what's already available to solve
> your problems in a very elegant way. I'll have a look at these bundles and
> probably switch to them instead of maintaining my own stuff!
When looking at the initial problem, I am pretty muc
> Awesome! Sometimes you just need to know what's already available to solve
> your problems in a very elegant way. I'll have a look at these bundles and
> probably switch to them instead of maintaining my own stuff!
>
Same here. I have spent a few hours writing scripts that keep a list
of neces
itware.com]
Gesendet: Montag, 9. Januar 2012 17:05
An: Michael Stürmer
Cc: cmake@cmake.org
Betreff: Re: [CMake] Copying of 3rd party DLLs in a POST-BUILD step
2012/1/9 Michael Stürmer :
> I have found some topics related to my issue on the web, but none so far
> helped me to fix it:
>
>
&
2012/1/9 Michael Stürmer :
> I have found some topics related to my issue on the web, but none so far
> helped me to fix it:
>
>
>
> I use Visual Studio 2010 on Windows 7 64Bit.
>
>
>
> During my build, all binaries are collected in one folder, which makes it
> easier for me to debug the project. B
Hi,
Did you try FixupBundle from the BundleUtilities module ?
I use it on windows, at install time, to copy all the dll required by an
executable, just next to the executable.
Very usefull to generate a standalone installer. The good thing is that
it introspects your executable (via the window
On 01/09/2012 10:05 AM, Michael Stürmer wrote:
> I have found some topics related to my issue on the web, but none so far
> helped me to fix it:
>
> I use Visual Studio 2010 on Windows 7 64Bit.
>
> During my build, all binaries are collected in one folder, which makes it
> easier for me to de
On Mon, Jan 9, 2012 at 4:11 PM, Michael Jackson
wrote:
> The only issue I really have with this is that this macro requires there to
> be BOTH debug and Release libraries available and will copy BOTH no matter
> which configuration is being built. I am thinking that the
> "yourCopyDlls.cmake" c
I was going to chime in with my own macro:
#
#-- Copy all the Qt4 dependent DLLs into the current build directory so that
#-- one can debug an application or library that depends on Qt4 libraries.
macro (CMP_COPY_QT4_RUNTIME_LIBR
2012/1/9 Hauke Heibel :
> Hi Michael,
>
> What I do is running a custom command which itself executes a CMake
> script. Usually similar to
>
> add_custom_command(TARGET CopyDlls
> COMMAND ${CMAKE_COMMAND}
> -DMSVC_BUILD_CONFIG_DIR=${CMAKE_CFG_INTDIR}
> -DCMAKE_RUNTIME_OUTPUT_DIRECTOR
e: [CMake] Copying of 3rd party DLLs in a POST-BUILD step
Hi Michael,
What I do is running a custom command which itself executes a CMake
script. Usually similar to
add_custom_command(TARGET CopyDlls
COMMAND ${CMAKE_COMMAND}
-DMSVC_BUILD_CONFIG_DIR=${CMAKE_CFG_INTDIR}
-DCMAKE
Hi Michael,
What I do is running a custom command which itself executes a CMake
script. Usually similar to
add_custom_command(TARGET CopyDlls
COMMAND ${CMAKE_COMMAND}
-DMSVC_BUILD_CONFIG_DIR=${CMAKE_CFG_INTDIR}
-DCMAKE_RUNTIME_OUTPUT_DIRECTORY=${CMAKE_RUNTIME_OUTPUT_DIRECTORY}
I have found some topics related to my issue on the web, but none so far helped
me to fix it:
I use Visual Studio 2010 on Windows 7 64Bit.
During my build, all binaries are collected in one folder, which makes it
easier for me to debug the project. But to be able to run the program actually,
19 matches
Mail list logo
