On Tue, Nov 03, 2015, Martell Malone wrote:
> Just to clear things up here.
>
> I intend to include the source into the mingw-w64-tools folder so building
> for any host should not be a problem.
>
> As for the option I just would like a configure option in the crt to force
> using it instead of d
Sure, it makes absolutely sense.
Kai
2015-11-03 23:33 GMT+01:00 Martell Malone :
>> I believe it is best outside of the CRT's build process actually.
>> If you require it as part of the CRT's build, you'll have to build it
>> first which will be an issue for native builds. Sure you could build th
>
> I believe it is best outside of the CRT's build process actually.
> If you require it as part of the CRT's build, you'll have to build it
> first which will be an issue for native builds. Sure you could build the
> CRT without and then rebuild it with it but it's not very friendly to
> make the
Hello Martell,
Great work. Please go ahead and merge new tool to master.
I agree to Adrien's comment that this tool should be also buildable by
different hosts. So we shouldn't bind its build on Windows-targets
only.
Thanks,
Kai
2015-11-03 22:33 GMT+01:00 Adrien Nader :
> Hi,
>
> On Thu, Oct 29
Hi Martell,
No there are no objections from my POV.
So please go ahead and commit.
Thanks,
Kai
2015-11-03 19:43 GMT+01:00 Martell Malone :
> ping!
> Kai is there any objections to committing this and getting an option in
> configure?
> It's holding me up simplifying the build process for a clang
On Tue, Nov 03, 2015, David Grayson wrote:
> Both mingw-w64 and libusb-compat define a header called "usb.h". This issue
> was sort of discussed on this mailing list five years ago:
>
> https://sourceforge.net/p/mingw-w64/mailman/mingw-w64-public/thread/aanlkti%3dkikjoqdmb3u8brdxrry0vqqejbjbqgq
Hi,
On Thu, Oct 29, 2015, Martell Malone wrote:
> Hi,
>
> Kai and I discussed this previously but I would like to present to everyone
> a tool to generate import libs based on layout and code structure of gendef.
>
> I would like propose
> https://github.com/martell/genlib
> to be merged as part
ping!
Kai is there any objections to committing this and getting an option in
configure?
It's holding me up simplifying the build process for a clang based
toolchain :(
On Thu, Oct 29, 2015 at 4:47 PM, Martell Malone
wrote:
> You have a functional Clang/libc++ toolchain? That's awesome! Are all
Both mingw-w64 and libusb-compat define a header called "usb.h". This issue
was sort of discussed on this mailing list five years ago:
https://sourceforge.net/p/mingw-w64/mailman/mingw-w64-public/thread/aanlkti%3dkikjoqdmb3u8brdxrry0vqqejbjbqgqz40...@mail.gmail.com/?page=1
Back then, Xiaofan w
Thanks, JonY! --David
On Tue, Nov 3, 2015 at 4:56 AM, JonY wrote:
> On 11/3/2015 06:38, JonY wrote:
>>> If someone could commit this, that would be great! Thanks!
>>>
>>> --David Grayson
>>>
>>
>> Looks good to me, if nobody objects, I will commit it soon.
>>
>
> Done, applied to master.
>
> --
On 11/3/2015 06:38, JonY wrote:
>> If someone could commit this, that would be great! Thanks!
>>
>> --David Grayson
>>
>
> Looks good to me, if nobody objects, I will commit it soon.
>
Done, applied to master.
0xD4EBC740.asc
Description: application/pgp-keys
signature.asc
Description: OpenP
On 11/3/2015 16:07, Ismail Donmez wrote:
> Hi,
>
> Currently mingw-w64 release tarballs are using the posix tar format which is
> the default for gnu tar for some time. But there is a bad consequence,
> neither WinRAR or 7-zip can handle posix tar archives correctly.
>
> So for the upcoming rel
Hi,
Currently mingw-w64 release tarballs are using the posix tar format which is
the default for gnu tar for some time. But there is a bad consequence,
neither WinRAR or 7-zip can handle posix tar archives correctly.
So for the upcoming releases I suggest using tar --format=gnu which will use
13 matches
Mail list logo
