diff options
author | Laurent Bercot <ska-skaware@skarnet.org> | 2014-12-18 23:30:55 +0000 |
---|---|---|
committer | Laurent Bercot <ska-skaware@skarnet.org> | 2014-12-18 23:30:55 +0000 |
commit | 76e4960aa9b9badbd9caa376e303f9360ebb7ccd (patch) | |
tree | 374eb4611aaaa3af6110a447aa1773b01ee021cf /doc/crosscompile.html | |
parent | a46c6ca31cfd61d25fb3579807e3405764bcec72 (diff) | |
download | skalibs-76e4960aa9b9badbd9caa376e303f9360ebb7ccd.tar.xz |
Documentation fixes
Diffstat (limited to 'doc/crosscompile.html')
-rw-r--r-- | doc/crosscompile.html | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/crosscompile.html b/doc/crosscompile.html index ba22b31..4098afd 100644 --- a/doc/crosscompile.html +++ b/doc/crosscompile.html @@ -76,8 +76,10 @@ architecture</strong>, via the --with-sysdeps option to configure. <p> The easiest way to get the correct sysdeps for a target achitecture is -to natively compile skalibs on that target, and steal the produced sysdeps -files. It can be easily done with a virtual machine, qemu for instance. +to natively run skalibs' <tt>./configure</tt> script on that target, +and steal the produced sysdeps files, which are normally written to the +<tt>./sysdeps.cfg</tt> directory. +Doing this is easy with a virtual machine, qemu for instance. You could also (politely) ask for precompiled sysdeps on the skaware mailing-list, if you cannot find them anywhere on the Internet. </p> |