KConfig XT and maintaining compatibility

Unai Garro Unai.Garro at ee.ed.ac.uk
Fri Nov 14 15:47:20 GMT 2003


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


> am_edit just doesn't care about conditionals at all. No matter how you
> write them.
 

uh, really? I must fix my automake, since it works on all the other 
conditionals :)

Oh, and more interestingly, I used to copy the code from juK :)

I quote from it:

================
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)

>
> > 
> > Alternatively, the unsermake-friendly way is to just define the set of
> > includes in the configure.in.in like:

ah, I'll check that. I was wondering why unsermake couldn't build it.

>
> That's the version that makes sure it will never work with unsermake.
> I can't see what's friendly about that.

Well, so far I haven't used unsermake since nobody gave me a solution. I seem 
to remain in the same status for now :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/tPkMWNUXeOoCNE0RAgfMAKCtAhu+EzVQsuICJIvsXv15LqAAjgCgip98
ZmVo/rSkf4wF3cSOr8zg8uQ=
=ZXg2
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list