In particular,
I moved the hunk below forward to "Modify dev warning options to affect
deprecated warnings", the commit where it actually becomes needed
because the default changes.
I'm not sure I follow, which hunk are we talking about here?
Please add a Help/release/dev/cmake-W-options.rst fi
I've just upgraded my work development system to Ubuntu 15.10. While
testing the FindBoost work in a separate thread, I noticed that with
this release the system linker is using --as-needed by default. This
means that the system no longer respects the compiler linker arguments,
and will delib
The following issue has been SUBMITTED.
==
https://public.kitware.com/Bug/view.php?id=15850
==
Reported By:Jonathan Doman
Assigned To:
On Tue, Nov 17, 2015 at 3:09 PM, Levi Morrison
wrote:
> On Tue, Nov 17, 2015 at 2:38 PM, Brad King wrote:
>
>> On 11/17/2015 04:34 PM, Levi Morrison wrote:
>> > On Tue, Nov 17, 2015 at 2:07 PM, Levi Morrison wrote:
>> >>> icpc: command line warning #10159: invalid argument for option '-std'
>> >
On Tue, Nov 17, 2015 at 3:35 PM, Brad King wrote:
> Hi Folks,
>
> For reference, the current CMake indentation style is:
>
> https://en.wikipedia.org/wiki/Indent_style#Whitesmiths_style
>
> but with 2 space indentation instead of 4 as shown on that page.
> The style was popular when CMake started
On Tue, Nov 17, 2015 at 2:38 PM, Brad King wrote:
> On 11/17/2015 04:34 PM, Levi Morrison wrote:
> > On Tue, Nov 17, 2015 at 2:07 PM, Levi Morrison wrote:
> >>> icpc: command line warning #10159: invalid argument for option '-std'
> >> Hmm. Can you tell me what the value of -std was for that invo
On 11/17/2015 04:34 PM, Levi Morrison wrote:
> On Tue, Nov 17, 2015 at 2:07 PM, Levi Morrison wrote:
>>> icpc: command line warning #10159: invalid argument for option '-std'
>> Hmm. Can you tell me what the value of -std was for that invocation?
>
> Hazarding a guess I think it might be gnu++14
Hi Folks,
For reference, the current CMake indentation style is:
https://en.wikipedia.org/wiki/Indent_style#Whitesmiths_style
but with 2 space indentation instead of 4 as shown on that page.
The style was popular when CMake started (year 2000) but is not
very widely used anymore.
For Emacs, se
On Tue, Nov 17, 2015 at 2:07 PM, Levi Morrison
wrote:
> Also after fixing the above I see in
>> Tests/CompileFeatures/CMakeFiles/CMakeOutput.log the following:
>>
>> Detecting CXX [-std=c++14] compiler features compiled with the
>> following output:
>> ...
>> icpc: command line warnin
On Tue, Nov 17, 2015 at 10:12 PM, Robert Dailey
wrote:
> On Tue, Nov 17, 2015 at 6:57 AM, Paul Smith wrote:
>> On Tue, 2015-11-17 at 08:14 +, Stuermer, Michael SP/HZA-ZSEP wrote:
>>> In short, there is no fully automated style checking. If someone would
>>> come up with a tool & configuration
On Tue, Nov 17, 2015 at 6:57 AM, Paul Smith wrote:
> On Tue, 2015-11-17 at 08:14 +, Stuermer, Michael SP/HZA-ZSEP wrote:
>> In short, there is no fully automated style checking. If someone would
>> come up with a tool & configuration I would love to use this. So far I
>> tested astyle and the
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=15849
==
Reported By:Chris M
Assigned To:
===
>
> Also after fixing the above I see in
> Tests/CompileFeatures/CMakeFiles/CMakeOutput.log the following:
>
> Detecting CXX [-std=c++14] compiler features compiled with the
> following output:
> ...
> icpc: command line warning #10159: invalid argument for option '-std'
>
> This is wit
On 11/17/2015 03:57 PM, Levi Morrison wrote:
> Also, it is worth pointing out that some of the features are partially
> supported in earlier versions, but in the FeatureTests.cmake I put it
> only for the first version that claims complete compatibility
> - is that the correct action?
Yes, thanks.
On 11/17/2015 03:23 PM, Levi Morrison wrote:
> Attached is the patch.
Thanks. In the CompileFeatures test output one can see
Detecting CXX compile features - failed
Then in Tests/CompileFeatures/CMakeFiles/CMakeError.log one can see
the error:
.../Tests/CompileFeatures/CMakeFiles/featu
On Tue, Nov 17, 2015 at 1:23 PM, Levi Morrison
wrote:
> > I'm not sure how to edit Tests/CompileFeatures/CMakeLists.txt, though.
>> > I don't even know what half of this file is trying to accomplish.
>> > It seems like it is pure duplication of work; these checks are saying
>> > EXPECT_C_STATIC_A
>
> > I'm not sure how to edit Tests/CompileFeatures/CMakeLists.txt, though.
> > I don't even know what half of this file is trying to accomplish.
> > It seems like it is pure duplication of work; these checks are saying
> > EXPECT_C_STATIC_ASSERT=1 if some compiler conditions are true but
> > I al
On 17-Nov-15 15:48, Roger Leigh wrote:
On 17/11/2015 07:53, Ruslan Baratov wrote:
On 16-Nov-15 21:01, rle...@codelibre.net wrote:
I have attached a patch to add imported targets to FindBoost, in the
form
of Boost:: (e.g. Boost::date_time) or Boost::Boost as a
generic
interface library for head
On 11/17/2015 01:13 PM, Levi Morrison wrote:
> I have updated Modules/Compiler/Intel-CXX-FeatureTests.cmake.
Great.
> I'm not sure how to edit Tests/CompileFeatures/CMakeLists.txt, though.
> I don't even know what half of this file is trying to accomplish.
> It seems like it is pure duplication o
On Tue, Nov 17, 2015 at 11:13 AM, Levi Morrison
wrote:
> On Tue, Nov 17, 2015 at 6:50 AM, Brad King wrote:
>
>> On 11/16/2015 03:14 PM, Levi Morrison wrote:
>> > It seems my attachments are getting scrubbed or something?
>>
>> It was just that one message that was missing one. This one worked.
On Tue, Nov 17, 2015 at 6:50 AM, Brad King wrote:
> On 11/16/2015 03:14 PM, Levi Morrison wrote:
> > It seems my attachments are getting scrubbed or something?
>
> It was just that one message that was missing one. This one worked.
>
> >> How did you test these? For full testing we need the CMa
On 11/17/2015 11:03 AM, Setze Post wrote:
> First ever upstreamed upstreamed mail from me, please gently inform me
> if I took the wrong route here.
> Running Gentoo Linux x86_64 and compiling with LTO enabled in C*FLAGS,
> the configuration stage seems to fail compiling CMake 3.4.0 as described
>
In my case, I’ve switched all my company builds from xcodebuild (or msbuild) to
Ninja as it is much faster and parallelises the build better on all platforms.
CI loop is much faster thanks to this.
There is some maintenance to make sure the generated Ninja and Xcode projects
both work to suppor
Am 17.11.2015 17:08, schrieb David Chen:
We’ve been getting a warning from FindGTest.cmake about CMP0064 when
building SimpleITK. The warning occurs at lines 127, 129 and 131 when
the variable ${test_type} is equal to “TEST”. With CMP0064 this TEST
could be interpreted as commands in the if() a
First ever upstreamed upstreamed mail from me, please gently inform me
if I took the wrong route here.
Running Gentoo Linux x86_64 and compiling with LTO enabled in C*FLAGS,
the configuration stage seems to fail compiling CMake 3.4.0 as described
here: https://bugs.gentoo.org/show_bug.cgi?id=565744
We’ve been getting a warning from FindGTest.cmake about CMP0064 when building SimpleITK. The warning occurs at lines 127, 129 and 131 when the variable ${test_type} is equal to “TEST”. With CMP0064 this TEST could be interpreted as commands in the if() and elseif() statements unless the policy is
On 11/16/2015 10:52 PM, Robert Dailey wrote:
> I also forgot to mention that this patch is based on the 'next'
> branch. Originally it was based on 'master' but I rebased it to
> 'next'. Let me know if this is correct. I'm assuming the master branch
> is used for maintenance releases only and would
The following issue has been SUBMITTED.
==
https://public.kitware.com/Bug/view.php?id=15848
==
Reported By:gang65
Assigned To:
On 11/16/2015 03:14 PM, Levi Morrison wrote:
> It seems my attachments are getting scrubbed or something?
It was just that one message that was missing one. This one worked.
>> How did you test these? For full testing we need the CMake test
>> suite to pass with the Intel compilers. In partic
On Tue, 2015-11-17 at 08:14 +, Stuermer, Michael SP/HZA-ZSEP wrote:
> In short, there is no fully automated style checking. If someone would
> come up with a tool & configuration I would love to use this. So far I
> tested astyle and the C++ edition of ReSharper (unfortunately quite
> expensive
> -Original Message-
> From: Kislinskiy, Stefan [mailto:s.kislins...@dkfz-heidelberg.de]
> Sent: Tuesday, November 17, 2015 10:11 AM
> To: Stuermer, Michael SP/HZA-ZSEP; CMake Developers
> Subject: AW: [cmake-developers] Code style auto-formatting
>
> Do you know ClangFormat[1]? Pretty p
Do you know ClangFormat[1]? Pretty popular choice these days. You just put a
format description file into your repository (which can be based on popular
styles + your exceptions to keep the file rather small). It can be integrated
into many editors including the Visual Studio IDE. You probably w
On 17/11/2015 07:53, Ruslan Baratov wrote:
On 16-Nov-15 21:01, rle...@codelibre.net wrote:
I have attached a patch to add imported targets to FindBoost, in the form
of Boost:: (e.g. Boost::date_time) or Boost::Boost as a
generic
interface library for header-only components.
Since it's `Boost::d
2015-11-15 20:32 GMT+01:00 Markus Rickert :
> Hi,
>
> similar to the previous patch for CPackDeb, the attached patch adds
> component-specific settings for group and name of an RPM package.
>
> CPACK_RPM__PACKAGE_GROUP allows setting the group of the
> component with the main libraries to "Developm
I asked something similar half a year ago:
https://cmake.org/pipermail/cmake-developers/2015-June/025498.html
In short, there is no fully automated style checking. If someone would come up
with a tool & configuration I would love to use this. So far I tested astyle
and the C++ edition of ReShar
35 matches
Mail list logo
