From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Andrew Fish <afish@apple.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Richardson, Brian" <brian.richardson@intel.com>,
Graeme Gregory <graeme.gregory@linaro.org>,
Linaro UEFI <linaro-uefi@lists.linaro.org>,
Ryan Harkin <ryan.harkin@linaro.org>,
"haojian.zhuang@linaro.org" <haojian.zhuang@linaro.org>,
Chenhui Sun <chenhui.sun@linaro.org>,
Heyi Guo <heyi.guo@linaro.org>, "Duran, Leo" <leo.duran@amd.com>,
Marcin Wojtas <mw@semihalf.com>, Evan Lloyd <Evan.Lloyd@arm.com>,
Alan Ott <alan@softiron.co.uk>
Subject: Re: [RFC] migration of OpenPlatformPkg to tianocore
Date: Thu, 22 Jun 2017 13:49:18 +0100 [thread overview]
Message-ID: <20170622124918.GJ26676@bivouac.eciton.net> (raw)
In-Reply-To: <CAKv+Gu8fFJ8ZvdozVccUHDpKSbAyuV+1dnqUNwmgURXYMjYXtA@mail.gmail.com>
On Thu, Jun 22, 2017 at 11:46:16AM +0000, Ard Biesheuvel wrote:
> On 22 June 2017 at 11:39, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> > On 21 June 2017 at 17:44, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> >> Hi all,
> >>
> >> I have now pushed updated versions of devel-OpenPlatformPkg branches
> >> to edk2-platforms and edk2-non-osi. I now also have a Readme.md at the
> >> top-level of edk2-platforms describing
> >>
> >> All the silly hacks are gone, and all platforms now build.
> >>
> >> I would really appreciate if people could have a look (and a play).
> >>
> >
> > Cello does not build atm in the new arrangement:
> >
> > build.py...
> > : error 000E: File/directory not found in workspace
> > OpenPlatformPkg/Drivers/Xhci/RenesasFirmwarePD720202/RenesasFirmwarePD720202.inf
> > is not found in packages path:
> > /home/ard/build/edk2/../edk2-platforms
> > /home/ard/build/edk2/../edk2-non-osi
>
> I also think the new PACKAGES_PATH breaks the inclusion of Dsdt.hex:
>
> /home/ard/build/edk2-platforms/Silicon/AMD/Styx/AcpiTables/Dsdt.c:22:20:
> fatal error: Dsdt.hex: No such file or directory
> #include <Dsdt.hex>
> ^
> compilation terminated.
>
> which resides at
>
> Build/Cello/DEBUG_GCC5/AARCH64/edk2-platforms/Silicon/AMD/Styx/AcpiTables/AcpiAml/OUTPUT/Dsdt.hex
>
> but the include is defined as
>
> GCC:*_*_AARCH64_PLATFORM_FLAGS =
> -I$(BIN_DIR)/Silicon/AMD/Styx/AcpiTables/AcpiAml/OUTPUT
You're not reading the documentation ;) (Have a glance at Readme.md.)
Yes, this is the behaviour I had before this latest reshuffle.
Mike's proposed (and functional) workaround is to not have "edk2" as
your WORKSPACE, but a common superdirectory of edk2, edk2-platforms
and edk2-non-osi.
Hopefully at some point we can get rid of this restriction, but for
now it's sort of necessary.
/
Leif
next prev parent reply other threads:[~2017-06-22 12:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 22:55 [RFC] migration of OpenPlatformPkg to tianocore Leif Lindholm
2017-05-05 13:45 ` Yao, Jiewen
2017-05-05 14:03 ` Yao, Jiewen
2017-06-01 15:33 ` Leif Lindholm
2017-06-01 16:49 ` Kinney, Michael D
2017-06-02 14:29 ` Leif Lindholm
2017-06-07 14:58 ` Leif Lindholm
2017-06-13 23:13 ` Kinney, Michael D
2017-06-14 17:05 ` Leif Lindholm
2017-06-21 17:44 ` Leif Lindholm
2017-06-22 11:39 ` Ard Biesheuvel
2017-06-22 11:46 ` Ard Biesheuvel
2017-06-22 12:49 ` Leif Lindholm [this message]
2017-06-22 15:57 ` Ard Biesheuvel
2017-06-22 16:15 ` Leif Lindholm
2017-06-22 12:38 ` Leif Lindholm
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=20170622124918.GJ26676@bivouac.eciton.net \
--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