From: "Cohen, Eugene" <eugene@hp.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Debugging why Build Rebuilds Something
Date: Thu, 21 Mar 2019 09:49:44 +0000 [thread overview]
Message-ID: <CS1PR8401MB118903B18389F649C68B4465B4420@CS1PR8401MB1189.NAMPRD84.PROD.OUTLOOK.COM> (raw)
I'm experiencing an annoying problem where OpenSslLib is constantly being rebuilt. I don't think I've done anything unusual or different to it but nevertheless it gets built almost every time I rebuild the same platform.
I don't believe any source file timestamps are changing so I think this may be the build.py tool deciding to re-generate stuff. (As a side note: does the Autogen process only run when changes are detected on dependencies? I assume this must be the case otherwise everything would get rebuilt, right?)
Is there a debug flag that can be turned on to see why build might choose to rebuild something? The normal build report and debug flags don't see to provide the information for "why" something is being rebuilt.
Thanks,
Eugene
next reply other threads:[~2019-03-21 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 9:49 Cohen, Eugene [this message]
2019-03-21 10:01 ` Debugging why Build Rebuilds Something Gao, Liming
2019-03-21 10:15 ` Cohen, Eugene
2019-03-21 10:43 ` Cohen, Eugene
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CS1PR8401MB118903B18389F649C68B4465B4420@CS1PR8401MB1189.NAMPRD84.PROD.OUTLOOK.COM \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox