I have tried to get MinGW to work. I think i got the 32bit version to work. The 64bit version is a jungle. I have spent hours, and got nowhere, even the "all in one" installation things isn't useful. May be doing it totally wrong, i would hope so at least.
--------------------- Originally posted by CrotchMonster but without the asterisks i drove it to the and next to the gar. i had outside the two kids with the e30 m3s its like ahtast f*ck awq3wweom womnnee with red intiro and bacl and diman shwar sand wihite next thing i k
Getting the MinGW-w64 to work. But according to that guide, which i have actually followed before (though didn't get which msys, i mean the one stated is very old, and the other's are just sources). I should be able to compile to 64bit with the 32bit version? Then what is MinGW-w64?
--------------------- Keith '73 2002 2002 Steel Gray Mcoupe
MinGW-w64 is a fork of the original MinGW.org project. Initially, MinGW-w64 was forked with the goal of adding 64-Bit support (which MinGW didn't have at that time), but that doesn't mean that 64-Bit support is its only purpose. Neither do you need a 64-Bit compiler to create 64-Bit binaries. Actually, nowadays most people seem to prefer MinGW-w64 over MinGW.org. For example, official Qt binaries for Windows (32-Bit and 64-Bit) are made with MinGW-w64... See also:
Ah i see. Well i couldn't get MinGW-w64 to work. It had this nice installer. It installed all fine, but i couldn't use it, i didn't know if i was supposed to manually add Msys or something later. And running the Bash just return an Echo.
Again: All you need is the MSYS shell (e.g. from ) and a suitable build of MinGW-w64, e.g. the Komisar's GCC 4.8.2 package from . You don't need any installer. Just unzip the MSYS package to, for example, "C:\Sandbox\MSYS", and the MinGW package to, for example, "C:\Sandbox\MinGW". Then open the MSYS shell, mount your MinGW path to /mingw and run the commands that I posted . Code:
It asks for it, else i can't start x264. And yes it does say Posix. Not that good at this stuff, so pretty confused. Mind i am doing an 64bit build, if that has anything to do with it (host target configure as the guide you linked stated).
--------------------- '94 ///177-technic "don't sweat the TECHNIC" "Driving is a passion. Make love to a corner."
If your x264 binary asks for a "libwinpthread-1.dll" at runtime, then your obviously have built x264 with libwinpthreads - the shared (DLL) variant. You probably don't want libwinpthreads, because it has problems with x264. If you want POSIX threading, use the pthread-w32 library instead. As said before, if you compile with Komisar's GCC 4.8.2 package, it already includes pthread-w32. And it includes a static variant, so no DLL needed.
Search
Users
Entrance
RE: Compile for MinGW32 with Cygwin
