windows: declare port complete #107
Closed
Labels
Milestone
Comments
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. |
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. |
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. |
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 |
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 |
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 |
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.
|
go for Windows download page: http://code.google.com/p/go-windows/ |
|
Comment 13 by ibw@isaacwagner.me: Many people are running a linux distro on VirtualBox with much success. |
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. |
You might as well try it using http://www.suacommunity.com/ . I haven't tried it though. |
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 |
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? |
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. |
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. |
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. |
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)? |
|
Owner changed to builder@golang.org. |
issue #1741 will not be resolved for Go 1. I think we can probably close this, but leaving for Alex or Andrew. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
by yukuku:
The text was updated successfully, but these errors were encountered: