On Sun, Jun 17, 2012 at 1:07 PM, Xiaofan Chen wrote:
> Usually I use MinGW.org (32bit) and TDM64 for libusb/libusbx/libusbk
> related testing. So today I gave the personal build of rubenvb a try
> and tried to build libusbx 1.0.12 release but somehow it failed.
> TDM64 is okay. Tested under Window
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
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
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'
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
Usually I use MinGW.org (32bit) and TDM64 for libusb/libusbx/libusbk
related testing. So today I gave the personal build of rubenvb a try
and tried to build libusbx 1.0.12 release but somehow it failed.
TDM64 is okay. Tested under Windows XP 64bit.
The reason might be the bundled dlltool.exe insid
> 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
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
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
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
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
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
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
13 matches
Mail list logo
