Recent versions of Bison (I'm using 3.8.2) generate header guards which seem to be based on the absolute path of the generated header file. Since this Bison-generated code will be included in the release tarballs of our project, it is not desirable to reveal absolute paths from the machine where Bison was originally run. Is there a way to control the header guards that are generated?
0 Answers
Related