...by allowing our special @___... tokens anywhere within an install name,
so that external modules can configure --prefix=/@___... etc. This removes
the need for the special extshl and EXTRPATH=LOADER. Also, a new
OUT2BIN_NONE can be used for external modules where the generated libraries
need the default EXTRPATH=OOO, but generated executables are only used
during the build and such need RPATH=NONE.
SAL_UNUSED_PARAMETER (expanding to __attribute__ ((unused)) for GCC)
is used to annotate legitimately unused parameters, so that static
analysis tools can tell legitimately unused parameters from truly
unnecessary ones. To that end, some patches for external modules
are also added, that are only applied when compiling with GCC and
add necessary __attribute__ ((unused)) in headers.
The silly apkbuilder tool doesn't add extra native libs to an .apk
package unless their name ends with .so. It just silently ignores
them. So, force libtool to avoid versioning suffix for Android.
Yeah, unclear whether apkbuilder is what we will end up using to
construct the APKs of actual LO code using Android apps. But at this
stage when just trying to build a unit testing app, it seems to be the
simplest way to get the .apk properly signed and all to just use a
normal Ant project, and let Ant run apkbuilder.
In the spirit of 12759f67a36d52a345be6002d7017551e8414c59, change
external lib's config.sub to eat the arm-unknown-linux-androideabi
host os string. Also, permit shared libs again - seems Android can
handle those.
Added dictionaries to cross-build-toolset - idxdict is needed.
Should build up to sfx2 - some residual static lib issues there,
and in raptor.
Makes it easier to build other stuff. Whether we will actually run
normal unit tests at build time, or ever, or not when cross-compiling
to some platform is a different matter...
