JelleSpijker

Nice then I might focus on adding rotation to the individual tiles and grouped tiles to generate even more complex infill patterns. I believe I have a working branch open.

Weird that hardly nobody knows the WKT files which stands for, and I kid you not: Well Known Text representation https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry We only use a small subset of that format tho: https://github.com/Ultimaker/CuraEngine_plugin_infill_generate/blob/aaeebbd3c2c795184e94b404c46941c94739bb5e/include/infill/content_reader.h#L30 - LINESTRING - MULTILINESTRING - POLYGON

I love these new tiles @cuq! Certainly these first tiles would make excellent new additions, I made a FR request for you to consider adding these to the plugin for the next minor release: https://github.com/Ultimaker/CuraEngine_plugin_infill_generate/issues/8 On a side note I'm planning on adding some rudimentary SVG support, but that will probably be a hobby weekend PR and I'm not sure when I have the time for that.

the binary of a bundled plugin needs needs to live in the bin directory (next to CuraEngine.exe etc) because Mac Apps are very picky about the folder and file structure. https://github.com/Ultimaker/Cura/pull/16776

Assuming you are working on Windows and you have the following external build dependencies installed: Visual Studio 2022 C++, Python 3.6 or higher, sip 6.6.x or higher, CMake 3.23.x or higher, Ninja 1.10 or higher, Conan 1.52 or higher. Getting to build and use CuraEngine should work with the following commands which are all run from Powershell as a normal user: First we're gonna make sure that you start from a fresh situation, by updating Conan and making sure that you have SIP installed 6.6.2 (6.7.x seems to have a bug) pip install conan --upgrade --force pip install sip==6.6.2 conan remove "*" -f conan config install https://github.com/ultimaker/conan-config.git conan profile new default --detect Then we're gonna clone CuraEngine and install the dependencies with the help of Conan. Notice the: -c tools.env.virtualenv:powershell=True argument, Since it is rather difficult to to determine in which shell the commands are run and which environment Conan needs to generate we need to explicitly set that to the Powershell environment. Normally we would have set this globally by default but the Conan recipes, for OpenSSL and CPython don't play nice with this yet. git clone https://github.com/Ultimaker/CuraEngine cd CuraEngine conan install . --build=missing --update -c tools.env.virtualenv:powershell=True conan install . --build=missing --update -s build_type=Debug -c tools.env.virtualenv:powershell=True This should download and build all dependencies, both release and debug and also create a build directory with a folder named generators in there, these contain the CMake modules with the information needed to link and build CuraEngine with the dependencies. We can now generate the Ninja build files with CMake for each build type: cmake --preset release cmake --preset debug and build CuraEngine for the build_type you want (note I'm not sure about the order of the --build and --preset release flag, if it fails try switching those) cmake --build --preset release The above command should build CuraEngine.exe in the directory: build/Release folder. We can now activate the environment containing the Environmental paths for Windows, defined in the conanrun.ps1 which can be found in build/generator folder. This should add the location of the shared dependencies to the PATH. Alternatively you can also try to add the Conan deploy generator https://docs.conan.io/en/latest/reference/generators/deploy.html#deploy-generator to the install command: -g deploy This will copy all shared dll to the user space. If you then copy these dll's over to the Build folder next to CuraEngine.exe Windows will find these and use them.