Re: [cmake-developers] [patch] Document -H and -B

2016-07-05 Thread Dave Gittins
I think we should add new normalised forms but still mention the deprecated
names in the docs.

You can't put the cat back in the bag - like it or not, those option names
seem quite widely used. Developers will join a project and see them in use.
Currently they will find no mention of them in docs but find something on
StackOverflow (which may or may not be accurate), and they will stay like
that even if new forms are available. That's what I observe in the field.

If you explain in docs that they are deprecated forms, those developers
will know what they actually do and that they are deprecated, and many will
replace with the new form.

I believe those are your choices basically; I am really hoping you choose
the latter!

Dave
On 6 Jul 2016 06:31, "Brad King"  wrote:

On 07/05/2016 06:29 AM, Ruslan Baratov wrote:
> I don't see the point of introducing new options. Developers will still
> use -H/-B because it's backward compatible, well known and will work
> 100% because of internal CMake testing. That said if you want to improve
> the current behavior of -H/-B (like confusing with --help/no spaces
> between -H and ) I can take a look. Otherwise I'm
> not interested (usually it means that the improvement will be abandoned).

The conflict with the plain `-H` help option is another reason to
keep these options private.  I've outlined what is an acceptable
path to offer public options for this workflow.  If anyone wants
to do that then great.  Otherwise the status quo will persist.

-Brad
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] [patch] Document -H and -B

2016-07-05 Thread Brad King
On 07/05/2016 06:29 AM, Ruslan Baratov wrote:
> I don't see the point of introducing new options. Developers will still 
> use -H/-B because it's backward compatible, well known and will work 
> 100% because of internal CMake testing. That said if you want to improve 
> the current behavior of -H/-B (like confusing with --help/no spaces 
> between -H and ) I can take a look. Otherwise I'm 
> not interested (usually it means that the improvement will be abandoned).

The conflict with the plain `-H` help option is another reason to
keep these options private.  I've outlined what is an acceptable
path to offer public options for this workflow.  If anyone wants
to do that then great.  Otherwise the status quo will persist.

-Brad

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [patch] Document -H and -B

2016-07-05 Thread Ruslan Baratov via cmake-developers

On 01-Jul-16 15:58, Brad King wrote:


* Allow the form `-H  -B ` with the new names.

I don't see the point of introducing new options. Developers will still 
use -H/-B because it's backward compatible, well known and will work 
100% because of internal CMake testing. That said if you want to improve 
the current behavior of -H/-B (like confusing with --help/no spaces 
between -H and ) I can take a look. Otherwise I'm 
not interested (usually it means that the improvement will be abandoned).


Ruslo
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [patch] Document -H and -B

2016-07-01 Thread Brad King
On 06/30/2016 05:35 PM, Dave Gittins wrote:
> I don't understand the harm of documenting the options and making
> them public.

The discussion got side-tracked on how to do it with the currently
documented interface.

> Seems to me that they are
> a) used
> b) useful
> c) safe

We can consider making them public but in addition to the documentation
we should:

* Consider providing alternative options with more intuitive names
  and making those public instead.  Currently "-H" stands for "Home"
  which is an internal name within CMake's implementation and is not
  a name whose meaning is public-facing.

* Allow the form `-H  -B ` with the new names.

* Extend the test suite (e.g. RunCMake.CommandLine) with cases
  covering the public-facing options.

-Brad
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Dave Gittins
I don't understand the harm of documenting the options and making them
public. Brad can you explain?

I have worked with numerous colleagues who use them. So far nothing bad
happened to them!

Seems to me that they are
a) used
b) useful
c) safe

Is there context I am missing?

Dave
On 1 Jul 2016 7:31 a.m., "Ruslan Baratov via cmake-developers" <
cmake-developers@cmake.org> wrote:

