N characters long with M
>> semi-colon separated components
>> - look at "My Computer > Properties > Advanced > Environment Variables >
>> user PATH value" to see the new PATH value
>>
>> I will try this again on Monday with the installer you&#
ls. (Exactly what steps you took that produced the
> problem...)
>
>
> Thanks,
> David
>
>
> On Sat, Dec 12, 2009 at 7:31 AM, Mark Jones wrote:
>
>> I chose to add cmake to my PATH (on Win XP 32) during the installation.
>> After it finished I noticed that it c
h. I've never
> heard this sort of report before -- are you up to date with respect to VS
> service packs and updates?
>
>
> HTH,
> David
>
>
> On Sat, Dec 12, 2009 at 7:29 AM, Mark Jones wrote:
>
>> When I ran cmake for the first time it registered itself
I chose to add cmake to my PATH (on Win XP 32) during the installation.
After it finished I noticed that it completely overrode my PATH instead of
appending to it. Is this a known bug?
Thanks,
Mark
___
Powered by www.kitware.com
Visit other Kitware ope
When I ran cmake for the first time it registered itself with Visual Studio
2005. Now that it has done so, if I try to right click on any of my macros
(including those that existed prior to running cmake) and choose Edit to
edit the macros, a dialog comes up that says "Error", "Interface not
regis
those CMake commands...?
>
> http://cmake.org/cmake/help/cmake-2-8-docs.html#command:add_custom_command
> http://cmake.org/cmake/help/cmake-2-8-docs.html#command:add_custom_target
>
>
> HTH,
> David
>
>
> On Fri, Dec 11, 2009 at 9:17 AM, Mark Jones wrote:
>
>>
If I have a build system in place (that uses gmake) that I am already
comfortable with and would just like to use cmake to create Visual Studio
(or XCode) projects that simply have release and debug targets that call
gmake for me, can I do that with cmake? Or, does cmake always generate a
makefile
