[cmake-developers] [PATCH] Improve encoding handling on Windows

On Windows getenv uses ANSI codepage so it needs to be encoded to internally used encoding (eg. UTF-8). Here we use _wgetenv instead and encode that. Also typically Windows applications (eg. MSVC compiler) use current console's codepage for output to pipes so we need to encode that to internally

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

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

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

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

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

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

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

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

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

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

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

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:

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

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

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

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

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

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

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

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

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

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

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

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:

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

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

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

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

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

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

Re: [cmake-developers] cmake -E capabilities

On 06/30/2016 09:51 AM, Tobias Hunger wrote: > Compared to the bug report mentioned above the fields "multiconfig" and > "recursive" are missing. I could not figure out how to get that information:-/ There is no "recursive" generator, so that does not belong in the example anyway. The Makefile

Re: [cmake-developers] cmake -E capabilities

"Eclipse CDT4", > "KDevelop3", > "Kate", > "Sublime Text 2" > ], > "name" : "Unix Makefiles", > "toolSetSupport" : false > } >], >"

[cmake-developers] cmake -E capabilities

"CodeLite", "Eclipse CDT4", "KDevelop3", "Kate", "Sublime Text 2"  ],  "name" : "Unix Makefiles",  "toolSetSupport" : false   }    ],    "server-

Re: [cmake-developers] adding FindJsonCpp

Hi, 2016-06-29 19:31 GMT+02:00 Ben Boeckel : > On Wed, Jun 29, 2016 at 17:36:45 +0200, Farbos a wrote: >> I have a concern with generating package configs: >> >> 1 It seems to contain absolute path, so not really portable with git. > > The actual config files are