> On 01-Jul-16 00:14, Shawn Waldon wrote:
>
> On Thu, Jun 30, 2016 at 5:10 PM, Ruslan Baratov 
> wrote:
>
>> On 30-Jun-16 23:57, Shawn Waldon wrote:
>>
>> On Thu, Jun 30, 2016 at 4:54 PM, Ruslan Baratovwrote:
>>
>>> On 30-Jun-16 23:40, Brad King wrote:
>>>
 On 06/30/2016 04:28 PM, Ruslan Baratov wrote:

> On 30-Jun-16 23:18, Brad King wrote:
>
>> On 06/30/2016 03:56 PM, Ruslan Baratov wrote:
>>
>>> What is the public-use way to specify source-tree and build-tree by
>>> cmake options simultaneously?
>>>
>> cd $build && cmake $src
>>
> Will not work if $build not exists.
>
 mkdir -p "$build" && cd "$build" && cmake "$src"

>>>
>>> Next issue is that this command change directory, how can I move back to
>>> the directory where I was working on?
>>
>>
>> mkdir -p "$build" && pushd "$build" && cmake "$src" && popd
>>>
>> Doesn't go back if `cmake "$src"` failed
>>
> I think Brad may have a better idea with the subshell.  But to modify this
> to work even if `cmake "$src"` failed:
>
> mkdir -p "$build" && pushd "$build" && cmake "$src"; popd
>
> > echo $?
> 0
>
> for the CMakeLists.txt with errors
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake-developers
>
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Ruslan Baratov via cmake-developers

On 01-Jul-16 00:14, Shawn Waldon wrote:
On Thu, Jun 30, 2016 at 5:10 PM, Ruslan Baratov 
> wrote:


On 30-Jun-16 23:57, Shawn Waldon wrote:

On Thu, Jun 30, 2016 at 4:54 PM, Ruslan Baratovwrote:

On 30-Jun-16 23:40, Brad King wrote:

On 06/30/2016 04:28 PM, Ruslan Baratov wrote:

On 30-Jun-16 23:18, Brad King wrote:

On 06/30/2016 03:56 PM, Ruslan Baratov wrote:

What is the public-use way to specify
source-tree and build-tree by
cmake options simultaneously?

cd $build && cmake $src

Will not work if $build not exists.

mkdir -p "$build" && cd "$build" && cmake "$src"


Next issue is that this command change directory, how can I
move back to the directory where I was working on?


mkdir -p "$build" && pushd "$build" && cmake "$src" && popd


Doesn't go back if `cmake "$src"` failed

I think Brad may have a better idea with the subshell. But to modify 
this to work even if `cmake "$src"` failed:


mkdir -p "$build" && pushd "$build" && cmake "$src"; popd

> echo $?
0

for the CMakeLists.txt with errors
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Ruslan Baratov via cmake-developers

On 01-Jul-16 00:02, Brad King wrote:

On 06/30/2016 04:57 PM, Shawn Waldon wrote:

 mkdir -p "$build" && pushd "$build" && cmake "$src" && popd

Or use a ()-enclosed subshell:

  (mkdir -p "$build" && cd "$build" && cmake "$src")

-Brad

Okay, this one seems to work. Also you haven't show how `src` defined, 
e.g. I can't do 'src=.' so it should be src="`pwd`"


So instead of "cmake -H. -B_builds" we have (src="`pwd`" build=_builds 
mkdir -p "$build" && cd "$build" && cmake "$src")

And it's only for *nix.

What about Windows?

Such options definitely would be useful in CMake.

Ruslo


--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Shawn Waldon
On Thu, Jun 30, 2016 at 5:10 PM, Ruslan Baratov 
wrote:

> On 30-Jun-16 23:57, Shawn Waldon wrote:
>
> On Thu, Jun 30, 2016 at 4:54 PM, Ruslan Baratovwrote:
>
>> On 30-Jun-16 23:40, Brad King wrote:
>>
>>> On 06/30/2016 04:28 PM, Ruslan Baratov wrote:
>>>
 On 30-Jun-16 23:18, Brad King wrote:

> On 06/30/2016 03:56 PM, Ruslan Baratov wrote:
>
>> What is the public-use way to specify source-tree and build-tree by
>> cmake options simultaneously?
>>
> cd $build && cmake $src
>
 Will not work if $build not exists.

