Andre Weissflog
Andre Weissflog
Hach yes, I agree, but it's a bit of a bottomless pit, at least when doing it right. I wanted to sidestep the issue with the ```fips diag tools``` command...
Maybe a better option would be to add an alternative ```fips setup emscripten``` command which points fips to an existing (globally installed) SDK instead of setting up a local version....
@fungos ah right, that's why it looked so familiar :)
Agreed it's probably a good idea to check for this early and issue a warning before the emscripten install starts...
Yep, it's a bit more work to setup no_auto_import projects, but it's created exactly for that reason, to filter out imports that are not needed in some build configs.
From first glance it looks like CLion is using gcc via mingw, fips currently assumes that on Windows the VStudio compilers are used (unless it's a cross-compiling scenario). I'll see...
I don't have a solution sorry, I have installed MSYS2 now but cmake already fails to identify the compiler (I first ran ```./fips set config linux-make-release``` to manualle select a...
Hmm I'm not sure how compiling and linking GL programs on MingW would even work with the current build system setup, does MinGW have their own GL headers and GL...
I've been thinking a bit more about this: I guess for proper msys2 support it would make sense to handle this a bit like the RaspberryPi, it's a mostly Linux-like...
I haven't tried it with OSX frameworks yet, but fips defines a set of standard directories where it searches for link libraries both in the main project and dependencies with...