zdoom/zdoom-macos-deps
0
0
Fork 0
mirror of https://github.com/ZDoom/zdoom-macos-deps.git synced 2024-11-28 14:42:03 +00:00
Code Issues Projects Releases Packages Wiki Activity
*ZDoom binary dependencies for macOS
1565 commits 5 branches 4 tags 328 MiB
Python 84.4%
C++ 10.5%
Shell 2.5%
CMake 1.4%
C 1.2%
Find a file
alexey.lysiuk d01cee6100 wip [skip ci]
2024-03-09 12:27:52 +02:00
.github wip [skip ci] 2024-03-09 09:48:31 +02:00
.idea update pycharm project to use python 3.9 2023-02-19 10:56:08 +02:00
aedi wip [skip ci] 2024-03-09 12:27:52 +02:00
deps Merge branch 'main' into wip 2024-03-09 09:42:00 +02:00
patch wip [skip ci] 2024-02-22 17:16:00 +02:00
test add gme test 2024-01-24 12:39:51 +02:00
.gitignore ignore temp directory by git and idea 2022-08-16 12:26:36 +03:00
build.py aedi: update copyright years 2024-01-02 10:55:22 +02:00
dependencies.md correct png reference in dependency list 2022-09-03 12:11:32 +03:00
readme.md readme: remove info about macos sdk 2023-10-24 09:53:22 +03:00

readme.md

*ZDoom binary dependencies for macOS

This repository contains all binary dependencies required to build macOS application bundles of ZDoom-derived source ports. A few other projects are supported as well, with lesser priority though.

Build Targets Lint Code Test Libraries

Usage

Download source code, and build a target

build.py --target=<target-name>

Build target from existing source code

build.py --source=<path-to-source-code>

Generate Xcode project instead of building target, and open it

build.py --source=...|--target=... --xcode

Run build.py without arguments for complete list of options.

Prerequisites

Xcode 12.2 or newer is required in order to build universal binaries. Launch Xcode once to finish its installation. In theory, it is possible to use older versions of Xcode to build Intel target only by adding --disable-arm command line option.

Directories

  • build directory stores all intermediary files created during targets compilation, customizable with --build-path command line option
  • deps directory stores all dependencies (headers, libraries, executable and additional files) in the corresponding subdirectories
  • output directory stores built main targets, customizable with --output-path command line option
  • prefix directory stores symbolic links to all dependencies combined as one build root
  • sdk directory can contain macOS SDKs that will be picked if match with macOS deployment versions
  • source directory stores targets source code, customizable with --source-path command line option
  • temp directory stores temporary files, customizable with --temp-path command line option