Admin message

Attention: i10git will shutdown soon!

This i10git GitLab server was migrated to gitos.rrze.fau.de due to hardware issues with the current host. This affects all production repositories, including waLBerla, lbmpy, pystencils and HyTeG.

Login: Gitos supports DFN-AAI and eduGAIN. If your institution does not support either, please use our GitHub mirrors.

Onboarding: All repositories belonging to groups were migrated. To regain access, first log in to gitos.rrze.fau.de once to activate your account. Then email cs10-admin@fau.de with your old i10git and your new gitos.rrze username (the @) as shown on your respective user profiles. We will reassign your accordingly. Note: Repositories from former courses (e.g. advpt) were not migrated.

Personal repositories in individual user namespaces were not migrated. Please export these yourself before the old server is shut down.

Expected shutdown by the end of 2026. Until then, the old i10git server will still be reachable with all repositories archived (read only). However, due to the ongoing hardware issues, it may remain unreliable and will receive no further maintenance.

The parent group is archived. This project and its data are read-only.
CMake Integration
The source file generator should integrate seamlessly with the CMake build system. The user should be able to call a code generation script and add its output files to a target in a transparent and intuitive way with minimal syntactic overhead. The code generator should be configurable through CMake, such that project-global settings can be specified in a single place. Global settings should transparently control any code generation scripts in the project, be accessible from within them, and should be overridable where necessary. ## Inclusion and global configuration The source file generator should be includable to any CMake project via `find_package`. It should work out-of-the-box with zero configuration. Optional global configuration includes the specification of the default output file extensions. Default is `.h/.cpp`, but some projects may use the `.hpp/.cpp` convention; others generate CUDA code and will want to use `.h/.cu`. It should be possible to register a *configurator* Python script which will be automatically imported and run by every code generation script in the project. This configurator would handle any project-specific setup of the code generator; e.g. register default field mappings. ## Source generation for CMake targets Due to the 1:1 correspondence principle between generator scripts and their output files enforced by the code generator, integration with CMake targets becomes straightforward. The basic syntax for registering a script with the build system and adding its output to a target should resemble ``` pystencilssfg_generate_target_sources( TARGET <target> SCRIPTS <scripts> [DEPENDS <dependencies>] [FILE_EXTENSIONS <extensions>] [HEADER_ONLY] ) ``` `<target` may be a libary, an executable, etc. Here, each script is executed and its generated sources (`kernels_a.hpp`, `kernels_a.cpp`, ...) are added to the target. Dependencies may be specified (for triggering rebuilds), and the global file extension setting can be overridden. Optionally, the code generation scripts may be specified as generating only a header file.
issue