This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
developersguide:crosscompiling [2016/08/23 17:23] antoineleca [Build compatibility] Add Windows Subsystem for Linux (a.k.a. Ubuntu on Windows, or Bash on Windows) |
developersguide:crosscompiling [2017/03/11 17:29] lionelsambuc [Getting the sources] |
||
---|---|---|---|
Line 25: | Line 25: | ||
<code> | <code> | ||
- | $ git clone git://git.minix3.org/minix minixsrc | + | $ mkdir minix |
- | $ cd minixsrc | + | $ cd minix |
+ | $ git clone git://git.minix3.org/minix src | ||
+ | $ cd src | ||
</code> | </code> | ||
- | NOTE: The releasetools script will generate object files and put them //outside// the source directory; it will move up out of the git repo and start touching stuff there. I.e., if you've cloned to ~/foo/minixsrc/ and build from there, things will start showing up in ~/foo/ as an artifact of the build process. You probably don't want this (and the build process probably shouldn't do this...), so if that's a problem for you, try double-wrapping it: instead of cloning to ~/foo/minixsrc/ try creating a "minix" container directory and cloning to ~/foo/minix/src. | + | NOTE: The releasetools script will generate object files and put them //outside// the source directory; i.e., if you've cloned to ~/minix/src/ and build from there, things will start showing up in ~/minix/ as an artifact of the build process. |
===== Crossbuilding for x86 ===== | ===== Crossbuilding for x86 ===== |