It seems that in CMake 3.9/AUTOGEN the VS generator uses the *_autogen
target more often than necessary (it could use PRE_BUILD instead).
Let's assume a target `B` that depends on
- a *GENERATED* file `FA`
- a linked library `LA`
- a utility target `TA` (via `add_dependencies()`)
Using the VS
That would mean a lot of duplication for just redefining a particular value.
Each compiler will have likely a way too handle the definition of multiple
flags with the same purpose and based on that prepending or adding could be
performed internally.
Van: Brad
On 08/23/2017 11:27 AM, maikel van den Hurk wrote:
> change ... optimisation from O3 (CMake internal setting) to O2.
If you want to change the default flags instead of only adding
(prepending) to them then you need to set all the flags by
setting the cache entry directly. A toolchain file that
Thanks I was exactly looking for this in particularly, must have searched
wrongly!
Though I wonder for example how could I for example change in my toolchain file
which is setting up a GCC based compiler for example in release context the
optimisation from O3 (CMake internal setting) to O2.
On 08/23/2017 09:56 AM, maikel van den Hurk wrote:
> I was wondering why there is no ability to define
> CMAKE__FLAGS(_) within a CMake Toolchain file, but still
> benefit from the CMAKE__INIT_FLAGS(_) detected from CMake
> internals.
This has been possible since commit v3.7.0-rc1~392^2
I was wondering why there is no ability to define CMAKE__FLAGS(_)
within a CMake Toolchain file, but still benefit from the
CMAKE__INIT_FLAGS(_) detected from CMake internals.
Is certain extension considered before? Or are then any reasons to not do this?
Would be interested to hear if this
On 08/23/2017 05:15 AM, Craig Scott wrote:
> how long until we up the minimum Visual Studio version from 2010
> to at least 2013?
That's only blocked on me finding time to update the nightly testing
infrastructure. It requires moving several builds to other machines.
-Brad
--
Powered by
Probably just asking what a number of people are now thinking, but if we're
now requiring C++11 to build CMake, how long until we up the minimum Visual
Studio version from 2010 to at least 2013? Seems a bit optimistic to still
be trying to support 2010 as the minimum standard and also state C++11
> > > > it looks like C++11 is now a requirement for CMake itself.
> > >
> > > Yes. We just merged this:
> > > https://gitlab.kitware.com/cmake/cmake/merge_requests/1132
> > >
> > > but you beat us to the announcement.
> >
> > I saw the MR last week and was delighted. The iterator type
