6d0d39b2ca
bind_test.go compares the generated Go files against golden files checked in the repository. The bind package formats some of the generated Go files, so any changes in the go formatter can break the tests. This change makes the test more robust by applying formatting based on the currently used go version. Since a golden file often includes multiple go files generated by the bind, the `gofmt` function splits the golden file using the gobindPreamble marker and then run format.Source for each chunk. In order to ease the golden file splitting, this CL also moves the gobindPreamble to the beginning of each generated file consistently. It turned out bind omits formatting for some go files (generated for reverse binding). That needs to be fixed but it is a much bigger fix. Thus, in this CL, we apply the formatting on the bind's output as well. This CL also updates the gobindPreamble to follow the style guide for generated code. https://golang.org/s/generatedcode Fixes golang/go#34619 Change-Id: Ia2957693154face2848e051ebbb2373e95d79593 Reviewed-on: https://go-review.googlesource.com/c/mobile/+/198322 Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
24 lines
535 B
Plaintext
24 lines
535 B
Plaintext
// Code generated by gobind. DO NOT EDIT.
|
|
|
|
// JNI functions for the Go <=> Java bridge.
|
|
//
|
|
// autogenerated by gobind -lang=java -javapkg=com.example customprefix
|
|
|
|
#include <android/log.h>
|
|
#include <stdint.h>
|
|
#include "seq.h"
|
|
#include "_cgo_export.h"
|
|
#include "customprefix.h"
|
|
|
|
|
|
JNIEXPORT void JNICALL
|
|
Java_com_example_customprefix_Customprefix__1init(JNIEnv *env, jclass _unused) {
|
|
jclass clazz;
|
|
}
|
|
|
|
JNIEXPORT void JNICALL
|
|
Java_com_example_customprefix_Customprefix_f(JNIEnv* env, jclass _clazz) {
|
|
proxycustomprefix__F();
|
|
}
|
|
|