VERSION_MINOR 11)
-set(CMake_VERSION_PATCH 20180302)
+set(CMake_VERSION_PATCH 20180303)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
You miss a runtime search path when linking your executable. And this is what
you achieved with install_name_tool with an additional step.
To avoid this additional step, see
I was able to get 3.9.6 to compile setting CMAKE_PREFIX_PATH to the same
path that I pass .bootstrap with --prefix. I also had to patch
the Modules/Compiler/GNU.cmake file to use -idirafter rather than -isystem
as the latter leads to issues with #include_next.
I'm still perplexed why 3.10.2
Hello all,
When making a pure Swift bundle Xcode automatically copies `libswiftCore.dylib`
as follows.
```
./Tests/SwiftOnly/Debug/SwiftOnly.app
└── Contents
├── Frameworks
│ └── libswiftCore.dylib
├── Info.plist
├── MacOS
│ └── SwiftOnly
├── PkgInfo
└──
I have a completely insulated boostrapped toolchain+binaries setup
(located under /home/tools), following much of the Linux From Scratch book,
that has been able to build everything that I throw at it. Most things just
work with a simple --prefix option, as I have also edited the GCC specs
file
Oh good point on OpenSSL, their official build steps are awkard enough, let
alone trying to emulate them in CMake!
For what it's worth, we've upgraded boost-cmake to Boost 1.65 so far with no
changes required to any of the modules we use.
The other 3rd party module manager we're looking into
Interesting project, so thanks for the link!
The problem we have is that changing the build system for external projects
isn’t really acceptable. In this boost-cmake build they ripped out jam and
replaced it with cmake, which is kind of cool, but such action is not a good
plan for OpenSSL. If
Hi Cameron,
For boost integration into our cmake project, we're using this (slightly
customised for our use):
https://github.com/Orphis/boost-cmake
It unzips boost into your build folder, and builds the required packages on
demand (not all of boost, just the boost modules you use).
It works
I’m using ExternalProject_Add to download a Git project that is a pre-requisite
of my project. For the sake of the discussion I’ve wrapped OpenSSL and Boost in
this manner placing tagged version of the source in my repo.
Building them isn’t really a problem, they run, take a long time
