Bug#40512: marked as done (user-defined C++ compiler options ignored) by "W. Tasin" <tasin at fhm.edu>

[Stephan Kulow]

Your message with subj: Bug#40512: user-defined C++ compiler options ignored

  In KDevelop 2.1 there is the possibility to switch on the exception 
handling by "Project->Options...->"configure settings".

The project templates of KDE/KDevelop switch off the exception handling 
for certain reasons (especially because about 66% of the project 
templates are made for QT and KDE development).
Please look at the following threads:

http://lists.kde.org/?l=kde-devel&m=99651260609781&w=2
http://lists.kde.org/?l=kde-devel&m=99652451026332&w=2
http://lists.kde.org/?l=kde-devel&m=99788768311869&w=2

For all the others the GUI switch was made in KDevelop 2.1.

Ciao

Walter

james.fischer at nexsi.com wrote:

>Package: kdevelop
>Version: 2.0.2 (using KDE 2.2.2 -1)
>Severity: normal
>Installed from:    Red Hat Linux 7.2
>Compiler:          gcc 3.x
>OS:                Linux (i686) release 2.4.7-10
>OS/Compiler notes: Not Specified
>
>KDevelop 2.0 and 2.1 both have a design flaw that implicitly disables C++ compiler options that the user tries to enable via the GUI. For example: 
>
.....

-- 
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>






has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 8 Apr 2002 20:25:30 +0000
Received: (qmail 18680 invoked by uid 33); 8 Apr 2002 20:25:30 -0000
Date: 8 Apr 2002 20:25:30 -0000
Message-ID: <20020408202530.18679.qmail at mail.kde.org>
To: submit at bugs.kde.org
Subject: user-defined C++ compiler options ignored
From: james.fischer at nexsi.com
X-KDE-Received: -66.35.207.149

Package:           kdevelop
Version:           2.0.2 (using KDE 2.2.2 -1)
Severity:          normal
Installed from:    Red Hat Linux 7.2
Compiler:          gcc 3.x
OS:                Linux (i686) release 2.4.7-10
OS/Compiler notes: Not Specified

KDevelop 2.0 and 2.1 both have a design flaw that implicitly disables C++ compiler options that the user tries to enable via the GUI. For example: 

<KDevelop 2.0,>

1) Start KDevelop 2.0 and create a C++ terminal project.

2) Select "Project | Options..." from the main menu.

3) Select "Compiler Options"

4) Type "-fexceptions" in the "additional options:" text entry field.

5) Click "OK"

6) Select "Build | Rebuild" from the main menu.

7) Observe the output in the "messages" window. Specifically, note the fact that KDevelop has implicitly added the -fno-exceptions option *AFTER* the user-defined option "-fexceptions" -- e.g.

<messages>

make[3]: Entering directory `/home/jfischer/temp/'
cc++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -O0 -g3 -Wall -fexceptions -fno-exceptions -fno-check-new  -c main.cpp
</messages>

In this case, KDevelop blindly injects the conflicting compiler option '-fno-exceptions' *AFTER* the user-defined option '-fexceptions'. Consequently, the C++ code cannot use C++ exception handling -- a required component for ANSI C++ code that uses the STL.

</Kdevelop 2.0>
This is clearly a design flaw. No other C/C++ development IDE on planet Earth: a) provides a dialog box for the user to define compiler options, and then b) injects conflicting, product-defined compiler options *after* the user-defined compiler options.

[n.b. The g++ 2.9x C++ compiler series IS DEFINITELY NOT ISO/ANSI C++ compliant. That compiler series was developed BEFORE the ISO/ANSI C++ standard even existed. The ISO/ANSI C++ standard library is vastly different from the C++ library that shipped with g++ 2.9x. When using the ISO/ANSI C++ standard template library -- e.g., iostreams, containers, memory allocation / deallocation, locales, etc. -- RTTI and exception handling MUST BE ENABLED BY DEFAULT. If there is any doubt to the validity of this statement, please read the ISO/ANSI C++ standard [ISO/ANSI 14882:1998]. The standard can be purchased and downloaded in Adobe Acrobat format for $18[US] from the following web site:

    http://webstore.ansi.org/

Click on the "standards search" link, and then search for "14882-1998". (Note: If you search for "14882:1998" the engine will bring up the $250[US] printed, bound manual and not the $18 Adobe Acrobat .pdf file.)]


(Submitted via bugs.kde.org)
(Called from KBugReport dialog. Fields Compiler manually changed)