#mingw64 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #mingw64, aggregated by home.social.
-
Руководство по сборке Qt под Windows из исходников с MinGW
Официальный способ установки готовых бинарников Qt - через онлайн инсталлятор. Однако он требует обязательной регистрации. Да еще и недоступен на территории РФ. Есть и другие способы получить бинарники, или собрать с компилятором от Microsoft , однако не всегда эти способы приемлемы. Сборка из исходников под Windows может оказаться несколько нетривиальна для новичков, потому сделал небольшую инструкцию по сборке Qt 5 и Qt 6. А так же рассмотрена базовая настройка QT Creator.
-
Руководство по сборке Qt под Windows из исходников с MinGW
Официальный способ установки готовых бинарников Qt - через онлайн инсталлятор. Однако он требует обязательной регистрации. Да еще и недоступен на территории РФ. Есть и другие способы получить бинарники, или собрать с компилятором от Microsoft , однако не всегда эти способы приемлемы. Сборка из исходников под Windows может оказаться несколько нетривиальна для новичков, потому сделал небольшую инструкцию по сборке Qt 5 и Qt 6. А так же рассмотрена базовая настройка QT Creator.
-
Руководство по сборке Qt под Windows из исходников с MinGW
Официальный способ установки готовых бинарников Qt - через онлайн инсталлятор. Однако он требует обязательной регистрации. Да еще и недоступен на территории РФ. Есть и другие способы получить бинарники, или собрать с компилятором от Microsoft , однако не всегда эти способы приемлемы. Сборка из исходников под Windows может оказаться несколько нетривиальна для новичков, потому сделал небольшую инструкцию по сборке Qt 5 и Qt 6. А так же рассмотрена базовая настройка QT Creator.
-
@holgerschurig I just heard that #emacs 31 (current development branch) now can be link with ucrt when compiled using #mingw64, and that significantly reduces boot time on windows
-
Установка GCC в сборке MinGW
Установка коллекции компиляторов GCC (GNU Compilers Collection) в Windows и первичная настройка для дальнейшей работы.
-
Smacked head-first into a stupid issue with the #libcurl package deployed by #MinGW / #MSYS / #MinGW64 - turns out that if you copy the DLLs out of the MinGW environment (you know, like if you want to actually *deploy* an application that uses them), libcurl suddenly starts freaking out about "SSL CA cert" problems.
Someone on StackOverflow noticed there's an alternate "mingw-w64-x86_64-curl-winssl" package that doesn't seem to suffer from this issue (which I confirmed). What a damned mess!
-
Smacked head-first into a stupid issue with the #libcurl package deployed by #MinGW / #MSYS / #MinGW64 - turns out that if you copy the DLLs out of the MinGW environment (you know, like if you want to actually *deploy* an application that uses them), libcurl suddenly starts freaking out about "SSL CA cert" problems.
Someone on StackOverflow noticed there's an alternate "mingw-w64-x86_64-curl-winssl" package that doesn't seem to suffer from this issue (which I confirmed). What a damned mess!
-
Smacked head-first into a stupid issue with the #libcurl package deployed by #MinGW / #MSYS / #MinGW64 - turns out that if you copy the DLLs out of the MinGW environment (you know, like if you want to actually *deploy* an application that uses them), libcurl suddenly starts freaking out about "SSL CA cert" problems.
Someone on StackOverflow noticed there's an alternate "mingw-w64-x86_64-curl-winssl" package that doesn't seem to suffer from this issue (which I confirmed). What a damned mess!
-
Smacked head-first into a stupid issue with the #libcurl package deployed by #MinGW / #MSYS / #MinGW64 - turns out that if you copy the DLLs out of the MinGW environment (you know, like if you want to actually *deploy* an application that uses them), libcurl suddenly starts freaking out about "SSL CA cert" problems.
Someone on StackOverflow noticed there's an alternate "mingw-w64-x86_64-curl-winssl" package that doesn't seem to suffer from this issue (which I confirmed). What a damned mess!
-
Smacked head-first into a stupid issue with the #libcurl package deployed by #MinGW / #MSYS / #MinGW64 - turns out that if you copy the DLLs out of the MinGW environment (you know, like if you want to actually *deploy* an application that uses them), libcurl suddenly starts freaking out about "SSL CA cert" problems.
Someone on StackOverflow noticed there's an alternate "mingw-w64-x86_64-curl-winssl" package that doesn't seem to suffer from this issue (which I confirmed). What a damned mess!
-
The version of #yaml-cpp currently shipped by #MSYS for #MinGW64 has a bug that prevents exporting a symbol to the shipped DLL. It's not MSYS' fault, because yaml-cpp hasn't put out an updated formal release since 10 months before fixing this: https://github.com/jbeder/yaml-cpp/issues/1026#issuecomment-1122305522
-
The version of #yaml-cpp currently shipped by #MSYS for #MinGW64 has a bug that prevents exporting a symbol to the shipped DLL. It's not MSYS' fault, because yaml-cpp hasn't put out an updated formal release since 10 months before fixing this: https://github.com/jbeder/yaml-cpp/issues/1026#issuecomment-1122305522
-
The version of #yaml-cpp currently shipped by #MSYS for #MinGW64 has a bug that prevents exporting a symbol to the shipped DLL. It's not MSYS' fault, because yaml-cpp hasn't put out an updated formal release since 10 months before fixing this: https://github.com/jbeder/yaml-cpp/issues/1026#issuecomment-1122305522