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
Using CMake commands such as add_custom_command in conjunction with add_custom_target, it should be relatively straightforward to emit the generated grammar file as part of the build, with the token/bnf files as dependencies. This way, they would not need to be checked in and remove a source of possible error with the source files going out of sync with the generated files. More importantly, this change would make grammar changes easier to review.
The text was updated successfully, but these errors were encountered:
Yea, that makes sense, but chances are the JDK isn't too steep a requirement for people wanting to build azslc. I think we get more value in the long run with having leaner code reviews. Note that if the generated files are checked in, it's very difficult to verify that the committer is actually checking in the right data (let alone maliciously modifying it).
Using CMake commands such as
add_custom_command
in conjunction withadd_custom_target
, it should be relatively straightforward to emit the generated grammar file as part of the build, with the token/bnf files as dependencies. This way, they would not need to be checked in and remove a source of possible error with the source files going out of sync with the generated files. More importantly, this change would make grammar changes easier to review.The text was updated successfully, but these errors were encountered: