[SOVLED]How to compile with Escape From Monky Island support

General chat related to ScummVM, adventure gaming, and so on.

Moderator: ScummVM Team

Post Reply
Jamie Marchant
Posts: 3
Joined: Sun Oct 20, 2019 4:15 pm

[SOVLED]How to compile with Escape From Monky Island support

Post by Jamie Marchant »

I compiled ResidualVM in Fedora(there are no binaries in the package manager or the website) but the terminal said that Escape From Monky Island was not built in. How do I recompile ResidualVM with Escape compiled in?
Last edited by Guest on Mon Oct 21, 2019 12:09 am, edited 1 time in total.
Nitrus
Posts: 177
Joined: Wed May 18, 2011 9:49 am

Re: How to compile with Escape From Monky Island support

Post by Nitrus »

Hi Jamie,
If you're sure you have all the datafiles set-up correctly, try running the configure script with the following flag:

Code: Select all

--enable-engine=monkey4
Jamie Marchant
Posts: 3
Joined: Sun Oct 20, 2019 4:15 pm

Re: How to compile with Escape From Monky Island support

Post by Jamie Marchant »

Thank you!
undrwater
Posts: 6
Joined: Fri Feb 07, 2020 12:40 am

Re: How to compile with Escape From Monky Island support

Post by undrwater »

Nitrus wrote:Hi Jamie,
If you're sure you have all the datafiles set-up correctly, try running the configure script with the following flag:

Code: Select all

--enable-engine=monkey4
In the git version, I notice there is no "monkey4" listed in the "engines" directory.

I'm using a gentoo ebuild, and when I run:

Code: Select all

residualvm --list-engines
Engine ID       Engine Name                                           
--------------- ------------------------------------------------------
grim            Grim
myst3           Myst III
stark           Stark
I don't see monkey4 listed. When I try to run "Escape..." I just get a black screen. I figure that's what's happening.
Nitrus
Posts: 177
Joined: Wed May 18, 2011 9:49 am

Re: [SOVLED]How to compile with Escape From Monky Island sup

Post by Nitrus »

The monkey4 engine is a subset (or superset depending on how you look at it) of the grim engine, also visible here:
https://github.com/residualvm/residualv ... ure.engine

I can't check at the moment, though the list command might not be including the GrimE variant.
The logic for this is here:
https://github.com/residualvm/residualv ... t.cpp#L142
It might be disregarding it when listing, though it is there.

If you're able to Add the game and run it, it's likely that you have the correct files.
I assume you followed the guide here or here.
It might be good to check the data by running the step described here:
https://forums.residualvm.org/viewtopic ... 2180#p2180
Also might be good to post a list of your directory here so we can take a look.

Finally, it's possible that no-one's done a Gentoo ebuild in a long time (I can see that the last daily addition is from 6/7 years ago), so there might be Gentoo-specific issues.

EDIT: following a GitHub/Bitbucket rabbit hole, I found this here regarding ebuilds, which might interest you. It looks to be more up to date.

EDIT2: Looking at it more closely, you'd probably want to add the following addition to Line 68 as well:

Code: Select all

dists/engine-data/residualvm-emi-patch.m4b
Post Reply