I just figured out that replying to a mailing list message means your post is off topic .. sorry folks Marius jogged my memory .. the builds that i got to work needed pacman -S pacman -S mingw-w64-x86_64-gettext Note .. this is the complete package with source and include files there is also mingw-w64-x86_64-gettext-runtime @Marius .. your specific suggestion was to use mingw-w64-ucrt-x86_64-gettext-runtime which i think is going to fail on two points it is the runtime so maybe no include files? certainly no source code it is for UCRT rather than for MinGW as i write the build is now happily chewing thru the build for reference .. this is my projects additional include path ${workspaceFolder}/** ${workspaceFolder}/src/** ${workspaceFolder}/src/core/** ${workspaceFolder}/src/gui/** ${workspaceFolder}/src/io/** ${workspaceFolder}/src/utils/** ${workspaceFolder}/build/OpenSCAD_autogen/** C:/bin/glib-dev_2.26.1-1_win64/lib/glib-2.0/include C:/bin/glib-dev_2.26.1-1_win64/include/glib-2.0/ ** C:/lib/eigen-3.4.0/ ** C:/bin/Qt/6.9.0/mingw_64/include/ ** C:/bin/Qt/6.9.0/mingw_64/include/QtCore/ ** C:/lib/QScintilla_src-2.14.1/src/ ** C:/bin/Qt/6.9.0/mingw_64/include/ ** C:/lib/boost_1_89_0/tools/boost_install/ ** C:/lib/boost_1_89_0/ ** C:/mingw64/include/ ** with this all name references are resolved in Visual Studio Code .. even into the libraries like eigen and boost i had to manually install boost, gettext, Qt, QScintilla, eigen , and glib so that VSC is able to show me what types everything is and lets me browse all the source code and the buld just finished .. another success on windows .. just too sleepy to do my testing now LOL laters folks -- jeff is vulcan_ in the cloud

On 10/27/2025 6:12 PM, Jeffrey Hayes via Discuss wrote: > I just figured out that replying to a mailing list message means your > post is off topic .. sorry folks > > Marius jogged my memory .. the builds that i got to work needed  > > pacman -S pacman -S mingw-w64-x86_64-gettext ... which is present if you install MSYS2 and follow the instructions.  (I just did it.) One key thing that might be easy to miss - I missed it the first time I redid it today - is the direction to start an MSYS2 window using the "MSYS2 MinGW x64" link.  (Which has been renamed to MSYS2 MINGW64, but one hopes that that's a pretty obvious match.) > for reference .. this is my projects additional include path > ${workspaceFolder}/** > ${workspaceFolder}/src/** > ${workspaceFolder}/src/core/** > ${workspaceFolder}/src/gui/** > ${workspaceFolder}/src/io/** > ${workspaceFolder}/src/utils/** > ${workspaceFolder}/build/OpenSCAD_autogen/** > C:/bin/glib-dev_2.26.1-1_win64/lib/glib-2.0/include > <http://C:/bin/glib-dev_2.26.1-1_win64/lib/glib-2.0/include> > C:/bin/glib-dev_2.26.1-1_win64/include/glib-2.0/ > <http://C:/bin/glib-dev_2.26.1-1_win64/include/glib-2.0/>** > C:/lib/eigen-3.4.0/ <http://C:/lib/eigen-3.4.0/>** > C:/bin/Qt/6.9.0/mingw_64/include/ > <http://C:/bin/Qt/6.9.0/mingw_64/include/>** > C:/bin/Qt/6.9.0/mingw_64/include/QtCore/ > <http://C:/bin/Qt/6.9.0/mingw_64/include/QtCore/>** > C:/lib/QScintilla_src-2.14.1/src/ > <http://C:/lib/QScintilla_src-2.14.1/src/>** > C:/bin/Qt/6.9.0/mingw_64/include/ > <http://C:/bin/Qt/6.9.0/mingw_64/include/>** > C:/lib/boost_1_89_0/tools/boost_install/ > <http://C:/lib/boost_1_89_0/tools/boost_install/>** > C:/lib/boost_1_89_0/ <http://C:/lib/boost_1_89_0/>** > C:/mingw64/include/ <http://C:/mingw64/include/>** And while I'm happy that your work on using VS Code is coming along... not a single thing on that list (except arguably the last) is coming from the instructions. > i had to manually install *boost, gettext, Qt, QScintilla, eigen*, and > *glib *so that VSC is able to show me what types everything is and > lets me browse all the source code Cool.  And again, not in the instructions. You keep talking about needing to do things that are not in the instructions, that are not required if you follow the instructions, so why are you surprised when I assume that you're trying to do something that isn't covered by the instructions? I just created a new MSYS2 environment, following the instructions.  There were two things that seem to have changed in how MSYS2 is documented and installed: * The initial install instructions no longer explicitly tell you to upgrade after installing.  (So I didn't.) * The Start Menu link is now "MSYS2 MINGW64", instead of "MSYS2 MinGW x64".  One hopes that that's an obvious enough match, but if it isn't... the fact that the instructions refer to something that doesn't exist should be a big clue that the problem is near there.  I've updated our documents to match the current install. And other than those two items, OpenSCAD built and runs without any off-script tweaks.

On 10/27/2025 8:36 PM, Jordan Brown via Discuss wrote: > One key thing that might be easy to miss - I missed it the first time > I redid it today - is the direction to start an MSYS2 window using the > "MSYS2 MinGW x64" link.  (Which has been renamed to MSYS2 MINGW64, but > one hopes that that's a pretty obvious match.) The MSYS2 install optionally leaves you with a UCRT64 shell running.  That's not what we need, but the distinction is easy to miss so I added a specific note reminding you to use the MINGW64 shell.