[cmake-developers] [CMake 0016023]: OS X CMake.app (version 3.5) contains empty CFBundleIdentifier, which is malformed

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=16023 == Reported By:Sean McBride Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.5.0-510-g7cd4496

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 7cd44969f80853ae4e26c428192bd7364e7ef94e (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.0-521-g7a56d86

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 7a56d861f71e5d929a48f477657b70c6cad16159 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.5.0-267-g33594f2

_VERSION_MINOR 5) -set(CMake_VERSION_PATCH 20160319) +set(CMake_VERSION_PATCH 20160320) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] Cmake fails to build libssh2 - wants VC 2010 told for VC 2015 build

Just get the tarball from: https://github.com/libssh2/libssh2/tarball/libssh2-1.7.0 On Tue, Mar 15, 2016 at 7:50 AM, Barry Scott wrote: > On Tue, 15 Mar 2016 10:37:04 +0300 > Sergei Nikulov wrote: > > > Just checked with following steps > > >

[Cmake-commits] CMake branch, master, updated. v3.5.0-252-g9082590

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 908259084f139187af202aaf5c39052804d8969e (commit) from

Re: [cmake-developers] more use of cmXMLWriter

Hi all! Hi Daniel! Thank you for the work done. I'm the developer CPack IFW generator. I heard about cmXMLWriter and planned to use it, but I couldn't find the time to do it. I looked 0007-CPack-IFW-port-to-cmXMLWriter.patch and at first glance everything should work as before, but I haven't

Re: [cmake-developers] Ninja and add_subdirectory EXCLUDE_FROM_ALL

On 03/16/2016 12:13 PM, Charles Huet wrote: >> On 03/16/2016 04:59 AM, Charles Huet wrote: >>> If you have other ideas on how to improve this patch, I'll be happy to >>> implement them. All paths that are given to WritePhonyBuild in the outputs and depends options should be sent through

[Cmake-commits] CMake branch, master, updated. v3.5.0-251-gcd569b9

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 cd569b962dbeaa7ea718021c16582cddd158df3a (commit) via

Re: [CMake] Building with Cmake using Boost problem

Am 16. März 2016 22:13:14 MEZ, schrieb Karel Geiregat : >According to the cmake documentation of FindBoost > you have to >name >the required libraries as described; > >"date_time" for "libboost_date_time" You do

