Re: Cross compiling with autotools

[Kjell Ahlstedt <kjell ahlstedt bredband net>]

Can you build other packages, e.g. glibmm, which libxml++ depends on? 
How about glib and libsigc++? If you can build other packages, then 
there must be some important difference in the configure.ac files of 
those packages and libxml++.

When I compared the configure.ac files of glibmm and libxml++, I noticed 
that glibmm has
  LT_INIT([win32-dll])
where libxml++ has
  LT_INIT([dlopen win32-dll disable-static])
but I don't know if that's important. I suspect it's not. It's 
AC_PROG_CXX that expands to compiler tests in the configure file.

Kjell

2013-04-19 10:39, lcidfire googlemail com skrev:
> For casablanca, I need to get libxml++ cross compiled via Emscripten.
> Upon trying I very soon fail since autoconfig wrongly checks for the 
> compiler building a default executable (which would be wrong too for 
> e.g. Android-ARM).
> I try to configure via:
> emconfigure ./configure --host=i386-pc-linux-gnu --enable-static=yes 
> --enable-shared=no CPPFLAGS="`empkg-config --cflags libxml-2.0`" 
> LIBS="`empkg-config --libs libxml-2.0`"
>
> But it fails with:
> checking whether the C++ compiler works... no
> configure: error: in `/libxml++/2.36.0':
> configure: error: C++ compiler cannot create executables
>
> My question is whether someone could walk me through how to modify 
> your autotools setup or whether it might be better to fork libxml++ 
> and to build it using SCons.