On Thu, 2019-03-14 at 13:30 -0400, frodak17 wrote:
> On Thu, Mar 14, 2019 at 12:53 PM frodak17 wrote:
> > On Thu, Mar 14, 2019 at 1:13 AM Paul Smith
> > wrote:
> > > I have a situation where I've created a custom command to
> > > generate .cpp
> > >
> > > files to be compiled (in my case running
On Thu, Mar 14, 2019 at 12:53 PM frodak17 wrote:
>
>
> On Thu, Mar 14, 2019 at 1:13 AM Paul Smith wrote:
>
>> I have a situation where I've created a custom command to generate .cpp
>> files to be compiled (in my case running bison/flex).
>>
>> I'm using CMake 3.13.4
>>
>> set(MyParserOutput
>
On Thu, Mar 14, 2019 at 1:13 AM Paul Smith wrote:
> I have a situation where I've created a custom command to generate .cpp
> files to be compiled (in my case running bison/flex).
>
> I'm using CMake 3.13.4
>
> set(MyParserOutput
> ${OUT_DIR}/MyParser.tab.cpp
> ${OUT_DIR}/MyParser.t
I have a situation where I've created a custom command to generate .cpp
files to be compiled (in my case running bison/flex).
I'm using CMake 3.13.4
However, I have to compile this code in two different ways for two
different targets. I am seeing the Visual Studio generator re-running
bison/flex
