[Cmake-commits] CMake branch, next, updated. v3.4.0-1550-g523ccb5

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1548-g48f4880

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

[cmake-developers] [CMake 0015867]: Meta-projects generated for Visual Studio 2013 solutions are always multi-byte

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15867 == Reported By:Marcel Beister Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.4.0-1534-gaad2a58

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

Re: [cmake-developers] [PATCH] Add NIOS2 CPU support

On Monday, November 30, 2015 at 04:40:55 PM, Brad King wrote: > On 11/26/2015 03:48 PM, Marek Vasut wrote: > > Add necessary bits to support the NIOS2 little-endian CPU. > > Thanks. I split the KWSys part out to send to its upstream here: > > http://review.source.kitware.com/20445 > > Once

Re: [cmake-developers] [PATCH] Qt4Macros generate resources with same file name

Yes, I found that. Thanks for the view, I will work an more acceptable patch later this week. Have a nice day~~ On Mon, Nov 30, 2015, 11:48 PM Clinton Stimpson wrote: > On Tuesday, November 24, 2015 11:01:27 AM Joseph Shen wrote: > > Dear CMake developers: > > > > Please

[Cmake-commits] CMake branch, master, updated. v3.4.0-619-g3c6a366

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

Re: [cmake-developers] [PATCH] FindBoost: Add imported targets

On 11/30/2015 11:26 AM, rle...@codelibre.net wrote: > I have improved the parsing speed somewhat and added some progress > diagnostics to inform the user what's happening to compensate for the time > it takes to process the dependencies. It's still slower than I'd ideally > like, but it's a bit

[Cmake-commits] CMake branch, next, updated. v3.4.0-1536-ga2d81f6

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

Re: [cmake-developers] [PATCH] FindBoost: Add imported targets

> On 11/30/2015 11:26 AM, rle...@codelibre.net wrote: >> I have improved the parsing speed somewhat and added some progress >> diagnostics to inform the user what's happening to compensate for the >> time >> it takes to process the dependencies. It's still slower than I'd >> ideally >> like, but

Re: [cmake-developers] [CPackDMG][Patch] Enable use of single license for multiple languages

On 11/26/2015 08:00 AM, Levermann, Simon wrote: > since license texts are often not translated into other languages, this > patch enables the CPack DragnDrop generator to use a single license > file for all languages instead of having to keep a copy of the same > file around under multiple

Re: [cmake-developers] [PATCH] Qt4Macros generate resources with same file name

On Tuesday, November 24, 2015 11:01:27 AM Joseph Shen wrote: > Dear CMake developers: > > Please view attached small patch that try to fix Qt4Macros generate > resources with same file name error. > > Right now, in the CMake main branch, using cmake with Qt4 library > add resources project can

[Cmake-commits] CMake branch, next, updated. v3.4.0-1531-gd8d7bbd

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

Re: [cmake-developers] [PATCH] Fix building on musl-libc

On 11/25/2015 11:15 PM, Kylie McClain wrote: > Hi, this is a really short patch that fixes building cmake on musl-libc. > #if defined( _MSC_VER ) > typedef unsigned short mode_t; > +#else > +#include > #endif Thanks. Does work here instead? It should provide mode_t:

Re: [cmake-developers] [CMake] Obtaining header file dependencies of a source file manually

On 11/30/2015 01:56 PM, Dan Liew wrote: > It doesn't look completely impossible. For Ninja, it looks like it has > some support for compiler generated dependency files [2] Yes, it may be possible for Ninja. > There is an alternative which I suggested in the post. Have CMake > determine the

Re: [CMake] [cmake-developers] Obtaining header file dependencies of a source file manually

On 11/30/2015 01:56 PM, Dan Liew wrote: > It doesn't look completely impossible. For Ninja, it looks like it has > some support for compiler generated dependency files [2] Yes, it may be possible for Ninja. > There is an alternative which I suggested in the post. Have CMake > determine the

Re: [cmake-developers] [CMake] Obtaining header file dependencies of a source file manually

On 30 November 2015 at 18:35, Brad King wrote: > On 11/30/2015 01:32 PM, Dan Liew wrote: >> It works but only for makefile generators... That's an annoying >> limitation. I'll file a feature request to get this implemented for >> other generators. > > It happens to work for

Re: [CMake] [cmake-developers] Obtaining header file dependencies of a source file manually

On 30 November 2015 at 18:35, Brad King wrote: > On 11/30/2015 01:32 PM, Dan Liew wrote: >> It works but only for makefile generators... That's an annoying >> limitation. I'll file a feature request to get this implemented for >> other generators. > > It happens to work for

Re: [CMake] [cmake-developers] Obtaining header file dependencies of a source file manually

