complier_injection.sh assumes the existence of a makefile in the <code class="notransl

How to build with custom inform? about inform HOT 2 OPEN

tbodt commented on August 20, 2024

How to build with custom inform?

from inform.

Comments (2)

tbodt commented on August 20, 2024

The make-integration-settings.mk is missing? Only the Linux and Windows ones exist anywhere on GitHub. https://github.com/search?q=path%3Amake-integration-settings.mk&type=code

from inform.

tbodt commented on August 20, 2024

Was able to get it working by writing my own make-integration-settings.mk, and also checking out the extensions branch that is actually compatible with the current inform core.

# Make settings for integrating Inform's user interface and core software.
# This file contains only those settings likely to differ on different
# platforms, and the idea is that each user interface maintainer will keep
# his or her own version of this file.

# Toby Nelson forgot to commit the make-integration-settings.mk for Mac so I'm reverse engineering it here.

INTEGRATION = TRUE

# Now, the locations to which resources must be copied, inside the
# application. These pathnames mustn't contain spaces:

BUILTINCOMPS = ../InformApp/inform/TempStagingArea/Contents/MacOS
INTERNAL = ../InformApp/inform/TempStagingArea/Contents/Resources/Internal
BUILTINHTML = ../InformApp/inform/TempStagingArea/Contents/Resources
BUILTINHTMLINNER = ../InformApp/inform/TempStagingArea/Contents/Resources/en.lproj
ADVICEHTML = ../InformApp/inform/TempStagingArea/Contents/Resources/en.lproj

# Various executables are copied into the BUILTINCOMPS folder, but their
# filenames when copied there have sometimes differed between platforms.

INBLORBNAME = cBlorb
INFORM6NAME = inform6
INFORM7NAME = ni
INTESTNAME = intest

# Indoc options for generating the inside-the-application documentation:

INDOCOPTS = osx_dev_app
HTMLPLATFORM = macos