You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this is working as intended. If you're using cgo, you want to compile any .c
files with GCC, not 6c. Otherwise you can't write your C code in a separate file. And
extending that to .s files is a very small step.
So I would say that you are after some mechanism that lets you control, in a package
that uses cgo, which compiler/assembler should be used to compile/assemble a specific
.c/.s file. We could abuse build tags to make this work, but otherwise I don't see how
to get anything other than what you have.
Agree.
Brad, you are writing too complex package :)
You can mode .s files to a separate package, but make them implement functions in the
first package, so you don't rename and introduce wrappers.
The text was updated successfully, but these errors were encountered: