Bill,
On Friday 23 May 2008 09:27:54 Bill Hoffman wrote:
> But that would only work if they are using the IDE, nmake and make
> builds would still not work. Another approach is to use a forwarding
> executable. Have a wrapper program that sets PATH as needed to run
> things, and then execs the p
David,
On Friday 23 May 2008 09:14:11 David Cole wrote:
> If you want to write reg values with cmake, you can execute cmake as a
> sub-process with -E command line args (for example, using
> EXECUTE_PROCESS(COMMAND ${CMAKE_COMMAND} in your CMakeLists.txt file)
>
> Use the write_regv -E sub-co
KSpam wrote:
Bill,
On Friday 23 May 2008 06:14:27 Bill Hoffman wrote:
So, there is not much CMake can do for you. The only thing you can do
on windows is make sure that .exe and .dll files are all in the same
directory. Windows always looks first in the directory of the .exe for
any .dll file
Bill,
On Friday 23 May 2008 06:14:27 Bill Hoffman wrote:
> So, there is not much CMake can do for you. The only thing you can do
> on windows is make sure that .exe and .dll files are all in the same
> directory. Windows always looks first in the directory of the .exe for
> any .dll files it nee
If you want to write reg values with cmake, you can execute cmake as a
sub-process with -E command line args (for example, using
EXECUTE_PROCESS(COMMAND ${CMAKE_COMMAND} in your CMakeLists.txt file)
Use the write_regv -E sub-command:
cmake -E
CMake Error: cmake version 2.6-patch 0
Usage: cma
Arjen,
On Thursday 22 May 2008 23:35:33 Arjen Markus wrote:
> Having CMake set the necessary registry entries would not help with
> binary distributions of your product. I do not whether that is relevant
> to you, but in general that would be a problem:
> - Your clients may have the libraries inst
So, there is not much CMake can do for you. The only thing you can do
on windows is make sure that .exe and .dll files are all in the same
directory. Windows always looks first in the directory of the .exe for
any .dll files it needs. CMake can put the files in the same directory.
That is w
KSpam wrote:
HS,
On Thursday 22 May 2008 02:05:33 Hendrik Sattler wrote:
KSpam schrieb:
Using this add-in would require that I create a corresponding .slnenv
file for each .sln file generated by CMake. In my case, the contents of
the .slnenv files can be the same (I am just setting P
HS,
On Thursday 22 May 2008 02:05:33 Hendrik Sattler wrote:
> KSpam schrieb:
> > Using this add-in would require that I create a corresponding .slnenv
> > file for each .sln file generated by CMake. In my case, the contents of
> > the .slnenv files can be the same (I am just setting PATH).
> >
>
KSpam schrieb:
Using this add-in would require that I create a corresponding .slnenv file for
each .sln file generated by CMake. In my case, the contents of the .slnenv
files can be the same (I am just setting PATH).
What is the best way to accomplish generating a .slnenv file for each
gener
I have been searching for a convenient way to deal with PATH on Windows. Here
are my requirements:
1) Multiple third party libraries, each with their own unique dll directory
(i.e. no shared directory to dump dlls in)
2) Third party library locations can change (i.e. I want to upgrade lib FOO t
11 matches
Mail list logo
