Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

windows: declare port complete #107

Closed
gopherbot opened this issue Nov 12, 2009 · 35 comments
Closed

windows: declare port complete #107

gopherbot opened this issue Nov 12, 2009 · 35 comments
Milestone

Comments

@gopherbot
Copy link

@gopherbot gopherbot commented Nov 12, 2009

by yukuku:

What steps will reproduce the problem?
1. Use windows
2. Don't use linux
3. Insist on trying Go in windows

What is the expected output? 
golang.org provides a binary package for Windows users to download.

What do you see instead?
Instructions for linux and darwin users and compilations from source is needed.
@rsc
Copy link
Contributor

@rsc rsc commented Nov 12, 2009

Comment 1:

We understand that Windows support is important to a huge number of people.
Go doesn't run on Windows yet, so there are no binaries we could provide.
We do hope that people in the community will help us get Go running on Windows.
I've retitled this issue "Windows support for Go" so that others who are interested
can follow it to get updates, but I can't predict how long it will take.
Some people have reported success playing with Go on Windows by installing inside 
AndLinux.  That's probably the best workaround for now.

Status changed to LongTerm.

@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 12, 2009

Comment 2 by cool.fire.666:

If you like you can have a Linux shell on my server and try it on there.
If you're interested, email me at cool_fire_666[at]hotmail.com
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 18, 2009

Comment 3 by yukuku:

You can try Go although you are using Windows.
http://gofmt.com/compile.html  lets you write, compile, link, and run Go programs on
the servers.
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 19, 2009

Comment 4 by soemin.mark:

good idea yukuku, cheers!
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 20, 2009

Comment 5 by hectorchu:

My effort to port go to Windows can be seen here:
http://code.google.com/r/hectorchu-go-windows/
Enough support has been implemented to run an empty main() program.
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 20, 2009

Comment 6 by soemin.mark:

cool! going to compile it now, thx
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 20, 2009

Comment 7 by dezelin:

I have also started to port Go to Windows. 
Here's the initial patch set: http://golang.org/cl/156088/
It is far from finished, but you can also compile empty main() program with it.
I think maybe we can join our effort and work with your source repository if you wish 
to merge in this patch set.
I am currently working on lib9 wait() and _wait() implementation but there's a lot of 
work to be done in order to finish the port.
Best regards
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 20, 2009

Comment 8 by dezelin:

I have also started to port Go to Windows. 
Here's the initial patch set: http://golang.org/cl/156088/
It is far from being finished, but you can also compile empty main() program with it.
I think maybe we can join our effort and work with your source repository if you wish 
to merge in this patch set.
I am currently working on lib9 wait() and _wait() implementation but there's a lot of 
work to be done in order to finish the port.
Best regards
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 20, 2009

Comment 9 by dezelin:

I have also started to port Go to Windows. 
Here's the initial patch set: http://golang.org/cl/156088/show
It is far from being finished, but you can also compile empty main() program with it.
I think maybe we can join our effort and work with your source repository if you wish 
to merge in this patch set.
I am currently working on lib9 wait() and _wait() implementation but there's a lot of 
work to be done in order to finish the port.
Best regards
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 22, 2009

Comment 10 by hectorchu:

My port can now compile and run the following program:
package main
import "os"
func main() {
        os.Stdout.WriteString("hello, world\n");
        f, _ := os.Open("test", os.O_CREATE|os.O_WRONLY, 0);
        f.WriteString("hello, world in a file\n");
}
Cool huh? I'm going to start looking at getting the work done so far committed to the
go central repository.
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 23, 2009

Comment 11 by hectorchu:

go for Windows download page:
http://code.google.com/p/go-windows/
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 25, 2009

Comment 12 by floroeske:

übergeil
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 26, 2009

Comment 13 by ibw@isaacwagner.me:

Many people are running a linux distro on VirtualBox with much success.
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 27, 2009

Comment 14 by roger.dewayne:

If you want to learn Go right now and your primary PC is Windows-based, then, yes, 
VirutalBox used to host, say, Xubuntu, makes a fine environment. I run a 4 GB Sony 
laptop and have set up a 768 MB VM to run Xubuntu 9.10. Once you have basic install 
in place, just need to 'sudo apt-get install bison' and 'sudo apt-get install 
mercurial', then proceed with the usual Go install instructions.
Once I've run the VirutalBox guest additions, I run the VM in seemless mode. The 
Linux editor window and shell windows are side-by-side my Windows apps on the Windows 
desktop. I'm using gedit 2.26.1 as my Go source editor for now. Selecting C 
highlighting gives reasonable enough color syntax to Go source code.
It would be nice to start creating Windows-specific programs written in Go, but for 
the purpose of learning Go programming, this approach is entirely viable.
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Dec 15, 2009

Comment 15 by krishnendu007:

Can we Use Cygwin for running go on Windows OS?
@afriza
Copy link

@afriza afriza commented Dec 16, 2009

Comment 16:

