Peter Heywood

Ratesetter requries custom arg parsing (for custom input / output files). As `argc`/`argv` are accessible in main, this can be worked around, but having a nice programatic way to deal...

Current output flags are also not standard convetion, Should short options should only be a single letter, long options use hyphens not underscores. ``` -os, --out_step Step log file (XML...

Useful references: https://cmake.org/cmake/help/git-stage/guide/importing-exporting/index.html#exporting-targets https://cmake.org/cmake/help/v3.18/manual/cmake-packages.7.html#creating-relocatable-packages

Ownership within `CUDAAgentModel` is not idea (although logical) for all cases, as others are used in placed where `CUDAAgentModel` is (and should due to rtc) only forward declared.

pytest-benchmark might be relevant if we want to add a similar thing to the python interface https://pypi.org/project/pytest-benchmark/

Namespaces we definately want: + `flamegpu` - The main namespace which everything belongs to + `flamegpu::visualiser` - The namespace for everthing vis related + `flamegpu::util` - helper functions and other...

A workaround could be to make it programatically accessible, which is already the case in python as `pyflamegpu.SEATBELTS` iirc. In C++ there's the define so its' available at preproc time...