mulle-cosmopolitan

To test build use mulle-sde craft craftorder -- --sdk cosmopolitan

⛺ mulle-cosmopolitan support for mulle-c

mulle-cosmopolitan builds the libc of cosmopolitan and provides custom compilers mulle-gcc.cosmopolitan and mulle-clang.cosmopolitan to build projects that link against this libc. Such executables are supposed to be OS independent as long as the platform runs on intel compatible processors.

Other system headers will not be available!

Add mulle-cosmopolitan to your mulle-sde project

Add mulle-cosmopolitan-cc and mulle-cosmopolitan as dependencies. It is intended that you set cosmopolitan as your MULLE_CRAFT_SDKS environment variable:

mulle-sde dependency add --marks no-header,no-link,only-craft-sdk-cosmopolitan --github mulle-cc mulle-cosmopolitan
mulle-sde dependency add --marks no-header,no-link,only-craft-sdk-cosmopolitan --github mulle-cc mulle-cosmopolitan-cc
mulle-sde dependency move mulle-cosmopolitan-cc top
mulle-sde dependency move mulle-cosmopolitan top
mulle-sde env --global set --append MULLE_CRAFT_SDKS cosmopolitan

Add cosmo-cc build tools

It's usually convenient to install them somewhere on the system, so that the build process does not download the tools every time. This only works for version 3.2, because of some unfortunately hardcoded version number in the build script:

COSMOCC_VERSION=3.2
(
   cd /opt
   sudo mkdir cosmopolitan
   sudo chown `id -u` cosmopolitan
)

url="https://github.com/jart/cosmopolitan/releases/download/${COSMOCC_VERSION}/cosmocc-${COSMOCC_VERSION}.zip"
dir="/opt/cosmopolitan/"${COSMOCC_VERSION}"
mulle-fetch -v "${url}" "${dir}"

It is important that you link the installation into a local addiction directory (in each executable project that you want to build):

triple="`arch`-`uname -s | tr '[:upper:]' '[:lower:]'`-cosmo"

mkdir -p "addiction/${triple}"
(
	cd addiction

    ln -sf /opt/cosmopolitan/${COSMOCC_VERSION}/bin
    ln -sf /opt/cosmopolitan/${COSMOCC_VERSION}/include
    ln -sf /opt/cosmopolitan/${COSMOCC_VERSION}/libexec
    ln -sf /opt/cosmopolitan/${COSMOCC_VERSION}/${triple}/lib ${triple}/lib
)
mulle-sde env set ADDICTION_DIR '${MULLE_VIRTUAL_ROOT}/addiction'

If it's, there the build process will pick it up.

(old note)

Outside of a mulle-sde environment, you may need to define the environment variable DEPENDENCY_DIR that is the root of your cosmopolitan installation. If DEPENDENCY_DIR is not defined, the compiler will then look for ${MULLE_VIRTUAL_ROOT}/dependency. If that directory is missing or MULLE_VIRTUAL_ROOT is undefined, the compiler will use its grand-parent directory as a fallback. (e.g. /usr/local/bin/mulle-gcc.cosmopolitan will use /usr/local as DEPENDENCY_DIR)

Dependency setup

The file structure of the DEPENDENCY_DIR as create by mulle-cosmopolitan is slightly non-standard for a cosmopolitan build and will look like this:

├── include
│   ├── alloca.h
.....
│   ├── cosmopolitan
│   │   └── cosmopolitan.h
│   ├── ctype.h
.....
│   ├── netinet
│   │   ├── in.h
.........
│   │   └── udp.h
.....
│   ├── sys
│   │   ├── dir.h
........
│   │   └── wait.h
.....
│   └── wctype.h
├── lib
│   ├── ape.lds
│   ├── ape-no-modify-self.o
│   ├── cosmopolitan.a
│   ├── crt.o
│   ├── libdl.a
│   ├── libm.a
│   └── libpthread.a

The lib<name>.a libraries are just empty shells, so the linker finds something.

Author

Nat! for Mulle kybernetiK