MINGW-packages | Package scripts for MinGW-w64 targets to build under MSYS2
kandi X-RAY | MINGW-packages Summary
kandi X-RAY | MINGW-packages Summary
Package scripts for MinGW-w64 targets to build under MSYS2.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of MINGW-packages
MINGW-packages Key Features
MINGW-packages Examples and Code Snippets
Community Discussions
Trending Discussions on MINGW-packages
QUESTION
Consider this minimal example:
...ANSWER
Answered 2019-Dec-12 at 11:18The issue can be fixed by patching /mingw64/include/c++/9.2.0/bits/fs_path.h
.
At lines 666-692, there is a definition of class filesystem_error
. It has to be moved up to line 614, to be right above the definition of u8path()
.
I think it's a libstdc++ bug. I've reported it here.
class filesystem_error
is used several times in bits/fs_path.h
, and every use of it is below the definition, except for the problematic line 636.
That line is wrapped in #ifdef _GLIBCXX_FILESYSTEM_IS_WINDOWS
, so I guess the Clang developers don't run libstdc++ compatibility tests on Windows.
UPD: This is fixed in GCC 9.3.
QUESTION
I'm having a hard time debugging this issue: https://github.com/cnjinhao/nana/issues/445
I have previously asked about LTO vs static object initialization and edited the library's code to implement Meyer's singletons so that the correct order of initialization happens. Hello worlds still crash, although library's functions have mostly dissappeared from stack traces:
...ANSWER
Answered 2019-Aug-03 at 16:13The cause of the crash was that the nana library had -static-libgcc -static-libstdc++
in its CMake files as public dependency. The executable and all other libraries had them linked dynamically. Suprisingly, there were no symbol clashes but the standard library code in the executable was corrupted.
Solved by removing these flags from nana's CMake files.
QUESTION
I am trying to build a static Cairo library on Windows under MSYS2/MinGW-w64 & am having trouble linking to libpixman-1.a
static library. The linker errors are as follows:
ANSWER
Answered 2019-Jul-24 at 06:19Building pixman library with MMX, SSE2, & SSSE3 optimizations disabled fixes the problem & allows me to build static only cairo library:
QUESTION
I am having troubles when trying to upgrade my Portable Msys2 under Win 10 with pacman -Syuu
, as detailed below.
I did this before with no problem.
What could the problem and solution be?
...ANSWER
Answered 2019-Apr-13 at 15:04You can disable the timeout of pacman with the parameter --disable-download-timeout
. Then you should be able to download
http://repo.msys2.org/mingw/x86_64/mingw-w64-x86_64-qt5-5.12.1-5-any.pkg.tar.xz
It's described on the man-page for pacman.
Also --gpgdir
to Specify a directory of files used by GnuPG to verify package signatures might be useful.
Additional you can consider using the parameter --noconfirm
to bypass any and all “Are you sure?” messages.
About the certificates I'm not sure, perhaps the local paths are not configured correctly. Nevertheless you've two domains, that still serve by http
.
In browser the download works btw. it just has finished, the screenshot is still showing the download in progress:
QUESTION
When I cross-compile Qt 5.8.0 from source myself and use it to build the Qt "Dynamic Layouts" example from Qt Widgets for Microsoft Windows, it looks old-fashioned, as if it were running on Windows 2000, as shown in the left window below. However, if I compile the exact same program using the pre-built mingw-w64-x86_64-qt5-static package (version 5.8.0-1) from MSYS2, it looks like a nice modern Windows application, as shown in the right window below. How can I fix my version of Qt so that GUIs built with it will look nice? Is there a configuration option I am missing?
One thing to look into is the QWindowsVistaStyle
class. I noticed that when I compiled my program in MSYS2, I had to add -luxtheme
because that class referred to some functions from there, like GetThemeColor
. Those functions are only available in Windows Vista and later. When I cross-compiled using my own Qt on Linux, I didn't need that library, so perhaps that class was somehow disabled in my build.
I built the cross-compiled Qt and the old-looking Dynamic Layouts example using commit f51d834 of my nixcrpkgs repository. If you look at the code in that commit, it will show you exactly what commands were run to build the mingw-w64 cross-compiler, and build Qt, and build the Qt examples, including Dynamic Layouts. You can build it yourself if you install Nix, download nixcrkpkgs, and then run nix-build -A pkgs.i686-w64-mingw32.qt.base-examples
in the nixcrpkgs directory. You can see my build recipe for the Qt package in that commit.
I ran this script in a MINGW64 shell in MSYS2 to build the example and got good results. It relies on the mingw-w64-x86_64-qt5-static package from MSYS2. You can see the build recipe for that package.
...ANSWER
Answered 2019-Mar-21 at 16:24Qt-based GUIs will automatically select the default theme depending on your OS. If you want to override it, you are looking for QApplication's setStyle
method, which lets you define the style used for your application, regardless of the OS it runs on.
QUESTION
I have been trying to create a standalone GUI app for Mac OSX based on a python 3 script (version 3.7). The .py script works perfectly when launched directly from the terminal. However this is for my father that needs assistance when downloading a .jpg, so he needs a simple double click app.
Unfortunately all the tools I try to use seem to have known bugs with the modules I'm using (py2App = openpyxl / pyinstaller = tkinter). The one I'm trying to use now is cx_Freeze.
However there is again a know bug with Python 3.7 described
I've been trying to fix this on my mac OSX machine but cannot find the file that is being referred to (on this GIT-hub, the code linked by the first post hereabove).
I would like to fix this bug, but I would also like to understand why this is happening to increase my knowledge of both python and creating standalone apps.
Unfortunately, I'm not good enough to understand how to fix it by reading the GIT-hub posts (as they are directed to Windows systems and I do not find the files), nor why this bug occurs.
Thanks in advance for your help.
for info, here is a copy of the terminal output when launching the created executable:
...ANSWER
Answered 2019-Feb-25 at 08:05To find the path to the freezer.py
file you need to modify, run the following in a Python console:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install MINGW-packages
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page