Hi René,
This is great! Thank you very much!
Rob
René Rebe wrote:
Hi Rob,
the build system can not detect any arbitrary file that might belong
to a package. You therefore can (re-)build single packages with
the Build-Target -job option:
sudo scripts/Build-Target -job 1-linux26
the ?- prefix is the stage number, your embedded cross build will
mostly build all in the cross stage 1, thus the 1-linux26. The toolchain
is build in the stage 0, so if you would want to rebuild your cross
compiler it would be -job 0-gcc, and if your build would have native
builds those would mostly live in stage 5, e.g. -job 5-openoffice-org
Yours,
René
rob wrote:
Hello everybody,
I'm not very experienced with T2 yet, so I probably just miss
something. But here's my question:
I have build the embedded target, which went fine. Now I want to
rebuild the kernel using my own configuration file.
The conffile is stored as config/default/linux.cfg
In the T2 configuration file the following settings are done:
* Apply custom kernel build configuration settings
(none) Do not perform any automatic kernel configuration
Then I did 'sudo scripts/Build-Target', but it doesn't rebuild the
kernel. The build system just goes through all steps, finds nothing
to be done and rebuilds the rootfs. It does read the linux.cfg file
though, and placed the rules in the T2 conffile.
How can I force the build system to rebuild the linux26 package? Or
should I just do a 'scripts/Cleanup' and rebuild the whole target?
Thanks in advance,
Rob Wilbers
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
