where is the gccoptions dialog in gideons code ?

[Otto Bruggeman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry for the late reply, been too busy...

On Fri, 7 Dec 2001, Bernd Gehrmann wrote:
> 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?

Argh shit, you are right, i was thinking that the dialog would be embedded
in the projectoptions dialog and not as a seperate dialog that would pop
up when pressed on the '...' button. I simply forgot to look there, my
bad.

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

Ok, i will add it to this part.

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

Ah thanks for the explanation, i'll move the code in the autoproject dir
then and provide a cvs diff to catch all my stupid mistakes :) when i am
ready with the code before i commit.

There are a few ways to insert the macros into the buildsystem:
- - Put it in a <appname>.m4.in file and put that with aclocal.m4.in and
acinclude.m4.in into acinclude.m4. This requires a Makefile.am rule and
some code in the project wizard to change the <appname> into the real
name in the top Makefile.am.
- - Add it to either aclocal.m4.in or to acinclude.m4.in (i need some place
in the file where i can safely add the macros without interfering with
other stuff and finding them back later). This avoids changing rules in
the Makefile.ams

I think the first method is the best one. This is the least intrusive and
seperates the users macros from the template macros.

Anyway these are my first thought about where ot put this autoconf
macros. So if someone else (Walter ??) has better ideas please tell me.
Later i might add some automake stuff such as conditional compilation of
directories and such with configure.in.in files but this wil take me quite
some time to finish this because i dont have much spare time atm.

Otto

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Made with pgp4pine 1.75-6

iD8DBQE8HO4PDc93sltYd+ERAnlwAKCgwY1M2HTn/wPi7GUZFZVTsVfnZgCdFDq8
TGuYBbmrtXKnvnzCIC95KRQ=
=0U5n
-----END PGP SIGNATURE-----