Salutations. I right now use CXX_STANDARD and CXX_STANDARD_LIBRARY for some
test projects since I want to utilize smart pointers. As I am on a Mac, my
preferred IDE is Xcode (sometimes called XCode), so I generate Xcode
targets by default. I've noticed, however, that whenever I use CXX_STANDARD
and
On 6/29/15, Brad King wrote:
> On 06/25/2015 09:24 AM, Eric Wing wrote:
>> I pushed up a couple of repos for everybody to try.
>
> Thanks. From that I was able to make some progress with getting
> CMakeDetermineSwiftCompiler to work.
>
> I've made two tweaks to CMakeDetermineCompilerId to make it
dear Brad,
thanks for testing it on your side and also for the suggestions!
I can consistently reproduce it locally on 3 different machines (Ubuntu
14.04
and Arch derivative; gfortran 4.8.4 and 5.1.0).
I have Git bisected the history and this is the commit that broke this
example on my
machines:
Sorry, I've added in the missing method to cmake.cxx, which updates the
WarningLevel map according to the boolean provided. cmake-gui compiles
without errors again.
I could add support for the new options to the GUI, in which case I
would probably also go back to the changes I made to cmake.cx
What is the difference between the intended uses of those existing options
and the intended uses of the new options, given that -Wno-dev is mostly
useful for third parties to silence policy warnings?
Working on this issue, I did find the different variables/options a bit
confusing. dev and depr
On 07/02/2015 04:14 AM, Radovan Bast wrote:
> We have observed a changed and surprising behavior in CMake 3.3.0-rc3
> with Fortran module dependency scanning and preprocessing compared to
> earlier CMake versions (for instance 3.2.3).
I don't recall any changes related to this since 3.2. I also c
On 07/01/2015 12:14 PM, Todd Gamblin wrote:
> - Is there some reason CMake adds the -qalias=noansi arg for XLC?
It was added here:
Add initial XL C compiler flags for safer builds
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e1729238
but I don't recall why it was included among the other
dear CMake developers,
We have observed a changed and surprising behavior
in CMake 3.3.0-rc3 with Fortran module dependency scanning and
preprocessing compared to earlier CMake versions
(for instance 3.2.3). I have checked open bugs and email
list archives but could not find this mentioned.
To gi
