Cross assembler that can build for multiple targets.
196
Dockerfiles for containers with various versions of pasmo assembler to build binaries that target various CPUs.
There are several Dockerfiles to create containers of different versions of pasmo assembler. Dockerfiles exist for
Multistage builds are used to help keep the final image size as small as possible.
In the first stage a specific alpine base image is used to extract source files from a tar file, then to build the binaries from source. This stage is given an identifier that can be used as a reference in the following stage.
The second stage uses a specific Alpine Linux image that has glibc included. The binary is copied from the 'builder' stage and PATH environment variable is updated with the location of the pasmo binary.
| Folder | Location | Description |
|---|---|---|
| Pasmo | /usr/local/pasmo | Pasmo installation folder. |
| Project | /home/dev/project | Project source file folder |
The container will process a Makefile in the project directory that has been mapped when the container is started. Here are some examples:
| Shell | Command |
|---|---|
| PowerShell | docker run --rm -v ${PWD}:/home/dev/project gkbmdz/pasmo |
| CMD | docker run --rm -v %CD%:/home/dev/project gkbmdz/pasmo |
| Linux | docker run --rm -v $(pwd):/home/dev/project gkbmdz/pasmo |
The default user within the container is root, this means that any files created will be owned by root and not the user that started the container. When starting the container from Linux, use the following to ensure that created files are owned by the user that started the container:
docker run --rm -v $(pwd):/home/dev/project --user "$(id -u):$(id -g)" gkbmdz/pasmo
Content type
Image
Digest
Size
12.2 MB
Last updated
over 4 years ago
docker pull gkbmdz/pasmo:0.5.5