On 17 December 2010 14:45, Earnie <ear...@users.sourceforge.net> wrote: > Dmitrijs Ledkovs wrote: >> >> Fair enough. How is it compiled from source (bootstrap steps if such >> are required)? What compiler do you use to compile MSYS from source? > > We handle that manually. Only MSYS developers will care and it is > documented on www.mingw.org. >
I will try this when I have time =) should be fun. >> Does it make sense to have msys-compatible precompiled Gtk, Qt etc >> available from Debian-Msys port? > > No. > ok. >> Can I use compiled for mingw.org libraries in MSYS environment? > > Yes, it is the purpose of MSYS. > ok. >> Can I use compiled for mingw-w64 libraries in MSYS environment? > > Yes, I believe the mingw64 users are using MSYS now. > ok. >> Can I use Visual Studio compiled libraries in MSYS environment? > > Yes. > > MSYS doesn't provide a compiler for general consumption that uses the > MSYS runtime. Therefore there is no need for a triplet that is publicly > defined. It does provide a compiler for those who wish to help with > MSYS development and the triplet remains privately defined in that case. > ok. >> >> The answers to above questions will tell us whether dpkg should have > msys defined as debian-arch/os. >> > > There is no reason for it. > great. >> >> I have read the website. My first understanding that it is >> user-space around Mingw.org runtime which runs on Windows platforms >> to provide user tools to e.g. have a shell capable of running >> autoconf and etc. Thus I thought that we can provide msys as a suite >> of packages compiled as part of Debian-Mingw port. That way you could >> install Debian-Mingw port in a chroot and instead of using >> cross-compiler use e.g. linux + wine + msys = to get msys shell which >> is equivalent to msys shell on Windows. >> >> Hope this makes sense. As you can see I'm not entirely sure what >> MSYS is and what MSYS isn't and where that border lies on the >> mingw-cygwin-w64 spectrum. >> > > The goal of MSYS when I created it was simple, "Provide a tool that > could be used to execute configure and make for the MinGW user." > Executing uname in MSYS from my Windows XP 32bit system yields a string > that will identify the environment as MINGW32 but that string is > modifiable by the end user with an environment variable named MSYSTEM. > Currently MSYSTEM is set to MINGW32 but could be set to MINGW64 or MINGW > or CYGWIN or WINDOWS or SOMEOTHERFOOSTRING and the MSYS uname will > report that system. > ok. > Earnie > I have a better understanding now and I will provide updated patch with resulting debian/gnu triplets for new review. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
