[Mingw-w64-public] Why is mingw32 -> mingw64 so large?

2009-07-03 Thread Wesley W. Terpstra
Good evening.

We've been using your mingw64 toolchains as part of the Win64 port of MLton.
As we're approaching a new release, I was looking into bundling a win64
toolchain into our installer. I was surprised to see that the toolchain
zip-file is 190MB! This seems excessively large considering that a similar
toolchain targetting win32 from mingw.org is under 40MB. Is there a good
reason for this?
--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] Why is mingw32 -> mingw64 so large?

2009-07-03 Thread NightStrike
The biggest reason is that zip, as well as windows, doesn't support
symlinks.  There's a legacy requirement that we can't get rid of yet
to have the /mingw dir and the /x86_64-w64-mingw32 dir be identical.
Under linux, we can just symlink the two.  But on windows and with
zip, it's easier to just duplicate them.

On Fri, Jul 3, 2009 at 7:15 PM, Wesley W. Terpstra wrote:
> Good evening.
>
> We've been using your mingw64 toolchains as part of the Win64 port of MLton.
> As we're approaching a new release, I was looking into bundling a win64
> toolchain into our installer. I was surprised to see that the toolchain
> zip-file is 190MB! This seems excessively large considering that a similar
> toolchain targetting win32 from mingw.org is under 40MB. Is there a good
> reason for this?
>
>
> --
>
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] Why is mingw32 -> mingw64 so large?

2009-07-03 Thread NightStrike
On Fri, Jul 3, 2009 at 9:45 PM, Wesley W. Terpstra wrote:
> On Sat, Jul 4, 2009 at 2:05 AM, NightStrike  wrote:
>>
>> There's a legacy requirement that we can't get rid of yet
>> to have the /mingw dir and the /x86_64-w64-mingw32 dir be identical.
>
> What is this requirement? Can I safely erase one directory if certain
> conditions are met?
>

I forget the details of what the dependency is.  You could delete one,
and make a junction point to another.  Kai could probably explain the
dependencies better.

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


Re: [Mingw-w64-public] Why is mingw32 -> mingw64 so large?

2009-07-03 Thread Wesley W. Terpstra
On Sat, Jul 4, 2009 at 2:05 AM, NightStrike  wrote:

> There's a legacy requirement that we can't get rid of yet
> to have the /mingw dir and the /x86_64-w64-mingw32 dir be identical.


What is this requirement? Can I safely erase one directory if certain
conditions are met?
--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public