[Cmake-commits] CMake branch, master, updated. v3.9.0-326-g6f08ce1

[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  6f08ce1a4f6b91a9911dde282f49f53f133c0593 (commit)
  from  a8d8d2fd05e65444e52adb5164a38f3c64b247d5 (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=6f08ce1a4f6b91a9911dde282f49f53f133c0593
commit 6f08ce1a4f6b91a9911dde282f49f53f133c0593
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Fri Jul 21 00:01:05 2017 -0400
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Fri Jul 21 00:01:05 2017 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 1f0d469..33c363b 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 9)
-set(CMake_VERSION_PATCH 20170720)
+set(CMake_VERSION_PATCH 20170721)
 #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
http://public.kitware.com/mailman/listinfo/cmake-commits

[CMake] Referencing an OBJECT library

[Edward Diener]

According to the CMake docs for an OBJECT library called, let's say, 
'xxx', the reference to that OBJECT library is through 
$. I understand this but I am curious about the 
reason for such syntax. After all a STATIC or SHARED library 'xxx' you 
can just use xxx to refer to the library. Why the difference in CMake 
syntax reference between OBJECT libraries added with the add_library 
command and STATIC or SHARED libraries added with the add_library command ?


--

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

Re: [CMake] file(COPY) is copying even if file hasn't changed

[Nicholas Devenish]

For what it's worth, I'm not seeing this on Sierra 10.12.5, CMake
3.9.0 on a simple test case of:

cmake_minimum_required(VERSION 3.5 FATAL_ERROR)
file(COPY afile DESTINATION .)

I ran through Instruments to check the otherwise silent copy, it
copies the first time but thereafter only stat calls are ever made,
the file timestamp stays matching the source, and even the INSTALL
option also gives the "Up-to-date" message. It looks as though a chmod
might be run, but that doesn't seem to affect the output stamp.

So it must be something more complicated. Are you able to reduce the
behaviour to a simple test-case?

Completely wild guess: Are you running on something different from
HFS, like APFS? If my reading of the chmod isn't wrong, I suppose *in
theory* a different filesystem could treat a chmod attempt as a
modification

Nick

On Thu, Jul 20, 2017 at 5:00 PM, Robert Dailey  wrote:
> FYI I decided to file an issue for this here:
> https://gitlab.kitware.com/cmake/cmake/issues/17087
>
> On Wed, Jul 19, 2017 at 4:05 PM, Robert Dailey  
> wrote:
>> Oh also file(INSTALL) does the same thing; the "Installing:" message
>> gets printed each time for the same file, and never says that it is
>> "up to date".
>>
>> On Wed, Jul 19, 2017 at 4:04 PM, Robert Dailey  
>> wrote:
>>> According to the documentation for file(COPY) [1]: "Copying preserves
>>> input file timestamps, and optimizes out a file if it exists at the
>>> destination with the same timestamp"
>>>
>>> However this is not the case. My host OS is Windows 10 and I'm using
>>> CMake 3.9.0-rc5. Each time my CMakeLists.txt is run, the file(COPY) is
>>> copying over the file even if it didn't change. The "date modified"
>>> timestamp for the destination file is updated. I do not want the copy
>>> to occur if the source file has not changed (this appears to be the
>>> intended behavior based on the documentation).
>>>
>>> Am I understanding this correctly or is this a bug?
>>>
>>> [1]: https://cmake.org/cmake/help/latest/command/file.html
> --
>
> 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
-- 

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

Re: [CMake] file(COPY) is copying even if file hasn't changed

[Robert Dailey]

FYI I decided to file an issue for this here:
https://gitlab.kitware.com/cmake/cmake/issues/17087

On Wed, Jul 19, 2017 at 4:05 PM, Robert Dailey  wrote:
> Oh also file(INSTALL) does the same thing; the "Installing:" message
> gets printed each time for the same file, and never says that it is
> "up to date".
>
> On Wed, Jul 19, 2017 at 4:04 PM, Robert Dailey  
> wrote:
>> According to the documentation for file(COPY) [1]: "Copying preserves
>> input file timestamps, and optimizes out a file if it exists at the
>> destination with the same timestamp"
>>
>> However this is not the case. My host OS is Windows 10 and I'm using
>> CMake 3.9.0-rc5. Each time my CMakeLists.txt is run, the file(COPY) is
>> copying over the file even if it didn't change. The "date modified"
>> timestamp for the destination file is updated. I do not want the copy
>> to occur if the source file has not changed (this appears to be the
>> intended behavior based on the documentation).
>>
>> Am I understanding this correctly or is this a bug?
>>
>> [1]: https://cmake.org/cmake/help/latest/command/file.html
-- 

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

[Cmake-commits] CMake branch, master, updated. v3.9.0-325-ga8d8d2f

[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  a8d8d2fd05e65444e52adb5164a38f3c64b247d5 (commit)
   via  e14ad2e376ee648cd0a9daf91c6a12ee6085f6e2 (commit)
   via  dca5df16c51dd9426f415ed7943402036e0ad08c (commit)
   via  131c721f542cd6f8805967d847965510172a2c6b (commit)
  from  f6a85bdbb19c4d8124f683db17c634fa48a62c02 (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=a8d8d2fd05e65444e52adb5164a38f3c64b247d5
commit a8d8d2fd05e65444e52adb5164a38f3c64b247d5
Merge: e14ad2e dca5df1
Author: Brad King 
AuthorDate: Thu Jul 20 14:52:15 2017 +
Commit: Kitware Robot 
CommitDate: Thu Jul 20 10:52:20 2017 -0400

Merge topic 'autogen-generated-files'

dca5df16 Autogen: Process GENERATED files. Add CMP0071.

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e14ad2e376ee648cd0a9daf91c6a12ee6085f6e2
commit e14ad2e376ee648cd0a9daf91c6a12ee6085f6e2
Merge: f6a85bd 131c721
Author: Brad King 
AuthorDate: Thu Jul 20 14:51:05 2017 +
Commit: Kitware Robot 
CommitDate: Thu Jul 20 10:51:12 2017 -0400

Merge topic 'vs-lang-std'

131c721f MSVC: Add flags for C++ language standards

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=dca5df16c51dd9426f415ed7943402036e0ad08c
commit dca5df16c51dd9426f415ed7943402036e0ad08c
Author: Sebastian Holtermann 
AuthorDate: Sun Jul 16 16:51:14 2017 +0200
Commit: Sebastian Holtermann 
CommitDate: Tue Jul 18 18:11:31 2017 +0200

Autogen: Process GENERATED files. Add CMP0071.

This lets AUTOMOC and AUTOUIC process GENERATED files which
used to be ignored before.
A new policy CMP0071 ensures that the old behavior of ignoring
GENERATED files is enabled when the CMake compatibility version
CMAKE_MINIMUM_REQUIRED is < 3.10.

Closes #16186

diff --git a/Help/manual/cmake-policies.7.rst b/Help/manual/cmake-policies.7.rst
index eb9af27..c81ba59 100644
--- a/Help/manual/cmake-policies.7.rst
+++ b/Help/manual/cmake-policies.7.rst
@@ -57,6 +57,7 @@ Policies Introduced by CMake 3.10
 .. toctree::
:maxdepth: 1
 
+   CMP0071: Let AUTOMOC and AUTOUIC process GENERATED files. 
CMP0070: Define file(GENERATE) behavior for relative paths. 

 
 Policies Introduced by CMake 3.9
diff --git a/Help/policy/CMP0071.rst b/Help/policy/CMP0071.rst
new file mode 100644
index 000..61f14dc
--- /dev/null
+++ b/Help/policy/CMP0071.rst
@@ -0,0 +1,34 @@
+CMP0071
+---
+
+Let :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC` process
+:prop_sf:`GENERATED` files.
+
+CMake 3.10 and newer process regular *and* :prop_sf:`GENERATED` source files
+in :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`.
+In CMake 3.9 and lower, only regular source files were processed in
+:prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`,
+:prop_sf:`GENERATED` source files were ignored.
+
+This policy affects how :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC` process
+source files that are :prop_sf:`GENERATED`.
+
+The ``OLD`` behavior for this policy is to *ignore* :prop_sf:`GENERATED`
+source files in :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`.
+
+The ``NEW`` behavior for this policy is to process :prop_sf:`GENERATED`
+source files in :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC` just like regular
+source files.
+
+.. note::
+  To exclude source files from :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`
+  processing, the boolean source file properties
+  :prop_sf:`SKIP_AUTOMOC`, :prop_sf:`SKIP_AUTOUIC` and :prop_sf:`SKIP_AUTOGEN`
+  can be set accordingly.
+
+This policy was introduced in CMake version 3.10.  CMake version
+|release| warns when the policy is not set and uses ``OLD`` behavior.
+Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW``
+explicitly.
+
+.. include:: DEPRECATED.txt
diff --git a/Help/release/dev/autogen-generated-files.rst 
b/Help/release/dev/autogen-generated-files.rst
new file mode 100644
index 000..da2fc4e
--- /dev/null
+++ b/Help/release/dev/autogen-generated-files.rst
@@ -0,0 +1,8 @@
+autogen-generated-files
+---
+
+* When using :prop_tgt:`AUTOMOC` or :prop_tgt:`AUTOUIC`,
+  source files that are :prop_sf:`GENERATED` will be processed as well.
+  They were ignored by :prop_tgt:`AUTOMOC` and :prop_tgt:`AUTOUIC`
+  in earlier releases.
+  See policy :policy:`CMP0071`.
diff --git a/Source/cmPolicies.h 

Re: [cmake-developers] Best way to append "--no-undefined" to shared link flags?

[Brad King]

On 07/18/2017 04:52 PM, Robert Dailey wrote:
> set( CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS}
> -Wl,--no-undefined" )

That's fine, but you can use `string(APPEND)` to shorten the code:

  string(APPEND CMAKE_SHARED_LINKER_FLAGS " -Wl,--no-undefined")

> After talking more with the NDK devs on github though, they seem to
> indicate this should happen by default (or at least, it does with the
> CMake that ships with the NDK according to Dan Albert).

I don't think the NDK build system itself did that back when we first
developed CMake's NDK support.  It looks like their NDK-provided
toolchain does do it by default, but with an option to turn it off.

> Does --no-defined get specified by default for other platforms?
> Or is it just Android that isn't getting it?

CMake doesn't add --no-undefined by default on any platform.

-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] [cmake-developers] Best way to append "--no-undefined" to shared link flags?

[Brad King]

On 07/18/2017 04:52 PM, Robert Dailey wrote:
> set( CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS}
> -Wl,--no-undefined" )

That's fine, but you can use `string(APPEND)` to shorten the code:

  string(APPEND CMAKE_SHARED_LINKER_FLAGS " -Wl,--no-undefined")

> After talking more with the NDK devs on github though, they seem to
> indicate this should happen by default (or at least, it does with the
> CMake that ships with the NDK according to Dan Albert).

I don't think the NDK build system itself did that back when we first
developed CMake's NDK support.  It looks like their NDK-provided
toolchain does do it by default, but with an option to turn it off.

> Does --no-defined get specified by default for other platforms?
> Or is it just Android that isn't getting it?

CMake doesn't add --no-undefined by default on any platform.

-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

Re: [CMake] Create user and group with CPack

[Eric Noulard]

2017-07-20 13:48 GMT+02:00 Kristian :

> Ok, I changed the postinstall script based on your suggestions:
>
> i.e. I changed these two lines:
> > WEB_GROUP_ID="$(getent group "${WEB_GROUP}" | cut -d: -f3)"
> and
> > useradd "$WEB_USER" -g "${WEB_GROUP}" -M -r -s /sbin/nologin -c
>
> And it worked now. Thank you for your help. :)
>

You are welcome.

As you may have guessed the first line
WEB_GROUP_ID="$(getent group "${WEB_GROUP}" | cut -d: -f3)"

may be suppressed if
useradd "$WEB_USER" -g "${WEB_GROUP}" -M -r -s /sbin/nologin -c

is OK.
--
Eric
-- 

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

Re: [CMake] Create user and group with CPack

[Kristian]

Ok, I changed the postinstall script based on your suggestions:

i.e. I changed these two lines:
> WEB_GROUP_ID="$(getent group "${WEB_GROUP}" | cut -d: -f3)"
and
> useradd "$WEB_USER" -g "${WEB_GROUP}" -M -r -s /sbin/nologin -c

And it worked now. Thank you for your help. :)



2017-07-20 12:35 GMT+02:00 Eric Noulard :
>
>
> 2017-07-20 12:01 GMT+02:00 Kristian :
>>
>> Hi,
>>
>> thank you for your reply. Yes, I add the script with
>> > set(CPACK_RPM_POST_INSTALL_SCRIPT_FILE
>> > "${CMAKE_CURRENT_SOURCE_DIR}/postinstall")
>>
>> and it basically works, because this file is changing a settings file
>> without any problems. Only the add of the group and the user does not
>> work, somehow.
>>
>> This is the part in the postinstall script, which should add group and
>> user:
>>
>> =
>> WEB_USER=web1
>> WEB_GROUP=web1
>>
>> # create group
>> groupadd "${WEB_GROUP}" --force --system
>> # retrieve group id
>> WEB_GROUP_ID="$(getent group '$WEB_GROUP' | cut -d: -f3)"
>> echo "Group '${WEB_GROUP}' added with id '${WEB_GROUP_ID}'"
>> # create user
>> useradd "$WEB_USER" -g "${WEB_GROUP_ID}" -M -r -s /sbin/nologin -c
>> "Web user - created during the installation."
>> echo "User '${WEB_USER}' added."
>> =
>>
>> And this is, what is being printed during installation:
>> =
>> Group 'web1' added with id ''
>> useradd: group '' does not exist
>> User 'web1' added.
>> =
>
>
> What is the shebang your ar using at the top of this script?
>
> this syntax:
> WEB_GROUP_ID="$(getent group '$WEB_GROUP' | cut -d: -f3)"
>
> may be bash only.
>
> not sure it makes a difference but you could try:
>
> WEB_GROUP_ID="$(getent group '${WEB_GROUP}' | cut -d: -f3)"
>
> note that getting the numeric group id seems unecessary.
>
> useradd "$WEB_USER" -g "${WEB_GROUP}" -M -r -s /sbin/nologin -c
>
> should work, useradd should work equally well with numeric or symbolic id of
> a group.
>
>
> --
> Eric
-- 

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

Re: [CMake] Create user and group with CPack

[Eric Noulard]

2017-07-20 12:01 GMT+02:00 Kristian :

> Hi,
>
> thank you for your reply. Yes, I add the script with
> > set(CPACK_RPM_POST_INSTALL_SCRIPT_FILE "${CMAKE_CURRENT_SOURCE_DIR}/
> postinstall")
>
> and it basically works, because this file is changing a settings file
> without any problems. Only the add of the group and the user does not
> work, somehow.
>
> This is the part in the postinstall script, which should add group and
> user:
>
> =
> WEB_USER=web1
> WEB_GROUP=web1
>
> # create group
> groupadd "${WEB_GROUP}" --force --system
> # retrieve group id
> WEB_GROUP_ID="$(getent group '$WEB_GROUP' | cut -d: -f3)"
> echo "Group '${WEB_GROUP}' added with id '${WEB_GROUP_ID}'"
> # create user
> useradd "$WEB_USER" -g "${WEB_GROUP_ID}" -M -r -s /sbin/nologin -c
> "Web user - created during the installation."
> echo "User '${WEB_USER}' added."
> =
>
> And this is, what is being printed during installation:
> =
> Group 'web1' added with id ''
> useradd: group '' does not exist
> User 'web1' added.
> =
>

What is the shebang your ar using at the top of this script?

this syntax:
WEB_GROUP_ID="$(getent group '$WEB_GROUP' | cut -d: -f3)"

may be bash only.

not sure it makes a difference but you could try:

WEB_GROUP_ID="$(getent group '${WEB_GROUP}' | cut -d: -f3)"

note that getting the numeric group id seems unecessary.

useradd "$WEB_USER" -g "${WEB_GROUP}" -M -r -s /sbin/nologin -c

should work, useradd should work equally well with numeric or symbolic id
of a group.


--
Eric
-- 

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

Re: [CMake] Create user and group with CPack

[Kristian]

Hi,

thank you for your reply. Yes, I add the script with
> set(CPACK_RPM_POST_INSTALL_SCRIPT_FILE 
> "${CMAKE_CURRENT_SOURCE_DIR}/postinstall")

and it basically works, because this file is changing a settings file
without any problems. Only the add of the group and the user does not
work, somehow.

This is the part in the postinstall script, which should add group and user:

=
WEB_USER=web1
WEB_GROUP=web1

# create group
groupadd "${WEB_GROUP}" --force --system
# retrieve group id
WEB_GROUP_ID="$(getent group '$WEB_GROUP' | cut -d: -f3)"
echo "Group '${WEB_GROUP}' added with id '${WEB_GROUP_ID}'"
# create user
useradd "$WEB_USER" -g "${WEB_GROUP_ID}" -M -r -s /sbin/nologin -c
"Web user - created during the installation."
echo "User '${WEB_USER}' added."
=

And this is, what is being printed during installation:
=
Group 'web1' added with id ''
useradd: group '' does not exist
User 'web1' added.
=


2017-07-20 11:17 GMT+02:00 Eric Noulard :
>
>
>
> 2017-07-20 10:39 GMT+02:00 Kristian :
>>
>> Hi,
>>
>> I create a RPM package with CPack. When installing this package on a
>> target system, it should create an additional user and group.
>>
>> My current solution is a postinstall script, wich runs at the end of
>> the installation. There, I added commands to create a user and a group
>> (groupadd, useradd). But somehow, they aren't created when installing
>> this RPM package.
>
>
> Did you specify this post install script to CPackRPM?
> https://cmake.org/cmake/help/v3.7/module/CPackRPM.html#variable:CPACK_RPM_POST_INSTALL_SCRIPT_FILE
>
> You can check that the generated RPM does include the script with:
>
>  rpm -qp --scripts  .rpm
>
>>
>> For testing, I install this RPM package in a docker
>> container.
>>
>> I also tried, if these commands (groupadd, useradd) are working on the
>> docker container and they are, so this shouldn't be a problem.
>>
>> So, how can I create a user and a group with CPack / 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:
>> http://public.kitware.com/mailman/listinfo/cmake
>
>
>
>
> --
> Eric
-- 

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

Re: [CMake] Create user and group with CPack

[Eric Noulard]

2017-07-20 10:39 GMT+02:00 Kristian :

> Hi,
>
> I create a RPM package with CPack. When installing this package on a
> target system, it should create an additional user and group.
>
> My current solution is a postinstall script, wich runs at the end of
> the installation. There, I added commands to create a user and a group
> (groupadd, useradd). But somehow, they aren't created when installing
> this RPM package.


Did you specify this post install script to CPackRPM?
https://cmake.org/cmake/help/v3.7/module/CPackRPM.html#variable:CPACK_RPM_POST_INSTALL_SCRIPT_FILE

You can check that the generated RPM does include the script with:

 rpm -qp --scripts  .rpm


> For testing, I install this RPM package in a docker
> container.
>
> I also tried, if these commands (groupadd, useradd) are working on the
> docker container and they are, so this shouldn't be a problem.
>
> So, how can I create a user and a group with CPack / 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:
> http://public.kitware.com/mailman/listinfo/cmake
>



-- 
Eric
-- 

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

Re: [CMake] CPack Multicore Usage

[Konstantin Tokarev]

20.07.2017, 11:22, "Jörg Kreuzberger" :
> Hi
>
> My Project is compiling multicore without any problems using Unix makefiles 
> or ninja.
>
> In calls to cpack only one core is used if Makefiles are used. Is there any 
> option to enable multicore?

Yes, you should run make -jN, where N is a number of your cores or slightly 
larger

> If i use ninja in cpack builds, the cpack build is broken, cause there seems 
> no dependencies considered?
>
> Is ninja use in cpack intended? Or are there any contraints using ninja and 
> cpack?
>
> Greetz, Joerg
>
> --
>
> 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

-- 
Regards,
Konstantin
-- 

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

[CMake] Create user and group with CPack

[Kristian]

Hi,

I create a RPM package with CPack. When installing this package on a
target system, it should create an additional user and group.

My current solution is a postinstall script, wich runs at the end of
the installation. There, I added commands to create a user and a group
(groupadd, useradd). But somehow, they aren't created when installing
this RPM package. For testing, I install this RPM package in a docker
container.

I also tried, if these commands (groupadd, useradd) are working on the
docker container and they are, so this shouldn't be a problem.

So, how can I create a user and a group with CPack / 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:
http://public.kitware.com/mailman/listinfo/cmake

[CMake] CPack Multicore Usage

[Jörg Kreuzberger]

Hi

My Project is compiling multicore without any problems using Unix makefiles or 
ninja.

In calls to cpack only one core is used if Makefiles are used. Is there any 
option to enable multicore?
If i use ninja in cpack builds, the cpack build is broken, cause there seems no 
dependencies considered?

Is ninja use in cpack intended? Or are there any contraints using ninja and 
cpack?

Greetz, Joerg

-- 

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