Re: [cmake-developers] Android variables

On 13-Nov-16 00:48, Florent Castelli wrote: > On 12/11/2016 13:35, Ruslan Baratov wrote: >> On 12-Nov-16 19:09, Florent Castelli wrote: >>> On 12/11/2016 06:53, Ruslan Baratov wrote: >>>> On 12-Nov-16 08:21, Florent Castelli wrote: >>>>> On 10/11/20

Re: [cmake-developers] Android variables

On 12-Nov-16 19:09, Florent Castelli wrote: > On 12/11/2016 06:53, Ruslan Baratov wrote: >> On 12-Nov-16 08:21, Florent Castelli wrote: >>> On 10/11/2016 16:05, Ruslan Baratov via cmake-developers wrote: >>>> Hi, >>>> >>>> I wonder i

Re: [cmake-developers] Android variables

On 12-Nov-16 08:21, Florent Castelli wrote: > On 10/11/2016 16:05, Ruslan Baratov via cmake-developers wrote: >> Hi, >> >> I wonder if it's possible to introduce next variables describing Android >> tools: >> * C preprocessor. Similar to CMAKE_CXX_COMPILER

Re: [cmake-developers] Android variables

On 11-Nov-16 21:09, Brad King wrote: > On 11/10/2016 10:46 PM, Ruslan Baratov wrote: >> the value >> "${CMAKE_CXX_ANDROID_TOOLCHAIN_PREFIX}cpp${CMAKE_CXX_ANDROID_TOOLCHAIN_SUFFIX}" > This expression is the documented way to get the paths to the Android tools. > I see no reason to add a

Re: [cmake-developers] Android variables

On 10-Nov-16 23:05, Ruslan Baratov via cmake-developers wrote: > * CMAKE_CXX_COMPILER = > /toolchains/${ANDROID_TOOLCHAIN_MACHINE_NAME}-4.9/prebuilt/linux-x86_64/bin/${ANDROID_TOOLCHAIN_MACHINE_NAME}-g++ Actually there are more variables here, ANDROID_COMPILER_V

Re: [cmake-developers] Android variables

string(REGEX REPLACE "-$" "" ||ANDROID_TOOLCHAIN_MACHINE_NAME|| "${||ANDROID_TOOLCHAIN_MACHINE_NAME||}") || ||? Ruslo ||On 11-Nov-16 00:29, Brad King wrote: > On 11/10/2016 10:05 AM, Ruslan Baratov via cmake-developers wrote: >> variables describing Android tools:

[cmake-developers] Android variables

Hi, I wonder if it's possible to introduce next variables describing Android tools: * C preprocessor. Similar to CMAKE_CXX_COMPILER the variable that will contain the path to preprocessor. Example: * CMAKE_CXX_COMPILER =

Re: [cmake-developers] Remove RPATH on install

On 28-Sep-16 23:34, Brad King wrote: On 09/28/2016 04:09 PM, Ruslan Baratov via cmake-developers wrote: ` -Wl,-rpath,` to CMAKE_EXE_LINKER_FLAGS. That adds it in a way that hides its presence from CMake. CMake has its own way to specify RPATH entries in the build tree. It will replace

[cmake-developers] Remove RPATH on install

Hi, I want to link the library to all executables in project so I'm adding ` -Wl,-rpath,` to CMAKE_EXE_LINKER_FLAGS. That works fine however after install step this RPATH was not removed and full path to remains as part of executable in LC_RPATH. As far as I understand there is no such

Re: [cmake-developers] Downloading file from S3 private bucket

Ruslo On 13-Sep-16 16:28, Ruslan Baratov wrote: On 13-Sep-16 15:58, Brad King wrote: On 09/13/2016 07:42 AM, Ruslan Baratov via cmake-developers wrote: Will it be okay if CMake will optionally depend on OpenSSL? Or other third party crypto library? Currently the only place that needs it is through

Re: [cmake-developers] Downloading file from S3 private bucket

On 13-Sep-16 15:58, Brad King wrote: On 09/13/2016 07:42 AM, Ruslan Baratov via cmake-developers wrote: Will it be okay if CMake will optionally depend on OpenSSL? Or other third party crypto library? Currently the only place that needs it is through `curl`, and that uses either OpenSSL

