How to set PIC flag in build by use of cmake command line?
as in gcc is the option -fPIC
e.g.
cmake -G "Unix Makefiles" (.. ?)
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits
hello,
I have those errors when I launch python update_deps.py depuis
vulkan-basic-samples/scripts in attachment a print screen,
Under this print screen there is this line :
'CMakeLists.txt:94 (find_package)'
For the first error I am in add Vulkan Headers GitHub It looks like registry is
in
Bad timing...
Sent from my Xperia by Sony smartphone
Robert Maynard via CMake wrote
As was previously announced, CMake is stopping mailing list usage, and
has transitioned to a Discourse forum
As was previously announced, CMake is stopping mailing list usage, and
has transitioned to a Discourse forum (https://discourse.cmake.org).
While new posts to the mailing list are disabled, all previous
discussion will be archived so that the knowledge can be searched
going forward.
Hopefully I
On Fri, 27 Mar 2020 07:18:11 +0100
Hendrik Sattler wrote:
> Hi Carlo,
>
> The answer is already right in front of you: "a && b" executes b only
> if a returns positive (zero exit code). This is already done for the
> mkdir.
>
> And to answer the other question: no, you cannot assume a POSIX
Hi Carlo,
The answer is already right in front of you: "a && b" executes b only if a
returns positive (zero exit code). This is already done for the mkdir.
And to answer the other question: no, you cannot assume a POSIX shell in a
Makefile.
HS
Am 27. März 2020 05:53:39 MEZ schrieb Carlo
Hello!
I'm writing a patch for cmake to address
https://gitlab.kitware.com/cmake/cmake/issues/19703
but I need a little help; I'm only familiar with
GNU/Linux and single target generator Makefile.
In terms of a Makefile, if one uses ExternalProject_Add_Step, see
Hi all,
I have a system of executables/libraries where all are built with “-static”
(ARM muslc toolchain). However, I have one shared object target which should be
linked dynamically. I.e. I get the error:
“attempted static link of dynamic object `lib/libmy_shared_object.so'”
Ideas on how to
I am happy to announce that CMake 3.17.0 is now available for download at:
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.17
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.17/release/3.17.html
Some of the
Hello,
with a simple GUI Qt application I’m unable to stop at a given breakpoint.
Could it be that the xcodeproj is not generated correctly?
I’m using cmake 3.16, Qt 5.14.1 and Xcode 11.3.1 on Catalina 10.15.3
Thanks in advance
Best Regards
Roman
--
Powered by kitware.com/cmake
Kitware
Hello,
What is at the moment the preferred way to deploy a Qt app to the Mac App Store
and to the iOS App Store ?
Thanks in advance
Best Regards
Roman
--
Powered by kitware.com/cmake
Kitware offers various services to support the CMake community. For more
information on each offering,
According to the documentation:
https://cmake.org/cmake/help/v3.17/prop_cache/TYPE.html
It looks like STATIC cache variables are supposed to be visible from the
CMake GUI, but not modifiable. But when I open a project that has some
STATIC variables in the CMake GUI it looks like you can't even
I am proud to announce the third CMake 3.17 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.17
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.17/release/3.17.html
Some of the more
I've been working on a relatively complicated project that uses multiple
CMake modules. Some of these modules internally include other modules. The
issue is, when one of my modules internally includes another module, all of
the functions from the internal module become visible globally throughout
I'm building this new windows system... I installed the latest cmake
I'm attempting to build this project with visual studio
1) it couldn't find an assembler until I put gcc in the path (i'm not sure
what part is requiring assembly I'll dig into that later) I added NASM to
the path, and that
Thank you; prepending C:/cygwin64/bin To CMAKE_PROGRAM_PATH was all I needed to
do to fix the problem.
-Original Message-
Date: Thu, 5 Mar 2020 14:28:27 +0100
From: Eric Doenges
You can prepend C:\cygwin64\bin to the CMAKE_PROGRAM_PATH variable so that it
looks there first.? While the
You can prepend C:\cygwin64\bin to the CMAKE_PROGRAM_PATH variable so
that it looks there first. While the find_package documentation does
not mention CMAKE_PROGRAM_PATH, I know this works for bison and flex
because that is what we do in our project (presumably, find_program is
used
To compile my application I need to use the Flex and Bison applications. To
compile under Linux, all I need to do in my CMakeLists.txt file to find them is
find_package(FLEX REQUIRED)
find_package(BISON REQUIRED)
...and everything works as expected.
In Windows, however, I'm using the
Hi Bill,
Thanks a lot for your quick response! Using your idea I could set the
Fortran module directory per module target, and add those directories as
target_include_directories to the executables. Worked like a charm!
Lukas
PS. As example, I adapted my cat/dog CMakeLists.txt to this to get to
We are pleased to announce that CMake 3.16.5 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.16.5 since 3.16.4:
On 04/03/2020 09:24, Lukas van de Wiel wrote:
we are running a Fortran code containing several dozen modules. These
are build in two versions, differentiated by #ifdef statements. The
archive files of the two versions are being kept apart by different
file names, but the .mod files have fixed
Dear more experienced cmake user,
we are running a Fortran code containing several dozen modules. These are
build in two versions, differentiated by #ifdef statements. The archive
files of the two versions are being kept apart by different file names, but
the .mod files have fixed names, based on
вт, 3 мар. 2020 г. в 07:52, Ray Satiro via CMake :
>
> I am building libssh with cmake. I have two versions of OpenSSL on my
> system and need libssh to use the later version of OpenSSL, which is in
> /usr/local/ssl/lib. I need that rpath both before and after install, as
> libssh should always
I am building libssh with cmake. I have two versions of OpenSSL on my
system and need libssh to use the later version of OpenSSL, which is in
/usr/local/ssl/lib. I need that rpath both before and after install, as
libssh should always use that version of OpenSSL. To do that I've been
passing
I am proud to announce the second CMake 3.17 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.17
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.17/release/3.17.html
Some of the more
You may want to move this to https://discourse.cmake.org/, as this mailing list
is going away (note, Im not with the cmake org at all.. just a user..)
That said,typically, when a CMake based library is included into a larger cmake
project, it will set some variables. SUBLIB_DIR for instance..
Hi all,
I really cannot say I am an expert with CMake however I have been using
it for a while now, even though mainly by copying and pasting snippet
of code from the web therefore not understanding things properly.
I am working on a project which depends on a libary which is itself
built
Reminder the CMake Discourse forum ( https://discourse.cmake.org )
is the preferred location for CMake questions and discussions. The
current mailman-based mailing lists will be disabled in April 2020,
and their archives will remain available after that.
Reminder for those who prefer email over
Hi,
I hope I can still post here? I don't have a "discourse" account.
Let me summarize what we have here. We have projects with some
hunderds CMakeLists.txt. The "main" typically use several
add_subdirectory directives for the use libraries in form of:
add_subdirectory(${path_lib_a} liba)
Hello,
I started learning CMAKE recently. I am encountering the philosophy of
targets and properties since version 3.0.
I have a project where I should build OpenCV residing in my project folder
as /myproject/third-party/opencv and then link it's library to my own
target.
After searching a lot
Hi,
I am trying to use a third party library
(https://github.com/zaphoyd/websocketpp)
It exports a Config.cmake file when building , but I want to use it from
my workspace in which I cloned it .
I tried using find_package(websocketpp CONFIG), but cmake replies
websocketpp_DIR not found.
Hello,
please help. I have problem with installing gtest/gmock on MINGW64.
Attachyed are Terminal output and CmakeOutput.log
best regards
St.Trzasak
The system is: MINGW64_NT-10.0-18362 - 3.0.7-338.x86_64 - unknown
Compiling the C compiler identification source file "CMakeCCompilerId.c"
I am proud to announce the first CMake 3.17 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.17
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.17/release/3.17.html
Some of the more
Am 10.02.20 um 14:23 schrieb Kyle Edwards via CMake:
On Mon, 2020-02-10 at 12:49 +, hex wrote:
hello,
My build step is not thread-safe (the instruction in the COMMAND
part). Every build step depends on one source file:
add_custom_command(
DEPENDS on_source.file
OUTPUT
I was trying to do this:
find_package(ICU 59.1 QUIET
COMPONENTS
data
i18n
io
tu
uc
)
if(ICU_FOUND)
include_directories(BEFORE ${ICU_INCLUDE_DIRS})
message("ICU_LIBRARIES=${ICU_LIBRARIES}")
endif()
And at configuration time, ICU_FOUND was turning up with double quotes
around it, and as we
On Mon, 2020-02-10 at 12:49 +, hex wrote:
> hello,
>
> My build step is not thread-safe (the instruction in the COMMAND
> part). Every build step depends on one source file:
>
> add_custom_command(
> DEPENDS on_source.file
> OUTPUT
>
hello,
My build step is not thread-safe (the instruction in the COMMAND part).
Every build step depends on one source file:
/add_custom_command(//
// DEPENDS on_source.file//
// OUTPUT//
// object_file_for_source_file//
// COMMAND not-thread-safe-compiler
Hi All,
I'm not sure if people are more active on here or Discourse right now, so
I'm cross-posting. Please reply on the Discourse thread if possible, but
I'll take whatever I can get : )
https://discourse.cmake.org/t/cuda-aarch64-cross-compile-fails-to-validate-nvcc/593
I am stuck trying to
I typically "set(CMAKE_Fortran_FLAGS ...)" variable in my CMake
project to set compile flags for all Fortran targets. Is this
undesired practice?
I haven't had any problems using multiple compilers, *except* for
Intel Ifort on Windows. Ifort on Linux is fine.
Here are the flags that CMake
We are pleased to announce that CMake 3.16.4 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.16.4 since 3.16.3:
We are pleased to announce that CMake 3.15.7 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.15.7 since 3.15.6:
On Mon, Feb 3, 2020 at 9:22 PM Hendrik Sattler wrote:
> Am 3. Februar 2020 20:48:50 MEZ schrieb "Jędrzej Dudkiewicz"
> :
> >Hello,
> >
> >I cross-compile a project from x86_64-linux-gnu to
> >arm-linux-gnueabihf. Currently this is done using hand-written
> >Makefiles, but I"m moving it to cmake.
Am 3. Februar 2020 20:48:50 MEZ schrieb "Jędrzej Dudkiewicz"
:
>Hello,
>
>I cross-compile a project from x86_64-linux-gnu to
>arm-linux-gnueabihf. Currently this is done using hand-written
>Makefiles, but I"m moving it to cmake. This project uses custom
>version of `lemon` parser generator.
Hello,
I cross-compile a project from x86_64-linux-gnu to
arm-linux-gnueabihf. Currently this is done using hand-written
Makefiles, but I"m moving it to cmake. This project uses custom
version of `lemon` parser generator. Aforementioned lemon is included
as a source - this is single .c file that
Hello,
I have a problem with cross-compiling that i don't know how to solve
even after days of searching.
The situation is :
- Project compiled on ARM platform directly, works fine.
- Cross-compiled, final executable linking fails because of a transitive
library not found.
I am using a few
Hi, What is the recommended way of handling installation of targets in a monorepository? We've got a fairly large project with many targets. Some of the targets are libraries used by other targets, some are final executables. Different executables depend on different libraries. So far we only
We are pleased to announce that CMake 3.16.3 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.16.3 since 3.16.2:
A reminder that CMake is transitioning to Discouse, and by the end of
March 2020 the mailing lists will be read-only, and the archives
will remain available after that.
The Discourse forum for the CMake community is:
https://discourse.cmake.org
Discourse offers users more control over their
Setting BundleIsRelocatable to false was the solution
Best regards
Roman
> Am 08.01.2020 um 21:07 schrieb Roman Wüger :
>
> Hello,
>
> I generate a productbuild installer with CPack.
>
> When I start the installer and view the files then everthing is packaged as
> it should. But when I
Hello,
I generate a productbuild installer with CPack.
When I start the installer and view the files then everthing is packaged as it
should. But when I install them, then not all files are installed.
The install protocol from the installer succeeds with no errors.
Any hints?
Best Regards
Ok if someone is interested I solved it with a post-install script at the
moment. I installed it in the default location and moved it afterwards with the
post-install script to the ~/Library...
Regards
Roman
> Am 05.11.2019 um 15:02 schrieb Roman Wüger :
>
>
> Hello,
>
> The main wish is
On 2019-12-29 12:15+1100 Craig Scott wrote:
This one has sat in my inbox for a long time - sorry I'm only getting to it
now!
No problem, and big thanks for replying late rather than taking the
easier course of replying never. I haven't yet absorbed all of what
you said, but I am sure your
This one has sat in my inbox for a long time - sorry I'm only getting to it
now!
On Wed, Sep 18, 2019 at 9:21 AM Alan W. Irwin
wrote:
> Hi Craig:
>
> It appears you pretty much made the definitive statement about
> target_link_libraries (TLL) options at
>
On Mon, Nov 4, 2019 at 10:54 PM Philip Van Hoof
wrote:
> Hello,
>
> After Craig's very interesting presentation at CppCon 2019* I learned a
> bunch of new things which I of course immediately wanted to try out**.
>
> I read about the write_basic_package_version_file which is in
>
Another thing:
in case you don't want to re-generate the .ts files every time, you could
comment out:
file(GLOB_RECURSE TS_SOURCES "*.cpp" "*.h" "*.ui")
qt5_create_translation(QM_FILES ${TS_FILES} ${TS_SOURCES})
and use instead the following line with the .ts files already committed in
your
Bonjour Francis,
thank you for sharing this snippet.
I have read thoroughly your example and tried it but it seems to me that
this snippet is similar to the qt5_create_translation() function.
First of all, with cmake >= 3.0.0 and AUTORCC set to ON, adding
Hi,
Migrating a code to msys2 compilation (cmake inside msys ), it does not
find an include file for unknwon reason.
the file is located in a project defined as follow:
cmake_minimum_required(VERSION 3.10)
project(include_commun)
add_library(include_commun INTERFACE)
We are pleased to announce that CMake 3.16.2 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.16.2 since 3.16.1:
On 19.12.19 10:52, Cornelis Bockemühl wrote:
> In a project setup I am copying a number of shared library files into
> the executable directory (basically with a mechanism involving
> configure_file - because the "install" logic was simply too complicated
> for the project and for my limited brain
In a project setup I am copying a number of shared library files into the
executable directory (basically with a mechanism involving configure_file -
because the "install" logic was simply too complicated for the project and for
my limited brain capacity!).
On a Windows system this works
Am 17.12.19 um 17:35 schrieb Mateusz Loskot:
On Tue, 17 Dec 2019 at 16:39, Osman Zakir wrote:
I built Boost 1.72.0 while passing the "--layout=versioned" flag to b2, but
when I tried to rebuild Jinja2Cpp with the newer version of Boost using CMake, it failed
to generate project files and
Yeah, forgot.
I did specify the values for the flags on the actual thing.
-DBoost_COMPILER=-vc142, -DBoost_ARCHITECTURE=-x64 and -DBoost_DEBUG=ON. I'll
try specifying the version number like what you said. Thanks for that.
--
Powered by kitware.com/cmake
Kitware offers various services to
On Tue, 17 Dec 2019 at 18:43, Osman Zakir wrote:
>
> I tried passing -DBoost_COMPILER and -DBoost_DEBUG
That is incorrect!
The options must read -DBoost_DEBUG=ON
and -DBoost_COMPILER=-vc141 or vc142, depending on
what b2.exe generated in names for your MSVC version.
> but it seems it's only
I tried passing -DBoost_COMPILER and -DBoost_DEBUG but it seems it's only
looking for up to Boost 1.71.0; the test versions go up to there only. Should
I edit the FindBoost.cmake file to have it look for version 1.72.0 as well?
I'm using MSVC version 14.2, Visual Studio 2019. I'm using the
On Tue, 17 Dec 2019 at 16:39, Osman Zakir wrote:
>
> I built Boost 1.72.0 while passing the "--layout=versioned" flag to b2, but
> when I tried to rebuild Jinja2Cpp with the newer version of Boost using
> CMake, it failed to generate project files and said it couldn't filesystem
> and system
I built Boost 1.72.0 while passing the "--layout=versioned" flag to b2, but
when I tried to rebuild Jinja2Cpp with the newer version of Boost using CMake,
it failed to generate project files and said it couldn't filesystem and system
and also couldn't detect version information. Could someone
We are pleased to announce that CMake 3.15.6 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.15.6 since 3.15.5:
Hello,
I've got a small Problem with Cpack and BundleUtilities on Windows.
At the moment I want to copy *.dll file at install time and also include these in the created "installer".
When I install the program through VisualStudio, everything works like a charm. But when I invoke cpack via
Hello everyone,
I'm new to cmake so this will be a, more or less, stupid question.
I'm creating an multiplatform application that is dependent on curl, Qt, and ffmpeg.
I'd like to link them statically.
On Windows is the need to include the *.dll files. I tried to use fixup_bundle() for
Never mind, this tweak to the bootstrap script should take care of anything not
directly obvious. Could do with an automated test of the installed version but
the accepted version range is so large that doesn't seem to be the trouble.
```
if [ -x ${cmake_prefix_dir}/bin/cmake ] ;then
# use
On Thursday December 12 2019 09:36:03 Kyle Edwards wrote:
>If you want to skip bootstrapping, you can use a pre-existing CMake
>binary for your system to build the new CMake.
>
>This mailing list is deprecated. Please head over to Discourse for
>further discussion:
OK, thanks. To finish things
On Thu, 2019-12-12 at 15:15 +0100, René J.V. Bertin wrote:
> Hi,
>
> If I understand correctly, configuring CMake for building means
> bootstrapping a basic version of itself which is then run on the
> included CMakeLists.txt file. That takes a lot of time
> (comparatively) which begs the
Hi,
If I understand correctly, configuring CMake for building means bootstrapping a
basic version of itself which is then run on the included CMakeLists.txt file.
That takes a lot of time (comparatively) which begs the question if there's a
more-of-less official way to skip the bootstrap and
Hello,
I'm trying to solve following problem.
test as many different compilers as possible with no (or minimal)
maintenance burden.
As docker is the newest trend, I decided to give it a try (nearly using
it for the first time).
Also the GCC team has official docker images
We are pleased to announce that CMake 3.16.1 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.16.1 since 3.16.0:
Hello,
I am using the TI-CGT compiler and have been successful in getting all my
source files to compile. However, I am unable to get the link command to
successfully link, and I have crafted a manual link command which I have to
then manually enter into the terminal once the build compiles all
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 f7ca8fc24ccb4e7724d2228d9997b2df99e71133 (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 c57bcf3b3025875dfbfd1d1f6eca1291abf4d2f7 (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 735d731119e731c8a321f85824ee685005b38731 (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 ff270b8d337bd3fe7b95587c87e261b7f5893ea4 (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 7cd0c2be0154436ec459829dcc1eee192586e486 (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 ca2a3929c2c7d479b12bab96d1910eff87380861 (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 7fe99b813c6772f056fddc2c6ea7f73ccb3d3e1c (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, release has been updated
via 85fb95562bb7f04664f0b47d20f248c9779ff61f (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 53bc2000a4dc5296338f5997497c8f1d435fc259 (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 7046a5219893436cbe19b6973ac13fb489199601 (commit)
from
I am happy to announce that CMake 3.16.0 is now available for download at:
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.16
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.16/release/3.16.html
Some of the
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.16.0 has been created
at 24176cbf3f521c8e6704e9d9746ed42537527ade (tag)
tagging
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 1b4482f65dd41f21ec8abc0777b8dc1f0381bbd6 (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 ffe801062a63387b2c109eda034d74830d72a4ce (commit)
via
> To facilitate a transition period, the current mailman-based mailing lists
> will remain active until at least the end of March 2020, and their archives
> will remain available after that.
This transition period was announced both on the users list and here
on the developers list.
Since the
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 797e55a5ef718f8762b393358c3f221c314f21d1 (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 b1175431c385cb052769d4575576ebb19b6e594b (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 ff198efc77e7b2401aa5cc4d7b6b7c91838dde7b (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 8db38cfe3386c463ef40af8520a5df329f9fd596 (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 8741d9e262a66de86fac6008bbf466dc25f72ec6 (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 bb3d82232d06e553dedd430e6d7a1d0d917108dd (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 e17934c1834ef249107ba5fd46d5e6c2c9017534 (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 58da842063cc80e34ce3ae16aa8c5fb16cdc29dd (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 99f0881d8c6d0c435e595c5f9510da776827ee3e (commit)
via
1 - 100 of 92908 matches
Mail list logo
