Classes to compile, build, sign a project.

note to self: releases do not need to be compiled

To build a project with tool4d

tool4d compiler.4DProject --startup-method=build --user-param=.4DSettings,.4DProject,../../build --dataless

in --user-param, pass up to 3 POSIX paths:

extension	content
.xml or .4DSettings	build settings file
.json or .4DProject	project file
other	build destination path (relative path supported)

Note: When the build destination path is specified, the absolute path in the build settings file is ignored. The path would typically be ../../folder because the work folder is 2 levels up from the project file.

in --startup-method, pass one of the following:

• build: compile, build
• compile
• rebuild: clean compiled code, compile, build
• sign: run the signapp.sh script

To build a project with 4D

$buildProject:=File("{Settings}/BuildApp.4DSettings")
$compileProject:=File("{Project}/BuildApp.4DProject")

var $CLI : cs.BuildApp_CLI

$CLI:=cs.BuildApp_CLI.new()
$CLI.compile($compileProject)
$CLI.build($buildProject; $compileProject)

Packaging

• Do not zip 4D.entitlements or SignApp.sh on Windows. codesign will fail.
• SignApp.sh does not seem to work when a self hosted runner is launched as a service (requires investigation)