> For other generators that are Makefile or Ninja based I guess that > approach wouldn't work. Sorry that should read For other generators that **aren't** Makefile or Ninja based I guess that approach wouldn't work. -- Powered by www.kitware.com Please keep messages on-topic and check the

Re: [cmake-developers] Add CXX_STANDARD support for Intel C++ compilers

On Mon, Nov 30, 2015 at 11:33 AM, Brad King wrote: > On 11/30/2015 01:18 PM, Levi Morrison wrote: >> My latest patch is attached. All tests seem to be working for me on >> the compiler versions I have access to. Can you check it for any >> glaring errors? > > Good. This

Re: [cmake-developers] Add command line options for deprecation message control

Great, I've changed the nullptr references to NULL instead. Cheers, Michael >From 02016a44d1f6f571b96c54a0008c37e2e1fa3b7d Mon Sep 17 00:00:00 2001 From: Michael Scott Date: Sun, 1 Nov 2015 16:05:15 + Subject: [PATCH 1/8] Tests: Revise message in

[Cmake-commits] CMake branch, next, updated. v3.4.0-1538-g4ef2913

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

Re: [CMake] [cmake-developers] Obtaining header file dependencies of a source file manually

Hi Michael, > Not going into detail as I'm typing on the phone, but this really sounds > like a case where a "SuperBuild" > (http://www.kitware.com/media/html/BuildingExternalProjectsWithCMake2.8.html) > can help you to simplify things a lot. Thanks for the suggestion but this certainly is not a

Re: [cmake-developers] Add CXX_STANDARD support for Intel C++ compilers