[cmake-developers] Downloading file from S3 private bucket

Hi, Currently I'm investigating possibilities of downloading files from private S3 bucket using CMake. The only real issue I see for now is the computing of HMAC + SHA1. This look like a work for some new cryptographic module in family of 'string' functions similar to 'string(MD5|SHA1|...)'.

Re: [cmake-developers] [patch] One more pattern for extracting file name from URL

On 05-Jul-16 23:26, Brad King wrote: On 07/05/2016 04:13 PM, Ruslan Baratov wrote: Works fine on my tests. Thanks for testing! However I still vote for using default value for 'fname' instead of FATAL_ERROR. I think that behavior would be surprising. Not such surprising as some error in

Re: [cmake-developers] [patch] One more pattern for extracting file name from URL

On 05-Jul-16 22:03, Brad King wrote: On 07/01/2016 03:35 PM, Brad King wrote: I don't think we should duplicate the "(\\.|=)(7z|tar|tar\\.bz2|tar\\.gz|tar\\.xz|tbz2|tgz|txz|zip)$" expression. The stripping of ?.* can be done earlier, or done as part of the main match. Please try this

Re: [cmake-developers] [patch] One more pattern for extracting file name from URL

On 05-Jul-16 20:31, Ben Boeckel wrote: On Tue, Jul 05, 2016 at 19:49:46 +0300, Ruslan Baratov wrote: Archive can be unpacked by "cmake -E tar xf" which detect type automatically as far as I understand. At least this one used internally by ExternalProject (see the testing I've made before).

Re: [cmake-developers] [patch] One more pattern for extracting file name from URL

On 05-Jul-16 18:50, Ben Boeckel wrote: On Tue, Jul 05, 2016 at 18:43:25 +0300, Ruslan Baratov wrote: By default not, goes to -prefix/src/archive.tar . Right, but if a download directory is set, this won't work. Can the project name at least be added to the name? If user are forcing directory

Re: [cmake-developers] [patch] One more pattern for extracting file name from URL

On 01-Jul-16 15:01, Ruslan Baratov via cmake-developers wrote: Hi, With attached patch it's possible to extract name from URLs like 'https://.../archive.tar.gz?a=x=y'. Ruslo >From 5284eedbd1b038aab2eab73252eb41914afb14e1 Mon Sep 17 00:00:00 2001 From: Ruslan Baratov <rusla

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

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

Re: [cmake-developers] [patch] One more pattern for extracting file name from URL

On 01-Jul-16 16:04, Ben Boeckel wrote: On Fri, Jul 01, 2016 at 08:58:16 -0400, Brad King wrote: Also, the `([^/]*)\\?.*` part of the regex should be more like `([^/?]*)\\?.*` to avoid eagerly matching early `?`. This should also probably skip '#' characters for URLs with anchors. --Ben

Re: [cmake-developers] [patch] One more pattern for extracting file name from URL

On 01-Jul-16 15:58, Brad King wrote: On 07/01/2016 08:01 AM, Ruslan Baratov via cmake-developers wrote: With attached patch it's possible to extract name from URLs like 'https://.../archive.tar.gz?a=x=y'. Thanks. elseif(NOT "${fname}" MATCHES "(\\.|=)(7z|tar|tar\\.b

[cmake-developers] [patch] One more pattern for extracting file name from URL

Hi, With attached patch it's possible to extract name from URLs like 'https://.../archive.tar.gz?a=x=y'. Ruslo >From 0bab30e859541dde51e9e21d3a22ec80a649a30a Mon Sep 17 00:00:00 2001 From: Ruslan Baratov Date: Fri, 1 Jul 2016 14:55:29 +0300 Subject: [PATCH] Add

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 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 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 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 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

[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] [patch] iOS combined, some fixes

Great, thank you! On 25-Jun-16 14:56, Gregor Jasny wrote: On 21/06/16 18:48, Ruslan Baratov wrote: Is the patch applied? Let me know if there are any questions left about it. Pushed into next. Sorry for the delay. -- Powered by www.kitware.com Please keep messages on-topic and check

Re: [cmake-developers] [patch] iOS combined, some fixes

Is the patch applied? Let me know if there are any questions left about it. On 15-Jun-16 23:38, Ruslan Baratov via cmake-developers wrote: On 15-Jun-16 22:59, Gregor Jasny wrote: Hello, Thanks for the patch! On 15/06/16 16:41, Ruslan Baratov wrote: Sending some fixes found by testing

Re: [cmake-developers] [patch] iOS combined, some fixes

On 15-Jun-16 22:59, Gregor Jasny wrote: Hello, Thanks for the patch! On 15/06/16 16:41, Ruslan Baratov wrote: Sending some fixes found by testing with Xcode 7.3 We were chasing some errors regarding the unified build some time ago. But it appeared some for of heisenbug: the more I looked the

[cmake-developers] [patch] iOS combined, some fixes

Hi, Sending some fixes found by testing with Xcode 7.3 Ruslo >From 2026570b6f3c7c950ffbb83effa5a176d9133c89 Mon Sep 17 00:00:00 2001 From: Ruslan Baratov Date: Tue, 14 Jun 2016 23:44:41 +0300 Subject: [PATCH 1/2] CMakeIOSInstallCombined: add some sanity checks ---

Re: [cmake-developers] [Patch] ExternalProject: fix retry logic if error occurs

It's a little bit tricky to split refactor/new functionality exact but I've created several patches with step-by-step changes. Hope this helps in review. Ruslo On 18-May-16 22:50, Brad King wrote: On 05/18/2016 03:30 PM, Ruslan Baratov via cmake-developers wrote: I've attached patch

[cmake-developers] [Patch] ExternalProject: fix retry logic if error occurs

Hi, For now download retry attempt occurs in ExternalProject only if hash of archive mismatch. If error happens then script stop with FATAL_ERROR (example: https://ci.appveyor.com/project/ingenue/hunter/build/1.0.448/job/22kdl633f9w503ut). I've attached patch with applying retry logic in

Re: [cmake-developers] CMake API for warnings

This one looks like a plan. However I will not be able to work on the feature till ~15 May. So if anybody have a free time to start this work - feel free to do it and share patches :) Thanks, Ruslo On 22-Apr-16 20:36, Brad King wrote: On 04/20/2016 09:50 AM, Ruslan Baratov wrote: 1)

