> Generally when I use Visual Studio IDE for CMake-based Emscripten > projects, what I do is I use CMake to generate two solutions, once for > native Windows Visual Studio, and a second time for MinGW Makefiles for > Emscripten. For that I adapt the VS version to include all the > Emscripten-specific .cpp/.h files to be shown in the IDE (if there are any > such extra ones), and use VS as the text editor, while driving the > Emscripten builds via 'mingw32-make' from the command line. This has the > advantage that I can do Windows builds at the same time from the IDE as > well, to keep cross-comparing that the native version still builds and runs > ok if I do some mods. The CMake+Visual Studio+Emscripten integration > experiment did not feel like it was bringing anything more to the table, so > I dropped pursuing that further. > > Yes, I do it similar, but instead of mingw/make I'm generating a ninja project out of cmake, just for the reason that I couldn't get a Windows-native make to work reliably while the Windows-native version of ninja works fine and I didn't want to rely on a separate mingw installation. Most of the time I do emscripten work on OSX though, which is a bit less painful because it has a proper bash.
What I'm actually really looking for in an IDE-integration would be a better debugging experience though, and the cmake-server stuff won't help with that. I wonder if WebAssembly would fundamentally improve the debugging situation..? > The CMake server thing seems to fix the VS issues where CMake used a bunch > of VS macros as triggers to know when to reconfig before a build, and now > VS will be able to drive CMake rather than the other way around. That will > definitely be helpful, although I wonder if there will be hardcoded > assumptions that the compiler will be cl.exe, or if that can be dictated by > CMake toolchain files. > > 2016-10-09 12:44 GMT+03:00 Floh <[email protected] <javascript:>>: > >> ...this may be interesting for future IDE integrations: the next cmake >> version comes with a 'server mode', you basically start cmake with a >> special command line arg, and from then on, cmake listens on stdin for >> commands, and returns JSON formatted responses on stdout. >> >> https://cmake.org/cmake/help/v3.7/manual/cmake-server.7.html >> >> On one hand, this will integrate cmake projects better with Visual >> Studio: >> https://blogs.msdn.microsoft.com/vcblog/2016/10/05/cmake-support-in-visual-studio/ >> >> But I think it can also be used to add IDE-like features for cmake-driven >> projects (so... also emscripten projects), to lighter weight environment >> like Atom Editor, Visual Studio Code, vim, etc... >> >> This might be a better solution then creating specialized solutions like >> the current Visual Studio plugin. >> >> Cheers :) >> -Floh. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "emscripten-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
