[Cmake-commits] CMake branch, master, updated. v3.13.0-rc2-335-g4476005
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 44760059fcbd9e84bd560c2be9ea00c5483da8f2 (commit) from e5d298b8fdb12283291f37048ae8f68a60a6becb (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=44760059fcbd9e84bd560c2be9ea00c5483da8f2 commit 44760059fcbd9e84bd560c2be9ea00c5483da8f2 Author: Kitware Robot AuthorDate: Tue Nov 6 00:01:08 2018 -0500 Commit: Kitware Robot CommitDate: Tue Nov 6 00:01:08 2018 -0500 CMake Nightly Date Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index cfce90d..7918d80 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 20181105) +set(CMake_VERSION_PATCH 20181106) #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
Re: [CMake] Link order (Ubuntu)
Hi
This is the classical issue of GNU toolchain for many years, usually super
painful when the program has to be linked with several static libraries.
One easy way to solve this issue is that you could specify the same library
for multiple times if the manual order really doesn't work well, then the
generated binary might have the complete symbols.
Thanks very much.
On Tue, Nov 6, 2018 at 9:53 AM scrgiorgio wrote:
> i have the following CMakeList.txt:
>
>
> add_library(ImpLib SHARED IMPORTED GLOBAL)
> set_property(TARGET ImpLib APPEND PROPERTY INTERFACE_INCLUDE_DIRECTORIES
> ...)
> set_target_properties(ImpLib PROPERTIES IMPORTED_LOCATION ...)
>
> add_library(A SHARED)
> # COMMENTED! A uses ImpLib but cannot link it because some third-party
> executables requires 'run-time symbol resolution'
> # target_link_libraries(A PUBLIC ImpLib )
>
> add_library(B SHARED)
> target_link_libraries(B PUBLIC A)
> # COMMENTED! B uses ImpLib but cannot link it for the same previous reason
> # target_link_libraries(B PUBLIC ImpLib )
>
> # my executable requires ImpLib explicit/default cmake linking
> add_executable(MyExe)
> target_link_libraries(MyExe B)
> target_link_libraries(MyExe ImpLib )
>
> The CMake generated link order is (g++ -o ): "B;ImportedExtLib;A"
> But in this way A cannot find symbols from ImpLib (at least using g++).
>
> The right order is: "B;A;ImpLib"
>
> I tried with "target_link_libraries(A INTERFACE ImpLib)" but then B will
> link ImpLib
>
> I tried "set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS}
> -Wl,--start-group")" but sometimes it does not work.
>
> is it doable? Can I force the right order?
>
>
>
>
>
> --
> Sent from: http://cmake.3232098.n2.nabble.com/
> --
>
> 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
[CMake] Link order (Ubuntu)
i have the following CMakeList.txt:
add_library(ImpLib SHARED IMPORTED GLOBAL)
set_property(TARGET ImpLib APPEND PROPERTY INTERFACE_INCLUDE_DIRECTORIES
...)
set_target_properties(ImpLib PROPERTIES IMPORTED_LOCATION ...)
add_library(A SHARED)
# COMMENTED! A uses ImpLib but cannot link it because some third-party
executables requires 'run-time symbol resolution'
# target_link_libraries(A PUBLIC ImpLib )
add_library(B SHARED)
target_link_libraries(B PUBLIC A)
# COMMENTED! B uses ImpLib but cannot link it for the same previous reason
# target_link_libraries(B PUBLIC ImpLib )
# my executable requires ImpLib explicit/default cmake linking
add_executable(MyExe)
target_link_libraries(MyExe B)
target_link_libraries(MyExe ImpLib )
The CMake generated link order is (g++ -o ): "B;ImportedExtLib;A"
But in this way A cannot find symbols from ImpLib (at least using g++).
The right order is: "B;A;ImpLib"
I tried with "target_link_libraries(A INTERFACE ImpLib)" but then B will
link ImpLib
I tried "set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS}
-Wl,--start-group")" but sometimes it does not work.
is it doable? Can I force the right order?
--
Sent from: http://cmake.3232098.n2.nabble.com/
--
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] Link order problem (Ubuntu)
i have the following CMakeList.txt: the CMake generated link order is (g++ -o ): But in this way A cannot find symbols from ImpLib (at least using g++). The right order is Is it doable? I tried: but then B will link ImpLib I tried: but sometimes it does not work. is it doable? Can I force the right order? -- Sent from: http://cmake.3232098.n2.nabble.com/ -- 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] Default library name?
On 2018 M11 5, Mon 13:20:32 CET Robert Maynard wrote: > Yes, you can do that. I don't know if there is an easier way than the > following: you could have a look at the following variables: CMAKE_STATIC_LIBRARY_PREFIX CMAKE_STATIC_LIBRARY_SUFFIX CMAKE_SHARED_LIBRARY_PREFIX CMAKE_SHARED_LIBRARY_SUFFIX CMAKE_EXECUTABLE_SUFFIX Alex -- 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] Default library name?
>> So you could pass the name of the target as command line parameter.
We do all sorts of string operations on it. This wouldn't work with the
generator expression.
On Mon, Nov 5, 2018 at 11:12 AM Robert Maynard
wrote:
> The add_test command support generator expressions as part of the
> COMMAND component (
> https://cmake.org/cmake/help/v3.11/command/add_test.html). So you
> could pass the name of the target as command line parameter.
> On Mon, Nov 5, 2018 at 1:43 PM Hendrik Greving
> wrote:
> >
> > I see. We may be able to work with this. Thanks a lot!
> > generator expressions don't work with LINK_FLAGS (though I heard they
> will be supported in LINK_OPTIONS in 3.13, which would require us to
> migrate. But even then, generator expressions don't support and logic
> around this like file(GNERATE ..) or string(REPLACE ..) that our (cmake-)
> files use frequently. i.e. we are changing paths to upload on an Android
> target. Another big issue is that we are using the target name for add_test
> commands, i.e. in order to compute some library names based on the target
> name as part of the test command. I can't use file(GENERATE to derive the
> target name and put the add_test part into a .cmake script because add_test
> is not scriptable.
> > Thanks.
> >
> > On Mon, Nov 5, 2018 at 10:21 AM Robert Maynard <
> robert.mayn...@kitware.com> wrote:
> >>
> >> Yes, you can do that. I don't know if there is an easier way than the
> >> following:
> >>
> >> function(get_full_name target full_name)
> >> get_target_property(name ${target} NAME)
> >> get_target_property(suffix ${target} SUFFIX)
> >> get_target_property(prefix ${target} PREFIX)
> >> get_target_property(type ${target} TYPE)
> >>
> >> if(NOT prefix)
> >> set(prefix ${CMAKE_${type}_PREFIX})
> >> endif()
> >>
> >> if(NOT suffix)
> >> set(suffix ${CMAKE_${type}_SUFFIX})
> >> endif()
> >>
> >> set(${full_name} "${prefix}${name}${suffix}" PARENT_SCOPE)
> >> endfunction()
> >>
> >> You will need to modify it if you want to support custom per config
> >> names. Unless you really needs this information at configuration you
> >> should use the $ generator expression as it will
> >> always be correct.
> >> On Mon, Nov 5, 2018 at 1:04 PM Hendrik Greving
> >> wrote:
> >> >
> >> > The name property doesn't return the library name for libraries, i.e.
> on Linux, no lib prefix and .so suffix. Also the PREFIX and SUFFIX (see
> above) don't appear to be set. Is it possible to retrieve the default
> library name on a given platform?
> >> >
> >> > On Mon, Nov 5, 2018 at 9:57 AM Robert Maynard <
> robert.mayn...@kitware.com> wrote:
> >> >>
> >> >> That is correct behavior. OUTPUT_NAME is a customization point to
> >> >> allow projects to change the name, so if it isn't set CMake will use
> >> >> the NAME property.
> >> >> On Mon, Nov 5, 2018 at 12:42 PM Hendrik Greving
> >> >> wrote:
> >> >> >
> >> >> > I think OUTPUT_NAME is not set by default. I am getting
> var-NOTFOUND
> >> >> > Same for RUNTIME_OUTPUT_NAME, LIBRARY_OUTPUT_NAME, PREFIX and
> SUFFIX
> >> >> >
> >> >> > On Mon, Nov 5, 2018 at 9:26 AM Robert Maynard <
> robert.mayn...@kitware.com> wrote:
> >> >> >>
> >> >> >> At configure time you query OUTPUT_NAME target property
> >> >> >> (https://cmake.org/cmake/help/v3.11/prop_tgt/OUTPUT_NAME.html)
> and if
> >> >> >> not set you use NAME (
> >> >> >> https://cmake.org/cmake/help/v3.11/prop_tgt/NAME.html )
> >> >> >> On Mon, Nov 5, 2018 at 11:48 AM Hendrik Greving
> >> >> >> wrote:
> >> >> >> >
> >> >> >> > Hi, is there a way to get the default library or executable
> name at configure time (except obsolete LOCATION property)? i.e.
> lib${target_name}.so in Linux, where target_name is NAME target property?
> Thanks in advance.
> >> >> >> > --
> >> >> >> >
> >> >> >> > 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
Re: [CMake] Default library name?
The add_test command support generator expressions as part of the
COMMAND component (
https://cmake.org/cmake/help/v3.11/command/add_test.html). So you
could pass the name of the target as command line parameter.
On Mon, Nov 5, 2018 at 1:43 PM Hendrik Greving
wrote:
>
> I see. We may be able to work with this. Thanks a lot!
> generator expressions don't work with LINK_FLAGS (though I heard they will be
> supported in LINK_OPTIONS in 3.13, which would require us to migrate. But
> even then, generator expressions don't support and logic around this like
> file(GNERATE ..) or string(REPLACE ..) that our (cmake-) files use
> frequently. i.e. we are changing paths to upload on an Android target.
> Another big issue is that we are using the target name for add_test commands,
> i.e. in order to compute some library names based on the target name as part
> of the test command. I can't use file(GENERATE to derive the target name and
> put the add_test part into a .cmake script because add_test is not scriptable.
> Thanks.
>
> On Mon, Nov 5, 2018 at 10:21 AM Robert Maynard
> wrote:
>>
>> Yes, you can do that. I don't know if there is an easier way than the
>> following:
>>
>> function(get_full_name target full_name)
>> get_target_property(name ${target} NAME)
>> get_target_property(suffix ${target} SUFFIX)
>> get_target_property(prefix ${target} PREFIX)
>> get_target_property(type ${target} TYPE)
>>
>> if(NOT prefix)
>> set(prefix ${CMAKE_${type}_PREFIX})
>> endif()
>>
>> if(NOT suffix)
>> set(suffix ${CMAKE_${type}_SUFFIX})
>> endif()
>>
>> set(${full_name} "${prefix}${name}${suffix}" PARENT_SCOPE)
>> endfunction()
>>
>> You will need to modify it if you want to support custom per config
>> names. Unless you really needs this information at configuration you
>> should use the $ generator expression as it will
>> always be correct.
>> On Mon, Nov 5, 2018 at 1:04 PM Hendrik Greving
>> wrote:
>> >
>> > The name property doesn't return the library name for libraries, i.e. on
>> > Linux, no lib prefix and .so suffix. Also the PREFIX and SUFFIX (see
>> > above) don't appear to be set. Is it possible to retrieve the default
>> > library name on a given platform?
>> >
>> > On Mon, Nov 5, 2018 at 9:57 AM Robert Maynard
>> > wrote:
>> >>
>> >> That is correct behavior. OUTPUT_NAME is a customization point to
>> >> allow projects to change the name, so if it isn't set CMake will use
>> >> the NAME property.
>> >> On Mon, Nov 5, 2018 at 12:42 PM Hendrik Greving
>> >> wrote:
>> >> >
>> >> > I think OUTPUT_NAME is not set by default. I am getting var-NOTFOUND
>> >> > Same for RUNTIME_OUTPUT_NAME, LIBRARY_OUTPUT_NAME, PREFIX and SUFFIX
>> >> >
>> >> > On Mon, Nov 5, 2018 at 9:26 AM Robert Maynard
>> >> > wrote:
>> >> >>
>> >> >> At configure time you query OUTPUT_NAME target property
>> >> >> (https://cmake.org/cmake/help/v3.11/prop_tgt/OUTPUT_NAME.html) and if
>> >> >> not set you use NAME (
>> >> >> https://cmake.org/cmake/help/v3.11/prop_tgt/NAME.html )
>> >> >> On Mon, Nov 5, 2018 at 11:48 AM Hendrik Greving
>> >> >> wrote:
>> >> >> >
>> >> >> > Hi, is there a way to get the default library or executable name at
>> >> >> > configure time (except obsolete LOCATION property)? i.e.
>> >> >> > lib${target_name}.so in Linux, where target_name is NAME target
>> >> >> > property? Thanks in advance.
>> >> >> > --
>> >> >> >
>> >> >> > 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] Default library name?
I see. We may be able to work with this. Thanks a lot!
generator expressions don't work with LINK_FLAGS (though I heard they will
be supported in LINK_OPTIONS in 3.13, which would require us to migrate.
But even then, generator expressions don't support and logic around this
like file(GNERATE ..) or string(REPLACE ..) that our (cmake-) files use
frequently. i.e. we are changing paths to upload on an Android target.
Another big issue is that we are using the target name for add_test
commands, i.e. in order to compute some library names based on the target
name as part of the test command. I can't use file(GENERATE to derive the
target name and put the add_test part into a .cmake script because add_test
is not scriptable.
Thanks.
On Mon, Nov 5, 2018 at 10:21 AM Robert Maynard
wrote:
> Yes, you can do that. I don't know if there is an easier way than the
> following:
>
> function(get_full_name target full_name)
> get_target_property(name ${target} NAME)
> get_target_property(suffix ${target} SUFFIX)
> get_target_property(prefix ${target} PREFIX)
> get_target_property(type ${target} TYPE)
>
> if(NOT prefix)
> set(prefix ${CMAKE_${type}_PREFIX})
> endif()
>
> if(NOT suffix)
> set(suffix ${CMAKE_${type}_SUFFIX})
> endif()
>
> set(${full_name} "${prefix}${name}${suffix}" PARENT_SCOPE)
> endfunction()
>
> You will need to modify it if you want to support custom per config
> names. Unless you really needs this information at configuration you
> should use the $ generator expression as it will
> always be correct.
> On Mon, Nov 5, 2018 at 1:04 PM Hendrik Greving
> wrote:
> >
> > The name property doesn't return the library name for libraries, i.e. on
> Linux, no lib prefix and .so suffix. Also the PREFIX and SUFFIX (see above)
> don't appear to be set. Is it possible to retrieve the default library name
> on a given platform?
> >
> > On Mon, Nov 5, 2018 at 9:57 AM Robert Maynard <
> robert.mayn...@kitware.com> wrote:
> >>
> >> That is correct behavior. OUTPUT_NAME is a customization point to
> >> allow projects to change the name, so if it isn't set CMake will use
> >> the NAME property.
> >> On Mon, Nov 5, 2018 at 12:42 PM Hendrik Greving
> >> wrote:
> >> >
> >> > I think OUTPUT_NAME is not set by default. I am getting var-NOTFOUND
> >> > Same for RUNTIME_OUTPUT_NAME, LIBRARY_OUTPUT_NAME, PREFIX and SUFFIX
> >> >
> >> > On Mon, Nov 5, 2018 at 9:26 AM Robert Maynard <
> robert.mayn...@kitware.com> wrote:
> >> >>
> >> >> At configure time you query OUTPUT_NAME target property
> >> >> (https://cmake.org/cmake/help/v3.11/prop_tgt/OUTPUT_NAME.html) and
> if
> >> >> not set you use NAME (
> >> >> https://cmake.org/cmake/help/v3.11/prop_tgt/NAME.html )
> >> >> On Mon, Nov 5, 2018 at 11:48 AM Hendrik Greving
> >> >> wrote:
> >> >> >
> >> >> > Hi, is there a way to get the default library or executable name
> at configure time (except obsolete LOCATION property)? i.e.
> lib${target_name}.so in Linux, where target_name is NAME target property?
> Thanks in advance.
> >> >> > --
> >> >> >
> >> >> > 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] Default library name?
Yes, you can do that. I don't know if there is an easier way than the
following:
function(get_full_name target full_name)
get_target_property(name ${target} NAME)
get_target_property(suffix ${target} SUFFIX)
get_target_property(prefix ${target} PREFIX)
get_target_property(type ${target} TYPE)
if(NOT prefix)
set(prefix ${CMAKE_${type}_PREFIX})
endif()
if(NOT suffix)
set(suffix ${CMAKE_${type}_SUFFIX})
endif()
set(${full_name} "${prefix}${name}${suffix}" PARENT_SCOPE)
endfunction()
You will need to modify it if you want to support custom per config
names. Unless you really needs this information at configuration you
should use the $ generator expression as it will
always be correct.
On Mon, Nov 5, 2018 at 1:04 PM Hendrik Greving
wrote:
>
> The name property doesn't return the library name for libraries, i.e. on
> Linux, no lib prefix and .so suffix. Also the PREFIX and SUFFIX (see above)
> don't appear to be set. Is it possible to retrieve the default library name
> on a given platform?
>
> On Mon, Nov 5, 2018 at 9:57 AM Robert Maynard
> wrote:
>>
>> That is correct behavior. OUTPUT_NAME is a customization point to
>> allow projects to change the name, so if it isn't set CMake will use
>> the NAME property.
>> On Mon, Nov 5, 2018 at 12:42 PM Hendrik Greving
>> wrote:
>> >
>> > I think OUTPUT_NAME is not set by default. I am getting var-NOTFOUND
>> > Same for RUNTIME_OUTPUT_NAME, LIBRARY_OUTPUT_NAME, PREFIX and SUFFIX
>> >
>> > On Mon, Nov 5, 2018 at 9:26 AM Robert Maynard
>> > wrote:
>> >>
>> >> At configure time you query OUTPUT_NAME target property
>> >> (https://cmake.org/cmake/help/v3.11/prop_tgt/OUTPUT_NAME.html) and if
>> >> not set you use NAME (
>> >> https://cmake.org/cmake/help/v3.11/prop_tgt/NAME.html )
>> >> On Mon, Nov 5, 2018 at 11:48 AM Hendrik Greving
>> >> wrote:
>> >> >
>> >> > Hi, is there a way to get the default library or executable name at
>> >> > configure time (except obsolete LOCATION property)? i.e.
>> >> > lib${target_name}.so in Linux, where target_name is NAME target
>> >> > property? Thanks in advance.
>> >> > --
>> >> >
>> >> > 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] Default library name?
The name property doesn't return the library name for libraries, i.e. on
Linux, no lib prefix and .so suffix. Also the PREFIX and SUFFIX (see above)
don't appear to be set. Is it possible to retrieve the default library name
on a given platform?
On Mon, Nov 5, 2018 at 9:57 AM Robert Maynard
wrote:
> That is correct behavior. OUTPUT_NAME is a customization point to
> allow projects to change the name, so if it isn't set CMake will use
> the NAME property.
> On Mon, Nov 5, 2018 at 12:42 PM Hendrik Greving
> wrote:
> >
> > I think OUTPUT_NAME is not set by default. I am getting var-NOTFOUND
> > Same for RUNTIME_OUTPUT_NAME, LIBRARY_OUTPUT_NAME, PREFIX and SUFFIX
> >
> > On Mon, Nov 5, 2018 at 9:26 AM Robert Maynard <
> robert.mayn...@kitware.com> wrote:
> >>
> >> At configure time you query OUTPUT_NAME target property
> >> (https://cmake.org/cmake/help/v3.11/prop_tgt/OUTPUT_NAME.html) and if
> >> not set you use NAME (
> >> https://cmake.org/cmake/help/v3.11/prop_tgt/NAME.html )
> >> On Mon, Nov 5, 2018 at 11:48 AM Hendrik Greving
> >> wrote:
> >> >
> >> > Hi, is there a way to get the default library or executable name at
> configure time (except obsolete LOCATION property)? i.e.
> lib${target_name}.so in Linux, where target_name is NAME target property?
> Thanks in advance.
> >> > --
> >> >
> >> > 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] Default library name?
That is correct behavior. OUTPUT_NAME is a customization point to
allow projects to change the name, so if it isn't set CMake will use
the NAME property.
On Mon, Nov 5, 2018 at 12:42 PM Hendrik Greving
wrote:
>
> I think OUTPUT_NAME is not set by default. I am getting var-NOTFOUND
> Same for RUNTIME_OUTPUT_NAME, LIBRARY_OUTPUT_NAME, PREFIX and SUFFIX
>
> On Mon, Nov 5, 2018 at 9:26 AM Robert Maynard
> wrote:
>>
>> At configure time you query OUTPUT_NAME target property
>> (https://cmake.org/cmake/help/v3.11/prop_tgt/OUTPUT_NAME.html) and if
>> not set you use NAME (
>> https://cmake.org/cmake/help/v3.11/prop_tgt/NAME.html )
>> On Mon, Nov 5, 2018 at 11:48 AM Hendrik Greving
>> wrote:
>> >
>> > Hi, is there a way to get the default library or executable name at
>> > configure time (except obsolete LOCATION property)? i.e.
>> > lib${target_name}.so in Linux, where target_name is NAME target property?
>> > Thanks in advance.
>> > --
>> >
>> > 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] Default library name?
I think OUTPUT_NAME is not set by default. I am getting var-NOTFOUND
Same for RUNTIME_OUTPUT_NAME, LIBRARY_OUTPUT_NAME, PREFIX and SUFFIX
On Mon, Nov 5, 2018 at 9:26 AM Robert Maynard
wrote:
> At configure time you query OUTPUT_NAME target property
> (https://cmake.org/cmake/help/v3.11/prop_tgt/OUTPUT_NAME.html) and if
> not set you use NAME (
> https://cmake.org/cmake/help/v3.11/prop_tgt/NAME.html )
> On Mon, Nov 5, 2018 at 11:48 AM Hendrik Greving
> wrote:
> >
> > Hi, is there a way to get the default library or executable name at
> configure time (except obsolete LOCATION property)? i.e.
> lib${target_name}.so in Linux, where target_name is NAME target property?
> Thanks in advance.
> > --
> >
> > 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] Default library name?
At configure time you query OUTPUT_NAME target property
(https://cmake.org/cmake/help/v3.11/prop_tgt/OUTPUT_NAME.html) and if
not set you use NAME (
https://cmake.org/cmake/help/v3.11/prop_tgt/NAME.html )
On Mon, Nov 5, 2018 at 11:48 AM Hendrik Greving
wrote:
>
> Hi, is there a way to get the default library or executable name at configure
> time (except obsolete LOCATION property)? i.e. lib${target_name}.so in Linux,
> where target_name is NAME target property? Thanks in advance.
> --
>
> 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
[CMake] Default library name?
Hi, is there a way to get the default library or executable name at
configure time (except obsolete LOCATION property)? i.e.
lib${target_name}.so in Linux, where target_name is NAME target property?
Thanks in advance.
--
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-commits] CMake branch, master, updated. v3.13.0-rc2-334-ge5d298b
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 e5d298b8fdb12283291f37048ae8f68a60a6becb (commit) via 066db7576dda43c6a716b4201c0399a1e3ae9c2b (commit) via 36280e6157e883fb5257f211d24582b5e7ff4244 (commit) via 4cd059480a40cc4a2c7e326f8bb1fe11fe46ba0c (commit) via 85aceda0262bff58a0126b2d4e75756e0507fe3c (commit) from b83420e45d963e2decd94336b97c127c75eed990 (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=e5d298b8fdb12283291f37048ae8f68a60a6becb commit e5d298b8fdb12283291f37048ae8f68a60a6becb Merge: 066db75 85aceda Author: Brad King AuthorDate: Mon Nov 5 12:50:13 2018 + Commit: Kitware Robot CommitDate: Mon Nov 5 07:50:20 2018 -0500 Merge topic 'lwyu-hides-link-error' 85aceda026 cmNinjaNormalTargetGenerator: don't use `|| true` for link-what-you-use Acked-by: Kitware Robot Merge-request: !2546 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=066db7576dda43c6a716b4201c0399a1e3ae9c2b commit 066db7576dda43c6a716b4201c0399a1e3ae9c2b Merge: b83420e 36280e6 Author: Brad King AuthorDate: Mon Nov 5 07:49:06 2018 -0500 Commit: Brad King CommitDate: Mon Nov 5 07:49:06 2018 -0500 Merge branch 'release-3.13' https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=85aceda0262bff58a0126b2d4e75756e0507fe3c commit 85aceda0262bff58a0126b2d4e75756e0507fe3c Author: Ben Boeckel AuthorDate: Mon Oct 29 15:49:44 2018 -0400 Commit: Ben Boeckel CommitDate: Fri Nov 2 10:25:56 2018 -0400 cmNinjaNormalTargetGenerator: don't use `|| true` for link-what-you-use With the `|| true`, a linker error before running link-what-you-use would also use the `|| true` fragment and unconditionally succeed. Just skip the addition since `--lwyu=` ignores the return value anyways. Fixes #18524 diff --git a/Source/cmNinjaNormalTargetGenerator.cxx b/Source/cmNinjaNormalTargetGenerator.cxx index 6436969..1386706 100644 --- a/Source/cmNinjaNormalTargetGenerator.cxx +++ b/Source/cmNinjaNormalTargetGenerator.cxx @@ -506,7 +506,6 @@ std::vector cmNinjaNormalTargetGenerator::ComputeLinkCmd() gt.GetFullPath(cfgName, cmStateEnums::RuntimeBinaryArtifact, /*realname=*/true)); cmakeCommand += targetOutputReal; -cmakeCommand += " || true"; linkCmds.push_back(std::move(cmakeCommand)); } return linkCmds; --- Summary of changes: Source/cmNinjaNormalTargetGenerator.cxx | 1 - 1 file changed, 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, release, updated. v3.13.0-rc2-38-g36280e6
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, release has been updated via 36280e6157e883fb5257f211d24582b5e7ff4244 (commit) via 4cd059480a40cc4a2c7e326f8bb1fe11fe46ba0c (commit) via 98d59417b0c6ac3ea85e31517030dad93496 (commit) via c1ad5118deb0eb52c2130e0fb3363f44c25bf42e (commit) via 03bf934fbe93ef04d6c62c64912d2f212db997b7 (commit) via 2b3c1bb9b014cf34ab882b8ab9569846c274cc8a (commit) via 636bcefeab3b386e65efe03b199b9b2614d8a78d (commit) via 9835e9075037db3d23ade0ef865c562b08cf6023 (commit) via 9c6574795c404417939c889d8cb45095c4175474 (commit) from 03d00d63dfc2ee5ed3775eccdbd012245acba6ce (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 - --- Summary of changes: Source/cmAddCustomCommandCommand.cxx |6 - Source/cmAddCustomTargetCommand.cxx|7 - Source/cmCustomCommandGenerator.cxx|6 + Tests/CustomCommandWorkingDirectory/CMakeLists.txt |4 +- Utilities/.gitattributes |1 + Utilities/Scripts/update-curl.bash |2 +- Utilities/cmcurl/CMake/CMakeConfigurableFile.in|1 - Utilities/cmcurl/CMake/CurlTests.c | 16 + Utilities/cmcurl/CMake/curl-config.cmake.in| 66 +- Utilities/cmcurl/CMakeLists.txt| 93 +- Utilities/cmcurl/curltest.c| 184 +-- Utilities/cmcurl/include/curl/curl.h | 25 +- Utilities/cmcurl/include/curl/curlver.h|8 +- Utilities/cmcurl/include/curl/easy.h | 10 + Utilities/cmcurl/include/curl/system.h |2 +- Utilities/cmcurl/include/curl/typecheck-gcc.h |6 +- Utilities/cmcurl/include/curl/urlapi.h | 120 ++ Utilities/cmcurl/lib/CMakeLists.txt| 17 +- Utilities/cmcurl/lib/Makefile.inc |9 +- Utilities/cmcurl/lib/amigaos.h |1 - Utilities/cmcurl/lib/arpa_telnet.h |6 +- Utilities/cmcurl/lib/cookie.c | 26 +- Utilities/cmcurl/lib/curl_config.h.cmake |3 + Utilities/cmcurl/lib/curl_ldap.h |1 - Utilities/cmcurl/lib/curl_ntlm_wb.c| 18 +- Utilities/cmcurl/lib/curl_path.c |4 +- Utilities/cmcurl/lib/curl_path.h |2 +- Utilities/cmcurl/lib/curl_rtmp.c |4 +- Utilities/cmcurl/lib/curl_setup.h |5 +- Utilities/cmcurl/lib/curl_setup_once.h |1 - Utilities/cmcurl/lib/curl_sspi.c |7 +- Utilities/cmcurl/lib/curl_threads.c| 14 +- Utilities/cmcurl/lib/curl_threads.h|3 +- Utilities/cmcurl/lib/curlx.h |1 - Utilities/cmcurl/lib/dict.c|2 +- Utilities/cmcurl/lib/doh.c | 920 ++ Utilities/cmcurl/lib/doh.h | 105 ++ Utilities/cmcurl/lib/dotdot.c |2 + Utilities/cmcurl/lib/dotdot.h |2 +- Utilities/cmcurl/lib/easy.c| 23 +- Utilities/cmcurl/lib/easyif.h |1 - Utilities/cmcurl/lib/escape.c | 20 +- Utilities/cmcurl/lib/escape.h |4 +- Utilities/cmcurl/lib/file.c| 33 +- Utilities/cmcurl/lib/file.h|1 - Utilities/cmcurl/lib/ftp.c | 46 +- Utilities/cmcurl/lib/ftp.h |2 + Utilities/cmcurl/lib/getinfo.c |1 - Utilities/cmcurl/lib/gopher.c |2 +- Utilities/cmcurl/lib/hostasyn.c| 25 - Utilities/cmcurl/lib/hostcheck.h |1 - Utilities/cmcurl/lib/hostip.c | 78 +- Utilities/cmcurl/lib/hostip.h | 13 +- Utilities/cmcurl/lib/http.c| 245 ++-- Utilities/cmcurl/lib/http.h| 19 +- Utilities/cmcurl/lib/http2.c | 135 +- Utilities/cmcurl/lib/http2.h |1 - Utilities/cmcurl/lib/http_chunks.h |1 - Utilities/cmcurl/lib/http_proxy.c | 14 +- Utilities/cmcurl/lib/imap.c| 84 +- Utilities/cmcurl/lib/imap.h|1 + Utilities/cmcurl/lib/inet_ntop.h |1 -
