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 was browsing the official packages and noticed an issue. The wiki says to file an issue on the specific package, but issues seems to be disabled on (all?) of the official packages. I presume that's coming from GitHub's default for forked repos, but probably not what you want.
FWIW, the original issue that caught my attention is that google-flatbuffers should have multiple targets: at least one binary for the flatc compiler and one library--just like the bazel BUILD file. Compiling the main into a library isn't going to end well :)
Thanks,
Chris
The text was updated successfully, but these errors were encountered:
Hello again, awesome LoopPerfect folks,
I was browsing the official packages and noticed an issue. The wiki says to file an issue on the specific package, but issues seems to be disabled on (all?) of the official packages. I presume that's coming from GitHub's default for forked repos, but probably not what you want.
FWIW, the original issue that caught my attention is that google-flatbuffers should have multiple targets: at least one binary for the flatc compiler and one library--just like the bazel BUILD file. Compiling the main into a library isn't going to end well :)
Thanks,
Chris
The text was updated successfully, but these errors were encountered: