[Cmake-commits] CMake branch, master, updated. v3.13.0-rc1-135-gaab69cc

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  aab69ccd9b20a7560d2c656bc1a53a4afa587240 (commit)
  from  4fc8e8b023c4ebce94a8baacbc086b72ec399aba (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=aab69ccd9b20a7560d2c656bc1a53a4afa587240
commit aab69ccd9b20a7560d2c656bc1a53a4afa587240
Author: Kitware Robot 
AuthorDate: Thu Oct 18 00:01:07 2018 -0400
Commit: Kitware Robot 
CommitDate: Thu Oct 18 00:01:07 2018 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index afd6f42..beafab2 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
 # CMake version number components.
 set(CMake_VERSION_MAJOR 3)
 set(CMake_VERSION_MINOR 13)
-set(CMake_VERSION_PATCH 20181017)
+set(CMake_VERSION_PATCH 20181018)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.13.0-rc1-134-g4fc8e8b

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  4fc8e8b023c4ebce94a8baacbc086b72ec399aba (commit)
   via  33632898e9a831931fdb96089a244f53cdc37caf (commit)
  from  78681bf001f4f29cf2f452327587669078a39461 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4fc8e8b023c4ebce94a8baacbc086b72ec399aba
commit 4fc8e8b023c4ebce94a8baacbc086b72ec399aba
Merge: 78681bf 3363289
Author: Brad King 
AuthorDate: Wed Oct 17 18:11:13 2018 +
Commit: Kitware Robot 
CommitDate: Wed Oct 17 14:11:18 2018 -0400

Merge topic 'improve-readme'

33632898e9 README: Suggest "sudo" for "make install"

Acked-by: Kitware Robot 
Merge-request: !2493


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=33632898e9a831931fdb96089a244f53cdc37caf
commit 33632898e9a831931fdb96089a244f53cdc37caf
Author: David Demelier 
AuthorDate: Wed Oct 17 10:53:03 2018 +0200
Commit: Brad King 
CommitDate: Wed Oct 17 14:09:51 2018 -0400

README: Suggest "sudo" for "make install"

diff --git a/README.rst b/README.rst
index 1e8561a..775463e 100644
--- a/README.rst
+++ b/README.rst
@@ -62,7 +62,7 @@ within the CMake source directory or any other build 
directory of your
 choice. Once this has finished successfully, run ``make`` and
 ``make install``.  In summary::
 
- $ ./bootstrap && make && make install
+ $ ./bootstrap && make && sudo make install
 
 Windows
 ^^^

---

Summary of changes:
 README.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits

[Cmake-commits] CMake branch, master, updated. v3.13.0-rc1-132-g78681bf

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  78681bf001f4f29cf2f452327587669078a39461 (commit)
   via  f21d811c7c4c9b61c6c81414b3e8803db392183c (commit)
   via  121a036f73665a18ccadeaf50b00cc623d8ed9df (commit)
   via  acfe53c58817c662b935fbe0f0443de298371731 (commit)
   via  b8bb6ba653df9d53d93824bb7185bf022e9bf2ef (commit)
   via  bf572ac952d7ddf2b7208efc56f104844aea72e2 (commit)
  from  cd4ed3ecb2ecfe3e2043ae0338a02323a508e0dd (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=78681bf001f4f29cf2f452327587669078a39461
commit 78681bf001f4f29cf2f452327587669078a39461
Merge: f21d811 121a036
Author: Brad King 
AuthorDate: Wed Oct 17 17:27:49 2018 +
Commit: Kitware Robot 
CommitDate: Wed Oct 17 13:27:56 2018 -0400

Merge topic 'better-empty-list-behavior'

121a036f73 cmListCommand: handle empty lists for list(REMOVE_AT)
acfe53c588 cmListCommand: make list(ACTION not_a_list) succeed when 
idempotent
bf572ac952 cmListCommand: check list(FILTER) operation before the list

Acked-by: Kitware Robot 
Merge-request: !2478


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f21d811c7c4c9b61c6c81414b3e8803db392183c
commit f21d811c7c4c9b61c6c81414b3e8803db392183c
Merge: cd4ed3e b8bb6ba
Author: Brad King 
AuthorDate: Wed Oct 17 17:26:27 2018 +
Commit: Kitware Robot 
CommitDate: Wed Oct 17 13:26:33 2018 -0400

Merge topic 'gem-string'

b8bb6ba653 cmGeneratorTarget::GetExportMacro: return const std::string*

Acked-by: Kitware Robot 
Merge-request: !2485


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=121a036f73665a18ccadeaf50b00cc623d8ed9df
commit 121a036f73665a18ccadeaf50b00cc623d8ed9df
Author: Ben Boeckel 
AuthorDate: Thu Oct 11 17:26:44 2018 -0400
Commit: Ben Boeckel 
CommitDate: Tue Oct 16 14:31:39 2018 -0400

cmListCommand: handle empty lists for list(REMOVE_AT)

Treat an empty list as a list with no valid bounds and return an error
message indicating that any given indices are out-of-bounds.

diff --git a/Help/release/dev/better-empty-list-behavior.rst 
b/Help/release/dev/better-empty-list-behavior.rst
index 12a131f..cd864f4 100644
--- a/Help/release/dev/better-empty-list-behavior.rst
+++ b/Help/release/dev/better-empty-list-behavior.rst
@@ -4,3 +4,6 @@ better-empty-list-behavior
 * The :command:`list` operations ``REMOVE_ITEM``, ``REMOVE_DUPLICATES``,
   ``SORT``, ``REVERSE``, and ``FILTER`` all now accept a non-existent variable
   as the list since these operations on empty lists is also the empty list.
+
+* The :command:`list` operation ``REMOVE_AT`` now indicates that the given
+  indices are invalid for a non-existent variable or empty list.
diff --git a/Source/cmListCommand.cxx b/Source/cmListCommand.cxx
index b46eb6d..b2acb90 100644
--- a/Source/cmListCommand.cxx
+++ b/Source/cmListCommand.cxx
@@ -1225,13 +1225,17 @@ bool 
cmListCommand::HandleRemoveAtCommand(std::vector const& args)
   const std::string& listName = args[1];
   // expand the variable
   std::vector varArgsExpanded;
-  if (!this->GetList(varArgsExpanded, listName)) {
-this->SetError("sub-command REMOVE_AT requires list to be present.");
-return false;
-  }
-  // FIXME: Add policy to make non-existing lists an error like empty lists.
-  if (varArgsExpanded.empty()) {
-this->SetError("REMOVE_AT given empty list");
+  if (!this->GetList(varArgsExpanded, listName) || varArgsExpanded.empty()) {
+std::ostringstream str;
+str << "index: ";
+for (size_t i = 1; i < args.size(); ++i) {
+  str << args[i];
+  if (i != args.size() - 1) {
+str << ", ";
+  }
+}
+str << " out of range (0, 0)";
+this->SetError(str.str());
 return false;
   }
 
diff --git a/Tests/RunCMake/list/EmptyRemoveAt0-stderr.txt 
b/Tests/RunCMake/list/EmptyRemoveAt0-stderr.txt
index b24a0ed..9368e88 100644
--- a/Tests/RunCMake/list/EmptyRemoveAt0-stderr.txt
+++ b/Tests/RunCMake/list/EmptyRemoveAt0-stderr.txt
@@ -1,4 +1,4 @@
 CMake Error at EmptyRemoveAt0.cmake:2 \(list\):
-  list REMOVE_AT given empty list
+  list index: mylist, 0 out of range \(0, 0\)
 Call Stack \(most recent call first\):
   CMakeLists.txt:3 \(include\)$
diff --git a/Tests/RunCMake/list/REMOVE_AT-EmptyList-result.txt 
b/Tests/RunCMake/list/REMOVE_AT-EmptyList-result.txt
new file mode 100644
index 000..d00491f
--- /dev/null
+++ b/Tests/RunCMake/list/REMOVE_AT-EmptyList-result.txt
@@ -0,0 +1 @@
+1
diff --git a/Tests/RunCMake/list/REMOVE_AT-EmptyList-stderr.txt 
b/Tests/RunCMake/list/REMOVE_AT-EmptyList-stderr.txt
new file 

[Cmake-commits] CMake branch, master, updated. v3.13.0-rc1-126-gcd4ed3e

[Kitware Robot]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".

The branch, master has been updated
   via  cd4ed3ecb2ecfe3e2043ae0338a02323a508e0dd (commit)
   via  004d9ebbd34fcd670b564c7234888016773b8404 (commit)
   via  b82b8705b2af4a7e3413de8aef6b3eb6371f08c4 (commit)
   via  275290375dbacc090962285da39e73687b44464f (commit)
   via  0c20d4d67b1f5da52da283f4237fb85a29385acd (commit)
   via  f7d92deff487810f21b4f7979a5fe1892fabd255 (commit)
   via  d543eb2260fff6c49ab6e5066d376c502e91bf9f (commit)
   via  1601388212e633d5e83d788cf6e52fd7c99e4883 (commit)
  from  88ef5737a25b40ce738041b8f9e00df20a131eb6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=cd4ed3ecb2ecfe3e2043ae0338a02323a508e0dd
commit cd4ed3ecb2ecfe3e2043ae0338a02323a508e0dd
Merge: 004d9eb d543eb2
Author: Brad King 
AuthorDate: Wed Oct 17 17:24:06 2018 +
Commit: Kitware Robot 
CommitDate: Wed Oct 17 13:24:27 2018 -0400

Merge topic 'ctor-remove'

d543eb2260 cmCustomCommand: remove the default constructor

Acked-by: Kitware Robot 
Reviewed-by: Brad King 
Merge-request: !2486


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=004d9ebbd34fcd670b564c7234888016773b8404
commit 004d9ebbd34fcd670b564c7234888016773b8404
Merge: b82b870 1601388
Author: Brad King 
AuthorDate: Wed Oct 17 17:23:44 2018 +
Commit: Kitware Robot 
CommitDate: Wed Oct 17 13:23:50 2018 -0400

Merge topic 'vs-improve'

1601388212 cmVisualStudio10TargetGenerator: Code improvement

Acked-by: Kitware Robot 
Merge-request: !2484


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b82b8705b2af4a7e3413de8aef6b3eb6371f08c4
commit b82b8705b2af4a7e3413de8aef6b3eb6371f08c4
Merge: 2752903 0c20d4d
Author: Brad King 
AuthorDate: Wed Oct 17 17:22:43 2018 +
Commit: Kitware Robot 
CommitDate: Wed Oct 17 13:22:49 2018 -0400

Merge topic 'FindLibinput-compile-options'

0c20d4d67b FindLibinput: Use _COMPILE_OPTIONS instead of _DEFINITIONS

Acked-by: Kitware Robot 
Merge-request: !2490


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=275290375dbacc090962285da39e73687b44464f
commit 275290375dbacc090962285da39e73687b44464f
Merge: 88ef573 f7d92de
Author: Brad King 
AuthorDate: Wed Oct 17 17:21:56 2018 +
Commit: Kitware Robot 
CommitDate: Wed Oct 17 13:22:04 2018 -0400

Merge topic 'ctest-coverage-gtm-percent'

f7d92deff4 CTest: Fix GTM coverage handling of entry point named "%"

Acked-by: Kitware Robot 
Merge-request: !2489


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0c20d4d67b1f5da52da283f4237fb85a29385acd
commit 0c20d4d67b1f5da52da283f4237fb85a29385acd
Author: Frederik Gladhorn 
AuthorDate: Tue Oct 16 15:56:09 2018 +0200
Commit: Brad King 
CommitDate: Tue Oct 16 11:07:41 2018 -0400

FindLibinput: Use _COMPILE_OPTIONS instead of _DEFINITIONS

The value may contain flags.

diff --git a/Modules/FindLibinput.cmake b/Modules/FindLibinput.cmake
index df66cff..1057c91 100644
--- a/Modules/FindLibinput.cmake
+++ b/Modules/FindLibinput.cmake
@@ -26,7 +26,7 @@ This will define the following variables in your project:
   the libraries to link against to use libinput.
 ``Libinput_INCLUDE_DIRS``
   where to find the libinput headers.
-``Libinput_DEFINITIONS``
+``Libinput_COMPILE_OPTIONS``
   this should be passed to target_compile_options(), if the
   target is not used for linking
 
@@ -38,7 +38,7 @@ This will define the following variables in your project:
 find_package(PkgConfig QUIET)
 pkg_check_modules(PKG_Libinput QUIET libinput)
 
-set(Libinput_DEFINITIONS ${PKG_Libinput_CFLAGS_OTHER})
+set(Libinput_COMPILE_OPTIONS ${PKG_Libinput_CFLAGS_OTHER})
 set(Libinput_VERSION ${PKG_Libinput_VERSION})
 
 find_path(Libinput_INCLUDE_DIR
@@ -69,7 +69,7 @@ if(Libinput_FOUND AND NOT TARGET Libinput::Libinput)
   add_library(Libinput::Libinput UNKNOWN IMPORTED)
   set_target_properties(Libinput::Libinput PROPERTIES
 IMPORTED_LOCATION "${Libinput_LIBRARY}"
-INTERFACE_COMPILE_OPTIONS "${Libinput_DEFINITIONS}"
+INTERFACE_COMPILE_OPTIONS "${Libinput_COMPILE_OPTIONS}"
 INTERFACE_INCLUDE_DIRECTORIES "${Libinput_INCLUDE_DIR}"
   )
 endif()

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f7d92deff487810f21b4f7979a5fe1892fabd255
commit f7d92deff487810f21b4f7979a5fe1892fabd255
Author: Joseph Snyder 
AuthorDate: Mon Oct 15 13:57:42 2018 +
Commit: Brad King 
CommitDate: Tue Oct 16 10:59:09 2018 -0400

CTest: Fix GTM coverage handling of entry point named "%"

Removing the "%" character from the name of the routine in the line

Re: [CMake] Pre-install targets?

[David Thompson]

Hi all,

After some hallway conversation, here is a follow-up:

The consensus was that there were 2 options for the documentation target:

+ Leave documentation out of the install step when documentation is not built 
as part of the ALL target.
+ Change the configuration option for documentation from a boolean to a 
tri-state enum, i.e.,

set(${PROJECT}_BUILD_DOCUMENTATION "never" CACHE STRING "When to build 
documentation.")
set_property(CACHE ${PROJECT}_BUILD_DOCUMENTATION PROPERTY STRINGS never 
manual always)

 so that automated builds for continuous integration can function (using 
"always" or "never")
 while developers can enable documentation but not be forced to refresh it 
every time they
 modify source code (using "manual").

For the latter, a recent change[1] to CMake has made the execution of 
install-rules consistently ordered when processing subdirectories, so it is 
possible to make the INSTALL target build documentation as needed with 
something like:

   if (${PROJECT}_BUILD_DOCUMENTATION STREQUAL "manual")
 install(CODE "execute_process(COMMAND \"${CMAKE_COMMAND}\" cmake --build 
\"${CMAKE_BINARY_DIR}\" --target docs --config $)")
   endif()

so long as care is taken within each directory's CMakeLists.txt to place the 
above before any install() directives related to the generated documentation.

David

[1]: https://gitlab.kitware.com/cmake/cmake/merge_requests/2434

> On Oct 11, 2018, at 09:09, David Thompson  wrote:
> 
> Hi all,
> 
> Is there a way to force a custom target (i.e., ADD_CUSTOM_TARGET) to be built 
> just before installation?
> 
> We have documentation added as a custom target that is **not** passed the 
> "ALL" keyword because generating the documentation is slow. However, that 
> target creates files that have a matching INSTALL, so "make install" or 
> "ninja install" will fail unless the target is built before installation. We 
> want to encourage developers to configure with documentation turned on, but 
> want buildbot/dashboard builds to work without magic options or special 
> configuration.
> 
> Along those lines:
> 
> 1. Is there any ordering of INSTALL(CODE ...) relative to INSTALL(FILES ...)? 
> If it is guaranteed to run first, we could force the target to build that way.
> 
> 2. Is there really nothing to replace the deprecated PRE_INSTALL_SCRIPT 
> property?
> 
>   Thanks,
>   David

-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] [ANNOUNCE] CMake 3.13.0-rc1 is ready for testing

[Robert Maynard]

Thanks for spotting this and this will need to be handled for 3.13. I
have opened an issue to track the progress of the fix:
https://gitlab.kitware.com/cmake/cmake/issues/18466
On Wed, Oct 17, 2018 at 9:37 AM Hendrik Sattler  wrote:
>
> Zitat von Robert Maynard :
> > * The "BundleUtilities" module may no longer be included at
> >   configure time. This was always a bug anyway. See policy "CMP0080".
>
> This now warns about the use of DeployQt4.cmake that ships with CMake.
> So this module should be fixed?
> At least it should set this policy to OLD for itself to avoid warnings
> for users that cannot change anything about it -> annoying.
>
> HS
>
>
> --
>
> 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:
> https://cmake.org/mailman/listinfo/cmake
-- 

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:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] [ANNOUNCE] CMake 3.13.0-rc1 is ready for testing

[Hendrik Sattler]

Zitat von Robert Maynard :

* The "BundleUtilities" module may no longer be included at
  configure time. This was always a bug anyway. See policy "CMP0080".


This now warns about the use of DeployQt4.cmake that ships with CMake.
So this module should be fixed?
At least it should set this policy to OLD for itself to avoid warnings  
for users that cannot change anything about it -> annoying.


HS


--

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:
https://cmake.org/mailman/listinfo/cmake

[cmake-developers] CMake Server and the "Language Server Protocol" support [Qt Creator 4.8 / Visual Studio Code]

[Cristian Adam]

Hi,

With the announcement of Qt Creator 4.8 Beta
  we can
see that it supports Microsoft's Language Server Protocol
.

How far is CMake from having such support in server mode?

Stephen Kelly had this in his January 2016's CMake Daemon client
demonstration . Having watched
that video I feel the urge of compiling his code and having that tool today.

Having that level of integration makes everything else feel like editing in
Notepad.

If such support would be available in Qt Creator, and Visual Studio Code
etc., people wouldn't rant
 that much
about CMake's language or documentation.

Cheers,
Cristian.
-- 

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:
https://cmake.org/mailman/listinfo/cmake-developers

Re: [cmake-developers] [ANNOUNCE] CMake 3.13.0-rc1 is ready for testing

[Rolf Eike Beer]

Am 2018-10-09 20:17, schrieb Brad King:

On 10/09/2018 02:00 PM, Rolf Eike Beer wrote:

Seems like you missed one part of the announcement mail ;)

Policies
==


The announcement comes from the release notes, and all policies
are mentioned there in relevant bullets.  We've never called them
out separately in such notes.  One can always see the list here:


https://cmake.org/cmake/help/v3.13/manual/cmake-policies.7.html#policies-introduced-by-cmake-3-13

separated by version.


The idea was that someone like me would look on the announcement and say 
"hey, these 2 policies should be set to new even in my code supporting 
old CMake versions because it makes sense to us".


Eike
--

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:
https://cmake.org/mailman/listinfo/cmake-developers

Re: [CMake] Error using sudo ./bootstrap && make && make install

[David Demelier]

Le 16/10/2018 à 23:04, Frank Tocci a écrit :

Hello,

I am trying to install Cmake and I am running into an error when I 
enter the install directory and run

sudo ./bootstrap && make && make install
as specified in the README file


Hello,

You're not supposed to do sudo bootstrap. You should always build as 
your user. Only make install has to be run as root.


So do the following:

./boostrap

make

sudo make install

I'll update the README.

regards


--

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:
https://cmake.org/mailman/listinfo/cmake