VERSION_MINOR 11)
-set(CMake_VERSION_PATCH 20180312)
+set(CMake_VERSION_PATCH 20180313)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
On Mon, Mar 12, 2018 at 15:11:28 -0500, Robert Dailey wrote:
> I'm going to add the CMake Dev group as well, since I asked this same
> question last year around May and I didn't get any response. Hoping
> for some help this time around. I don't see anything documented, so
> maybe the developers
On Mon, Mar 12, 2018 at 15:11:28 -0500, Robert Dailey wrote:
> I'm going to add the CMake Dev group as well, since I asked this same
> question last year around May and I didn't get any response. Hoping
> for some help this time around. I don't see anything documented, so
> maybe the developers
I'm going to add the CMake Dev group as well, since I asked this same
question last year around May and I didn't get any response. Hoping
for some help this time around. I don't see anything documented, so
maybe the developers know the best approach here.
On Mon, Mar 12, 2018 at 3:03 PM, Robert
I'm going to add the CMake Dev group as well, since I asked this same
question last year around May and I didn't get any response. Hoping
for some help this time around. I don't see anything documented, so
maybe the developers know the best approach here.
On Mon, Mar 12, 2018 at 3:03 PM, Robert
Sometimes I need to manually take action on the dependencies of my
targets. Without keeping track of the dependencies externally using
global or custom target properties, is there a way to obtain the list
of targets that a target depends on? This would be the same list of
targets passed to
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 89d00bfcee33a724a9a51e5a7cf40ab0785d9a9b (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 bab82b0935e543ceceddf8e339dd026d201692fe (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 378a11cdbad6732971e91d5999f5788e26e35438 (commit)
via
So after a bit of hacking it seems that Cmake should provide something like:
CMAKE_OSX_BITCODE_ENABLE
Which would pass -fembed-bitcode to the compiler and linker and remove the
option in Darwin.cmake for -Wl,-headerpad_max_install_names in
CMAKE_SHARED_LIBRARY_CREATE_C_FLAGS.
Does this sound
I’m building frameworks for iOS/tvOS with bitcode at the command-line. In order
to compile and link I need to add two things:
target_compile_options( library PUBLIC -fembed-bitcode )
target_link_libraries( library PUBLIC -fembed-bitcode )
This works, but yields the complaint that:
ld: warning:
On 03/09/2018 07:58 PM, Ondřej Čertík wrote:
> How do I make CMake pass the "Check for working Fortran compiler" phase?
The problem reported in issue 17810 is caused by trying to
enable C with MSVC and Fortran with GNU together at the same
time, e.g. `project(MyProj C Fortran)`. These tools
Thank you for the hint, and I run in a similiar problem. Building from
scratch solved the issue.
Sorry for the noise.
Am 11.03.2018 um 23:07 schrieb Craig Scott:
This could be a case of needing to clear out an old CMake cache. That
problem you mentioned was supposed to have been fixed
13 matches
Mail list logo
