On 2009-12-12 12:02-0500 Bill Hoffman wrote:
Some things just can not be done cross platform. For example reading/
writing the windows registry, creating an OSX application bundle, and
sym-links. Also, some computers don't even have shared libraries. Should we
disable those features from CM
On 12. Dec, 2009, at 17:42 , Alan W. Irwin wrote:
> On 2009-12-12 09:44-0500 David Cole wrote:
>
>> On Fri, Dec 11, 2009 at 10:04 AM, Michael Wild wrote:
>> Bummer. What where they THINKING??? (if at all...). It seems to me
>> that M$ just CAN'T get it right. No matter how many times they try,
cmake-gui is available on mac, Linux and windows since CMake 2.6.0...
HTH,
David
On Saturday, December 12, 2009, Steven Wilson
wrote:
> Is there an actual GUI for Mac OSX (Similar to Windows) other than the curses
> GUI?
>
> Thanks,
>
> Steve
>
___
P
Alan W. Irwin wrote:
On 2009-12-12 09:44-0500 David Cole wrote:
On Fri, Dec 11, 2009 at 10:04 AM, Michael Wild wrote:
Bummer. What where they THINKING??? (if at all...). It seems to me
that M$ just CAN'T get it right. No matter how many times they try,
how many good examples are out there, th
On 2009-12-12 09:44-0500 David Cole wrote:
On Fri, Dec 11, 2009 at 10:04 AM, Michael Wild wrote:
Bummer. What where they THINKING??? (if at all...). It seems to me
that M$ just CAN'T get it right. No matter how many times they try,
how many good examples are out there, they always manage to se
Is there an actual GUI for Mac OSX (Similar to Windows) other than the
curses GUI?
Thanks,
Steve
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topi
On Fri, Dec 11, 2009 at 10:04 AM, Michael Wild wrote:
>
> Bummer. What where they THINKING??? (if at all...). It seems to me that M$
> just CAN'T get it right. No matter how many times they try, how many good
> examples are out there, they always manage to seriously screw something
> up... Come t
Why would add_custom_command call the C++ compiler?
add_custom_command will add a build rule that runs whatever command you tell
it to run. You also have to tell it what the OUTPUT is (full path to a file)
and what the DEPENDS (also full paths to files) are...
It doesn't do anything with the C++
There are bug reports about that, but I cannot reproduce that bug here...
What CMake installer were you running? Where did you get it from?
See these bugs for more details:
http://public.kitware.com/Bug/view.php?id=9878
http://public.kitware.com/Bug/view.php?id=8959
If you have steps to reproduce
All CMake does is create a directory and copy a file to your user macros
folder and add some registry keys to tell Visual Studio that macros are
there.
The folder is something like:
{YOUR_MY_DOCUMENTS_FOLDER}\Visual Studio
2005\Projects\VSMacros80\CMakeMacros
And the reg keys are at something lik
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
Hi David,
The documentation for add_custom_command seems to imply that it will only
add a build command and not replace a build command. The way that I
interpret this is that cmake will generate a vcproj that executes my custom
build command (gmake) that I add using add_custom_command but will al
13 matches
Mail list logo