There is a configure option --without-compression, which gets rid of the
need for libz. There is also --without-libxml2. If your not using exceptions, you might want to use --without-exceptions as well...

All you really need to do is make sure the resulting arm libcc* files are on a valid library search path directory on the target. You may have to manually build sym links also. Nothing else should be needed for a runtime install.

Conrad T. Pino wrote:
Hi David,

The "demo" and "tests" directories don't build as
part of the default build.  Is that normal?

Both "demo" and "tests" directories depend upon
"libz.so" and loading for the host target is easy.

I guess loading the "libz.so" for the ARM target
is easy if you know what to do.  I manually down
loaded the two "*.deb" files, unpacked them with
"dpkg-deb" and manually copied the library and
header files into my cross compile tool set.

The "demo" and "tests" directories for both Intel
and ARM are now built.

I suspect "make install" is next for Intel host.

The ARM system is less than minimul so "make" is
not an option.  What's the manual equivalent for
"make install"?

Conrad

begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
adr:;;;;;;USA
email;internet:[EMAIL PROTECTED]
x-mozilla-html:FALSE
url:http://www.gnutelephony.org
version:2.1
end:vcard

_______________________________________________
Bug-commoncpp mailing list
Bug-commoncpp@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-commoncpp

Reply via email to