KConfig XT and maintaining compatibility

Unai Garro Unai.Garro at ee.ed.ac.uk
Sun Nov 16 05:10:41 GMT 2003


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


> > ================
> > if link_lib_GST
> > gstlibs = -lkdegst -lkdegstplay
> > endif
> >
> > juk_LDADD = $(gstlibs) $(mblibs) -lartskde $(LIB_KIO) $(taglib_libs)
> > ================
> >
> > What's the difference? here (gstlibs) is being expanded and obviously the
> > conditional is checked. The conditional (link_lib_GST is defined in
> > configure.in.in, same as my xt_exists check)
>
> Expandings libs is fine.
> Expandings sources is much harder - how do you create targets and
> dependencies, for sources that you don't know?

the other (simpler) option would be making some change so that KDE 3.1 
versions ignore any ".kcfg" files in the sources. That would allow all apps 
in extragear and nonbeta begin porting to KConfig XT.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/twbUWNUXeOoCNE0RAuvhAJ9ttJthw+buyk9kiszqBjLBoTixvwCg3UdM
VBtHimnmrk8/DR+9vzlVX1Q=
=thHl
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list