[Cmake-commits] CMake branch, master, updated. v3.14.4-1107-ge13b18e

[Kitware Robot via Cmake-commits]

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  e13b18e2c70f42c23ed7e7fddb93557ce19b7359 (commit)
  from  ed593cbe645d7e5a0131b0695a607999e70af5c6 (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=e13b18e2c70f42c23ed7e7fddb93557ce19b7359
commit e13b18e2c70f42c23ed7e7fddb93557ce19b7359
Author: Kitware Robot 
AuthorDate: Tue May 28 00:01:06 2019 -0400
Commit: Kitware Robot 
CommitDate: Tue May 28 00:01:06 2019 -0400

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 69f3f97..0a23023 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 14)
-set(CMake_VERSION_PATCH 20190527)
+set(CMake_VERSION_PATCH 20190528)
 #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.14.4-1106-ged593cb

[Kitware Robot via Cmake-commits]

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  ed593cbe645d7e5a0131b0695a607999e70af5c6 (commit)
   via  711f1bf1db0bbfb64323f81ee52864560776ebff (commit)
   via  b7b7f1806acf8aabd5cd99e3d08fac15f4f95bdc (commit)
   via  902af25512545db441043ea8f1fd2637fa1e1129 (commit)
  from  c0e763d6880e842d8fc874e58c93583e014bd988 (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=ed593cbe645d7e5a0131b0695a607999e70af5c6
commit ed593cbe645d7e5a0131b0695a607999e70af5c6
Merge: 711f1bf 902af25
Author: Craig Scott 
AuthorDate: Mon May 27 21:55:29 2019 +
Commit: Kitware Robot 
CommitDate: Mon May 27 17:55:45 2019 -0400

Merge topic 'doc-typo-CTEST_CUSTOM_WARNING_xxx'

902af25512 Help: Fix typo for CTEST_CUSTOM_WARNING_xxx vars

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=711f1bf1db0bbfb64323f81ee52864560776ebff
commit 711f1bf1db0bbfb64323f81ee52864560776ebff
Merge: c0e763d b7b7f18
Author: Craig Scott 
AuthorDate: Mon May 27 21:53:04 2019 +
Commit: Kitware Robot 
CommitDate: Mon May 27 17:53:43 2019 -0400

Merge topic 'doc-install-export-android-mk'

b7b7f1806a Help: Fix typo in install(EXPORT_ANDROID_MK) example

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


https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b7b7f1806acf8aabd5cd99e3d08fac15f4f95bdc
commit b7b7f1806acf8aabd5cd99e3d08fac15f4f95bdc
Author: John Freeman 
AuthorDate: Sat May 25 14:57:08 2019 -0400
Commit: John Freeman 
CommitDate: Sun May 26 09:09:07 2019 -0500

Help: Fix typo in install(EXPORT_ANDROID_MK) example

diff --git a/Help/command/install.rst b/Help/command/install.rst
index 7571aae..ab6fef6 100644
--- a/Help/command/install.rst
+++ b/Help/command/install.rst
@@ -660,9 +660,9 @@ and installed by the current project.  For example, the code
 
   install(TARGETS myexe EXPORT myproj DESTINATION bin)
   install(EXPORT myproj NAMESPACE mp_ DESTINATION lib/myproj)
-  install(EXPORT_ANDROID_MK myexp DESTINATION share/ndk-modules)
+  install(EXPORT_ANDROID_MK myproj DESTINATION share/ndk-modules)
 
-will install the executable myexe to ``/bin`` and code to import
+will install the executable ``myexe`` to ``/bin`` and code to import
 it in the file ``/lib/myproj/myproj.cmake`` and
 ``/share/ndk-modules/Android.mk``.  An outside project
 may load this file with the include command and reference the ``myexe``

https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=902af25512545db441043ea8f1fd2637fa1e1129
commit 902af25512545db441043ea8f1fd2637fa1e1129
Author: Craig Scott 
AuthorDate: Sun May 26 22:30:39 2019 +1000
Commit: Craig Scott 
CommitDate: Sun May 26 22:31:23 2019 +1000

Help: Fix typo for CTEST_CUSTOM_WARNING_xxx vars

These variables apply to the `ctest_build` command, not `ctest_test`

Relates: #19217

diff --git a/Help/variable/CTEST_CUSTOM_WARNING_EXCEPTION.rst 
b/Help/variable/CTEST_CUSTOM_WARNING_EXCEPTION.rst
index 36fa37d..a03d473 100644
--- a/Help/variable/CTEST_CUSTOM_WARNING_EXCEPTION.rst
+++ b/Help/variable/CTEST_CUSTOM_WARNING_EXCEPTION.rst
@@ -2,6 +2,6 @@ CTEST_CUSTOM_WARNING_EXCEPTION
 --
 
 A list of regular expressions which will be used to exclude when detecting
-warning messages in build outputs by the :command:`ctest_test` command.
+warning messages in build outputs by the :command:`ctest_build` command.
 
 .. include:: CTEST_CUSTOM_XXX.txt
diff --git a/Help/variable/CTEST_CUSTOM_WARNING_MATCH.rst 
b/Help/variable/CTEST_CUSTOM_WARNING_MATCH.rst
index a35be96..18aa6b3 100644
--- a/Help/variable/CTEST_CUSTOM_WARNING_MATCH.rst
+++ b/Help/variable/CTEST_CUSTOM_WARNING_MATCH.rst
@@ -2,6 +2,6 @@ CTEST_CUSTOM_WARNING_MATCH
 --
 
 A list of regular expressions which will be used to detect warning messages in
-build outputs by the :command:`ctest_test` command.
+build outputs by the :command:`ctest_build` command.
 
 .. include:: CTEST_CUSTOM_XXX.txt

---

Summary of changes:
 Help/command/install.rst | 4 ++--
 Help/variable/CTEST_CUSTOM_WARNING_EXCEPTION.rst | 2 +-
 Help/variable/CTEST_CUSTOM_WARNING_MATCH.rst | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)


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

