System Integrity Protection (SIP, introduced with macOS 10.11) prevents
you from writing into various system directories (like /usr) even as the
root user. You can either install cmake to a different location (like
/usr/local, which apparently is not protected), or disable SIP entirely
(which
I'm building CMake cmake-3.15.4.tar.gz on OS X 10.12. The machine is
stripped down, and only has the COmmand Line tools. No Xcode and
friends.
I configured with:
./configure --prefix=/usr
Configure appears OK. Make appears OK. Install is failing:
$ sudo make install VERBOSE=1
...
t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 32b7686..458cc86 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,7 +1,7 @@
# CMake version number components.
set(CMake_VERSION_MAJOR 3)
set(CMake_VERSION_MINOR 16)
-set(CMake_VERSION_PATCH 20191014)
+set(CMake_VER
I hit a problem with the CMake/Xcode Generator using Xcode 11. (I
think this problem started in Xcode 10 actually, but now I'm blocked
really hard and need to solve this.)
By default, Xcode is now trying to do "Sign to run locally" for the
Code Signing Identity (CODE_SIGN_IDENTITY) property, by
If it makes sense one could add mingw platform so next time cmake won't
speak warnings
# This is the CMakeCache file.
# For build in directory:
/home/user/project/blatt-1-aufgabe-3-tendermonster/build
# It was generated by CMake: /usr/bin/cmake.exe
# You can edit this file to change values found
On 2019-10-13 17:15-0400 Paul Smith wrote:
A unity source file can lump together N real source files from the same
target (library/executable) as long as those files don't have extra
source-specific flags, because all other files in a given target have
the same flags.
I agree that it is not
In the build directory, the build rules are generally like the would be in
the source too... so you can just go into src/libwhatever and do 'make' in
that branch.
like if your target was visual studio or some IDE, you could click on a
single project to build, and it would of course check and
On Mon, Oct 14, 2019, at 9:13 AM, David Aldrich wrote:
> Hi
>
> I am trying to convert a large software project from makefiles to CMake. The
> project is organised as a set of shared ‘star’ libraries, linked to a static
> ‘kernel’ library. The current directory arrangement is:
>
>
Hi
I am trying to convert a large software project from makefiles to CMake.
The project is organised as a set of shared ‘star’ libraries, linked to a
static ‘kernel’ library. The current directory arrangement is:
|--stars
| |-- star1_lib
| |-- source files
|
Hi Paul,
As another reference point, I verified that -DCMAKE_UNITY_BUILD=ON
works with the VTK-m ( https://gitlab.kitware.com/vtk/vtk-m ) project.
I only verified using a clean CMake 3.16 build directory.
On Thu, Oct 10, 2019 at 6:43 PM Paul Smith wrote:
>
> On Thu, 2019-10-10 at 14:57 -0400,
Dear all,
I am using external project. I would like to patch a source file. I came
out with a cmake script that does the string replacement I'm interested in.
I tested in a standalone project, with the following CMakeLists.txt
cmake_minimum_required(VERSION 3.4)
project(patching_string)
file
Hi,
I have got some problems finding cdk lib in my debian system
I used find_library without success
libcdk can be found in /usr/lib/x86_64-linux-gnu/
and cdk in include system path cdk/cdk.h
Regards,
S.Ancelot
--
Powered by www.kitware.com
Please keep messages on-topic and check the
12 matches
Mail list logo
