API for configure.in
Etay Meiri
cl1 at netvision.net.il
Mon Feb 4 20:32:04 UTC 2002
> I think so, too...
> but please try to include AM_WITH_MPATROL in all different project types
> and maybe you see some problems.
>
OK, I would.
> Which is the correct position where AM_WITH_MPATROL should be included?
In a small test I did with kdevelop's C project I put the macro right after
AC_ENABLE_STATIC(no)
and it worked ok. Basically I think you can put it anywhere among the other tests.
> Does it create conflicting situations with the acinclude.m4.in macro calls?
>
You would have to elaborate here because I'm not an autoconf guru.
> >Does
> >kdevelop provide anything for that? How about hacking configure.in directly
> >from my 'Enable mpatrol' menu item in kdevelop.
> >
> It is a good idea... apart from the fact, that maybe you should do this
> effort for gideon (aka KDevelop cvs-HEAD)?
>
Right now I'm having a lot of problem compiling QT3 from CVS. running configure
fails when building qmake because it seems a lot of includes (like qnamespaces.h)
are messed up and although they are there, they are not included right. I'm
starting with KDE_2_2_BRANCH because I'm already familiar with it. Once I get
it working and have a working KDE3, I'll make it work on Gideon too.
> My idea for now to patch configure.in(.in) in an easy way is:
> - search configure.in.in, if not present then use configure.in.
> - search inside this file for lines like
> dnl CXXFLAGS= dnl __kdevelop__
> or
> CXXFLAGS= .......... dnl __kdevelop__
>
> - if one of these is found the switch in the GUI is enabled (can be used)
> - if someone activate the exception handling inside the GUI then the
> line should change to
> CXXFLAGS="$CXXFLAGS $USE_EXCEPTIONS" dnl __kdevelop__
> and reverse.
>
> IMHO AM_WITH_MPATROL should be inserted/deleted the same way.
Seems like this is how I'll do this for mpatrol. On the long term we should
provide APIs like:
bool AddConfigureMacro(const char*);
bool RemoveConfigureMacro(const char*);
bool DoesExistConfigureMacro(const char*);
That would get the job done.
--
Etay Meiri
cl1 at netvision.net.il
More information about the KDevelop-devel
mailing list