Hi everyone,
any feedback on this?
As a summary, it's about adding the default include paths of GCC to the
variables "CMAKE_*_IMPLICIT_INCLUDE_DIRECTORIES" to avoid CMake modules
or scripts to mess up with them, more specifically with their order.
Cheers,
Olivier
On 2018-11-3 21:41,
t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index ad29c57..5f7dd8a 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 20181107)
+set(CMake_VER
Hello,
I can use cmake-gui successfully with “Visual Studio 15 2017 Win64,” but am not
successful with using “Codeblocks – Nmake Makefiles.” I can use both
successfully from the commandline to make Makrfiles.
Does cmake-gui work with codeblocks? If it does, can somebody suggest some
I finally found this hack:
target_link_libraries(MyExe B $ ImpLib)
so I'm forcing the 'A' dependency to appear before the ImpLib.
Note that if I use:
target_link_libraries(MyExe B A ImpLib)
it does not work. I think it's because Cmake it's internally erasing
unnecessary dependencies.
Oh, if that's shared libraries, maybe you have to setup the LD_LIBRARY_PATH
well for the shared libraries before linking, it just allows the linker to
be able to locate the all necessary dynamic libraries during the linking.
It happens sometimes on Linux, but not exists on OSX and Windows.
On
On 2018-11-07 22:48- Osman Zakir wrote:
I want to remove CMake from my Docker image in order to reduce the image size
(I'm also going to remove g++, make and build-essential -- it's after the
executable program has been built). How do I do this?
My opinion is this question is off-topic
I want to remove CMake from my Docker image in order to reduce the image size
(I'm also going to remove g++, make and build-essential -- it's after the
executable program has been built). How do I do this?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
Ok, that works for us!
On Wed, Nov 7, 2018 at 2:29 PM Robert Maynard
wrote:
> Yes you can get if a target is imported by seeing if the IMPORTED
> property is set to true. (
> https://cmake.org/cmake/help/v3.12/prop_tgt/IMPORTED.html )
> On Wed, Nov 7, 2018 at 5:24 PM Hendrik Greving
> wrote:
>
Yes you can get if a target is imported by seeing if the IMPORTED
property is set to true. (
https://cmake.org/cmake/help/v3.12/prop_tgt/IMPORTED.html )
On Wed, Nov 7, 2018 at 5:24 PM Hendrik Greving
wrote:
>
> Ok, it seems to be IMPORT_LOCATION, not IMPORTED_LOCATION
> We have a (.cmake) file
Ok, it seems to be IMPORT_LOCATION, not IMPORTED_LOCATION
We have a (.cmake) file that shared among things that use it for build
targets and external projects for imported targets. Is there a way to find
out whether a target is imported or a build target?
On Wed, Nov 7, 2018 at 2:19 PM Robert
I am not seeing any cmake errors/warnings when I do so :)
On Wed, Nov 7, 2018 at 5:15 PM Hendrik Greving
wrote:
>
> Ok! Except (see above) I do not think one can actually read
> IMPORTED_LOCATION, can I?
> Thanks! - again!
>
> On Wed, Nov 7, 2018 at 2:07 PM Robert Maynard
> wrote:
>>
>>
Ok! Except (see above) I do not think one can actually read
IMPORTED_LOCATION, can I?
Thanks! - again!
On Wed, Nov 7, 2018 at 2:07 PM Robert Maynard
wrote:
> Looking at CMP0026 more, I believe should be able to read either the
> IMPORTED_LOCATION or LOCATION for any import target without
Looking at CMP0026 more, I believe should be able to read either the
IMPORTED_LOCATION or LOCATION for any import target without triggering
the policy, as the policy only pertains to 'build' targets and not
'import' targets.
On Wed, Nov 7, 2018 at 4:51 PM Hendrik Greving
wrote:
>
> Is
Is IMPORTED_LOCATION a property one can read? I was under the assumption
that setting IMPORTED_LOCATION becomes LOCATION (for imported targets). And
as such, reading this LOCATION generates the warning. I just tried and it
indeed didn't let me read IMPORTED_LOCATION.
On Wed, Nov 7, 2018 at 12:36
I believe that IMPORTED_LOCATION is safe to use.
On Wed, Nov 7, 2018 at 3:27 PM Hendrik Greving
wrote:
>
> So IMPORTED_LOCATION is obsolete as well? (since reading LOCATION is obsolete)
>
> On Wed, Nov 7, 2018 at 11:39 AM Robert Maynard
> wrote:
>>
>> With generator expressions making the
So IMPORTED_LOCATION is obsolete as well? (since reading LOCATION is
obsolete)
On Wed, Nov 7, 2018 at 11:39 AM Robert Maynard
wrote:
> With generator expressions making the reading of LOCATION non-viable
> during configuration time ( since the actual location is now evaluated
> at generate
Did cmake finish to completion when generating the Makefiles?
On Wed, Nov 7, 2018 at 11:46 AM Steffen Dettmer
wrote:
> Hi,
>
> One (of really many) build trees contains a file "depend.make.tmp" and
> ignores dependencies leading to broken (incremental) builds. There
> also is a "depend.make"
With generator expressions making the reading of LOCATION non-viable
during configuration time ( since the actual location is now evaluated
at generate time ), the general solution is that you need to move your
LOCATION reading logic also to generate time. In general this means
using something
Hello,
w/ LOCATION property made obsolete, how can one read a target's LOCATION
for imported targets? Previously, IMPORTED_LOCATION was conveyed for such
targets, but reading the LOCATION property of imported targets leads to the
same warning as for project targets?
Thanks in advance
--
I have a very simple CMAKE to generate a .exe target (say xyz.exe) with several
.cpp source files and some external .lib files (boost and wxwidgets).
For some reason, CMAKE generates a .lib for the target (xyz.lib) and then
generate the .exe (xyz.exe) using the /IMPLIB liner option to pull in
I am proud to announce the third CMake 3.13 release candidate.
https://cmake.org/download/
The first 3.13.0 release candidates included a change to allow
generator expressions in "install(CODE)" and "install(SCRIPT)".
This has been reverted in rc2 due to breaking backwards
compatibility. See
I am proud to announce the third CMake 3.13 release candidate.
https://cmake.org/download/
The first 3.13.0 release candidates included a change to allow
generator expressions in "install(CODE)" and "install(SCRIPT)".
This has been reverted in rc2 due to breaking backwards
compatibility. See
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 8d70ed5a10362209d265a15d993f319235aea7e5 (commit)
from
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 48de9169d0624b323462c084b68cb1fdb693d91b (commit)
via
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 3bad96c9888932ec2b792f2febfee6cc58bf8bbd (commit)
via
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 7e6b78759904dcf31d780a6e2f14f3821f4f23df (commit)
via
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 annotated tag, v3.13.0-rc3 has been created
at 3b466627c5d387c21b003d641c14685c7a6c2335 (tag)
tagging
Hi,
One (of really many) build trees contains a file "depend.make.tmp" and
ignores dependencies leading to broken (incremental) builds. There
also is a "depend.make" file in the same directory saying "Empty
dependencies file. This may be replaced when dependencies are built.",
so I assume the tmp
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 71db32660eed1f70c06b624e661f8f5c2b938907 (commit)
via
SION_PATCH 20181107)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
___
30 matches
Mail list logo
