mcpp.toml

[package]
namespace   = "mcpplibs"
name        = "openkal-macos"
version     = "0.3.4"
description = "An implementation of openkal for macOS, written on the kernel's own calls. Its purpose is as much to test the specification as to be used."
license     = "Apache-2.0"

# The layer this package supplies, in the vocabulary the engine resolves.
#
# `mcpp:kernel-abi` names the platform interface a C library sits on. On a
# traditional stack that seam is unnamed — a C library issues system calls or
# calls the platform's own entry points directly — and naming it is what lets
# one C library sit above several platforms. `=openkal` is the interface this
# package answers to; several packages answer to it and the engine knows none
# of them by name.
provides    = ["mcpp:kernel-abi=openkal"]
authors     = ["mcpplibs"]
repo        = "https://github.com/mcpplibs/openkal-macos"

[dependencies]
openkal = "0.7.0"

[build]
# The flags are attached to this package's own sources rather than to the whole
# build. A module interface records the dialect it was compiled under, so a
# translation unit compiled without exceptions cannot import one compiled with
# them; the conformance tests import the specification's modules, and they are
# consumers rather than parts of the implementation.
flags = [
  { glob = "src/**", cxxflags = ["-fno-exceptions", "-fno-rtti",
                                 "-fno-stack-protector"] },
]

[features]
default = []

# Whether this implementation is the whole of the program's environment.
#
# Ordinarily a program already carries a runtime that has received control from
# the loader and that creates execution contexts, and this implementation
# borrows both. That is the default.
#
# Where it does not, this implementation supplies the entry point and creates
# contexts through the one name in this system's thread library that no C
# library defines --- which is the only name reachable from a program that
# defines every ordinary one.
standalone = { defines = ["OKM_STANDALONE"] }