Richard Shaw wrote:
> Hmm... I guess we shouldn't add it to the cmake macro then :) I
> usually wait and see if there's a problem first and then try that as
> the fix. I haven't had a situation where it gave me bad flags yet, but
> I did have a package that hard coded "Release" with bad flags (-O3
Richard Shaw wrote:
> Hmm... I guess we shouldn't add it to the cmake macro then :) I
> usually wait and see if there's a problem first and then try that as
> the fix. I haven't had a situation where it gave me bad flags yet, but
> I did have a package that hard coded "Release" with bad flags (-O3
On Tue, Feb 28, 2012 at 5:19 PM, Rex Dieter wrote:
> Kevin Kofler wrote:
>
>> Richard Shaw wrote:
>>> I've noticed with several packages lately that frequently the wrong
>>> build flags are used or appened to the ones the cmake macro sets.
>>> Sometimes this can happen because the main cmake confi
Kevin Kofler wrote:
> Richard Shaw wrote:
>> I've noticed with several packages lately that frequently the wrong
>> build flags are used or appened to the ones the cmake macro sets.
>> Sometimes this can happen because the main cmake configuration file
>> forces the type to "Release" (bad!) but no
Richard Shaw wrote:
> I've noticed with several packages lately that frequently the wrong
> build flags are used or appened to the ones the cmake macro sets.
> Sometimes this can happen because the main cmake configuration file
> forces the type to "Release" (bad!) but not always.
>
> I've found t
