From roman.wueger at gmx.at  Thu Jan  2 06:41:19 2020
From: roman.wueger at gmx.at (=?utf-8?Q?Roman_W=C3=BCger?=)
Date: Thu, 2 Jan 2020 12:41:19 +0100
Subject: [CMake] [cmake-developers] productbuild: Installing to absolute
 system path or to user home path
In-Reply-To: <90332C82-1C1F-457D-871D-865DC9497725@gmx.at>
References: <90332C82-1C1F-457D-871D-865DC9497725@gmx.at>
Message-ID: <6256D893-2DFC-4B4F-8C7C-48BAD04D1BEC@gmx.at>

Ok if someone is interested I solved it with a post-install script at the moment. I installed it in the default location and moved it afterwards with the post-install script to the ~/Library...

Regards
Roman

> Am 05.11.2019 um 15:02 schrieb Roman W?ger <roman.wueger at gmx.at>:
> 
> ?
> Hello,
> 
> The main wish is to install to the user directory as described in the documentation, the absolute path to the ?all users? works already:
> 
> Here is the description from the manual, also attached as an image
> 
> Automatic plug-in loading
> Lightroom automatically checks for plug-ins in the standard Modules folder where other Lightroom settings are stored:
>    In Mac OS (current user) In Mac OS (all users)
> In Windows XP
> plug-in and also installs a helper application.
> Plug-ins that are installed in this location are automatically listed in the Plug-in Manager dialog. You can use the dialog to enable or disable such a plug-in, but not to remove it. The Remove button is dimmed when such a plug-in is selected.
> ~/Library/Application Support/Adobe/Lightroom/Modules /Library/Application Support/Adobe/Lightroom/Modules
> C:\Documents and Users\username\Application Data\Adobe\Lightroom\Modules
> C:\Users\username\AppData\Roaming\Adobe\Lightroom\Modules You may want to use this location if, for example, you are writing an installer that installs a Lightroom
>    In Windows 7/Vista
> 
> <image0.jpeg>
> 
> 
> Regards
> Roman
> 
>>> Am 01.11.2019 um 05:10 schrieb David Aguilar <davvid at gmail.com>:
>>> 
>> ?
>> I would also suggest avoiding absolute paths so that the user can tell you where to root the installation.
>> 
>> One way to do that is to use GNUInstallDirs so that the user can specify the install prefix.  And maybe you want to let them user their home directory be default if they've not specified it:
>> 
>> 
>> include(GNUInstallDirs)
>> 
>> if (CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
>>     # NOTE: default to the home directory, assumes $HOME is defined in the environment
>>     set(CMAKE_INSTALL_PREFIX $ENV{HOME} CACHE PATH "Installation prefix" FORCE) 
>> endif ()
>> 
>> [... usual stuff here ...]
>> 
>> # NOTE: relative path
>> install(TARGETS target_name DESTINATION "Library/Application Support/Adobe/Lightroom/Modules")
>> 
>> 
>> Then the user would just "make && make install" and it'll install to their ~/Library directory by default.
>> 
>> Then, if they have the permissions to do so, they can install to the global system location using:
>> 
>> cmake -D CMAKE_INSTALL_PREFIX=/ . &&
>> make &&
>> sudo make install
>> 
>> Mixing both in the same cmake invocation can be done, but now you've made it impossible to install into other locations (for testing, packaging, etc).
>> 
>> For example, someone might want to package it without sudo, so they might want to do this instead of "sudo make install":
>> 
>>     make DESTDIR=$PWD/tmp install
>> 
>> and then you have a tmp/Library/ directory structure that can be made into a macOS .pkg installer:
>> 
>>     pkgbuild --install-location / --identifier org.domain.pkgs.example --version 1.0.0 --root tmp example-1.0.0.pkg
>> 
>> And now you have a .pkg installer that updates the global /Library directory without needing to be root to build it.
>> 
>> 
>> Question -- is this a situation where you want a single build to install into both locations, or is the literally the same plugin and it only needs to be in one of the two locations (global vs. user)?  I interpreted your question to be about the latter, where the user really only needs one or the other, and it's the same plugin in both cases.
>> 
>> I don't know if cpack handles this for you, but hopefully this is helpful advice.
>> 
>> 
>>> On Thu, Oct 31, 2019 at 10:19 AM David Cole via cmake-developers <cmake-developers at cmake.org> wrote:
>>> According to the docs, the INSTALL command uses the absolute path if
>>> it is given as the DESTINATION, so .... it should work.
>>> https://cmake.org/cmake/help/latest/command/install.html
>>> 
>>> Did you try using a double quoted string, instead of escaping the
>>> space with a backslash?
>>> 
>>> I think this should work for the absolute one:
>>> INSTALL( ... DESTINATION "/abs/path/to/some folder")
>>> 
>>> For the one in the home directory, I'm not sure if a string that
>>> starts with "~" is considered absolute or not, so it may or may not
>>> end up where you expect it. Can you resolve it before hand with a
>>> get_filename_component call, (or otherwise), and pass in a string that
>>> begins with "/" ...?
>>> 
>>> 
>>> Hope this helps,
>>> David C.
>>> 
>>> 
>>> On Mon, Oct 28, 2019 at 4:36 PM Roman W?ger <roman.wueger at gmx.at> wrote:
>>> > Hello,
>>> > I tried to install a file/directory with productbuild on macOS which is generated with CPack
>>> > The most of the files are installed correctly, but I have two problems:
>>> >
>>> > If I want to install to ?/Library/Application\ Support/Adobe/Lightroom/Modules?
>>> > If I want to install to the users modules folder ?~/Library/Application\ Support/Adobe/Lightroom/Modules?
>>> >
>>> > How can I archive these two?
>>> >
>>> > I already tried the following with no luck:
>>> > install(DIRECTORY $<TARGET_FILE_DIR:${PROJECT_NAME}>/${CMAKE_PROJECT_NAME}.lrplugin
>>> >                 DESTINATION /Library/Application\ Support/Adobe/Lightroom/Modules)
>>> >
>>> > install(DIRECTORY $<TARGET_FILE_DIR:${PROJECT_NAME}>/${CMAKE_PROJECT_NAME}.lrplugin
>>> >                 DESTINATION ~/Library/Application\ Support/Adobe/Lightroom/Modules)
>>> > Best Regards
>>> >
>>> > Roman
>> -- 
>> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cmake.org/pipermail/cmake/attachments/20200102/9875cf4a/attachment.html>

From roman.wueger at gmx.at  Wed Jan  8 15:02:07 2020
From: roman.wueger at gmx.at (=?utf-8?Q?Roman_W=C3=BCger?=)
Date: Wed, 8 Jan 2020 21:02:07 +0100
Subject: [CMake] Problems with installer on macOS
Message-ID: <1D3F4436-9182-495E-BA4B-436AC54020E5@gmx.at>

?Hello,

I generate a productbuild installer with CPack.

When I start the installer and view the files then everthing is packaged as it should. But when I install them, then not all files are installed.

The install protocol from the installer succeeds with no errors.

Any hints?

Best Regards
Roman

From roman.wueger at gmx.at  Mon Jan 13 06:13:36 2020
From: roman.wueger at gmx.at (=?utf-8?Q?Roman_W=C3=BCger?=)
Date: Mon, 13 Jan 2020 12:13:36 +0100
Subject: [CMake] Problems with installer on macOS
In-Reply-To: <1D3F4436-9182-495E-BA4B-436AC54020E5@gmx.at>
References: <1D3F4436-9182-495E-BA4B-436AC54020E5@gmx.at>
Message-ID: <D75940D0-15EF-4B71-972F-625A10B9459B@gmx.at>

Setting BundleIsRelocatable to false was the solution

Best regards 
Roman

> Am 08.01.2020 um 21:07 schrieb Roman W?ger <roman.wueger at gmx.at>:
> 
> ?Hello,
> 
> I generate a productbuild installer with CPack.
> 
> When I start the installer and view the files then everthing is packaged as it should. But when I install them, then not all files are installed.
> 
> The install protocol from the installer succeeds with no errors.
> 
> Any hints?
> 
> Best Regards
> Roman
> -- 
> 
> Powered by kitware.com/cmake
> 
> Kitware offers various services to support the CMake community. For more information on each offering, please visit https://cmake.org/services
> 
> Visit other Kitware open-source projects at https://www.kitware.com/platforms
> 
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
> 
> This mailing list is deprecated in favor of https://discourse.cmake.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cmake.org/pipermail/cmake/attachments/20200113/a6a7f041/attachment.html>

From robert.maynard at kitware.com  Mon Jan 13 17:05:50 2020
From: robert.maynard at kitware.com (Robert Maynard)
Date: Mon, 13 Jan 2020 17:05:50 -0500
Subject: [CMake] [ANNOUNCE] CMake Discourse forum now available
In-Reply-To: <CAFzjYVo7fNF+N4pixeu8vAfhPYjZh0Dyq23N7zpwW6aqfqDLeg@mail.gmail.com>
References: <CAFzjYVo7fNF+N4pixeu8vAfhPYjZh0Dyq23N7zpwW6aqfqDLeg@mail.gmail.com>
Message-ID: <CAFzjYVo-oo94y3tpxepvG88bsxGaE2=xhP+oyyoW1kvppMSnDg@mail.gmail.com>

A reminder that CMake is transitioning to Discouse, and by the end of
March 2020 the mailing lists will be read-only, and the archives
will remain available after that.

The Discourse forum for the CMake community is:

  https://discourse.cmake.org

Discourse offers users more control over their level of participation,
allowing them to subscribe or unsubscribe by category or individual topic.
Users may choose to participate by web forum, email, or both.

To get started, see our Forum Help page:

  https://discourse.cmake.org/faq

User accounts may be created using Email Registration, a GitHub Account, or a
Google Account.

For those who prefer email over web forums, the Forum Help page includes
instructions to participate in the forum purely via email.  Creating topics in
the forum via email (and receiving replies) is supported *with or without*
registering a user account.  User accounts may be configured to receive email
notifications for forum activity at several levels of granularity, or to
receive email notifications for all activity like a mailing list.

On Tue, Nov 5, 2019 at 12:13 PM Robert Maynard
<robert.maynard at kitware.com> wrote:
>
> A Discourse forum is now available for the CMake community:
>
>   https://discourse.cmake.org
>
> Discourse offers users more control over their level of participation,
> allowing them to subscribe or unsubscribe by category or individual topic.
> Users may choose to participate by web forum, email, or both.
>
> To get started, see our Forum Help page:
>
>   https://discourse.cmake.org/faq
>
> User accounts may be created using Email Registration, a GitHub Account, or a
> Google Account.
>
> For those who prefer email over web forums, the Forum Help page includes
> instructions to participate in the forum purely via email.  Creating topics in
> the forum via email (and receiving replies) is supported *with or without*
> registering a user account.  User accounts may be configured to receive email
> notifications for forum activity at several levels of granularity, or to
> receive email notifications for all activity like a mailing list.
>
> To facilitate a transition period, the current mailman-based mailing lists
> will remain active until at least the end of March 2020, and their archives
> will remain available after that.
>
> See you on discourse.cmake.org!

From robb at datalogics.com  Mon Jan 13 17:55:04 2020
From: robb at datalogics.com (Rob Boehne)
Date: Mon, 13 Jan 2020 22:55:04 +0000
Subject: [CMake] Altered target library
Message-ID: <8320CB9F-E761-4C6B-BC24-A2089B414CF1@datalogics.com>

All,

We have a shared library we deliver to clients in two different ways ? one has a license manager linked in, and it?s installed into a different directory.  Everything else has been moved from VS & Makefiels to CMake except support for this.

Is there a CMake way to create a second target, with the same name but different options or source file properties & link options, but to a different directory?
Ideally we would not have to duplicate the rather large CMakeLists.txt ? but I could break all the things that are the same out into a dependency.  I had the thought that perhaps I could inherit from the first target to create the second, but I?m not aware of that feature in CMake.

Any ideas?

Thanks


[cid:image002.png at 01D3D0E3.DCFE6710]
Rob Boehne
Senior Software Architect | Datalogics, Inc.
+1.312.853.8351<tel:(312)%20853-8351> | robb at datalogics.com<mailto:robb at datalogics.com>
datalogics.com<http://www.datalogics.com/> | blogs.datalogics.com<http://blogs.datalogics.com/>
Connect with us: Facebook<https://www.facebook.com/DatalogicsInc> | Twitter<https://twitter.com/DatalogicsInc> | LinkedIn<https://www.linkedin.com/company/datalogics?actionToken=p=p%3Dbiz-company-login%26c%3D3217e65a-bdc2-4b38-8f9c-13c982e8c529%26m%3Dcompany_feed%26n%3D0&t=a%3DisFolloweeOfPoster%253Dfalse%2526distanceFromActor%253D-1%2526actorType%253D%2526likedByUser%253Dfalse%2526targetId%253D%2526recentCommentUrns%253D%2526targetType%253D%2526sponsoredFlag%253DORGANIC%2526verbType%253Dlinkedin%25253Ashare%2526objectType%253Dlinkedin%25253Aarticle%2526totalShares%253D0%2526activityId%253Durn%25253Ali%25253Aactivity%25253A6263731876121362433%2526recentLikerUrns%253D%2526actorId%253Durn%25253Ali%25253Acompany%25253A14000%2526totalComments%253D0%2526relevanceScore%253D0.0%2526recentCommenterUrns%253D%2526isPublic%253Dtrue%2526time%253D-1%2526totalLikes%253D0%2526objectId%253Durn%25253Ali%25253Aarticle%25253A7793179909183391510%2526distanceFromNestedActor%253D-1%26s%3DORG> | YouTube<https://www.youtube.com/user/Datalogics>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cmake.org/pipermail/cmake/attachments/20200113/dbdce8a5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 124449 bytes
Desc: image001.png
URL: <https://cmake.org/pipermail/cmake/attachments/20200113/dbdce8a5/attachment-0001.png>

From robert.maynard at kitware.com  Tue Jan 21 12:55:16 2020
From: robert.maynard at kitware.com (Robert Maynard)
Date: Tue, 21 Jan 2020 12:55:16 -0500
Subject: [CMake] [ANNOUNCE] CMake 3.16.3 available for download
Message-ID: <CAFzjYVq8FdR3j8L+wf_+DK2Nf9aU=97xBJTHyjBBfff2eMKSpg@mail.gmail.com>

We are pleased to announce that CMake 3.16.3 is now available for download.

Please use the latest release from our download page:
  https://cmake.org/download/

Thanks for your support!

-------------------------------------------------------------------------
Changes in 3.16.3 since 3.16.2:

Ashley Whetter (1):
  FindOpenSSL: Fix ordering of dependency link flags

Brad King (3):
  GNUtoMS: Add search path for VS 2019 environment scripts
  IRSL: Install msvcp140_{1,2,codecvt_ids}.dll if available
  CMake 3.16.3

Cristian Adam (4):
  ObjC: Add _COMPILE_LAUNCHER support
  ObjC: Add VISIBLITY_INLINES_HIDDEN support
  Unity Build: include language in generated source file name
  PCH: No repeated path for internal generated PCH files (MSVC case)

Kyle Edwards (2):
  CTest: Improve error handling when reading resource spec file
  CPack: Fix regression in DEB generator description

Marc Chevrier (3):
  FindPython*: Fix erroneous target properties setting
  macOS: Add support for new Xcode 11 frameworks directory
  FindPython: ensure new Xcode framework for Python3 is detected

Miro Hron?ok (1):
  FindPython: Add support for version 3.9

Neil Carlson (1):
  Fortran: Add support for NAG Fortran submodules

Pavel Liavonau (1):
  VS: Add Fortran link flag table entries for /OPT:*

Robert Maynard (1):
  CUDA: Do not device link if target has no CUDA usage

Sebastian Holtermann (1):
  Autogen: Enable SKIP_UNITY_BUILD_INCLUSION on AUTORCC generated files

Silvio Traversaro (2):
  FindMatlab: add R2019a and R2019b MATLAB_VERSIONS_MAPPING
  FindMatlab: in matlab_add_mex use the correct version file

From tdiff at yandex.ru  Thu Jan 30 05:10:06 2020
From: tdiff at yandex.ru (A.Dmitrovsky)
Date: Thu, 30 Jan 2020 13:10:06 +0300
Subject: [CMake] Installing targets from a monorepository
Message-ID: <18673571580379006@myt5-2a1eccb4c218.qloud-c.yandex.net>

An HTML attachment was scrubbed...
URL: <https://cmake.org/pipermail/cmake/attachments/20200130/eaa3e8b7/attachment.html>