Re: ROX-CLib: [PATCH] Improved build process

> ROX-CLib uses a single application directory for the source code and
> multiple binaries. It contains a shell script to try and do the right
> thing (find a binary for the current platform or compile a new one).
> This causes problems because:
>
> - the library isn't at a known location relative to the appdir, so a
> script has to be used to locate it
> - the platform guessing often gets it wrong, especially on multi-arch
> systems (if ROX-CLib contains 32- and 64-bit binaries then which one
> to use depends on the architecture of the program calling it...
> ROX-CLib has no way to know this and can either return the wrong one,
> or try to compile a new binary... typically in a read-only directory).
>
> This patch simplifies things by using a separate application directory
> for the source and each generated binary. Running the source
> application generates a binary application directory (using a GUI
> provided by 0compile), one sub-directory per architecture. Running a
> binary returns the pkg-config flags (for backwards compat; newer
> programs can get this information without running it). The binary is
> what you put on your LIBDIRPATH.
>
> The GUI provides a button to register the new binary with 0launch
> (which doesn't work due to a minor bug, fixed in 0compile's GIT repo;
> "0launch --feed" on the binary's feed works, though).