[QBS] Exception in Exception handling

Jochen Becher jochen_becher at gmx.de
Wed Sep 11 13:12:16 CEST 2013

For the values of a new property "exceptionHandling" I would reserve
"none" for some compiler settings which does disable exception handling
while "default" should omit any compiler option (and thus fall back to
the compiler's default setting).

Regards, Jochen

Am Mittwoch, den 11.09.2013, 12:06 +0200 schrieb Epting, Thomas:
> > > My thought was that you could add an exception specific property,
> for 
> > > example, as an override in case this would happen in a different use
> case.
> > > cpp.exception: '/EHa'
> I agree, in our specific case we also need to derive from the default
> '/EHsc', even though we're not using CLR.
> > You're right that the /EHsc switch should not be added unconditionally
> to the
> > compiler command line. We need a property for enabling CLR and make
> sure
> > that we do not add conflicting command line switches.
> >  I'm not so sure about a dedicated property for the /EH switches. At
> least I can't
> > think of proper property and value names at the moment.
> What about a property called "exceptionHandling"? Possible values could
> e.g. be "default" (for VC, option /EHsc is created) or "none" (in which
> case no compiler option is generated). If needed, a compiler specific
> cFlag can be used in addition to exceptionHandling: "none". I think this
> approach nicely covers the 95% case on Windows (where /EHsc is what you
> want) and enables you to change the option if you have specific needs.
> Another approach would be values describing the kind of exception
> handling (e.g. "cppOnly" aka /EHsc, "all" aka "/EHa").
> Thoughts?
> Regards,
> Thomas
> _______________________________________________
> QBS mailing list
> QBS at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qbs

More information about the Qbs mailing list