You might as well try it using http://www.suacommunity.com/ . I haven't tried it 
though.
@rsc
Copy link
Contributor

@rsc rsc commented Apr 27, 2010

Comment 17:

Windows support is not complete but some packages are now working.
Joe Poirier has been building downloadable binaries for people who
don't want to build from source.
http://code.google.com/p/gomingw/downloads/list
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Jul 24, 2010

Comment 18 by asksuperuser:

AndLinux doesn't work on 64 bits so can not test go with it on Windows 7
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Sep 6, 2010

Comment 19 by jfepstein:

I currently have Go installed via AndLinux on a 32 bit Vista install. It works just
fine. I had to install mercurial and bison using Synaptic, but other than that, it went
smoothly.
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Dec 16, 2010

Comment 20 by Davidrafagomes:

Does Google have any intentions of porting Go to Windows?
If not, I'll never use it :|
@alberts
Copy link
Contributor

@alberts alberts commented Dec 16, 2010

Comment 21:

There's a few things that still need to be fixed, but Go runs on Windows:
http://groups.google.com/group/golang-nuts/browse_thread/thread/0ac3d848b0b5b7cb
Maybe it's time to resolve this issue?
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Dec 17, 2010

Comment 22 by marko.kocic:

I wouldn't resolve it untill the link to Windows instller executable appears in
http://golang.org/doc/install.html page.
There's no much use of Go running on Windows if nobody is aware of it, and main
documentation page doesn't mention it.
@rurban
Copy link

@rurban rurban commented Feb 22, 2011

Comment 23:

I started working on a cygwin port before having seen the existing windows port. 
I only brought the first public release from 2009 to my holidays, now I have to merge
them.
I will now use the existing PE / 386 linker (I named it coff). Don't know if I should
use pthreads as in my first approach (as a nice wrapper) or native windows threads.
The cygwin libc is certainly more attractive than the limited msvcrt.
Other than that http://golang.org/doc/install.html mentions now the windows port so this
ticket should be closed.
I'm a bit busy now, but will come back sooon.
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Feb 22, 2011

Comment 24 by techtonik:

IMO Cygwin is a PITA. It is a whole new platform with its own bugs, so its better to run
Linux apps natively in VM than waste time with Cygwin ports.
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Nov 9, 2011

Comment 25 by thadguidry:

Cygwin uses MinGW as part of it's build.  Ideally, MinGW should be the one targeted for
Windows users building GO, not Cygwin.  I would encourage the GO developers to mention
or recommend Windows users to first install MinGW, run it's shell, and then proceed with
standard install instructions for GO to build. (I had to ask in the IRC channel to get
this easy trip to building/installing GO on Windows).  Further, users can open issues
for that standard MinGW build process when they occur, IMO.
@rsc
Copy link
Contributor

@rsc rsc commented Dec 9, 2011

Comment 26:

Labels changed: added priority-later.

@rsc
Copy link
Contributor

@rsc rsc commented Dec 12, 2011

Comment 27:

Labels changed: added priority-go1.

@kardianos
Copy link
Contributor

@kardianos kardianos commented Dec 14, 2011

Comment 28:

As of weekly.2011-12-06, I am able to both cross compile my programs from linux to
Windows 386 and amd64 executable, as well as compile 386 tooling(8g,6g,8l, 6l, etc)
using mingw on windows.  Go tools once compiled work great on their own.  The http
package and the filepath package works well on windows, at least I haven't come across
any problems.  In other words, Go on Windows works for me.
The only "pain point" is running a Go compiled program as a windows service.  It appears
there isn't a Go callback function that can be called back into from another thread.  
I do not have experience working with cgo on windows and thus can't comment on that
topic.
I look forward to the compiled "go command". Will it be possible to set the header type
when linking (-H windows or -H windowsgui)?
@alexbrainman
Copy link
Member

@alexbrainman alexbrainman commented Dec 15, 2011

Comment 29:

Added https://golang.org/issue/2565
@robpike
Copy link
Contributor

@robpike robpike commented Jan 13, 2012

Comment 30:

Owner changed to builder@golang.org.

@rsc
Copy link
Contributor

@rsc rsc commented Jan 24, 2012

Comment 31:

Status changed to Accepted.

@rsc
Copy link
Contributor

@rsc rsc commented Jan 30, 2012

Comment 32:

Labels changed: added go1-must.

@rsc
Copy link
Contributor

@rsc rsc commented Mar 26, 2012

Comment 34:

issue #1741 will not be resolved for Go 1.  I think we can probably close this, but
leaving for Alex or Andrew.
@adg
Copy link
Contributor

@adg adg commented Mar 26, 2012

Comment 35:

Labels changed: removed go1-must.

@adg
Copy link
Contributor

@adg adg commented Mar 26, 2012

Comment 36:

Yay.

Status changed to Done.

@gopherbot gopherbot added done labels Mar 26, 2012
@rsc rsc added this to the Go1 milestone Apr 10, 2015
@rsc rsc removed the priority-go1 label Apr 10, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
9 participants