On 8. 4. 2016 10:07, Julien Darthenay wrote: > The sources are provided, but all I can use to build them is either a MSVC's > project file or scripts for linux building. I expected I could use MSYS2 to > build SDL with the scripts for linux but I read in the wiki: "Use |msys2| > shell for running |pacman|, |makepkg|, |makepkg-mingw| and for building > POSIX-dependent software that you don't intend to distribute. Use |mingw| > shells for building native software and other tasks." > Does that mean I cannot use MSYS2 to build a libSDLmain.a who will be usable > without using MSYS2? I must confess I am a bit confused.
Hi. The key part of the statement is "Use |mingw| shells for building native software and other tasks.". We don't even have MSYS SDL, only mingw-w64 SDL. Stuff built with the msys2 toolchain is complicated, but stuff you build with the mingw-w64 toolchain isn't tied by any additional restrictions related to MSYS2. You still have to comply with the respective licenses of the software you intend to distribute (e.g. SDL2 is licensed under MIT, according to `pacman -Si mingw-w64-x86_64-SDL2`, but you also have to take care of its dependencies, if any). I suggest thinking about the option of adding OpenXCom (and/or other software) as a package in MSYS2. People could then just install MSYS2 and then run `pacman -S mingw-w64-x86_64-openxcom` and be done with it. :) -- David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------
_______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
