Re: [cmake-developers] BISON_TARGET doesn't use CMAKE_CURRENT_BINARY_DIR as WORKING_DIRECTORY

2019-01-08 Thread Brad King via cmake-developers
On 1/8/19 6:44 AM, Brad King wrote: > On 12/25/18 1:17 AM, Mingjie Xing wrote: >> The BISON_TARGET will run bison command in CMAKE_CURRENT_SOURCE_DIR. >> >> So I just wonder whither it is better for BISON_TARGET to use >> CMAKE_CURRENT_BINARY_DIR as WORKING_DIRECTORY. > > Unfortunately this went

Re: [cmake-developers] BISON_TARGET doesn't use CMAKE_CURRENT_BINARY_DIR as WORKING_DIRECTORY

2019-01-08 Thread Brad King via cmake-developers
On 12/25/18 1:17 AM, Mingjie Xing wrote: > The BISON_TARGET will run bison command in CMAKE_CURRENT_SOURCE_DIR. > > So I just wonder whither it is better for BISON_TARGET to use > CMAKE_CURRENT_BINARY_DIR as WORKING_DIRECTORY. Unfortunately this went unnoticed for years after the module was

[cmake-developers] BISON_TARGET doesn't use CMAKE_CURRENT_BINARY_DIR as WORKING_DIRECTORY

2018-12-24 Thread Mingjie Xing
Hello, I run into a problem when use FindBISON module in CMakeLists.txt. The BISON_TARGET will run bison command in CMAKE_CURRENT_SOURCE_DIR. The GNU Bison has problem for ‘—defines=‘ option because it will always generate the header file in the working directory. So, BISON_TARGET(Parser