More annoying default behavior

Thomas Matelich tmatelich at zetec.com
Thu Dec 14 16:58:33 UTC 2000


"W. Tasin" wrote:

> > 2)  Besides the obvious solution of using -fexceptions, where can I turn
> > off the default -fno-exceptions parameter to g++?
>
> This question is already answered in the FAQ-file of the kdevelop
> sources.
> Here some answers...
>
> Q: I´m developing an application which needs exception handling.
>    How can I make it?
> A: Edit the file configure.in in your toplevel source directory. Here,
> you
>    have to enter after the AC_CHECK_COMPILERS() macro:
>      CXXFLAGS="$CXXFLAGS $USE_EXCEPTIONS"
>    and after that you have to recreate your new "configure" by invoking
>    "make -f Makefile.dist" at the toplevel source directory and then
> restart
>    the configure script
>    (or inside KDevelop by using "Build/Autoconf and Automake" and
> "Build/Configure...").

First, isn't configure.in regenerated often?  Second why do you force these flags on us?

And to bring up a question that didn't get answered: How can I make it so that the libraries I generate
are not linked into my application?

--
Thomas O Matelich
Senior Software Designer
Zetec, Inc.
sosedada at usa.net
tmatelich at zetec.com




-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«



More information about the KDevelop mailing list