[Cmake-commits] CMake branch, master, updated. v3.5.2-519-ga2de7f3

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

Re: [cmake-developers] Code style auto-formatting

On Thu, Nov 19, 2015 at 3:26 PM, Brad King wrote: > On 11/19/2015 09:22 AM, Robert Dailey wrote: >> Tonight I will do some testing and submit a patch + example files >> converted to the style Brad suggested. We can fine-tune it as needed. > > Rather than a patch please work

Re: [cmake-developers] Integration of clang-tidy

On Wed, Apr 27, 2016 at 3:10 PM, Brad King wrote: > On 04/26/2016 05:32 PM, Daniel Pfeifer wrote: >> This is a follow up patch: > > Thanks. > >> -tidy_cmd.insert(tidy_cmd.end(), orig_cmd.begin()+1, orig_cmd.end()); >> +tidy_cmd.insert(tidy_cmd.end(),

Re: [cmake-developers] Integration of clang-tidy

On Wed, Apr 27, 2016 at 10:47 PM, Gregor Jasny wrote: > Hallo Daniel, > > On 09/04/16 00:31, Daniel Pfeifer wrote: >> I implemented the integration of `clang-tidy` along the lines of the >> `include-what-you-use` integration. >> There is a new `_CLANG_TIDY` target property

[cmake-developers] RFC: LLVM community CMake documentation

Hello cmake-developers, Earlier this year the LLVM community finished migrating to CMake as our one and only build system. One of the lingering things on my to-do list to help this transition is to write some basic documentation for the CMake language to help LLVM developers get a feel for the

Re: [cmake-developers] Integration of clang-tidy

Hallo Daniel, On 09/04/16 00:31, Daniel Pfeifer wrote: > I implemented the integration of `clang-tidy` along the lines of the > `include-what-you-use` integration. > There is a new `_CLANG_TIDY` target property that is initialized > with the value of the `CMAKE__CLANG_TIDY` variable. > It

[Cmake-commits] CMake branch, next, updated. v3.5.2-1110-g3483677

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1108-gb3f7515

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

[CMake] LINK_FLAGS directory property

Is there an equivalent directory property for the target level LINK_FLAGS property. I can’t see anything according to the documentation but was hoping there was an oversight and something actually existed. What I am trying to do is pass extra flags to the linker for every target in my project

Re: [CMake] project command not working, when used via macro (from an included file)

Perhaps I spoke to hastily. It seems the unsupported configuration is if project(...) is actually called from an include file, which makes sense given various scoping issues. Give that, what you have should work fine. What doesn't work as expected? It seems to work just fine when I try it from

[Cmake-commits] CMake branch, next, updated. v3.5.2-1102-g5635d5b

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

Re: [CMake] project command not working, when used via macro (from an included file)

Ok thanks. But it is unfortunate, since it means that really great macros, such as project_guarded (see http://stackoverflow.com/a/33100078) cannot be used everywhere, as a substitute for project. On Tue, Apr 26, 2016 at 8:04 PM, Chuck Atkins wrote: > ajneu, > > The

Re: [CMake] Install with full absolute path on OS X

Thanks. That was the solution. -- Mike Jackson [mike.jack...@bluequartz.net] clin...@elemtech.com April 26, 2016 at 2:57 PM To set the install name to an absolute path, it would probably be something like set_property(TARGET EMsoft PROPERTY INSTALL_NAME_DIR

[Cmake-commits] CMake branch, next, updated. v3.5.2-1098-g70948c3

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-516-g3c93436

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-513-g8a00c16

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

Re: [cmake-developers] Integration of clang-tidy

On 04/26/2016 05:32 PM, Daniel Pfeifer wrote: > This is a follow up patch: Thanks. > -tidy_cmd.insert(tidy_cmd.end(), orig_cmd.begin()+1, orig_cmd.end()); > +tidy_cmd.insert(tidy_cmd.end(), orig_cmd.begin(), orig_cmd.end()); What is the purpose of this hunk? Does clang-tidy

[Cmake-commits] CMake branch, next, updated. v3.5.2-1094-g690bc37

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

[cmake-developers] [CMake 0016085]: No Android Studio Generator

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

[cmake-developers] [CMake 0016084]: try_compile incorrect behavior for iOS universal build (device + simulator) with CMAKE_IOS_INSTALL_COMBINED

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

Re: [CMake] How to set link option

I think the variable CMAKE_EXE_LINKER_FLAGS or LINK_FLAGS may work, but since my project have some other issues, I have not reached to link steps. Thanks, Le Magnus Therning wrote > vakano > zhongle@ > writes: > >> Hi, >> >> I have some link option as below: >> >> -Wl, -rpath,

Re: [CMake] project command not working, when used via macro (from an included file)

May be using keyword NO_POLICY_SCOPE in include command will solve your problem… From: CMake > on behalf of Chuck Atkins > Date: Tuesday 26 April 2016 at 20:04 To: aj neu

[CMake] install/fast Makerule failing in buildroot

Hi all, I'm trying to include a package to buildroot (2016.02) with cmake as the build generator however, I've hit a bit of a snag. This particular version of buildroot is using CMake version 3.4.3. The package builds as expected, however during the install step, the following error is

Re: [cmake-developers] CMake API for warnings

On 26-Apr-16 01:58, Brad King wrote: On 04/23/2016 12:11 AM, Ruslan Baratov wrote: It means ignoring directory properties. So by default we will inherit settings. [snip] To disable inheriting we need to add extra argument (?) to *_compile_warnings: add_compile_warnings(DISABLE warn-A)