The C/C++ projects don't have a admin dir so unfortunately it is not that 
easy :-(

In addition to the files I mentioned in my last mail, you also have to copy 
these files in order to make a project work:
ltconfig
ltcf-c.sh
ltcf-cxx.sh
ltcf-gcj.sh

On suse 7.3 it then compiles :-)

Greetings,
eva


On Tuesday 30 October 2001 10:04, you wrote:
> On Monday, 29. October 2001 14:42, you wrote:
>
> Moin Eva!
>
> we got aware of certain problems by a mail yesterday complaining about the
> C templates. I contacted Walter to see what's wrong with the C and C++
> template. These don't use the KDE admin directory; only the Qt and KDE ones
> do, where I have fixed that in CVS. To update existing projects when using
> a newer automake, one needs to have KDevelop 2.0.2 from CVS, generate a
> KDE-test project and replace the admin directory in his project that he
> works on with the one in the test project. Then everything should be fine
> again.
>
> Ralf
>
> > Trying to make my projects compile again, I did the following:
> > I copied the files
> > admin/libtool.m4.in
> > admin/acinclude.m4.in
> > acconfig.h
> > acinclude.m4
> > aclocal.m4
> > into my C/C++ project. Furthermore I commentet out line 48 in
> > configure.in: dnl AC_REQUIRE([KDE_CHECK_EXTRA_LIBS])
> >
> > Now I get the following messages:
> >
> > cat acinclude.m4.in libtool.m4.in >acinclude.m4
> > aclocal
> > autoheader
> > autoheader: config.h.in is unchanged
> > automake
> > autoconf
> > configure.in:62: warning: AC_ARG_PROGRAM invoked multiple times
> > *** success ***
> >
> > Is that ok? Or still something to worry about?
> >
> > I also have to add, that on SuSE 7.2, we have an updated KDE (KDE 2.2.1)
> > and KDevelop crashes (only for C/C++). The project files already exist in
> > the directory, but not all |NAME| strings are replaced.
> >
> > Greetings,
> > eva
> >
> > On Monday 29 October 2001 14:21, you wrote:
> > > Hi,
> > >
> > > when making a new C or C++ project and also when doing "autoconf and
> > > automake" with an old C/C++ project I get the following messages:
> > >
> > > cat acinclude.m4.in libtool.m4.in >acinclude.m4
> > > aclocal
> > > autoheader
> > > ./aclocal.m4:549: error: m4_defn: undefined macro: _m4_divert_diversion
> > > aclang.m4:173: AC_LANG_RESTORE is expanded from...
> > > ./aclocal.m4:549: the top level
> > > autoconf: tracing failed
> > > gmake: *** [all] Error 1
> > > *** failed ***
> > >
> > > This is probably because of updated autoconf packages. Unfortunately I
> > > don't know anything about m4, autoconf, automake, etc.
> > > Has anyone a hint?
> > >
> > > Thank you,
> > > eva
> > >
> > > On Saturday 27 October 2001 23:38, you wrote:
> > > > Hi,
> > > > The CVS-version of KDevelop on branch KDE_2_2_BRANCH contains an
> > > > improved version of the debugger now.
> > > > You can debug multithreaded applications (both, Qt3 and Qt2 based).
> > > > Please, test and report problems so that we can release it stable
> > > > with KDevelop-2.0.2 (on the KDE-2.2.2 release)!
> > > >
> > > > Ciao,
> > > > F@lk
> > > >
> > > > P.S.: Grisha Mokhin and Nikita Youshchenko have fixed the editor
> > > > views for non-latin chars! :-)
> > > > If you enable the showing of static members, showing of strings in
> > > > VAR view will also work.
> > > >
> > > > _________________________________________________________
> > > > Do You Yahoo!?
> > > > Get your free @yahoo.com address at http://mail.yahoo.com
> > > >
> > > >
> > > > -
> > > > to unsubscribe from this list send an email to
> > > > kdevelop-request@kdevelop.org with the following body: unsubscribe
> > > > »your-email-address«
> >
> > -
> > to unsubscribe from this list send an email to
> > kdevelop-request@kdevelop.org with the following body: unsubscribe
> > »your-email-address«
>
> -
> to unsubscribe from this list send an email to
> kdevelop-request@kdevelop.org with the following body: unsubscribe
> »your-email-address«

-- 
Dijkstra:
"Testing can prove the presence of bugs, but not their absence."

-
to unsubscribe from this list send an email to kdevelop-request@kdevelop.org with the following body:
unsubscribe »your-email-address«