On 11/30/2015 01:18 PM, Levi Morrison wrote: > My latest patch is attached. All tests seem to be working for me on > the compiler versions I have access to. Can you check it for any > glaring errors? Good. This hunk: > + if (NOT CMAKE_CXX_COMPILER_FORCED) > +if (NOT

Re: [cmake-developers] Obtaining header file dependencies of a source file manually

Hi Michael, > Not going into detail as I'm typing on the phone, but this really sounds > like a case where a "SuperBuild" > (http://www.kitware.com/media/html/BuildingExternalProjectsWithCMake2.8.html) > can help you to simplify things a lot. Thanks for the suggestion but this certainly is not a

Re: [cmake-developers] Obtaining header file dependencies of a source file manually

Hi, On 30 November 2015 at 18:03, Dan Liew wrote: > Hi, > > On 30 November 2015 at 08:09, Petr Kmoch wrote: >> Hi Dan, >> >> you could look into the IMPLICIT_DEPENDS argument of add_custom_command: >>

Re: [CMake] [cmake-developers] Obtaining header file dependencies of a source file manually

On 11/30/2015 01:32 PM, Dan Liew wrote: > It works but only for makefile generators... That's an annoying > limitation. I'll file a feature request to get this implemented for > other generators. It happens to work for Makefile generators because it was easy to implement since those generators

Re: [cmake-developers] [PATCH] FindBoost: Add imported targets

On 11/30/2015 11:54 AM, rle...@codelibre.net wrote: > I do worry about the maintenance burden of hardcoding the information in > the script. I do too. We already have to update the script for each Boost release. This is among the reasons the work is better integrated with upstream Boost instead.

Re: [CMake] [cmake-developers] Obtaining header file dependencies of a source file manually

Hi, On 30 November 2015 at 08:09, Petr Kmoch wrote: > Hi Dan, > > you could look into the IMPLICIT_DEPENDS argument of add_custom_command: > https://cmake.org/cmake/help/latest/command/add_custom_command.html > > I don't have direct experience with it, but it looks like it

Re: [cmake-developers] Obtaining header file dependencies of a source file manually

Hi, On 30 November 2015 at 08:09, Petr Kmoch wrote: > Hi Dan, > > you could look into the IMPLICIT_DEPENDS argument of add_custom_command: > https://cmake.org/cmake/help/latest/command/add_custom_command.html > > I don't have direct experience with it, but it looks like it

Re: [cmake-developers] Add command line options for deprecation message control

On 11/29/2015 08:48 AM, Michael Scott wrote: > I've gone back and redone the patches with the suggestions you made Thanks. This is in pretty good shape now I think. However, I see use of `nullptr`. Please revise to use only C++98 constructs. -Brad -- Powered by www.kitware.com Please keep

[Cmake-commits] CMake branch, release, updated. v3.4.0-35-gf8deadc

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

[Cmake-commits] CMake branch, master, updated. v3.4.0-624-g2218962

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1544-g1d0b45a

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-1546-gd5dcfed

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

Re: [CMake] [cmake-developers] Obtaining header file dependencies of a source file manually

On Mon, Nov 30, 2015 at 7:01 PM, Dan Liew wrote: > Hi Michael, > >> Not going into detail as I'm typing on the phone, but this really sounds >> like a case where a "SuperBuild" >> (http://www.kitware.com/media/html/BuildingExternalProjectsWithCMake2.8.html) >> can help you to

Re: [cmake-developers] Obtaining header file dependencies of a source file manually

On Mon, Nov 30, 2015 at 7:01 PM, Dan Liew wrote: > Hi Michael, > >> Not going into detail as I'm typing on the phone, but this really sounds >> like a case where a "SuperBuild" >> (http://www.kitware.com/media/html/BuildingExternalProjectsWithCMake2.8.html) >> can help you to

Re: [CMake] Best way to handle application data path for local run vs. installation

On Monday, November 30, 2015 16:13:03 Ruslan Baratov via CMake wrote: > On 30-Nov-15 09:10, Dmitry Marakasov wrote: > > Hi! > > ... > > The best solution would be for cmake to fix path in executable file > > right after installation, something similar to what cmake does with > > rpaths. > > I

Re: [CMake] Best way to handle application data path for local run vs. installation

On 01-Dec-15 03:51, Alexander Neundorf wrote: On Monday, November 30, 2015 16:13:03 Ruslan Baratov via CMake wrote: > On 30-Nov-15 09:10, Dmitry Marakasov wrote: > > Hi! > > ... > > The best solution would be for cmake to fix path in executable file > > right after installation, something

Re: [CMake] Best way to handle application data path for local run vs. installation

For what it's worth, what we do here is have the executable search for a file named paths.cfg in the same directory it's located in, and read settings from that file to get the paths to load resources from. Then our CMake system is set up to create one paths.cfg when building, and another when

[Cmake-commits] CMake branch, master, updated. v3.4.0-625-ga6f5281

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

[cmake-developers] Fwd: [PATCH] Fix building on musl-libc

On Mon, Nov 30, 2015 at 10:40 AM, Brad King wrote: > Does work here instead? Yes, appears to work just fine. (sorry for any duplicate messages, meant to send this message to the mailing list as well, not just to Brad) -- Powered by www.kitware.com Please keep messages

[cmake-developers] [CMake 0015868]: Property INSTALL_NAME_DIR is completely ignored

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15868 == Reported By:Lucas Christian Assigned To:

Re: [CMake] [cmake-developers] Obtaining header file dependencies of a source file manually

Hi Dan, you could look into the IMPLICIT_DEPENDS argument of add_custom_command: https://cmake.org/cmake/help/latest/command/add_custom_command.html I don't have direct experience with it, but it looks like it could do what you're looking for. Petr On Sun, Nov 29, 2015 at 10:47 AM, Dan Liew

Re: [CMake] Best way to handle application data path for local run vs. installation

* Ruslan Baratov (ruslan_bara...@yahoo.com) wrote: > > - I don't want to make an applications search for its data relative > >to executable path > >- There's no cross-platform way to get an executable path > It's tricky but not impossible. Might be helpful: > *

Re: [CMake] Best way to handle application data path for local run vs. installation

On 30/11/2015 02:10, Dmitry Marakasov wrote: Hi! This question bugs me for a long time so I though maybe someone has a solution. I have a project which includes an application and some data for it. An application needs to know path to its data files, so I pass it via compiler definition:

[CMake] Custom command concurrency

Dear All, I'm running into a new issue with my custom commands. :-( I have a project with many subdirectories. Where most subdirectories generate some files during the build. Some of which need to be merged into a single file at the end of the build. In my current implementation the

Re: [CMake] Best way to handle application data path for local run vs. installation

On 30-Nov-15 09:10, Dmitry Marakasov wrote: Hi! This question bugs me for a long time so I though maybe someone has a solution. I have a project which includes an application and some data for it. An application needs to know path to its data files, so I pass it via compiler definition:

Re: [CMake] [cmake-developers] Obtaining header file dependencies of a source file manually

What does output_required_files() [0] do, and is it applicable here? [0] https://cmake.org/cmake/help/v3.4/command/output_required_files.html On Mon, Nov 30, 2015 at 2:09 AM, Petr Kmoch wrote: > Hi Dan, > > you could look into the IMPLICIT_DEPENDS argument of

Re: [CMake] [cmake-developers] Obtaining header file dependencies of a source file manually

On Mon, Nov 30, 2015 at 2:04 PM, iosif neitzke < iosif.neitzke+cm...@gmail.com> wrote: > What does output_required_files() [0] do, and is it applicable here? > > [0] https://cmake.org/cmake/help/v3.4/command/output_required_files.html First and foremost, it introduces deprecated behaviour into