[Build System] Missing images

[deejam]

Some images are missing in hrev42411. I guess it is because of the build system. If not, please correct this ticket.

gcc2h hrev42411.

Missing Haiku logo in boot splash

Missing Haiku logo in Installer

Missing Haiku logo in About System

[luroh]

Confirmed, using haiku-nightly-hrev42411-x86gcc2hybrid-vmware.tar.xz

[mmadia]

Yep, this is due to how the images are currently being built.

Basically, BOM builds x86-gcc2, x86-gcc4, and then the hybrids. To save time, the hybrids are built within the same generated directories. x86-gcc2, x86-gcc4, and x86-gcc4hybrid's targets are jam'd with -sHAIKU_DISTRO_COMPATIBILITY=default and x86-gcc2hybrid is jam'd with -sHAIKU_DISTRO_COMPATIBILITY=official , as part of #7616.

However, it seems that jam does not realize that the change in HAIKU_DISTRO_COMPATIBILITY will alter the binary objects.

[axeld]

Yes, jam does not track the contents of variables during the build. That's pretty much the only nice feature in cmake :-)

[mmadia]

The next batch of nightly images should display the logo. Could you check?

[luroh]

Nope, no logo in haiku-nightly-hrev42506-x86gcc2hybrid-vmware.tar.xz

[mmadia]

Since jam does not track the contents of variables, on every build cycle the following compiled objects are being deleted from <generated-dir>/objects/haiku/[x86|ppc|arm|m68k|mipsel]/release/ :

• apps/aboutsystem
• apps/installer/
• system/boot/loader/boot_loader.a
• boot/platform/generic/boot_platform_generic.a
• system/kernel/kernel_core.o

The hope was that jam would rebuild new objects with -sHAIKU_DISTRO_COMPATIBILITY=official. However, that too failed to produce images with the HAIKU logo.

Any pointers?

[deejam]

In hrev42942, the images are back in AboutSystem and Installer, but not in the boot splash.

[mmadia]

With Ingo's help, this should be resolved. The next x86gcc2hybrid image newer than hrev42942 should have the boot splash. Please confirm. Thanks!

[deejam]

Replying to mmadia:

With Ingo's help, this should be resolved. The next x86gcc2hybrid image newer than hrev42942 should have the boot splash. Please confirm. Thanks!

All three images are back in hrev43005. This ticket can be closed.

[deejam]

Why was this ticket invalid? Were the missing images only a dream?

[mmadia]

Good to hear. Thanks again.

For record keeping, these are the files being deleted:

• release/apps/aboutsystem
• release/apps/installer
• release/system/boot/loader/boot_loader.a
• release/system/boot/platform/generic/video_splash.o
• release/system/kernel/boot_splash.o
• common/apps/aboutsystem
• common/apps/installer

It was an issue with Build-O-Matic and not with Haiku's own sources. So it was a valid bug, just not for this bugtracker. Ideally, at comment:2, i would've moved this to OsDrawer (where buildomatic is hosted), but ... that's life :)

[anevilyak]

No, I just picked the wrong drop-down option.

[Disreali]

IIRC, the nightlies are supposed to have the red "Development" overlay on the boot screen. As of hrev43005, that is not the case. It only has the Haiku logo on the boot screen.

[deejam]

Replying to Disreali:

IIRC, the nightlies are supposed to have the red "Development" overlay on the boot screen. As of hrev43005, that is not the case. It only has the Haiku logo on the boot screen.

I thought so too, so I used Google images yesterday and looked at at least 100 boot images — none of which had the Development overlay. So I discarded it as me remebering it wrong.

[mmadia]

from hrev38946 Message:

Make the development boot splash more discret, relaying on the usual quite hidden bug theme. This also reduce its RLE compression size, which should fix #6710.

IIRC, the logo should have some ladybugs on it.

[deejam]

Replying to mmadia:

from hrev38946 Message:

Make the development boot splash more discret, relaying on the usual quite hidden bug theme. This also reduce its RLE compression size, which should fix #6710.

IIRC, the logo should have some ladybugs on it.

It has one ladybug.

Boot logo from gcc2h hrev43005 nightly build.

[mmadia]

Yes, that's the current 'development' logo for the boot splash. If you think it isn't clear enough, a new ticket could be made (and possibly assigned to phoudoin, as he was the last to work on it).

[deejam]

Replying to mmadia:

Yes, that's the current 'development' logo for the boot splash. If you think it isn't clear enough, a new ticket could be made (and possibly assigned to phoudoin, as he was the last to work on it).

I like it a lot. The discussion was whether (I was going to misspell it wether on purpose) the logo should have the Development overlay or not. This logo is much more cleaner!

Case close. ;-)

[Disreali]

Replying to mmadia:

from hrev38946 Message:

Make the development boot splash more discret, relaying on the usual quite hidden bug theme. This also reduce its RLE compression size, which should fix #6710.

IIRC, the logo should have some ladybugs on it.

Indeed it does. I did not realize that the overlay had been removed from the nightlies.

Replying to deejam:

I like it a lot. The discussion was whether (I was going to misspell it wether on purpose) the logo should have the Development overlay or not. This logo is much more cleaner!

Agreed, it much cleaner and bolder.

Case close. ;-)

Indeed. Sorry for the noise.

[Kev]

I am having the original issue reported here, on my first time trying a GCC4 build in a long time: haiku_unsupported-nightly-hrev45404-x86gcc4 . The boot screen looks exactly as in the screenshot, and also, the desktop background does not show the Haiku logo either.

[mmadia]

As HAIKU is currently distributed as a GCC 2 Hybrid, that is the only image type that is branded with the HAIKU trademarks. (yes, there are still numerous in-app and in-documentation references to "Haiku", but that's beside the point.)