On 03/24/2015 08:10 AM, Adam Strzelecki wrote:
Awesome! Thanks for sorting that out. Hope it will now serve well for Amine.
Would it be default for projects targeting min 3.3?
Yes. That is how policies work. The need to be aware of them goes
away over time as projects update their min req
Awesome! Thanks for sorting that out. Hope it will now serve well for Amine.
Would it be default for projects targeting min 3.3?
-- Adam
Wiadomość napisana przez Brad King brad.k...@kitware.com w dniu 23 mar
2015, o godz. 14:49:
On 03/18/2015 01:41 PM, Adam Strzelecki wrote:
IIUC the
On 03/17/2015 05:50 PM, Adam Strzelecki wrote:
Does this BYPRODUCTS extension landed into 3.2?
Yes.
is there any new POLICY to tell CMake to stop generating
implicit phony rules for Ninja as proposed in:
Not yet. For out-of-source builds the only place that the
phony rules can show up is
Brad King wrote:
This was in 'next' over the weekend and is clean on the dashboard.
To those that encountered problems requiring this feature, please
try it out to see if it works correctly for your use case.
I didn't fully review the branch, but I looked at commit 6e1c359f
(QtAutogen:
Hi Folks,
Picking up from this old thread:
explicit custom command side-effects (was: Severe regression caused by #14972
fixes)
http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/11207/focus=11225
and this issue:
Add explicit specification of custom command side effect
