On Tue, Dec 4, 2018 at 6:22 AM jclc via golang-nuts <golang-nuts@googlegroups.com> wrote: > > I'm very sorry for replying to this old thread, I forgot to post a reply > earlier. > > Unfortunately your reply doesn't really explain much that I didn't already > know. Simply put, I have two questions. > > Firstly, can precompiled .syso files be used to obviate the need for a > C-compiler entirely for the package user, or will you still need a C-compiler > and/or linker if a Go package has .syso files?
Yes, in general you will need a C compiler if the Go package has .syso files. The compiler will be run to invoke the C linker. > Secondly, is there a concrete example of a project where some source files > are compiled into a .syso file? If someone could just point me to a makefile, > that would probably show me all I need to know. I recall seeing some .syso > files in the compiler source tree but could not find a makefile or sources > for them. If it helps, the .syso files in the standard library are built by https://github.com/llvm-mirror/compiler-rt/blob/master/lib/tsan/go/buildgo.sh . Ian -- 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 https://groups.google.com/d/optout.
