where is the gccoptions dialog in gideons code ?

[Bernd Gehrmann]

On Fri, 7 Dec 2001, Otto Bruggeman wrote:
> i have been browsing through the code and i can't find the gcc
> optionsdialogcode as used currently in the projectoptions. I did find the
> gccoptions stuff in plugins/gccoptions but afaict this is not the code
> that is being shown in the project options because it uses multiple
> tabwidgets and should show the compiler warning flags and what i see in
> the projectoption it only uses one tab. So where is the code that is being
> used and why is the code in plugins/gccoptions not being used because it
> looks much better in my opinion ?

Hmm, not sure what you mean. When I click on Project->Project Options
->Compiler Options, I get text edits for FFLAGS, CFLAGS and CXXFLAGS.
There I can either enter the options by hand or click on the "..."
button to get a dialog. This dialog depends on the compiler used
(for C/C++ the only one implemented is gcc). For me, this dialog contains
the tabs General, Optimization, Fortran specifics (this one must be a 
bug ;-) , Warnings I and Warnings II. 

Is this different for you?

> I was looking through this code because i wanted to add a wizard thing or
> a couple of tabwidgets to add autotools macros to the project options for
> header/lib searches and the possibility to add custom macros to your
> project, but this is still in the early stages of development and is not
> even usable atm. Oh and should this be put in the parts dir as a part or
> in the plugins dir ? And how do i show it in the project options, what
> method to i have to implement ?

Sounds good :-) Since it's autoconf specific, I'd say the right place is
the autoproject part. AutoProjectPart::projectConfigWidget() shows how
the different widgets are embedded into the project options dialog.

In general, any part can plug into the project options dialog by
doing 

  connect( core(), SIGNAL(projectConfigWidget(KDialogBase*)),
           this, SLOT(projectConfigWidget(KDialogBase*)) );

and implemententing the slot, which gets the dialog as argument.
The dialog is a KDialogBase with any number of pages.

Bernd.