>>> mkdir -p "$build" && cd "$build" && cmake "$src"
>>>
>>
>> Next issue is that this command change directory, how can I move back to
>> the directory where I was working on?
>
>
> mkdir -p "$build" && pushd "$build" && cmake "$src" && popd
>>
> Doesn't go back if `cmake "$src"` failed
>
I think Brad may have a better idea with the subshell.  But to modify this
to work even if `cmake "$src"` failed:

mkdir -p "$build" && pushd "$build" && cmake "$src"; popd
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Ruslan Baratov via cmake-developers

On 30-Jun-16 23:57, Shawn Waldon wrote:

On Thu, Jun 30, 2016 at 4:54 PM, Ruslan Baratovwrote:

On 30-Jun-16 23:40, Brad King wrote:

On 06/30/2016 04:28 PM, Ruslan Baratov wrote:

On 30-Jun-16 23:18, Brad King wrote:

On 06/30/2016 03:56 PM, Ruslan Baratov wrote:

What is the public-use way to specify source-tree
and build-tree by
cmake options simultaneously?

cd $build && cmake $src

Will not work if $build not exists.

mkdir -p "$build" && cd "$build" && cmake "$src"


Next issue is that this command change directory, how can I move
back to the directory where I was working on?


mkdir -p "$build" && pushd "$build" && cmake "$src" && popd


Doesn't go back if `cmake "$src"` failed

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Brad King
On 06/30/2016 04:57 PM, Shawn Waldon wrote:
> mkdir -p "$build" && pushd "$build" && cmake "$src" && popd

Or use a ()-enclosed subshell:

 (mkdir -p "$build" && cd "$build" && cmake "$src")

-Brad

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Shawn Waldon
On Thu, Jun 30, 2016 at 4:54 PM, Ruslan Baratovwrote:

> On 30-Jun-16 23:40, Brad King wrote:
>
>> On 06/30/2016 04:28 PM, Ruslan Baratov wrote:
>>
>>> On 30-Jun-16 23:18, Brad King wrote:
>>>
 On 06/30/2016 03:56 PM, Ruslan Baratov wrote:

> What is the public-use way to specify source-tree and build-tree by
> cmake options simultaneously?
>
 cd $build && cmake $src

>>> Will not work if $build not exists.
>>>
>> mkdir -p "$build" && cd "$build" && cmake "$src"
>>
>
> Next issue is that this command change directory, how can I move back to
> the directory where I was working on?


mkdir -p "$build" && pushd "$build" && cmake "$src" && popd
>
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Rolf Eike Beer
Am Donnerstag, 30. Juni 2016, 23:54:42 schrieb Ruslan Baratov via cmake-
developers:
> On 30-Jun-16 23:40, Brad King wrote:
> > On 06/30/2016 04:28 PM, Ruslan Baratov wrote:
> >> On 30-Jun-16 23:18, Brad King wrote:
> >>> On 06/30/2016 03:56 PM, Ruslan Baratov wrote:
>  What is the public-use way to specify source-tree and build-tree by
>  cmake options simultaneously?
> >>> 
> >>> cd $build && cmake $src
> >> 
> >> Will not work if $build not exists.
> > 
> > mkdir -p "$build" && cd "$build" && cmake "$src"
> 
> Next issue is that this command change directory, how can I move back to
> the directory where I was working on?

pushd/popd or do the cd/cmake call in a subshell.

Eike

signature.asc
Description: This is a digitally signed message part.
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Ruslan Baratov via cmake-developers

On 30-Jun-16 23:40, Brad King wrote:

On 06/30/2016 04:28 PM, Ruslan Baratov wrote:

On 30-Jun-16 23:18, Brad King wrote:

On 06/30/2016 03:56 PM, Ruslan Baratov wrote:

What is the public-use way to specify source-tree and build-tree by
cmake options simultaneously?

cd $build && cmake $src

