KConfig XT and maintaining compatibility

[Scott Wheeler]

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

On Friday 14 November 2003 8:50, Unai Garro wrote:
> =================
> 
> #define optional sources when KConfigXT exists
> 
> if xt_exists
> xt_added=krecipes.kcfg
> endif
> 
> #define the krecipes sources
> 
> krecipes_SOURCES= ...................... $(xt_added)
> 
> 
> =================
> 
> 
> No matter what I do, the kconfig XT scripts don't seem to expand (xt_added),
> so the configure files are not compiled.

Uhm, well, it's not being expanded because you don't seem to be doing a test 
that would ever make that block of code get hit...

In your configure.in.in -- if you want a Makefile.am linking conditional like 
that you need to have some logic to set "have_xt" to "true" or "false" and 
then:

AM_CONDITIONAL(xt_exists, test x$have_xt = xtrue)

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

if test <some logic> = <some value> ; then
    xt_added=<something>
else
    xt_added=""
fi
AC_SUBST(xt_added)

- -Scott

- -- 
Many people would sooner die than think; in fact, they do so. 
- --Bertrand Russell
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE/tJ5kQu0ByfY5QTkRAhGbAKCbCgppERzhQUw/is9RhX776XKLBwCgzQ9F
BVZN7e1Lx9u4y79cN/vIV1I=
=7dgN
-----END PGP SIGNATURE-----