Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

update README to point to newer/easier mingw32 on osx #29

Closed
tmm1 opened this Issue · 4 comments

2 participants

@tmm1
diff --git a/README.rdoc b/README.rdoc
index 67d37f6..5e4922e 100644
--- a/README.rdoc
+++ b/README.rdoc
@@ -201,9 +201,9 @@ Installation depends will depend on your operating system/distribution. On
 Ubuntu and Debian machines, a simple <tt>apt-get install mingw32</tt> will be
 enough.

-On OSX, mingw32 is available via MacPorts: <tt>port install i386-mingw32-gcc</tt>
-(ensure you update your ports tree before hand as <tt>mingw32</tt> has been
-been broken).
+On OSX, download "MinGW 4.3.0" from http://crossgcc.rts-software.org/doku.php.
+After running the installer, make sure you add the appropriate directory to your
+path: <tt>export PATH=/usr/local/i386-mingw32-4.3.0/bin:$PATH</tt>

 === I have my tool-chain, now what?
@luislavena
Owner

Hello,

Thank you for the patch, however I've no experience with crossgcc packages or what feature is missing from standard mingw-w64 packages:

http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Automated%20Builds/

I would rather recommend these builds that I've tested than a newer package that install (mingw-w64 ones just extracts) and I have previous experience working with.

@tmm1

Any chance of updating the README? It still points to macports instructions which are really old.

@luislavena
Owner

@tmm1

Did you see my comment? I would rather prefer not refer to crossgcc at all since I've tested it.

@tmm1

Right, but can we update to point to the mingw-w64 darwin builds instead?

@luislavena luislavena was assigned
@luislavena luislavena closed this issue from a commit
@luislavena luislavena Better instructions for OSX. Closes GH-29
Recommend usage of mingw-w64 automated packages instead of old MacPorts ones.
c1a4b70
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.