Will not work if $build not exists.

mkdir -p "$build" && cd "$build" && cmake "$src"


Next issue is that this command change directory, how can I move back to 
the directory where I was working on?


--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Brad King
On 06/30/2016 04:28 PM, Ruslan Baratov wrote:
> On 30-Jun-16 23:18, Brad King wrote:
>> On 06/30/2016 03:56 PM, Ruslan Baratov wrote:
>>> What is the public-use way to specify source-tree and build-tree by
>>> cmake options simultaneously?
>> cd $build && cmake $src
> 
> Will not work if $build not exists.

mkdir -p "$build" && cd "$build" && cmake "$src"

-Brad

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Ruslan Baratov via cmake-developers

On 30-Jun-16 23:18, Brad King wrote:

On 06/30/2016 03:56 PM, Ruslan Baratov wrote:

What is the public-use way to specify source-tree and build-tree by
cmake options simultaneously?

cd $build && cmake $src


Will not work if $build not exists.

--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Brad King
On 06/30/2016 03:56 PM, Ruslan Baratov wrote:
> What is the public-use way to specify source-tree and build-tree by 
> cmake options simultaneously?

cd $build && cmake $src

-Brad

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Ruslan Baratov via cmake-developers

On 30-Jun-16 22:31, Brad King wrote:

On 06/30/2016 03:23 PM, Ruslan Baratov via cmake-developers wrote:

Patch with undocumented options -H/-B.

These are undocumented because they are internal options that
are not meant for public use.
What is the public-use way to specify source-tree and build-tree by 
cmake options simultaneously?
If there is no such, what is the problem with making existing options 
public?


Ruslo
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Brad King
On 06/30/2016 03:23 PM, Ruslan Baratov via cmake-developers wrote:
> Patch with undocumented options -H/-B.

These are undocumented because they are internal options that
are not meant for public use.

-Brad

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


[cmake-developers] [patch] Document -H and -B

2016-06-30 Thread Ruslan Baratov via cmake-developers

Hi,

Patch with undocumented options -H/-B.

Ruslo
>From 6c378bd6622ca26c43225787494d60f1a9867b22 Mon Sep 17 00:00:00 2001
From: Ruslan Baratov 
Date: Thu, 30 Jun 2016 22:17:14 +0300
Subject: [PATCH] Document -H and -B options

---
 Help/manual/OPTIONS_BUILD.txt | 20 
 Help/manual/cmake.1.rst   |  1 +
 2 files changed, 21 insertions(+)

diff --git a/Help/manual/OPTIONS_BUILD.txt b/Help/manual/OPTIONS_BUILD.txt
index b428a74..1caa954 100644
--- a/Help/manual/OPTIONS_BUILD.txt
+++ b/Help/manual/OPTIONS_BUILD.txt
@@ -1,3 +1,23 @@
+``-H``
+ Path to directory with CMakeLists.txt.
+
+ There must be no spaces between ``-H`` and 
+ (otherwise option will be interpreted as synonym to ``--help``). Always must
+ be used with ``-B`` option. Example:
+
+ ::
+
+   cmake -H. -B_builds
+
+ Use current directory as a source tree (i.e. start with
+ ``./CMakeLists.txt``) and put generated files to the ``./_builds`` folder.
+
+``-B``
+ Path to directory where CMake will store generated files.
+
+ There must be no spaces between ``-B`` and . Always
+ must be used with ``-H`` option.
+
 ``-C ``
  Pre-load a script to populate the cache.
 
diff --git a/Help/manual/cmake.1.rst b/Help/manual/cmake.1.rst
index 8f7c336..593bb2d 100644
--- a/Help/manual/cmake.1.rst
+++ b/Help/manual/cmake.1.rst
@@ -9,6 +9,7 @@ Synopsis
 .. parsed-literal::
 
  cmake [] ( | )
+ cmake -H -B []
  cmake [(-D =)...] -P 
  cmake --build  [...] [-- ...]
  cmake -E  [...]
-- 
1.9.1

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers