Re: 回复： 回复： 回复： 回复： 回复： 回复： Ninja compil ation fails after using include path file instead of " -I" option

@bdbadog I added those to the correct tools.

@liruncong I updated the branch so that it will not always try to start the
scons daemon. Please give it some testing.

On Sat, Apr 23, 2022 at 10:59 AM Bill Deegan <[email protected]>
wrote:

> Indeed that sounds reasonable.
> Please add that to the relevant compiler tool's..
>
> On Sat, Apr 23, 2022 at 1:51 PM Mats Wichmann <[email protected]> wrote:
>
>>
>> On 4/22/22 10:54, Daniel Moody wrote:
>> > I think I know why this is happening, Ninja will parse header
>> > dependencies via the "-MMD -MF" or "/showIncludes" options. Ninja must
>> > be told what format to parse from the output of these options. By
>> > default ninja uses MSVC format on windows, but you are using gcc and
>> > clang compilers on windows so msvc format is not correct.
>> >
>> > I have added a new configuration variable to allow you to tell scons
>> > what to configure ninja for, before ninja tool is loaded via
>> > env.Tool('ninja') in the SConstruct, you must set the
>> > variable NINJA_DEPFILE_PARSE_FORMAT, so it will look like this in the
>> > SContruct:
>> >
>> > env['NINJA_DEPFILE_PARSE_FORMAT'] = 'clang'
>> > env.Tool('Ninja')
>>
>> Isn't this something that the relevant compiler tool (gcc, msvc, clang,
>> mingw) could set up rather than introducing something the developer
>> needs to set?
>> _______________________________________________
>> Scons-users mailing list
>> [email protected]
>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>
>

_______________________________________________
Scons-users mailing list
[email protected]
https://pairlist4.pair.net/mailman/listinfo/scons-users