I am proud to announce the first CMake 3.4 release candidate.
Sources and binaries are available at:
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.4
Release notes appear below and are also published at
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, next has been updated
via f0dba830863feecb9b147632ae5b49c209249dc1 (commit)
via
On 10/04/2015 10:47 AM, Stephen Kelly wrote:
> So, is this thread really about a bug, or is it a feature request?
I think it has become a feature request to select link flags for language
standard levels. It is conflated with a bug fix because the link flags
are needed to support existing
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, next has been updated
via a868359d4b10a917c30174613c1aeb6bdf5d6fdf (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, next has been updated
via fc4520b4b8a2656ba636fc58a4923e1b9c475c6e (commit)
via
I am proud to announce the first CMake 3.4 release candidate.
Sources and binaries are available at:
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.4
Release notes appear below and are also published at
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.4.0-rc1 has been created
at 2b9bd8ea2dff25c70bb2067383c977e3db40dc67 (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, master has been updated
via 256bf8876a2e460afc37dbe17eb34482944be20b (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 5d315f32236dfebf3561789d17b2d86c504d (commit)
via
On 10/06/2015 07:51 AM, Daniele E. Domenichelli wrote:
> According to the sigc++ changelog, starting with version 2.5.1, sigc++
> requires c++11 enabled, hence this patch.
Thanks.
> +* Starting with sigc++ 2.5.1, c++11 must be enabled in order to use
> + sigc++.
Generally we don't do release
On 10/06/2015 09:42 AM, Robert Maynard wrote:
I am proud to announce the first CMake 3.4 release candidate.
This appears to have broken plplot's ada build on Fedora. Previous good
(cmake 3.3.2):
[ 22%] Building Ada object examples/ada/CMakeFiles/x00a.dir/x00a.o
cd
_VERSION_MINOR 4)
-set(CMake_VERSION_PATCH 20151006)
+set(CMake_VERSION_PATCH 20151007)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
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, next has been updated
via 3d6c305c4e458276e6ebadfe88a3ca2a88c7e010 (commit)
via
Hello.
I am using cmake 3.3.2.
The following script sets the CUDA_USE_STATIC_CUDA_RUNTIME option, then
finds the CUDA package.
cmake_minimum_required(VERSION 3.3)
option(CUDA_USE_STATIC_CUDA_RUNTIME OFF)
set(CUDA_TOOLKIT_ROOT_DIR "d:/work/CUDAToolkit")
message(STATUS
On Sun, Oct 04, 2015 at 16:47:40 +0200, Stephen Kelly wrote:
> The existing CMake feature deals with compilation, but does not deal with
> linking.
A generic target_link_options() is necessary for other things as well,
such as:
* -fsanitize=address needs to be passed to the linker to add
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, next has been updated
via c54c869a7127352d7e2ca757c5ecd039d12ae2ab (commit)
via
I am looking for a way to tell my project to link against external debug
libraries with a debug build and external release libraries with a
release build with Visual Studio.
I sort of want to be able to say something like
if (BuildingReleaseConfig)
find_package(OtherPackage REQUIRED COMPONENTS
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, next has been updated
via 884ba71d96fe4b62336f61c367f8cf785e3842df (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, next has been updated
via 4eafc01acb0a24effedaa6b1f9d798a8f971d852 (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, next has been updated
via 4a19e497cbdd9e2a17a259e0004f015af87f51fc (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, next has been updated
via 449739634258340947548467f73cc8c3479c2e90 (commit)
via
CMake supports multi-config generators such as Visual Studio and Xcode for
a long time.
There are two flavors of config-modules (and find-modules), the legacy one
which creates variables like MY_PACKAGE_LIBRARIES and the install-export
kind which creates IMPORTED targets.
Both kinds of modules
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, next has been updated
via 3af63d13e8827bf86b53a85376c5f76a67604e4f (commit)
via
On Mon, Oct 05, 2015 at 12:50:41 +0200, Daniel Wirtz wrote:
> thanks for the feedback, i've included most of it.
>
> Regarding the configure/build issue: that indeed is inconvenient and may
> cause irritation. on the other side, if there has been git activity
> fussing with any source files
So if this is the case, how does one "write correctly" the find/config
module so that both debug and release libraries are found? I've got a
library I depend on whose maintainer may not have built the best Find
module in the world. I've looked at
CMake performs deduplication of per-target flags for sure.
However I'm not sure if CMAKE_CXX_FLAGS is deduplicated. But I consider this
variable as global flags for the whole project which is defined at topmost
CMakeLists.txt. If you need to specify some flags specifically for a target use
On Oct 6, 2015, at 7:22 AM, Марсель Галимуллин wrote:
> I'm student of the University LETI and as a masrer's thesis I want to develop
> an extension to CMake. It is expected that this extension will automatically
> download missing library if instruction such as «find_package (Boost
>
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, next has been updated
via 93d9a39bcf9942e5763a2c67c2f100053c057eb8 (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, next has been updated
via 8b9266c92d3b6f2cc33ccc113a367fea04f31ba4 (commit)
via
Hello!I'm student of the University LETI and as a masrer's thesis I want to develop an extension to CMake. It is expected that this extension will automatically download missing library if instruction such as «find_package (Boost COMPONENTS system thread REQUIRED)» can not find the package. Could
On 10/06/2015 09:49 AM, Francesco Romano wrote:
> - Compilation of the project.
> I want the user to be able to compile the project on its machine
> (so build system = deployment system). Of course I can document
> that he has to explicitly pass the variable to cmake, but it
> does not seem too
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, next has been updated
via 7581b99a1b8fd2ae3f4b92c530c73fd35649ccae (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, next has been updated
via fab3860de1e08981f48638142cb2f85a7e9897df (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, next has been updated
via a5971e8b348e48ff5bbb489992d41905f6aa5d65 (commit)
via
Hello,
Starting with some recent update on my system that updated sigc++ from
2.4.0 to 2.6.1, I noticed that a few GTK2Targets tests depending on
sigc++ are failing.
According to the sigc++ changelog, starting with version 2.5.1, sigc++
requires c++11 enabled, hence this patch.
FindGTK2:
Hey,
so i've been working on a quite large build system for OpenCMISS, which
in turn consumes about 30 external packages itself.
the main repo (and cmake logic) can be found here:
https://github.com/OpenCMISS/manage (branch v1.0).
feel free to have a look around and use some of the logic.
Hi Roman,
I'm not necessarily only talking about CMAKE_CXX_FLAGS here. I define compile
flags for my targets in a number of different ways. Like:
find_package( ROOT COMPONENTS ${ROOT_LINK_COMPONENTS} REQUIRED )
include( ${ROOT_USE_FILE} )
...
add_definitions( ${ATLAS_DEFINITIONS} )
...
On 10/05/2015 04:36 PM, Tamás Kenéz wrote:
> Here is the patch which documents and tests those 4 variables
Great, thanks. Applied with minor tweaks:
Document and test CMAKE_[CURRENT_](BINARY|SOURCE)_DIR in script mode
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8bb908b1
-Brad
--
Thanks Brad for the answer.
Maybe I did not understand correctly your answers.
I’ll use as an example two use cases (which by the way are where we detected
the issue)
- Compilation of the project.
I want the user to be able to compile the project on its machine (so build
system = deployment
Hi,
What is the best way to check if a test is already defined using function
add_test?
My initial though was that if() can be used for that purpose but,
unfortunately, if (TEST ) is not supported for now.
Thanks.
Marc
--
Powered by www.kitware.com
Please keep messages on-topic and
On 10/06/2015 08:22 AM, Марсель Галимуллин wrote:
> automatically download missing library if instruction such as
> find_package (Boost COMPONENTS system thread REQUIRED) can not
> find the package.
In general this is outside the scope of a build system and falls
in the domain of package
On 10/05/2015 06:59 PM, Colin Tracey wrote:
> I sent a similar patch as plain text in an email to the list last
> Friday, but after observing the email traffic It looks like you
> prefer attachments. I also added documentation to this one.
Inline patches are fine and slightly preferred for me
hello list,
I am running Xcode (5 & 6) and using CMake to generate the Xcode project
files. We have a lot of targets for our project and we were looking into ways
of refactoring the Cmake codes in order to reduce the number of targets. For
example we have a lot of plugins that we compile
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, next has been updated
via 6e49b3c19d945d5a0822e3a8457451593b8b9369 (commit)
via
I have libpng16.dll, libpng16.lib, and png.h
Where should I put these files to cmake:FindPNG foud them?
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake
On 10/06/2015 12:20 PM, Daniele E. Domenichelli wrote:
> I updated the topic according to your comments. The new commit is this:
>
> FindGTK2: Enable c++11 for sigc++ 2.5.1 or later
> https://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=33eb8fa
LGTM.
> I'm not 100% sure that there
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, next has been updated
via 5636a8971908bd663f148081401cf48725bcf71c (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 c914d2bda278b588c1dca3e0fa5ec97a64c56c3c (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 9d5bfa53e63c894b1c774258882877f57d61638f (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, next has been updated
via 5f80b1b146e2f39b8998cb49ff734e2fc5bcac91 (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 53d90de3d9b536bcee45acc40183569895a9776e (commit)
via
51 matches
Mail list logo
