>
> Great work. Please go ahead and merge new tool to master.

Kai I have pushed, hopefully I can get some feedback on building and
running for the community :)
Thanks again guys.

Exciting times :D

On Wed, Nov 4, 2015 at 2:17 PM, Martell Malone <[email protected]>
wrote:

> The difference I see is that binutils is already a build dependency and
>> is always the first step. It's already there so depending on it doesn't
>> change anything. However this isn't the case for genlib.
>> Is it possible to build genlib with only the header set installed? That
>> would actually perfectly avoid my concerns.
>> Also does it have any kind of dependency on a given version of
>> mingw-w64?
>
>
> genlib is multi-target an in general only needs to be built for the build
> machine.
> So if you were to use it you would build it with the same compiler you are
> building your toolchain with.
> It does not need to worry about the target because it supports all of them
> with every build.
>
> The only scenario where bootstrapping this would be necessary would be for
> a canadian cross compiler ?
> It is not tied to a specific version of mingw-w64 so this should be
> possible.
> I have been dealing with clang and not gcc though so I haven't
> specifically been to worried about this setup
>
> On Wed, Nov 4, 2015 at 7:44 AM, Adrien Nader <[email protected]> wrote:
>
>> 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 dlltool.
>> >  ./configure --use-genlib
>> > It should not affect the current building in anyway and can be enabled
>> by
>> > choice.
>> >
>> > Does my explanation this make sense?
>>
>> That's how I had understood it.
>>
>> The difference I see is that binutils is already a build dependency and
>> is always the first step. It's already there so depending on it doesn't
>> change anything. However this isn't the case for genlib.
>>
>> Is it possible to build genlib with only the header set installed? That
>> would actually perfectly avoid my concerns.
>> Also does it have any kind of dependency on a given version of
>> mingw-w64?
>>
>> --
>> Adrien Nader
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Mingw-w64-public mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>>
>
>
------------------------------------------------------------------------------
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to