[CMake] how to link a test with library in build directory, not with installed version?

[Joachim Wuttke]

How to link a test with a library as obtained in the build directory,
not with the installed version, which may be outdated?

Disclosure: cross-posted from https://stackoverflow.com/questions/56328326.

== Use case ==

Suppose

  cmake; make; ctest; make install

works fine:
- generates libA,
- runs testB,
- installs libA to ${CMAKE_INSTALL_LIBDIR}.

Now I modify libA, and rerun
  make; ctest.
No reaction to my modifications:
  ldd testB
shows that the installed version of libA is used.
Which is plain nonsense for a test.

The test should always use the local version of libA, never the installed one.

== Towards a solution ==

I saw a lot of advise that involves RPATH, but found no variant that helps.

So I hard-coded the path by changing
  target_link_libraries(testB PRIVATE A)
into
  target_link_libraries(testB PRIVATE ${CMAKE_BINARY_DIR}/lib/libA.so).

This works, but is no longer platform independent.
How to solve my problem in a way that also works under Windows?

- Joachim



smime.p7s
Description: S/MIME Cryptographic Signature
-- 

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-developers] Is email notification of a failed CMake dashboard possible?

[David Cole via cmake-developers]

Before you login, it's just a "login" link. Once you've logged in, it
becomes a "My CDash" link.

On Sun, May 26, 2019 at 2:34 PM Alan W. Irwin
 wrote:
>
> On 2019-05-26 11:07+1000 Craig Scott wrote:
>
> > Notifications for builds are controlled through CDash. You can adjust your
> > CDash notifications to suit your preferences. Go to CDash, click on "My
> > CDash". You should see a list of "My Projects" and "Public Projects".
> > Subscribe to a project and it will appear under your "My Projects" area if
> > it isn't there already. For each subscribed project, you should see an icon
> > next to it under the Actions column which allows you to edit your
> > subscription and from there you can control what you receive email
> > notifications for. I'm not sure if there is a way to limit your
> > notifications to just certain sites though. You may need to ask on the
> > CDash mailing list for help with that.
>
> Hi Craig:
>
> Thanks for trying to help me, but I can find no mention of "My CDash"
> at either  or
> .  So can you be more
> specific about what URL I need to consult to control my notification
> preferences at **?
>
> Alan
>
> >
> >
> > On Sun, May 26, 2019 at 7:54 AM Alan W. Irwin 
> > wrote:
> >
> >> With a lot of initial configuration help from Brad King, I have been
> >> automatically submitting a Nightly dashboard for CMake (including the
> >> PLplot contract test) for some time now (see the "merlin" results at
> >>  and
> >> ).  On extremely rare
> >> occasions there is a failure in either of my CMake or KWSYS
> >> dashboards.  Is it possible for me to set up e-mail notification of
> >> such failures (and successes at first to make sure notification
> >> works), and if so, how?
> >>
> >> Alan
> >> __
> >> Alan W. Irwin
> >>
> >> Programming affiliations with the FreeEOS equation-of-state
> >> implementation for stellar interiors (freeeos.sf.net); the Time
> >> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> >> software package (plplot.org); the libLASi project
> >> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> >> and the Linux Brochure Project (lbproject.sf.net).
> >> __
> >>
> >> Linux-powered Science
> >> __
> >> --
> >>
> >> 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
> >>
> >
> >
> > --
> > Craig Scott
> > Melbourne, Australia
> > https://crascit.com
> >
> > Get the hand-book for every CMake user: Professional CMake: A Practical
> > Guide 
> >
>
> __
> Alan W. Irwin
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.org); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __
>
> Linux-powered Science
> __
> --
>
> 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
-- 

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 

Re: [CMake] Dependency cycle - why?

[Robert Maynard via CMake]

I misspoke. I meant that what you want to do with the custom commands
was supported by CMake.

