Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-18 Thread Earnie Boyd
On Sun, Jun 17, 2012 at 4:35 AM, Kai Tietz wrote: > Hi everybody, > > here come my 5-cent on that.  First libmingw32.a and libmingwex.a are > two pretty different things. > I'll throw in 2 more cents worth. The mingwex was started by mingw.org and meant to contain code maintained by us that exten

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-17 Thread JonY
On 6/18/2012 02:46, Derek Buitenhuis wrote: > >> That we change on gcc-side the link-time order for our private >> venture libraries for allowing to build some of them by VC, for which >> they aren't even designed, you can't believe really. >> So we are willing to provide a special library versi

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-17 Thread Derek Buitenhuis
On 17/06/2012 4:35 AM, Kai Tietz wrote: > Hi everybody, > > here come my 5-cent on that. First libmingw32.a and libmingwex.a are > two pretty different things. I agree. This is also why I think libmingwex should NOT have a dependency on libmingw32. > First, main-difference is the place in lin

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-17 Thread Kai Tietz
Hi everybody, here come my 5-cent on that. First libmingw32.a and libmingwex.a are two pretty different things. First, main-difference is the place in link-order. Second is their purpose. The libmingw32.a contains startup-related objects only and it would be a major flaw to put into it any C-r

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-16 Thread Derek Buitenhuis
On 17/06/2012 2:17 AM, JonY wrote: > [...] Thanks for the info. Hopefully others can comment and weigh in on this discussion. In the meantime... sleep... - Derek signature.asc Description: OpenPGP digital signature

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-16 Thread JonY
On 6/17/2012 13:27, Derek Buitenhuis wrote: > On 17/06/2012 1:15 AM, JonY wrote: >> Please read the comments in the def file, I don't have to hold your hands. > > I guess you didn't quite parse my sentence, so let my quote myself: > >> Can you elaborate on which MinGW extensions would have to rei

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-16 Thread Derek Buitenhuis
On 17/06/2012 1:15 AM, JonY wrote: > Please read the comments in the def file, I don't have to hold your hands. I guess you didn't quite parse my sentence, so let my quote myself: > Can you elaborate on which MinGW extensions would have to reimplement parts > of msvcrt? They word here is 'would'

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-16 Thread JonY
On 6/17/2012 12:35, Derek Buitenhuis wrote: > Can you elaborate on which MinGW extensions would have to reimplement > parts > of msvcrt? See the lib{32,64}/msvcrt.def files in SVN for mingw-w64-crt, particularly the functions marked as DATA. >>> >>> Can you be a little l

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-16 Thread Derek Buitenhuis
> As I have said, if we went with your current patch, changes will need to > go into separate libraries so it does not affect GCC. For God's sake man, -stop focusing on the current patch set-. Pretend it doesn't exist, if it helps. > Sure, I'm saying that mixing compiler code objects will cause u

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-16 Thread JonY
On 6/17/2012 11:41, Derek Buitenhuis wrote: > On 16/06/2012 11:25 PM, JonY wrote: >> On 6/17/2012 10:10, Derek Buitenhuis wrote: >>> On 16/06/2012 9:47 PM, JonY wrote: On 6/17/2012 09:17, Derek Buitenhuis wrote: > So, lately there's been some discussion relating to MSVC support in > l

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-16 Thread Derek Buitenhuis
On 16/06/2012 11:25 PM, JonY wrote: > On 6/17/2012 10:10, Derek Buitenhuis wrote: >> On 16/06/2012 9:47 PM, JonY wrote: >>> On 6/17/2012 09:17, Derek Buitenhuis wrote: So, lately there's been some discussion relating to MSVC support in libmingwex. Yes, I've been busy lately. An

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-16 Thread JonY
On 6/17/2012 10:10, Derek Buitenhuis wrote: > On 16/06/2012 9:47 PM, JonY wrote: >> On 6/17/2012 09:17, Derek Buitenhuis wrote: >>> So, lately there's been some discussion relating to MSVC support in >>> libmingwex. >>> >>> Yes, I've been busy lately. And frankly, I stopped caring too, but people

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-16 Thread Derek Buitenhuis
On 16/06/2012 9:47 PM, JonY wrote: > On 6/17/2012 09:17, Derek Buitenhuis wrote: >> So, lately there's been some discussion relating to MSVC support in >> libmingwex. >> >> Yes, I've been busy lately. And frankly, I stopped caring too, but people >> complained, so here's an email to the mailing li

Re: [Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-16 Thread JonY
On 6/17/2012 09:17, Derek Buitenhuis wrote: > So, lately there's been some discussion relating to MSVC support in > libmingwex. > > Yes, I've been busy lately. And frankly, I stopped caring too, but people > complained, so here's an email to the mailing list as people have requested. > The goal o

[Mingw-w64-public] MSVC Compatability in libmingwex - A Discussion on Design

2012-06-16 Thread Derek Buitenhuis
So, lately there's been some discussion relating to MSVC support in libmingwex. Yes, I've been busy lately. And frankly, I stopped caring too, but people complained, so here's an email to the mailing list as people have requested. The goal of this email to to iron out design issues before actually