Re: 回复： 回复： 回复： 回复： 回复： Ninja compilation fail s after using include path file instead of "-I" opti on

I added an example how to hook up the dependencies:

https://github.com/liruncong/NinJaTest/pull/1/files

On Wed, Apr 13, 2022 at 10:01 AM liruncong2018 <[email protected]> wrote:

> Hi,
> I generate some option files via env.Textfile ("build/__cpp_path.txt",
> "build/__define_options.txt", "build/__link_objects.txt",
> "build/__exe_cpp_path.txt") and make objs depend on corresponding files
> ,for example:
> env.Depends(objs, ["build/__cpp_path.txt", "build/__define_options.txt" ])
> env.Depends(target, "build/__link_objects.txt")
> But after enabling ninja, these manually added dependencies are ignored,
> which causes ninja to fail to compile.
> How to deal with this?
>
> ------------------ 原始邮件 ------------------
> *发件人:* "Daniel Moody" <[email protected]>;
> *发送时间:* 2022年4月13日(星期三) 凌晨0:02
> *收件人:* "SCons users mailing list"<[email protected]>;
> *抄送:* "liruncong2018"<[email protected]>;
> *主题:* Re: [Scons-users] 回复： 回复： 回复： 回复： 回复： Ninja compilation fails after
> using include path file instead of "-I" option
>
> Hello, that PR is meant to support shared @file with ninja, not intended
> for any improvements to TEMPFILE. Please test without TEMPFILE.
>
> On Tue, Apr 12, 2022 at 10:52 AM liruncong2018 via Scons-users <
> [email protected]> wrote:
>
>> Hi
>> I tested "https://github.com/SCons/scons/pull/4133", after enabling
>> ningja, except for the link failure, .c/.cpp/.S are successfully compiled
>> into .o, the total time is 6:48 .
>> This time is much greater than the previous time of 3:45 when ninja was
>> not enabled and the option file was shared using @file.
>> After using TEMPFILE instead of @file, the compilation time is basically
>> doubled whether ninja is enabled or not.
>> The TEMPFILE function should be improved to use shared files to prevent
>> the creation of a large number of temporary files.
>>
>> ------------------ 原始邮件 ------------------
>> *发件人:* "SCons users mailing list" <[email protected]>;
>> *发送时间:* 2022年4月11日(星期一) 晚上11:43
>> *收件人:* "SCons users mailing list"<[email protected]>;
>> *主题:* Re: [Scons-users] 回复： 回复： 回复： 回复： Ninja compilation fails after
>> using include path file instead of "-I" option
>>
>> I have a potential fix to the ninja tool so that it can decide to use
>> response files or not. This should allow you to use your own shared
>> response file.
>>
>> https://github.com/SCons/scons/pull/4133
>>
>> On Mon, Apr 11, 2022 at 10:01 AM Mats Wichmann <[email protected]> wrote:
>>
>>>
>>> On 4/11/22 08:57, liruncong2018 via Scons-users wrote:
>>> > Hi,
>>> > Even using msys2 does not solve all problems. The 32K limit solves my
>>> > compilation problems (.cpp -> .o) but not linking (.o -> target)
>>> because
>>> > the link command line has around 137K (about 2500 .o files). So
>>> > compilers such as gcc/clang/armclang will support "@file".
>>> > Currently, scons needs to set up Depends when using @file. This
>>> > dependency suggestion is still directly supported by scons, and users
>>> do
>>> > not need to write dependencies. It should also be supported when ninja
>>> > is enabled.
>>> > When LINKCOM uses "TEMPFILE", I get a link failure because armlink.exe
>>> > checks if --cpu is specified on the command line, so it is not
>>> > reasonable for "TEMPFILE" to put all options to a temporary file.
>>>
>>> Right... thus my suggestion - well, let's call it "musing" rather than
>>> "suggestion" because this might not work at all:
>>>
>>> > For ninja it currently looks like this:
>>> >
>>> > env["LINKCOM"] = '${TEMPFILE("$LINK $LINKFLAGS /OUT:$TARGET.windows
>>> > $_LIBDIRFLAGS $_LIBFLAGS $_PDB $SOURCES.windows", "$LINKCOMSTR")}'
>>> >
>>> > env["SHLINKCOM"] = '${TEMPFILE("$SHLINK $SHLINKFLAGS $_SHLINK_TARGETS
>>> > $_LIBDIRFLAGS $_LIBFLAGS $_PDB $_SHLINK_SOURCES", "$SHLINKCOMSTR")}'
>>> >
>>> > So I'm curious if moving $LINK $LINKFLAGS to the left of ${TEMPFILE
>>> > would help...
>>> _______________________________________________
>>> 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
>>
>

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