c++ exceptions and tarballs?

[Robin Kirkman]

I have written a program in KDevelop 1.4, c++, which relies heavily upon C++
exception handling (throw, catch). From the project directory itself, it
compiles just fine.

However, I tried making a source tarball with the Project->Make
Distribution->Source-tgz menu option and testing it in a separate directory, and
it failed horribly. Specifically, the g++ is being passed -fno-exceptions, which
I suppose optimizes most code, but is deadly to mine. I tried setting a compiler
flag from the project compile options (-fexceptions) but it had no effect. I
could find no way from within Kdevelop to disable -fno-exceptions, and i simply
do not grok the autoconf generated scripts well enough to mess with them.

Anyone have a solution?
--robin

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