Adding support for extra languages to CMake requires modifications at
the C++ level, if you want full support. Things such as installing,
and generator expressions require C++ level changes.

On Sat, May 25, 2019 at 10:47 AM Eric Noulard  wrote:
>
>
>
> Le sam. 25 mai 2019 à 13:51, Bill Somerville  a écrit :
>>
>> Hi Robert,
>>
>> thanks for that, the target name change does seem to help but I am still 
>> unable to achieve my goal. Here is a simplified example that demonstrates 
>> the problem:
>>
>> cmake_minimum_required (VERSION  3.1.0 FATAL_ERROR)
>> project (demo LANGUAGES NONE)
>> add_custom_target (prog_target COMMAND ${CMAKE_COMMAND} -E touch 
>> prog${CMAKE_EXECUTABLE_SUFFIX})
>> add_executable (prog IMPORTED)
>> add_dependencies (prog prog_target)
>> set_target_properties (prog PROPERTIES IMPORTED_LOCATION 
>> ${CMAKE_CURRENT_BINARY_DIR}/prog${CMAKE_EXECUTABLE_SUFFIX})
>> install (TARGETS prog RUNTIME DESTINATION bin)
>>
>> which gives the following error at CMake configuration:
>>
>> CMake Error at CMakeLists.txt:7 (install):
>>   install TARGETS given target "prog" which does not exist.
>>
>>
>> -- Configuring incomplete, errors occurred!
>>
>> So the target that 'add_executable(name IMPORTED)' creates is not a real 
>> executable target. I can change its properties but the 'install(TARGETS 
>> ...)' command thinks it does not exist. Note that a executable target is a 
>> very simple demonstration and I understand that I can use 'install(PROGRAM 
>> ...)' just about as easily, but when it comes to a shared library it gets a 
>> lot more complex when using, exporting, and instlling it, and it seems that 
>> IMPORTED targets fall well short of useful when they are actually produced 
>> by the current CMake project.
>>
>> I can understand that an IMPORTED target is perhaps not meant to be 
>> installable
>
>
> Robert will give his advice on that but I bet IMPORTED target were never 
> meant to be drop-in *replacement* of genuine target.

That is correct. Specifically imported targets aren't meant to be
exported or installed. They are meant to represent some item that
already exists on disk, and as such you should install the logic that
constructs the imported targets.
>
> They were meant to ease *reference to* object/lib:executable that are outside 
> the build of the project.
> e.g the doc says: 
> https://cmake.org/cmake/help/latest/command/add_library.html#imported-libraries
> "An IMPORTED library target references a library file located outside the 
> project"
>
> Nmelly a target that is "already installed somewhere" and that you want to 
> reference in your CMake build.
>
>>
>> but if so then your statement that "The goal that you have is fully 
>> supported by CMake" seems to be incorrect. To reiterate, I am trying to use 
>> foreign tools to make binary targets and wish to have CMake treat them *as 
>> if* they were created by supported languages like C, ++, or Fortran. Am I 
>> still missing something?
>
>
> My opinion is that IMPORTED target are not designed (as of today) for that 
> purpose.
>
> When you want to do what you seem to want you need to either:
> 1) add a "new LANGUAGE" (you seem to be willing to add golang)
> see: 
> https://stackoverflow.com/questions/7978517/how-do-i-get-cmake-to-work-with-the-go-programming-language
> and may be: https://github.com/aadidenko/golang-cmake-example (or fork of 
> this)
>
> 2) define a set of custom macros that mimic genuine target behaviour.
> may be see: https://github.com/cpconduce/go_cmake
>
> If you want to have a look at existing similar example shippped with CMake, 
> have a look at UseJava.cmake module 
> (https://cmake.org/cmake/help/latest/module/UseJava.html)
> You'll see that you have
> add_jar, which is similar to add_executable and create a custom target
> and
> install_jar which is similar to install on genuine target but plays with 
> target properties and install(FILES...) in order to mimic that.
> see: https://github.com/Kitware/CMake/blob/master/Modules/UseJava.cmake
>
> I'm not developing with golang but AFAIK go has a builtin "build system" so 
> bringing go as a language in CMake may not be the best option,
> but again I am no Go expert.
>
> The only reference of that kind of thing I found in the CMake mailing list is 
> oldish:
> https://cmake.org/pipermail/cmake-developers/2011-August/013715.html
>
> May be adding the support for "install" command for IMPORTED target is doable 
> but this seems to be a feature request to be discussed on developer mailing 
> list;
> Regards,
> Eric
>
>>
>> Regards
>> Bill Somerville.
>>
>> On 24/05/2019 20:23, Robert Maynard wrote:
>>
>> Hi,
>>
>> The goal that you have is fully supported by CMake. You have just run
>> into a bug in CMake, and you should report this to
>> https://gitlab.kitware.com/cmake/cmake/issues .
>> Basically at a very high level the name out the