On Wednesday 31 May 2006 01:44, William A. Hoffman wrote:
> Yes, that is what I am talking about. I don't think it will be hard to
> implement, and I am sure any hard coded approach will be regretted a few
> months later.
>
> Also,
>
> cmake --help (will print the help for the given project)
I
William A. Hoffman wrote:
> At 07:20 PM 5/30/2006, Brandon J. Van Every wrote:
> Whether it is command.com or msys or cygwin, there are a number of developers
> on
> windows that will use the command line. If we can provide a consistent
> interface across
I'm one of them :)
> unix and windows
At 07:20 PM 5/30/2006, Brandon J. Van Every wrote:
>James Mansion wrote:
>>>
>>>For those that run Windows (and don't have the unixtools installed) the
>>>preferred interface is a GUI anyway.
>>>
>>
>>
>>I don't think that's a good assumption. Windows has a command interpreter
>>(and in my e
James Mansion wrote:
For those that run Windows (and don't have the unixtools installed) the
preferred interface is a GUI anyway.
I don't think that's a good assumption. Windows has a command interpreter
(and in my experience people erroneously believe CMD.EXE is as limited
>For those that run Windows (and don't have the unixtools installed) the
>preferred interface is a GUI anyway.
I don't think that's a good assumption. Windows has a command interpreter
(and in my experience people erroneously believe CMD.EXE is as limited as
COMMAND.COM without having looked at
At 11:11 AM 5/30/2006, Alexander Neundorf wrote:
>If I understood Bill correctly, the idea is to provide a special file which is
>read by cmake and which provides mappings between full cmake variable names
>and short command line parameters.
>Like:
>CMAKE_MAP(CMAKE_INSTALL_PREFIX prefix)
>
>so th
Hi,
> Von: Thomas Zander <[EMAIL PROTECTED]>
>
> On Tuesday 30 May 2006 16:48, Alexander Neundorf wrote:
> > > But the 'configure' idea is exactly for that set of people who are
> > > used to doing so. And, honestly, unix shell (sh) are available
> > > everywhere. For those that run Windows (and
On Tuesday 30 May 2006 16:48, Alexander Neundorf wrote:
> > But the 'configure' idea is exactly for that set of people who are
> > used to doing so. And, honestly, unix shell (sh) are available
> > everywhere. For those that run Windows (and don't have the unixtools
> > installed) the preferred int
Hi Thomas,
> Von: Thomas Zander <[EMAIL PROTECTED]>
>
> On Tuesday 30 May 2006 14:58, you wrote:
> > I don't think we want to generate a configure script since it will only
> > run on systems with a unix shell.
>
> But the 'configure' idea is exactly for that set of people who are used to
> doin
Hi,
> Von: William A. Hoffman <[EMAIL PROTECTED]>
...
> to cmake configurable. I think we all agree that avoiding
> cmake -DSOME_REALLY_LONG_CAP_NAME=/some/path is a good thing.
> The question now, is what is the best way to provide better,
> configurable options
> to cmake. I think some fil
On Tuesday 30 May 2006 14:58, you wrote:
> I don't think we want to generate a configure script since it will only
> run on systems with a unix shell.
But the 'configure' idea is exactly for that set of people who are used to
doing so. And, honestly, unix shell (sh) are available everywhere.
For
At 04:05 AM 5/30/2006, Thomas Zander wrote:
>Maybe a little change in approach will solve some hard-to-crack issues.
>If the project manager just runs 'cmake --create-configure' after he made
>some changes in the build system, which in turn will generate a configure
>script with the projects opt
On Tuesday 30 May 2006 03:30, William A. Hoffman wrote:
> >> set_variable_property(CMAKE_INSTALL_PREFIX COMMNAD_LINE_OPT
> >> "--prefix")
> >
> >I don't think a configurable behavior is needed here. It is my opinion
> > that there is no need for freedom for these things. It is more
> > important to
Hi,
Why not having it configurable in a file so new mapping can be added without
recompiling.
It's much easier and shorter to remember ./configure --prefix=/usr instead of
cmake -DCMAKE_INSTALL_PREFIX=/usr or ./configure --verbose instead of cmake
-DCMAKE_VERBOSE_MAKEFILE
Millions of people h
Hi,
> Von: William A. Hoffman <[EMAIL PROTECTED]>
...
> I just don't like to have a hard coded list of "short cuts" as soon
> as you have one, someone will complain that they want one as well, and
> to add one, you will have to wait for a new version of cmake to come out
> if it is hard coded. W
At 03:16 PM 5/29/2006, Axel Roebel wrote:
>My idea was that there would be the special short cuts that are most often
>used:
>--prefix=* -DCMAKE_INSTALL_PREFIX=*
>--verbose -DCMAKE_VERBOSE_MAKEFILE
>--build=* -DCMAKE_BUILD_TYPE=*
Ok, is that the list of short cuts in total?
>and besides tha
16 matches
Mail list logo
