> > I thought that the the stuff in mingw32/64 repos was the compilers, > libraries, etc. for compiling for the respective platform, and the stuff in > msys was for the local build environment (sed, less, patch, make, etc.).
Thats right. When building for 32-bit, use mingw-32 shell and get the mingw32/ tree, -64 for the mingw64/ tree. /usr/bin, /bin, /usr/local/bin etc stays in the tail of the path, everything run out of the msys tree should interact only with text-type processing - i.e., setting up gcc to run; a binary link, while possible, will probably fail. Why would there be 2 separate binaries for 32/64? They are only running > locally. If you are only running locally then you would only need /mingw32 or /mingw64. You may want to build the same thing and test it in the alternate mode, which would require that you set up a separate path and library collection (i.e. /mingw32/bin .vs. /mingw64/bin). The correct one ended up being libopenssl-devel in the msys repo! My guess is that you are running from the MSYS shell and have not executed the mingw-64.bat or mingw-32.bat that will set you up for MINGW compilations that will build a project that runs natively. $ ls /var/cache/pacman/pkg | grep openssl libopenssl-1.0.2.d-1-x86_64.pkg.tar.xz mingw-w64-i686-openssl-1.0.2.c-1-any.pkg.tar.xz mingw-w64-i686-openssl-1.0.2.d-1-any.pkg.tar.xz mingw-w64-x86_64-openssl-1.0.2.c-1-any.pkg.tar.xz mingw-w64-x86_64-openssl-1.0.2.d-1-any.pkg.tar.xz openssl-1.0.2.d-1-x86_64.pkg.tar.xz On Mon, Oct 19, 2015 at 12:49 PM, Baruch Burstein <[email protected]> wrote: > Hi, > > I thought that the the stuff in mingw32/64 repos was the compilers, > libraries, etc. for compiling for the respective platform, and the stuff in > msys was for the local build environment (sed, less, patch, make, etc.). > But I must have misunderstood, because I tried getting the openssl > libraries to link a program with. I installed the openssl package from the > mingw64 repo, and was the openssl binary (the executable). Why would there > be 2 separate binaries for 32/64? They are only running locally. The > correct one ended up being libopenssl-devel in the msys repo! How would I > get different libs for developing 32/64 versions? > > Please explain the purpose of each repo. > > Thanks, > Baruch > > -- > ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Msys2-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/msys2-users > >
------------------------------------------------------------------------------
_______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