[Cmake-commits] CMake branch, next, updated. v3.5.0-541-g52badc5

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 52badc53fb23ba97db7a46b1bbb7d4cc3c47b858 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.0-508-ga8e3ae2

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 a8e3ae223f438f45fcd2ef3d1c774905731f3fca (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.0-525-gcfcba93

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 cfcba931392b24886b41037042353b43f9d46615 (commit) via

Re: [cmake-developers] Ninja and add_subdirectory EXCLUDE_FROM_ALL

Yes, sorry about that. Le mer. 16 mars 2016 à 15:46, Brad King a écrit : > On 03/16/2016 04:59 AM, Charles Huet wrote: > > Sure, done. > > > > If you have other ideas on how to improve this patch, I'll be happy to > > implement them. > > Great. Did you mean to attach a

Re: [CMake] Cmake cannot locate header file that exists on my system

You have to add the directory /usr/include/trilinos to the c++ include directories. The fastest workaround would be, to add the directory to the CMAKE_CXX_FLAGS using ccmake or cmake-gui. The better solution is to look for any hint regarding trilinos in the CMakeLists.txt of dakota and check,

[Cmake-commits] CMake branch, next, updated. v3.5.0-531-g3f41a53

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 3f41a53534a9df440745658161a8e083873df521 (commit) via

Re: [cmake-developers] CMake aliasing system

Ruslo, I think we all could argue both against and for implementing cmake-ini files inside the cmake command. I mean I'm also aware of all the pros and cons. It's just that we weigh differently. I like loosely connected simpler building blocks and my own cmake-wrapping extension script works fine,

[Cmake-commits] CMake branch, next, updated. v3.5.0-519-gbe7c99f

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 be7c99fb365692e332f6524139e3ea4b2d16d280 (commit) via

Re: [CMake] Cmake fails to build libssh2 - wants VC 2010 told for VC 2015 build

2016-03-16 15:40 GMT+03:00 Elizabeth Fischer : > Just get the tarball from: > > https://github.com/libssh2/libssh2/tarball/libssh2-1.7.0 > > We've already discussed/solved this The problem was --config RelWithDebugInfo should be --config RelWithDebInfo -- Best

[Cmake-commits] CMake branch, master, updated. v3.5.0-247-gd9fc4df

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 d9fc4dfe3c0d2857018758649f9d5f780b22e333 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.5.0-2-g44bbd2a

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 44bbd2a65c0d2a405b70b96c3d643ce4b5eb82f4 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.0-544-g020f72f

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 020f72fae1990c8da4e291e7cd07b6b220a85d05 (commit) via

Re: [CMake] File names with unbalanced square brackets

I think you can resolve your problem with the following syntax for foreach command: Foreach (FILE IN LISTS FILES) In this case the list is not expanded in your source so square brackets is no longer interpreted… From: CMake > on behalf

[Cmake-commits] CMake branch, master, updated. v3.5.0-265-g9cdb37e

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 9cdb37e9175b2e3c6367bc4863fda0404cb1c3a2 (commit) via

Re: [CMake] File names with unbalanced square brackets

Hi David: Per your comment on the SO thread about escaping the ['s with a backslash:You mean something like this: file( GLOB FILES "*" ) string( REPLACE "[" "\\[" FILES_UPD "${FILES}" ) That doesn't appear to work. I still get everything past the first [ run together in the foreach. Thanks,

Re: [cmake-developers] Ninja and add_subdirectory EXCLUDE_FROM_ALL

ConvertToNinjaPath sadly makes the path relative to the binary dir, not the source dir. I added a utility function 'ConvertToNinjaFolderRule' that does the same thing as ConvertToNinjaPath, but makes relative to the source dir, and adds the '/all' suffix. I also made the lines less than 79

[Cmake-commits] CMake branch, next, updated. v3.5.0-537-g8628ae3

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 8628ae30966f971b86e10abb729224ee9ad2c307 (commit) via

[CMake] Recompiling before when installing target

Is it possible recompile and link a single file before installing a target? I have some string I want to hardcode into the source, so I use configure_file() to add it to a .cpp file and compile it. However, these values are different if the project is installed using 'make install'. Is it possible

Re: [CMake] why no cumulative variable operations via the commandline?

Nicholas Braden wrote: > Ah, I understand now - I have a habit of forgetting that you can > configure existing CMake builds by repeatedly invoking cmake. I don't > know if such a feature exists but it definitely sounds useful. Yes, that would be another use case! R. -- Powered by

Re: [CMake] why no cumulative variable operations via the commandline?

Ah, I understand now - I have a habit of forgetting that you can configure existing CMake builds by repeatedly invoking cmake. I don't know if such a feature exists but it definitely sounds useful. On Sat, Mar 19, 2016 at 12:03 PM, René J. V. wrote: > Nicholas Braden wrote:

Re: [CMake] why no cumulative variable operations via the commandline?

Nicholas Braden wrote: > sense. Could you give an example of when you would find them useful? I > think maybe I am not understanding what you want. Yeah, I realise my explanation may not have been very clear. > If you just want to pass a list of values to a variable on the command > line,

Re: [CMake] Cmake cannot locate header file that exists on my system

Thanks for the quickfix Andreas, that fixed the problem. I've also found the bug that's the reason for the error, the compiler flags are mixing up relative and absolute pathnames. This is definitely a Dakota issue. Setting verbose option on when executing make gives me a better idea of what's

Re: [CMake] File names with unbalanced square brackets

Hi Petr: You're right! If I rename "c" to "c]", it treats the whole "/home/allen/test/b[;/home/allen/test/c]" as an element of the list. The other file names are correctly split apart. Thanks, Allen On Fri, Mar 18, 2016 at 3:17 AM, Petr Kmoch wrote: > Hi Allen. > > I'm not

[Cmake-commits] CMake branch, next, updated. v3.5.0-470-g0340538

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 03405388a88dd8a4c35c7bce8c7a3ff66978ea31 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.5.0-478-g310e701

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 310e701169c2e7704061935822a05c5d4c01b782 (commit) via

Re: [CMake] File names with unbalanced square brackets

Hi Allen. I'm not sure whether it's documented, but CMake interprets square brackets as escaping the semi-colon character (which means a semi-colon in square brackets will not work as a list item separator). You will probably have to translate the file names for CMake processing by replacing [

Re: [cmake-developers] Startup Project Configuration [mantis 15578]

Here's Davy's patch rebased against current master with a unit test added. Tested on Visual Studio 2013 only. Let me know if I screwed up the rebase. Some conflicts weren't totally obvious to me how to handle. Thanks, Taylor On Thu, Jun 18, 2015 at 9:10 AM, Brad King

[CMake] Proper way to redefine build type compiler options

What is considered best practice for (re)defining build-type compiler options for a project, especially one that may find itself as a subproject of something larger? To be concrete, say for Debug I want the project to use a set of warn/check options. Should I set (or add to) CMAKE_C_FLAGS_DEBUG,

Re: [CMake] why no cumulative variable operations via the commandline?

The command line is the first point where variables can be defined (all code runs after this), so I am not sure where you expect pre-existing values to come from in order for a += or -= to make sense. Could you give an example of when you would find them useful? I think maybe I am not

[Cmake-commits] CMake branch, next, updated. v3.5.0-506-g65e591c

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 65e591cea4a7257f2891db15136e09ce2db5da22 (commit) via

Re: [cmake-developers] CMake aliasing system

I've openned new issue for further discussion: * https://github.com/ruslo/CMake/issues/3 On 18-Mar-16 06:24, Tamás Kenéz wrote: Ruslo, I think we all could argue both against and for implementing cmake-ini files inside the cmake command. I mean I'm also aware of all the pros and cons. It's

[Cmake-commits] CMake branch, next, updated. v3.5.0-504-gb94aee6

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 b94aee61c7bbc9b64d408f41811e16ef8274ec03 (commit) via

[CMake] Cmake cannot locate header file that exists on my system

I'm attempting to install Dakota 6.3.0 using cmake 3.5.0 on a 64-bit Linux box from source (to link python and MATLAB), and Dakota is having trouble finding some dependencies. I've been able to install and use Dakota successfully on my previous machine (64-bit, OpenSUSE 13.2, cmake 3.3.0)

[cmake-developers] [CMake 0016021]: Cannot build on OS X with GCC

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=16021 == Reported By:Erik Schnetter Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.5.0-523-g94bdf23

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 94bdf2355be80aca48c18376f4f7e8b79f8c5c70 (commit) via

[CMake] Building with Cmake using Boost problem

Dear people at cmake Today, I have a problem with using cmake and Boost to build up Apache Avro , which is a data-serializer.I have to use that "avro" which can be built with cmake and boost. However, there is a problem when building up the component by using the

Re: [CMake] Building with Cmake using Boost problem (Karel Geiregat)

OH GOD ! Just saying, i have spent 3 days finding a solution to this problem since the files got provided from a 3th party provider. The team that got assigned to this project asked me (i'm senior QA and responsible for further development). In the meanwhile, this project has to be set in standby

[CMake] Difficulty making MPI and OpenMP Fortran shared library with CMake

I would like to use CMake for a personal project instead of make (which does work), but I can't seem to get CMake to work the way I think it should. The command "cmake ." runs fine, but the make produces this: Scanning dependencies of target MIFF Linking Fortran shared library libMIFF.so

[cmake-developers] Contribution for Issue #0015146

Hi, I like to contribute code for issue #0015146. I had issues to get the /MANIFESTUAC flag (Microsoft C/C++ Compiler) working in CMake. I saw that it is a known bug which is not resolved yet since 2014. So I tried my best to solve the issue. What I did: I introduced a new flag in

Re: [cmake-developers] Patch to only consider build dependencies between files in the source directory

On 03/17/2016 09:54 AM, Attila Krasznahorkay wrote: > Attached is a new attempt. It seems to work correctly in my tests > with the Makefile generator. Thanks. > + // If it's an absolute path, check if it starts with the source > + // direcotory: > + return ( ( path.find( SourceDir

Re: [cmake-developers] Ninja and add_subdirectory EXCLUDE_FROM_ALL

Awesome, thanks! I'll check monday and report, but this looks like it'll work the same as the patch I sent last, which I've been using the past few days. Looking forward to have this feature in CMake ! Le ven. 18 mars 2016 à 16:03, Brad King a écrit : > On 03/17/2016

[CMake] why no cumulative variable operations via the commandline?

Hi, I've been wondering about something that is a real stumbling block in a build/distribution system like MacPorts where settings can be modified in any number of consecutive steps. For instance, depending on what dependencies a package ("port") requires and how those dependencies are

[Cmake-commits] CMake branch, next, updated. v3.5.0-539-ga27d069

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 a27d069287eb0ed75c64ba0b7f9a8f393fecfa10 (commit) via

[cmake-developers] [CMake 0016025]: Add support WINDOWS_EXPORT_ALL_SYMBOLS for executable exports lib

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=16025 == Reported By:Yury Zhuravlev Assigned To:

Re: [cmake-developers] Patch to only consider build dependencies between files in the source directory

Hi Brad, Attached is a new attempt. It seems to work correctly in my tests with the Makefile generator. (Which, to be fair, is the only generator that we use in production mode at the moment...) Cheers, Attila 0001-CMAKE_DEPENDS_IN_PROJECT_ONLY-feature-addition.patch Description:

[Cmake-commits] CMake branch, next, updated. v3.5.0-527-g7d01f32

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 7d01f3219105fe43ce0059709e4a266847a270bd (commit) via

Re: [cmake-developers] Ninja and add_subdirectory EXCLUDE_FROM_ALL

On 03/16/2016 04:59 AM, Charles Huet wrote: > Sure, done. > > If you have other ideas on how to improve this patch, I'll be happy to > implement them. Great. Did you mean to attach a revised patch? Thanks, -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the

[Cmake-commits] CMake branch, master, updated. v3.5.0-244-gbf07128

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 bf0712866f3245034f5ee7d5835f5e4ed5f47626 (commit) via

[cmake-developers] Fwd: [CMake 0016022]: GenerateExportHeader DEFINE_NO_DEPRECATED define conflicts

Hi, regarding this issue report, I’ve just attached a patch for the current HEAD of the master branch that fixes the issue. Please have a look and it would be great if somebody could apply it. It currently causes problems in particular

Re: [CMake] fixup_bundle on Windows : issue with multiple exe applications

A multiple folder approach will be very difficult. The basic assumptions are: - On Windows, the "one executable path" is the destination path to which to copy all of the DLLs that need to be copied, so they all end up in the same directory. (You'd have to have multiple copies in multiple

[Cmake-commits] CMake branch, next, updated. v3.5.0-481-g9e7ee35

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 9e7ee356efb36298a07889e8c918278342cba5e5 (commit) via

Re: [CMake] Clarifying Cmake behavior

I did a bit more searching around, and, for me at least, setting Boost_REALPATH on also seems to be a valid solution to the problem, as the linker will no longer get confused between the system installed libraries and my custom ones. I dunno if that works in all situations, but it seems to be the