[haiku-development] Re: Bootloader Image not appearing
- From: Philippe Houdoin <philippe.houdoin@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 18 Nov 2010 23:50:10 +0100
>> Ok, thats great. Thanks, sorry to pollute this list with stupid
>> questions.
That was not one, as we clearly didn't documented this feature very well before.
Technically, the bootloader images (logo and icons) are conditionnaly
selected here:
http://dev.haiku-os.org/browser/haiku/trunk/headers/private/kernel/boot/images.h
This header then include either images-tm.h (official release),
images-tm-development.h (official non-release) or images-sans-tm.h
header.
Currently, the usual icons are available in each header, whatever
distro-compatibility config.
images-tm.h contains usual icons and the official boot logo:
http://dev.haiku-os.org/browser/haiku/trunk/data/artwork/boot_splash/splash_logo.png
images-tm-development.h contains usual icons and the development logo:
http://dev.haiku-os.org/browser/haiku/trunk/data/artwork/boot_splash/splash_logo-development.png
And images-sans-tm.h only contains usual icons and and empty logo.
So, except if you generate you own boot logo and icons images, in
"compatible" distro mode you will only get icons.
To generate a custom boot images-sans-tm.h file from your own images,
you must build generate_boot_screen tools, available under src/tools
(jam generate_boot_screen) and run it with your two PNG files. It will
generate an header file, rename it images-sans-tm.h and copy over the
default one.
Beware, there is today a 300kb limit to the size of haiku_loader
binary, and any too complex boot logo will make it too large, the
tarfs image which start at 300kb offset behind the haiku_loader will
then overwrite it partially and the logo will appear as corrupted,
which is exactly the case. This is a known bug.
Bye
Philippe
Other related posts:
