public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "David F." <df7729@gmail.com>
To: Guomin Jiang <guomin.jiang@intel.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] Updating to latest EDK2 and now get NMAKE: fatal error U1073: Don't know how to make.. on some items?
Date: Tue, 26 May 2020 00:18:00 -0700	[thread overview]
Message-ID: <29271.1590477480284232220@groups.io> (raw)
In-Reply-To: <DM6PR11MB2955F1D7B497ABB5B96664BB9DB00@DM6PR11MB2955.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

Let me start by what I did to get the build working with the old BaseTools.   I renamed BaseTools and put back the prior BaseTools from Nov 29 2018 (build.exe date).  It started building out of the gate, then hit nasm.inc not found, so digging around end up comparing old and new for things and brought over new NASM items from new GenMake.py to the old one.  Tried again, same thing, ended up fixing by bringing over the new build_rule.txt.  Now everything is building fine using VS2008 but the old BaseTools.

I can try using VS2017, I though I was staying with VS2008 is VS2017 added more behind the scenes stuff that I have to add replacements for (already have what I need for VS2008).  But I really don't remember. I'll do that when I get a chance once I catch up on things.

Okay, now on to Guomin message,  Those messages are saying it's not in the .inf, which looking in the .inf, they are not.  Although the headers themselves exist.  I got the edk2-libc repo from GIT.  The edk2 repo I still use svn update to update it.  Using tortoise tools on windows.

Thanks.

[-- Attachment #2: Type: text/html, Size: 1168 bytes --]

  reply	other threads:[~2020-05-26  7:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  7:55 Updating to latest EDK2 and now get NMAKE: fatal error U1073: Don't know how to make.. on some items? df7729
2020-05-25 20:51 ` [edk2-devel] " Michael D Kinney
2020-05-25 23:21   ` Andrew Fish
2020-05-26  0:21     ` Guomin Jiang
2020-05-26  7:18       ` David F. [this message]
2020-05-27  0:06         ` Guomin Jiang
2020-05-26 10:20 ` Tomas Pilar (tpilar)

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=29271.1590477480284232220@groups.io \
    --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