Luqman and I found out today some interesting bits from the mngw guys on
IRC...

I'm going to continue documenting what I find on the Wiki page
https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust

under a new 64bit Windows building section.

But here is the info so far:

(
I set my MinGW64 path with a statement at the bottom of my
MinGW/msys/1.0/etc/proifle with
# Enable MinGW64 path
export
PATH="/c/mingw-builds/x64-4.8.1-win32-seh-rev1/mingw64/bin:/usr/local:$PATH"
)

>From what we gathered the mingw-w64 toolchain installer [1] works well with
the following easy installer settings:

Install path is C:\mingw-builds

Version: (to be determined what the max version of GCC to be that build
correctly ? at 4.8.1 currently)
Architecture: x64
Threads: win32
Exception: seh
Build revision: (whichever latest for mingw-w64)

This was based on our conversation with jon_y in mingw channel.

[snip]
jon_y: be aware that if you use the posix thread gcc, all your code will
depend on the pthred dll whether you actually use pthreads or not
jon_y: libgcc itself pulls in pthreads
Thad: for our Rust (Windows) users...we'd choose win32 threads
Thad: we instruct them on how to build it within the MinGW/Msys environment
on our wiki
jon_y: sure, the link I gave you will not support C++11 threads
Thad: jon luqman says we don't need them. he would know.
jon_y: ok
Thad: so I think just the win32 thread with SEH for Win64 host is ideal
Thad: thanks so so much
jon_y: try to use the installer
Thad: yeah a simple switch for that... easy
jon_y: rather than pointing users to the link directly
Thad: yeah, agree.... we will... I'll write it up and modify our step by
step for Windows users today. Thanks !
jon_y: c++11 threads is the only reason you'd use the posix thread gcc on
windpws
jon_y: *windows
jon_y: np
Thad: I"ll also make a note about that as well.

[1] - http://sourceforge.net/projects/mingwbuilds  (green button download
installer.exe)




On Thu, Jul 4, 2013 at 7:37 PM, James Miller <[email protected]> wrote:

> On 2013-07-04 10:02:29, Graydon Hoare wrote:
> > On 13-07-03 11:32 PM, Lilly Matsson wrote:
> > >Hello!
> > >
> > >I recently made a post on Reddit
> > >(http://www.reddit.com/r/rust/comments/1hk25r/rust_on_64bit_windows_7/)
> > >asking about 64-bit Windows support, and kibwen urged me to post here to
> > >start some kind of discussion about the current state of 64-bit Windows
> > >support.
> > >
> > >So, what is the deal? What needs to be done to fully get 64-bit support
> > >for Windows? As I understand it, it has to do with LLVM.
> >
> >   - Add a new target and host config in the makefiles.
> >
> >   - Fiddle with the target-specific data layout string in
> >     librustc::back
> >
>
> I'm currently working on stuff related to these two points at the moment,
> for
> the record. Basically moving the current target-handling stuff all to one
> place
> and making it run through a `~Target` trait object. This is based off of
> the
> related code in Clang currently.
>
> The code I currently have will _theoretically_ support every major
> platform,
> with there currently being code for MingW32, Cygwin and Win32 separately.
> From what I can tell, 64-bit MinGW is still considered to be MinGW32, just
> on a
> 64-bit architecture (This is based on the fact that the LLVM target triple
> code
> doesn't have a 'mingw64' entry).
>
> This means that when I'm done, it should be pretty easy to "port" to a new
> platform just by updating some build files and fixing any breakage.
>
> --
> James Miller
> _______________________________________________
> Rust-dev mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/rust-dev
>



-- 
-Thad
Thad on Freebase.com <http://www.freebase.com/view/en/thad_guidry>
Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/>
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev

Reply via email to