PyXMake

This subpackage belongs to PyXMake and contains all core functionalities. It is installed automatically with the parent project. However, it is also separately available as a build system dependency. Please refer to the linked repository for documentation and application examples. If you came across the project via the GitLab Catalog Explorer, you can jump directly to the CI/CD Catalog section

Downloading

Use GIT to get the latest code base. From the command line, use

git clone https://gitlab.dlr.de/dlr-sy/pyxmake pyxmake

If you check out the repository for the first time, you have to initialize all submodule dependencies first. Execute the following from within the repository.

git submodule update --init --recursive

To fetch all required metadata for each submodule, use

git submodule foreach --recursive 'git checkout $(git config -f $toplevel/.gitmodules submodule.$name.branch || echo master) || git checkout main'

To update all refererenced submodules to the latest production level, use

git submodule foreach --recursive 'git pull origin $(git config -f $toplevel/.gitmodules submodule.$name.branch || echo master) || git pull origin main'

Installation

PyXMake can be installed from source using poetry. If you don't have poetry installed, run

pip install poetry --pre --upgrade

to install the latest version of poetry within your python environment. Use

poetry update

to update all dependencies in the lock file or directly execute

poetry install

to install all dependencies from the lock file. Last, you should be able to import PyXMake as a python package.

import PyXMake

CI/CD Catalog

PyXMake provides its software development and deployment capabilities as pre-built CI/CD components. The individual components can be integrated either directly via the CI/CD Catalog or classically via the "include" syntax. The components are divided into three groups:

• General
• Python
• Docker

To include a given component, use

include:
  - component: $CI_SERVER_FQDN/<groupname>/PyXMake/<component>@<tag>

where <groupname> depends on the local Gitlab repository, <component> refers to the name of the component under templates/* and <tag> to a specific version. <tag> can also be set to master to always use the latest yet potentially unstable version.

Contact

• Marc Garbade