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
However, that is not necessarily where the file is.
It would be good if it was also consulting the CLASSPATH (arguably, it even should look there first before going into guess-mode rummaging through directories).
While at it, looking for exactly version 4.12.0 is very specific, can we change that to 4.12.* to be future compatible in case there are new patchlevels coming out ?
The text was updated successfully, but these errors were encountered:
I took a look at where debian and homebrew put the asset, I didn't see anything about setting classpath or configuring the users's profile to have that var. Is it the standard for folks to maintain a classpath var like they might a PATH? Maybe antlr already has something to find where the jar is? But yeah easy to implement, just unfamiliar with Java ecosystem.
In NixOS, the jar file ends up in the CLASSPATH (and to show that it is not predictable: in my case, the setting is CLASSPATH=/nix/store/6cnfr2cy5ninj4xnhnqk8x4vkrz8bydn-antlr-4.12.0/share/java/antlr-4.12.0-complete.jar)
In the Java-world, CLASSPATH common - it is what PATH is for binaries.
The
cmake/modules/FindANTLR.cmake
looks in a few hard-coded well-known locations for a potential antlr*complete.jar.Surelog/cmake/modules/FindANTLR.cmake
Lines 13 to 21 in edb409a
However, that is not necessarily where the file is.
It would be good if it was also consulting the
CLASSPATH
(arguably, it even should look there first before going into guess-mode rummaging through directories).While at it, looking for exactly version 4.12.0 is very specific, can we change that to 4.12.* to be future compatible in case there are new patchlevels coming out ?
The text was updated successfully, but these errors were encountered: