just a heads up regarding Ubuntu Bash Shell on Windows10: if you open the
Ubuntu Bash Shell and type the command: "*lsb_release -a" *you might
discover it is running Ubuntu 14.04 you might want to run an upgrade to
Ubuntu 16.04 which is now available. See the following for installation
details
On Thu, 12 Oct 2017 22:08:44 -0700 (PDT), you wrote:
>
>On Thursday, October 12, 2017 at 8:31:52 PM UTC-4, Gerald wrote:
>>
>> The MSI is a Windows application, whereas apt-get would install the
>> Linux binary of go.
>>
>> WSL has you actually running Linux binaries on Windows unless you
>> sp
follow the procedure of installing go in linux.
set the following in .bashrc of your home directory at the end:
export PATH=$PATH:/usr/local/go/bin
export PATH=$PATH:$GOPATH/bin
worked for me just fine!
On Wednesday, October 11, 2017 at 8:04:28 AM UTC+3, Pat Farrell wrote:
>
> I've installed the
On Thursday, October 12, 2017 at 8:31:52 PM UTC-4, Gerald wrote:
>
> The MSI is a Windows application, whereas apt-get would install the
> Linux binary of go.
>
> WSL has you actually running Linux binaries on Windows unless you
> specifically go and choose a Windows executable.
>
The MSI fil
On Thu, 12 Oct 2017 00:03:41 -0400, you wrote:
>Other than the file names, I'm not convinced that there is any actual
>difference
>between the go.exe you get with the MSI and the go binary that apt-get
>installs
There is a difference.
The MSI is a Windows application, whereas apt-get would insta
WSL works perfectly well for Go development. It’s my primary dev environment
Just treat it like Linux and you’ll be fine.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send
On Wed, Oct 11, 2017 at 11:32 PM, wrote:
> Did you install the Windows or Linux go binary distribution?
>
I went to the distribution site and installed the .msi file
like any windows installation
I've been running bash since about 1987, so I'm partial to it.
Other than the file names, I'm not
Did you install the Windows or Linux go binary distribution?
Sounds like you might have installed the Window distribution and running it
in bash?
I installed the Linux go distribution and it worked just fine. I think I
created a symlink from /usr/local/go/bin/go to /usr/local/bin/go, or you
ca
On Thursday, 12 October 2017 11:23:08 UTC+11, Pat Farrell wrote:
> ... But there was nothing that told me why.
Are you asking me why all your Go code should live inside of single
directory? Hopefully others will reply. But I think it is because Go does
not use any config files to build programs.
I found how to force 'go build' to work under the bash shell on Winderz
you have to add a symlink in the program directory containing go.exe
such as
ln -s go.exe go
On Wednesday, October 11, 2017 at 7:59:04 PM UTC-4, brainman wrote:
>
> On Thursday, 12 October 2017 09:28:42 UTC+11, Pat Farre
On Thursday, 12 October 2017 09:28:42 UTC+11, Pat Farrell wrote:
> Yes, I didn't understand what a "workspace" is. Still don't know what
that buzzword means.
I suggested you read https://golang.org/doc/code.html - it should answer
your question. But if you prefer me explaining it (and I am not
On Wednesday, October 11, 2017 at 6:08:26 PM UTC-4, brainman wrote:
>
> > On Thursday, 12 October 2017 02:34:49 UTC+11, Pat Farrell wrote:
> > https://golang.org/doc/install
>
> This one says "... Next, make the directory src/hello inside your
> workspace ...". And, I take it, you skipped that st
> On Thursday, 12 October 2017 02:34:49 UTC+11, Pat Farrell wrote:
>
> https://golang.org/doc/install
This one says "... Next, make the directory src/hello inside your workspace
...". And, I take it, you skipped that step.
> ... Microsoft has decided to provide a real bash shell with real Ubunt
WSL is a (nice) hack with rough edges: you can invoke Windows applications
(go.exe) from that bash, or install the Linux go under WSL, and have "go" as
under Linux.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group
On Wednesday, October 11, 2017 at 4:12:45 AM UTC-4, brainman wrote:
>
> > On Wednesday, 11 October 2017 16:04:28 UTC+11, Pat Farrell wrote:
> > 1) is the standard documentation wrong/out of date?
>
> What documentation are you referring to? Did you read
> https://golang.org/doc/code.html ?
>
htt
On Wed, 11 Oct 2017 01:12:45 -0700 (PDT)
brainman wrote:
> What bash shell are you talking about? Windows does not come
> with bash shell.
Ooops, now it comes:
https://msdn.microsoft.com/en-us/commandline/wsl/about.
> If you have Linux install, then you should install Linux version of
> Go, no
> On Wednesday, 11 October 2017 16:04:28 UTC+11, Pat Farrell wrote:
> 1) is the standard documentation wrong/out of date?
What documentation are you referring to? Did you
read https://golang.org/doc/code.html ?
> 2) how do I get the go build process to create a hello.exe rather than
go.exe?
I
A Go project is organized as a file system. The directory your go source
files reside in indicate the name of the executable created with go build.
On Tuesday, October 10, 2017 at 10:04:28 PM UTC-7, Pat Farrell wrote:
>
> I've installed the go 1.9 binary distribution on my windows 10 laptop.
> I
18 matches
Mail list logo