Re: [cmake-developers] CMake API for warnings

On 26-Apr-16 01:58, Brad King wrote: On 04/23/2016 12:11 AM, Ruslan Baratov wrote: It means ignoring directory properties. So by default we will inherit settings. [snip] To disable inheriting we need to add extra argument (?) to *_compile_warnings: add_compile_warnings(DISABLE warn-A)

Re: [cmake-developers] CMake API for warnings

On 22-Apr-16 20:36, Brad King wrote: On 04/20/2016 09:50 AM, Ruslan Baratov wrote: 1) add_compile_warnings * similar to add_definitions, add_compile_options * modify COMPILE_WARNINGS directory property (append) 2) target_compile_warnings * similar to target_compile_options,

Re: [cmake-developers] CMake API for warnings

So here is a summary of this feature so far: Introducing new 3 functions for controlling compiler warnings: 1) add_compile_warnings * similar to add_definitions, add_compile_options * modify COMPILE_WARNINGS directory property (append) 2) target_compile_warnings * similar to

Re: [cmake-developers] CMake API for warnings

On 13-Apr-16 01:00, Brad King wrote: Hi Ruslo, Sorry for taking so long to respond here. I've been hoping to find time to think through the design deeply but I don't know when that may happen. Here is some more feedback. I invite others to jump in here. Without more interest I'm hesitant to

Re: [cmake-developers] CMake API for warnings

Sounds good? On 06-Apr-16 01:03, Ruslan Baratov via cmake-developers wrote: On 05-Apr-16 21:03, Brad King wrote: On 03/31/2016 12:47 PM, Ruslan Baratov wrote: What about 3 properties containing list of 's (groups unexpanded): * COMPILE_WARNINGS_DISABLE # e.g. "shift-sign-overflow;u

Re: [cmake-developers] CMake API for warnings

On 05-Apr-16 21:03, Brad King wrote: On 03/31/2016 12:47 PM, Ruslan Baratov wrote: What about 3 properties containing list of 's (groups unexpanded): * COMPILE_WARNINGS_DISABLE # e.g. "shift-sign-overflow;unused" * COMPILE_WARNINGS_ENABLE # e.g. "ALL" * COMPILE_WARNINGS_TREAT_AS_ERROR # e.g.

Re: [cmake-developers] CMake API for warnings

On 31-Mar-16 20:37, Brad King wrote: On 03/29/2016 11:24 AM, Ruslan Baratov wrote: OTOH many such switches are so specific that they should not be abstracted and can instead be added to COMPILE_OPTIONS with a $ genex guard. What about generating nothing for such cases? Yes, that makes sense.

Re: [cmake-developers] CMake API for warnings

On 28-Mar-16 21:05, Brad King wrote: On 03/28/2016 01:49 AM, Geoffrey Viola wrote: Thanks for the feedback. I’ll have to look more in-depth at Xcode specific issues. Take a look at this approach: * https://github.com/ruslo/sugar/wiki/Cross-platform-warning-suppression I took a look at your

Re: [cmake-developers] CMake API for warnings

On 29-Mar-16 21:24, Brad King wrote: On 03/29/2016 09:09 AM, Ruslan Baratov wrote: As a general note obviously I've used another approach because I decide to create CMake module which can be used with regular CMake versions :) Of course implementing this in CMake "from the box" is best. Are we

Re: [cmake-developers] CMake API for warnings

On 28-Mar-16 12:49, Geoffrey Viola wrote: Thanks for the feedback. I’ll have to look more in-depth at Xcode specific issues. > Take a look at this approach: > * https://github.com/ruslo/sugar/wiki/Cross-platform-warning-suppression I took a look at your repository. It’s very sophisticated.

Re: [cmake-developers] CMake API for warnings

On 28-Mar-16 21:05, Brad King wrote: On 03/28/2016 01:49 AM, Geoffrey Viola wrote: Thanks for the feedback. I’ll have to look more in-depth at Xcode specific issues. Take a look at this approach: * https://github.com/ruslo/sugar/wiki/Cross-platform-warning-suppression I took a look at your

Re: [cmake-developers] CMake API for warnings

I like an effort but not an implementation: * It would be nice to not to set flags globally since we have more fine control options like target_compile_options (i.e. different target may have different warning settings) * this will not work for Xcode since warnings should be set by

Re: [cmake-developers] CMake aliasing system

<mailto:john@example.com> --branch="master" > git push --remote="git://awesome.example.com <http://awesome.example.com>" This is a complete nonsense! So I'm planning to make a fork anyway and do some experiments even if it will not acce

Re: [cmake-developers] CMake aliasing system

some experiments even if it will not accepted to upstream. Ruslo Tamas On Mon, Mar 14, 2016 at 4:22 PM, Ruslan Baratov via cmake-developers <cmake-developers@cmake.org <mailto:cmake-developers@cmake.org>> wrote: On 14-Mar-16 21:59, Brad King wrote: On 03/12/2016 08:04 AM,

Re: [cmake-developers] CMake aliasing system

