Hi Ian,
OK I got it now. I have to separately compile the imported packages as .o
if I use gccgo and then link them to the final executable. Resolving the
dependency of the packages may be troublesome so go tool is good if we have
choice.
Thanks.
--
You received this message because you
On Fri, Jul 7, 2017 at 1:10 AM, wrote:
>
> So, is it strange that gccgo can't compile if the main.go imports some
> non-standard library package?
> Is it meaning with gccgo, we have to write a single go file to contain
> everything, or just import only the standard library
Hi Ian,
Thanks for your reply. Although I am a seasoned c programmer I am a go
beginner.
So, is it strange that gccgo can't compile if the main.go imports some
non-standard library package?
Is it meaning with gccgo, we have to write a single go file to contain
everything, or just import
On Thu, Jul 6, 2017 at 2:10 AM, ajee wrote:
>
> Before I post here I did a lot of search by Google, there are several (but
> not many) similar topics but all of them don't have valid answer or apply to
> me.
>
> I have a simple code tree like this:
>
> ├── main.go
> └──
Hi,
Before I post here I did a lot of search by Google, there are several (but
not many) similar topics but all of them don't have valid answer or apply
to me.
I have a simple code tree like this:
├── main.go
└── transform
├── css.go
├── html.go
├── html_test.go
└── http.go