Fwd: [kde-linux] Kdevelop and C++ exceptions

[W. Tasin]

Nash Hoogwater wrote:

>Hi,
>
>I asked this yesterday on kde-linux, but maybe you lot know the answer :-).
>
>Greetings,
>
>Nash
>
>----------  Forwarded Message  ----------
>
>Subject: [kde-linux] Kdevelop and C++ exceptions
>Date: Mon, 28 Jan 2002 18:14:54 +0100
>From: Nash Hoogwater <nrhoogwater at planet.nl>
>To: kde-linux at master.kde.org
>
>Hi list,
>
>I'm using exceptions (kdevelop from kde3beta1) and I get the following
>message:
>
>  sqlcursor.cpp:48: exception handling disabled, use -fexceptions to enable
>
>Can somebody tell we where to put this option to enable exceptions?
>
>Thanks in advance,
>
>Nash Hoogwater
>___________________________________________________
>This message is from the kde-linux mailing list.
>Account management:  http://mail.kde.org/mailman/listinfo/kde-linux.
>Archives: http://lists.kde.org/.
>More info: http://www.kde.org/faq.html.
>
>-------------------------------------------------------
>
In the FAQ file of the source-tarball (or from cvs) you can read sth. 
about your problem:

Q: Patching configure doesn't help, after starting autoconf my changings 
are lost.
   Where should I patch things?
A: There's a list of file, where you may patch things for the autotools.
   Makefile.am, configure.in.in, configure.in (only if there is no 
configure.in.in),
  

Q: I´m developing an application which needs exception handling.
   How can I make it?
A: Edit the file configure.in(.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...").

Q: The solutions above are nice, but I want this only for a certain 
subdirectory
   (e.g. a static lib of my project)
   How can I make it?
A: Edit the file Makefile.am in the desired source directory. Here, you
   have to enter somewhere outside the KDevelop specific part:
     KDE_CXXFLAGS=$(USE_RTTI)
   Take care this works only if your project is using am_edit.
   (It works only for newer acinclude.m4 & am_edit, AFAWK they must be
    younger than 12-09-1999, formerly it was known as APPEND_CXXFLAGS -
    in this KDevelop release you will find the right once.)

   You have to update your Makefile-framework as described above
   (make -f Makefile.dist; ./configure [options] or
    inside KDevelop by using "Build/Autoconf and Automake" and 
"Build/Configure...").

Q: Why patching configure.in(.in) with CXXFLAGS="$USE_EXCEPTIONS 
$CXXFLAGS" doesn't work?
A: Look at the answer to the question "Can AM_CXXFLAGS (inside a 
Makefile.am)
   be used for flags like -frtti or -fexceptions?" ;-)

etc...

HTH

Ciao

Walter

>
>
>_______________________________________________
>Kdevelop-devel mailing list
>Kdevelop-devel at barney.cs.uni-potsdam.de
>http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>

-- 
The KDevelop project: tasin at kdevelop.de [www.kdevelop.org]
--
oohhh sveglia.... il mondo e' ammalato, ma x colpa di chi.........
(Zucchero)
:-------W. Tasin, FB 04,FHM-------------------PGP-KeyID:0x7961A645----------:
<Key-Fingerprint: 1610 835F 0080 32F4 6140  6CF7 A7D0 44CD 7961A645>