Thank you very much!
--
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 an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit
to know. I recall seeing
some .syso files in the compiler source tree but could not find a makefile
or sources for them.
On Tuesday, October 30, 2018 at 6:33:21 AM UTC+2, Ian Lance Taylor wrote:
>
> On Sun, Oct 28, 2018 at 1:20 PM, jclc via golang-nuts
> > wrote:
> >
> >
There is an initiative to remove the requirement of having a C compiler for
certain CGO packages and this seems like a somewhat common thing to do,
even the Go race condition detector ships as a pre-built C blob in the Go
source tree. Yet I can't find any documentation on how to actually do
Currently I don't use them, but couldn't binary packages be used to
distribute CGO-dependent packages for developers who might not have a C
cross-compiler? I think the feature would be more commonly used if it
wasn't so impractical. Rather than abandoning the feature I'd like to see
it
Wow, so it really was that easy... Thanks a lot.
On Tuesday, October 9, 2018 at 11:04:24 PM UTC+3, Ian Lance Taylor wrote:
>
> On Tue, Oct 9, 2018 at 11:49 AM, jclc via golang-nuts
> > wrote:
> > I'm trying to make a graphical crash window on my program for my users
> w
I'm trying to make a graphical crash window on my program for my users who
will not have terminal access. I can panic with my own custom crash dumps
that include details that I can then handle after recover(), but I can't
get anything useful from a standard library panic. If the user tells me
So, I've been thinking about the GUI situation with Go and I'm seeing a lot
of interesting projects coming up lately. However, none of these really
satisfy my needs. All of these projects are suitable for larger graphical
applications, but what I want is a dead simple, dependency- and
