tommelt

This issue has technically been solved (by #873) but due to a switch of platform it never got merged. This would make a great *beginner* issue. If not I will...

I agree with @edbennett . `Limit log size -1` option isn't something I've used/found useful either... and `--graph` should definitely be cut because branches are not covered making this option...

@illuhad , thanks so much for your help. The test runs successfully now. I made sure to rebuild acpp using branch `hotfix/string-build-config-mapper-lifetime`, recompile the code and delete any previously cached...

Hi @vbalmer , I have been able to reproduce the errors with `ifort` and `ifx`. I am looking into it, but I also don't use windows. I think there might...

hi @vbalmer . I think I have finally fixed it :sweat_smile: Can you try these instructions (adjusting for paths etc.) ### checkout my test branch In git bash (or otherwise)...

Hi @vbalmer , I had a similar issue. I must admit I am not a windows user so I don't fully understand but it seems Windows has an issue finding...

@vbalmer , I also just wanted to say thanks for all your help spotting the issue in the first place and helping us to debug it. Our software is now...

hi @vbalmer , The main change that "fixed" it was the following change to `src/CMakeLists.txt`. https://github.com/Cambridge-ICCS/FTorch/blob/e9db293561d42c440e513ad6c5d2b297189b695e/src/CMakeLists.txt#L6-L9 Now `CMake` correctly builds FTorch so that it can be linked against by the...

Hi @dorchard I'm more than happy to help with the `CMake` side of things. Let me know when is convenient.

I think that's just the release notes stating that for _this_ release the `gcc` requirement has changed to `gcc>= 9.0`. Not that you have to use `gcc`.