On 14-Mar-16 21:59, Brad King wrote: On 03/12/2016 08:04 AM, Ruslan Baratov via cmake-developers wrote: I guess it is a well known fact that cmake command is almost never executed alone and for non-trivial examples usually hold some extra arguments (home directory, build directory, verbosity

[cmake-developers] Support CMAKE_IOS_INSTALL_COMBINED for single architecture targets

Hi, Though user can explicitly set CMAKE_IOS_INSTALL_COMBINED=OFF for targets with empty list of supported architectures for given SDK (say simulator) I think it make sense to handle this case correctly in CMake module too. Patch with fix and test attached. Thanks, Ruslo >From

[cmake-developers] CMake aliasing system

Hi, I guess it is a well known fact that cmake command is almost never executed alone and for non-trivial examples usually hold some extra arguments (home directory, build directory, verbosity level, toolchains, options, ...). Also I guess that such commands doesn't change from day-to-day

Re: [cmake-developers] Namespaces

On 29-Jan-16 01:17, Stephen Kelly wrote: Pau Garcia i Quiles wrote: add_subdirectory(pugixml/scripts) add_subdirectory(QtZeroConf) add_subdirectory(QtDropBox) add_subdirectory(websocketpp) This is an easy way to work with third-party dependences. Unfortunately this is 'easy, obvious and

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

On 21-Dec-15 17:19, Bartosz Kosiorek wrote: Thanks Ruslan for explanation. Currently we already building fat library for arm (armv7;armv7s;arm64) and x86 (i386;x86_64). That's why my original assumption was that it could be easily enabled for Simulator/device

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

On 18-Dec-15 22:46, Bartosz Kosiorek wrote: Thank you all for your tips/advice. From our experience IDE generators (eg. Visual Studio, Xcode) is much slower than Make or Ninja. I will attach benchmarks later. Unfortunately I'm unable to build Universal libraries for x86 and arm

Re: [cmake-developers] [PATCH] Re: Create subdirectories in Resource directory for Frameworks and Application bundle.

On 12-Dec-15 07:26, Bartosz Kosiorek wrote: Hi I have updated current documentation with examples, to reflect current status of CMake in OSX/iOS support. Such information is very useful for novice CMake developers, and it saves an hours of digging through mailing list and websites. This is

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

On 12-Dec-15 10:08, Bartosz Kosiorek wrote: Thanks Ruslan. I would like to create instruction which is universal for all generators. I think it's not possible. E.g. IOS_INSTALL_COMBINED will work only for Xcode. Currently we would like to support both Make/Ninja and Xcode generators,

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

On 12-Dec-15 03:46, Bartosz Kosiorek wrote: Hi To enable iOS build, I'm using following settings in CMakeLists.txt: set(APPLE_PLATFORM "iphonesimulator") I think this one not needed. Can't find any place where it parsed. set(CMAKE_OSX_SYSROOT

Re: [cmake-developers] Please comment on ios-universal topic

On 10-Dec-15 13:55, Gregor Jasny wrote: Hello, On 09/12/15 10:21, Ruslan Baratov wrote: IOS_INSTALL_COMBINED_BINARY Just to clarify you want to leave only one variable IOS_INSTALL_COMBINED_BINARY for the device + simulator on iOS platforms. Other platforms (in future) will be controlled by

Re: [cmake-developers] Please comment on ios-universal topic

On 09-Dec-15 04:51, Gregor Jasny wrote: Hello, On 02/12/15 13:44, Bartosz Kosiorek wrote: I would like to propose to rename property name to INSTALL_IOS_UNIVERSAL_LIBS. My thoughts about the property name: I added the necessary functionality to also combine Frameworks and App Bundles. So

Re: [cmake-developers] Fw: Please comment on ios-universal topic

On 03-Dec-15 14:57, Bartosz Kosiorek wrote: Thanks Ruslan for feedback. I think that this new property should work also for FRAMEWORK and should support both OSX and iOS In that way it is already done for: - for SHARED library adding FRAMEWORK property produce correct Framework for iOS or

Re: [cmake-developers] Fw: Please comment on ios-universal topic

On 02-Dec-15 19:44, Bartosz Kosiorek wrote: Hi. Currently we already support similar target properties: - INSTALL_NAME_DIR - INSTALL_RPATH - INSTALL_RPATH_USE_LINK_PATH It will be great to follow the same name convention. Because this new property is only applicable for INSTALL step, I would

Re: [cmake-developers] [PATCH] FindBoost: Add imported targets

On 17-Nov-15 15:48, Roger Leigh wrote: On 17/11/2015 07:53, Ruslan Baratov wrote: On 16-Nov-15 21:01, rle...@codelibre.net wrote: I have attached a patch to add imported targets to FindBoost, in the form of Boost:: (e.g. Boost::date_time) or Boost::Boost as a generic interface library for

Re: [cmake-developers] [PATCH] iOS Framework Bundle support

On 13-Nov-15 20:59, Bartosz Kosiorek wrote: Hello. Main reason for using Makefile instead of Xcode is performance reason. Xcode generator is much slower that Makefile in our project. The performance was improved in Cmake 3.2 but still it is much slower on Xcode. Similar slowness could be

Re: [cmake-developers] [PATCH] FindBoost: Add imported targets

On 16-Nov-15 21:01, rle...@codelibre.net wrote: I have attached a patch to add imported targets to FindBoost, in the form of Boost:: (e.g. Boost::date_time) or Boost::Boost as a generic interface library for header-only components. Since it's `Boost::date_time` I expect that it will be

Re: [cmake-developers] Patch: install universal iOS libraries

On 28-Oct-15 00:56, Gregor Jasny wrote: Hello, I hope to have finished the review by end of this week. On 25/10/15 15:34, Ruslan Baratov wrote: + set(cmd lipo -info "${filename}") Minor nitpick: lipo should probably be called via xcrun. Otherwise it might not know how to handle new

Re: [cmake-developers] Filesystem timestamp checks

On 21-Oct-15 03:25, Ben Boeckel wrote: On Wed, Oct 21, 2015 at 01:53:42 +0600, Ruslan Baratov wrote: On 20-Oct-15 21:42, Ben Boeckel wrote: On Tue, Oct 20, 2015 at 04:56:47 +0600, Ruslan Baratov via cmake-developers wrote: * I don't want to patch every script. To be precise I prefer to &quo

Re: [cmake-developers] Filesystem timestamp checks

On 20-Oct-15 21:42, Ben Boeckel wrote: On Tue, Oct 20, 2015 at 04:56:47 +0600, Ruslan Baratov via cmake-developers wrote: * I don't want to patch every script. To be precise I prefer to "Fix something in one place so it works 100% and forget about it" then "Every time I start cr

[cmake-developers] [Patch] Documentation file(GLOB): ordering note

Add a note that order of files is not defined >From 9cd9fbb12ef73b72526190573cba0392ead5fd9f Mon Sep 17 00:00:00 2001 From: Ruslan Baratov Date: Wed, 21 Oct 2015 02:53:37 +0600 Subject: [PATCH] Documentation: file(GLOB*) order is not guaranteed Since this command use

Re: [cmake-developers] Filesystem timestamp checks

On 19-Oct-15 19:30, Brad King wrote: On 10/15/2015 03:58 PM, Ruslan Baratov wrote: 3. Apply changes to CMakeLists.txt "immediately", CMakeLists.txt modification time 105 4. Run rebuild: `cmake --build _builds`. Since CMakeLists.txt (105) is not "newer" then Makefile (105) there will be no

[cmake-developers] Filesystem timestamp checks

Originally from: https://cmake.org/Bug/view.php?id=15769 Here is the scenario of not triggering rebuild of project while CMakeLists.txt changed: 1. Create CMakeLists.txt (modification time 100 units) 2. Run generate (create project from scratch): `cmake -H. -B_builds`. Takes 5 units, Makefile

Re: [cmake-developers] automatically download library

On 08-Oct-15 18:06, Marsel Galimullin wrote: The idea is that CMake has possibility to contact with package managers for download necessary libraries. If “find_package” can’t find a library, it need to call apt-get install. Example: auto_downland(apt-get) find_package (Boost COMPONENTS

Re: [cmake-developers] [CMake 0015769]: OS X: Filesystem timestamp checks use only 1s resolution

On 10-Oct-15 01:00, Ruslan Baratov via cmake-developers wrote: On 08-Oct-15 21:03, Mantis Bug Tracker wrote: The following issue has been ASSIGNED. == https://cmake.org/Bug/view.php?id=15769

Re: [cmake-developers] [CMake 0015769]: OS X: Filesystem timestamp checks use only 1s resolution

On 08-Oct-15 21:03, Mantis Bug Tracker wrote: The following issue has been ASSIGNED. == https://cmake.org/Bug/view.php?id=15769 == Reported By:

Re: [cmake-developers] Patch: install universal iOS libraries

On 07-Oct-15 16:57, Gregor Jasny wrote: Hello, thank you for working on this. This is really hairy stuff. On 24/09/15 11:10, Ruslan Baratov via cmake-developers wrote: Patches help to install universal iOS (device + simulator) libraries by triggering some extra instructions (build + fuse

[cmake-developers] Patch: install universal iOS libraries

Hi, Patches help to install universal iOS (device + simulator) libraries by triggering some extra instructions (build + fuse) after "regular" library installation finished. This behavior controlled by CMake variable CMAKE_IOS_INSTALL_UNIVERSAL_LIBS. = Example = > cat CMakeLists.txt

Re: [cmake-developers] Fixing bug #12506 (iOS install)

On 26-Aug-15 22:53, Gregor Jasny wrote: Hallo, On 13/08/15 12:56, Ruslan Baratov wrote: On 13-Aug-15 08:46, Gregor Jasny wrote: On 13/08/15 01:44, Ruslan Baratov via cmake-developers wrote: Sending patches with fix. Now it's possible to install simulator libraries by: cmake --build

Re: [cmake-developers] Setting up environment using ExternalProject_Add

On 11-Aug-15 07:49, James Johnston wrote: I have found it annoyingly difficult to set up an environment for a build when using ExternalProject_Add. I can confirm that there is an additional mess with the environment sometimes and not just about setting it (like vcvarsall.bat for Visual

Re: [cmake-developers] Fixing bug #12506 (iOS install)

On 13-Aug-15 08:46, Gregor Jasny wrote: Hi, On 13/08/15 01:44, Ruslan Baratov via cmake-developers wrote: Sending patches with fix. Now it's possible to install simulator libraries by: cmake --build _builds --config Release --target install -- -sdk iphonesimulator and device libraries

Re: [cmake-developers] Fixing bug #12506 (iOS install)

On 07-Aug-15 01:43, Ruslan Baratov via cmake-developers wrote: Hi, I'm thinking about fixing bug http://public.kitware.com/Bug/view.php?id=12506 and before I go deeper in CMake internals just want to ask is there any work-in-progress attempts already or hints/directions of how it can be done

Re: [cmake-developers] Fixing bug #12506 (iOS install)

On 07-Aug-15 11:31, Gregor Jasny wrote: Hi, On 07/08/15 00:43, Ruslan Baratov via cmake-developers wrote: Hi, I'm thinking about fixing bug http://public.kitware.com/Bug/view.php?id=12506 and before I go deeper in CMake internals just want to ask is there any work-in-progress attempts already

[cmake-developers] Fixing bug #12506 (iOS install)

Hi, I'm thinking about fixing bug http://public.kitware.com/Bug/view.php?id=12506 and before I go deeper in CMake internals just want to ask is there any work-in-progress attempts already or hints/directions of how it can be done? Thanks, Ruslo -- Powered by www.kitware.com Please keep

Re: [cmake-developers] [MODERN] CMake 3.3 vs Qt 5.5 vs MSVC2015

On 23-Jul-15 12:32, Konstantin Podsvirov wrote: Hi dear CMake developers! Meet modern CMake built on MSVC2015 c QtDialog based on Qt 5.5 from today :-) Windows 32bit: http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe Windows 64bit:

Re: [cmake-developers] find_package config mode search path rule #5 error prone

On 07-May-15 00:00, Tamás Kenéz wrote: Hi, The search path rule #5 reads: Search project build trees recently configured in a cmake-gui(1). This can be skipped if NO_CMAKE_BUILDS_PATH is passed. It is intended for the case when a user is building multiple dependent projects one after

[cmake-developers] find_dependency with optional dependencies

Hi, I'm trying to figure out what is the best way to use 'find_dependency' if dependent package is optional (e.g. can be controlled by some build option): # CMakeLists.txt option(BOO_WITH_FOO Build Boo with Foo ON) if(BOO_WITH_FOO) find_package(Foo CONFIG REQUIRED)

Re: [cmake-developers] BundleUtilities check exit code

On 10-Feb-15 19:01, Brad King wrote: On 02/09/2015 12:17 PM, Ruslan Baratov via cmake-developers wrote: This patch let do the check that exit code is 0, i.e. install_name_tool exits successfully. Applied with minor refactoring: BundleUtilities: Teach fixup_bundle to check install_name_tool

[cmake-developers] BundleUtilities check exit code

Hi, This patch let do the check that exit code is 0, i.e. install_name_tool exits successfully. Ruslan From 74a52160f7b74907acfcbca91b925ea5589019b7 Mon Sep 17 00:00:00 2001 From: Ruslan Baratov ruslan_bara...@yahoo.com Date: Mon, 9 Feb 2015 20:09:41 +0300 Subject: [PATCH] fixup_bundle: check

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

On 17-Dec-14 21:11, Matthew Woehlke wrote: On 2014-10-13 10:39, Brad King wrote: On 10/10/2014 07:45 AM, Ruslan Baratov wrote: Locking directory is equivalent to locking file `cmake.lock` in directory /path/to/shared/directory/: I think this can be activated buy a DIRECTORY option. Why do we

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

On 05-Dec-14 17:12, Brad King wrote: On 12/05/2014 09:10 AM, Ruslan Baratov wrote: file: Add LOCK subcommand to do file and directory locking http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e6db4c5a Great, thank you! So will this be applied to cmake 3.1.0? No, sorry. The feature

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

On 05-Dec-14 17:09, Brad King wrote: On 12/05/2014 09:03 AM, Ruslan Baratov wrote: Actually why not use 'strtoll' and 'long long' ? I'm not sure that function or type exists portably on some of the older host platforms we support. The long type should be plenty big for timeout values, and

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

On 25-Nov-14 21:29, Brad King wrote: * The background.(bat|sh) files need to have quoting to work with spaces in the path. Please try running tests with a source/build tree with spaces. * Instead of background scripts, can you have a parent process take a lock, run a child with a

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

On 17-Nov-14 18:06, Brad King wrote: Yes, please change to that so a proper error can be produced for the new API when 123xyz is given as a timeout, for example. Function added cmSystemTools::StringToInt Please look at adding a case to the test suite for this. An outer process could take the

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

ConvertToWindowsExtendedPath fix + tests From e994378d61e64136043d9db614762e79927766cb Mon Sep 17 00:00:00 2001 From: Ruslan Baratov ruslan_bara...@yahoo.com Date: Fri, 14 Nov 2014 21:09:35 +0400 Subject: [PATCH 1/6] Add class cmFileLockResult --- Source/cmFileLockResult.cxx | 111

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

On 14-Nov-14 22:58, Brad King wrote: - Please add more test cases covering all the file(LOCK) argument processing error messages. Done. Also I've found parse issue which is based on `sscanf` behaviour, e.g. string '123xyz' will be successfully parsed as a integer (%d). Same issue for

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

On 11-Nov-14 21:28, Brad King wrote: * All headers and sources need to include cmStandardIncludes.h first, directly or indirectly through other headers. It can affect the way certain standard library headers are preprocessed on some platforms, and needs to be consistent across all

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

Done On 31-Oct-14 16:39, Brad King wrote: On 10/31/2014 09:07 AM, Ruslan Baratov wrote: Does anybody ready to implement it or you want me to send the patches? Please work on the patches. You can use git format-patch to format them and post here either inline or as attachments. Thanks, -Brad

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

Does anybody ready to implement it or you want me to send the patches? Ruslo On 29-Oct-14 16:48, Brad King wrote: On 10/28/2014 04:28 PM, Ruslan Baratov wrote: What do you think about this: Thanks for drafting the signature. file( LOCK path [DIRECTORY] # if present locked file

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

On 13-Oct-14 18:39, Brad King wrote: With all the above in mind, please brainstorm and propose a more complete signature set. You can use the keyword/value pairing common in other commands to avoid needing a positional argument for every value. What do you think about this: file( LOCK

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

On 08-Oct-14 16:45, Brad King wrote: On 10/08/2014 07:52 AM, Ruslan Baratov wrote: Okay :) I just not sure that I understand to pass to some other process goal correctly. That was just an example of why one might want to drop management of the lock by CMake without actually unlocking it.

Re: [cmake-developers] New command 'file(LOCK_DIRECTORY ...)'

). Ruslo Thanks, David C. On Fri, Oct 10, 2014 at 7:45 AM, Ruslan Baratov via cmake-developers cmake-developers@cmake.org wrote: On 08-Oct-14 16:45, Brad King wrote: On 10/08/2014 07:52 AM, Ruslan Baratov wrote: Okay :) I just not sure that I understand to pass to some other process goal correctly

  1   2   >