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

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

Re: [cmake-developers] Idea for Multi-Toolchain Support

On Sat, Dec 22, 2018 at 10:58 AM Torsten Robitzki wrote: > Hi, > > > Am 17.12.2018 um 21:18 schrieb Kyle Edwards via cmake-developers < > cmake-developers@cmake.org>: > > > > Then, executables and libraries could have a toolchain specified: > > > > add_executable(BuildUtility TOOLCHAIN DEFAULT

Re: [cmake-developers] Idea for Multi-Toolchain Support

> Am 24.12.2018 um 17:07 schrieb Kyle Edwards : > > On Sat, 2018-12-22 at 16:57 +0100, Torsten Robitzki wrote: >> What I’m still missing is support to define dependencies between >> different targets (build by different toolchains), so that I can >> describe that I require a tool that is build

Re: [cmake-developers] Idea for Multi-Toolchain Support

On Sat, 2018-12-22 at 16:57 +0100, Torsten Robitzki wrote: > What I’m still missing is support to define dependencies between > different targets (build by different toolchains), so that I can > describe that I require a tool that is build with the HostToolChain, > to generate a file that is