From: "Cohen, Eugene" <eugene@hp.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Debugging why Build Rebuilds Something
Date: Thu, 21 Mar 2019 10:15:26 +0000 [thread overview]
Message-ID: <CS1PR8401MB1189D8363B8351B2F2B461B7B4420@CS1PR8401MB1189.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E4089FC@SHSMSX104.ccr.corp.intel.com>
Great - I will try this now, thanks Liming!
From: Gao, Liming <liming.gao@intel.com>
Sent: Thursday, March 21, 2019 4:02 AM
To: Cohen, Eugene <eugene@hp.com>; edk2-devel@lists.01.org
Subject: RE: Debugging why Build Rebuilds Something
Could you help check the timestamp of AutoGen files in OpenSslLib output directory?
After the first build, copy OpenSslLib output directory to another directory
After the second build, compare the output directory between two builds, please check whether there is the difference for AutoGen.h and Makefile. If no difference, please directly trig Makefile to see whether rebuild happen. If rebuild happen, it may be the issue in Makefile. Then, further check Makefile.
Thanks
Liming
>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>Cohen, Eugene
>Sent: Thursday, March 21, 2019 5:50 PM
>To: edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>
>Subject: [edk2] Debugging why Build Rebuilds Something
>
>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
>
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>
>https://lists.01.org/mailman/listinfo/edk2-devel<https://lists.01.org/mailman/listinfo/edk2-devel>
next prev parent reply other threads:[~2019-03-21 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 9:49 Debugging why Build Rebuilds Something Cohen, Eugene
2019-03-21 10:01 ` Gao, Liming
2019-03-21 10:15 ` Cohen, Eugene [this message]
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=CS1PR8401MB1189D8363B8351B2F2B461B7B4420@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