Hi Michael,
good timing - I just sent off the other mail... :-)
> I assure you that I always have you "embedded guys" in mind.
I have no doubt. But I guess it's also very difficult to meet the wishes
of such a diverse userbase - people like me want it to be as small as
possible, without any dependencies to other packages. Other people want
to make lcd4linux part of a bigger application, and hence need
python/perl/c++/Java/whatever bindings...
> There *should* be no problem, because autoconf (especially the
> python.m4) is meant to check if you have python (-devel), and
> deactivates all that python stuff if there is none.
Right - but autoconf seems to find the python stuff installed on my
devel box, which is there just fine, but isn't found during the actual
compile (since it's _not_ installed in my sandbox for compiling/linking
against uClibc). Remember, I'm doing a little bit of a cross-compile, so
whenever configure picks up something that's installed on the devel box
but not in the sandbox for uClibc, I'm in trouble.
I guess it's just one of the usual problems, where "configure" assumes
that the box that the program is being compiled on is the same as the
one it will run on.
> Or did I miss something?
No - I just didn't use the --with-plugins directive properly. Once I
used that the compile worked (by specifying every plugin except python),
and with the patch I sent in my previous mail, it also works with
"all,!python".
Martin
|
