friendlyanon

> for what purpose should we have cmake files if we would expect the user to manually intervene anyway In this case, it's a peculiarity of the GNU toolchain that...

It's not a hack, it's a toolchain requirement. Toolchain requirements can be satisfied using command line variables (`-D=`), preloaded cache variables (`-C`), or a toolchain file (`-DCMAKE_TOOLCHAIN_FILE=` or the newer...

Based on comments in https://old.reddit.com/r/cpp/comments/1b0zem7/what_is_the_state_of_modules_in_2024/ things aren't quite there yet. I have to also take care that things can be run in CI, so GitHub Actions also needs the necessary...

I'll only add modules stuff to the templates once `import std;` works in GitHub Actions with the pre-installed toolchains. AFAIK, libstdc++ hasn't even been modularized yet.

Thanks for clearing that up, I greatly appreciate it! IANAL, but hopefully the Conan team will have a better idea on how to approach this with that information.

So, I'm trying to work on upstreaming the related changes from my fork, but I'm having trouble. I have created a C89-ish file that reproduces the `test.bin` data for testing...

Thanks. I have indeed completed the process. Now I'm using Aegis with automatic backups to my own self-hosted Nextcloud instance. For anyone who might read this: Never ever trust Google...

There is the `pyz` release if you don't want to or for whatever reason can't install anything. If that works for you please close the issue.

Any updates on this? Due to how I have the project structured, it needs the templates in a zip file (or in pyz) to preserve the directory structure. This necessitates...

> spin up a totally new environment for every build but if you are building local copies they can clash That's not a typical workflow, but from experience your requirement...