|
Lines 25-34
compiling is all the same.
Link Here
|
| 25 |
|
25 |
|
| 26 |
<p> |
26 |
<p> |
| 27 |
You should install the kernel into the sysroot so that if you want to |
27 |
You should install the kernel into the sysroot so that if you want to |
| 28 |
cross-compile packages which include kernel modules, the process should be |
28 |
cross-compile packages which include kernel modules, the process will be |
| 29 |
transparent. If you don't need such packages, then of course the actual place |
29 |
transparent. Otherwise, the actual place where you build the kernel does |
| 30 |
where you build the kernel does not matter. Some people build all their |
30 |
not matter. Some people build all their kernels in <path>/usr/src/</path> |
| 31 |
kernels in <path>/usr/src/</path> for example. |
31 |
for example. |
| 32 |
</p> |
32 |
</p> |
| 33 |
|
33 |
|
| 34 |
</body> |
34 |
</body> |
|
Lines 64-69
chop off that trailing <c>gcc</c> and that's what you use:
Link Here
|
| 64 |
</p> |
64 |
</p> |
| 65 |
|
65 |
|
| 66 |
<p> |
66 |
<p> |
|
|
67 |
There is an additional variable, <c>INSTALL_MOD_PATH</c>, which defines where |
| 68 |
the <path>/lib</path> directory will be created, and all the modules stored. |
| 69 |
While you don't have to transfer the kernel sources to your target device, |
| 70 |
if you build any modules, you'll want this directory. |
| 71 |
</p> |
| 72 |
|
| 73 |
<p> |
| 67 |
There are really two ways you can setup the system. You can modify the |
74 |
There are really two ways you can setup the system. You can modify the |
| 68 |
toplevel Makefile or you can override the relevant variables on the command |
75 |
toplevel Makefile or you can override the relevant variables on the command |
| 69 |
line. How you do it is largely a matter of taste, so we'll cover both. Pick |
76 |
line. How you do it is largely a matter of taste, so we'll cover both. Pick |
| 70 |
- |
|
|
