Alas, you can't just copy your favorite flavor of qemu (or some other
binary which offers you a cpu transparency method) inside
/scratchbox/devkits/cputransp/bin and use it.
You'll need either to do some hacking or compile a static version which
is (in my opinion) no less trouble than adding it to to cputransp
package and recompiling that.
However, you might want to try defining a custom transparency in the
environment. See if SBOX_CPUTRANSPARENCY_METHOD will meet your needs.
Regards,
Jussi
Steve Lemke wrote:
On Feb 7, 2007, at 3:35 AM, Jussi Hakala wrote:
You are right. In the future, we might think of eliminating the
architectures that are clearly wrong from the selection.
As a related question, in the future could scratchbox generate this list
dynamically?
Currently the list is installed along with the initial set of
CPU-transparency (qemu) binaries.
This makes it harder to add new ones separately without having to
re-build the cputransp package or resort to other hacks with pre/post
install scripts.
The list of compilers appears to be generated dynamically; I'd really
like to see the same done for the list of CPU-transparency components.
--Steve
_______________________________________________
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
_______________________________________________
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
