wish: a way to keep cgo related generated files.

[bstarynk]

It would be nice to have some documented way to keep the cgo related generated (C) files.
I am a newbie, and had hard time to understand some strange gcc errors (in my sqlitelog.go file) because I mis-coded a cgo comment.

Perhaps accepting a directory keeping the generated files, e.g.
#cgo keep-generated-directory: /tmp/thedirectory would put all generated files in /tmp/thedirectory/

or maybe a documented flag to gb build such as gb build -keep-temp /tmp/thedirectory

Thanks.

Basile Starynkevitch.

[davecheney]

I think there is a -work flag, or similar which will not delete temporary directories after the build runs.

…

On Thu, 9 Mar 2017, 08:17 Basile Starynkevitch ***@***.***> wrote: It would be nice to have some *documented* way to keep the cgo related generated (C) files. I am a newbie, and had hard time to understand some strange gcc errors because I mis-coded a cgo comment. Perhaps accepting a directory keeping the generated files, e.g. #cgo keep-generated-directory: /tmp/thedirectory would put all generated files in /tmp/thedirectory/ — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#697>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAcA9h8yUHvKVsz12ZjgvJW6TW4K9zCks5rjxr0gaJpZM4MXUiJ> .