With the new version of the Hollywood language released a while ago, there have also been changes to the binary files, where, in my opinion, something doesn’t quite add up.

In practice, the new development version of Hollywood significantly streamlines the binaries by removing libraries that are now required externally.

Well, or rather badly: previously, some applications ‘that didn’t include the library internally’ would look for it in the programme folder or in the system’s Libs/Hollywood folder.

Now, however, all required libraries, “and there are quite a few”, must be located in the programme folder. In practice, this means the system will end up with dozens and dozens of duplicate libraries. If we then add that some older Hollywood applications refuse to use new libraries and instead require a specific older version, the confusion only increases.

The Amiga philosophy dictates that all libraries, as is the case with other operating systems, must be located in a single system folder: ‘Libs’ for AROS and Amiga. This ensures there is only one copy, making updates straightforward; otherwise, they would all need to be updated as applications are updated.

What is the status regarding AROS64 BTw? do I assume right Hollywood only supports AROS32? (I have a Hollywood GUI - done by a Betatester, I never used Hollywood - for Dungeonkeeper here).

First and foremost, developers creating their own software within the Hollywood application should start putting more pressure on Hollywood’s developer to finally release a 64-bit version...

Hollywood currently only supports 32-bit, but it is possible to run many Hollywood applications on AROS 64-bit using the built-in ‘EmuV0’ emulator
https://www.forum...426#p22426

The attached thread lists the various Hollywood app compatibilities with AROS 64-bit; if you like, we can test your Hollywood GU!
https://www.arosw...post_10678