public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "jbrasen.qdt" <jbrasen.qdt@qualcommdatacenter.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: GenFds issue with multiple paths in PACKAGES_PATH
Date: Wed, 4 Apr 2018 23:06:10 +0200	[thread overview]
Message-ID: <CAKv+Gu8=pL-co-G9nPvHv_ZR3DDj-R_Ddxmf=S+3n=N6dSDRYA@mail.gmail.com> (raw)
In-Reply-To: <52be5673039b42eab80216a23ae85230@NASANEXM01B.na.qualcomm.com>

On 4 April 2018 at 19:00, jbrasen.qdt
<jbrasen.qdt@qualcommdatacenter.com> wrote:
> Hello,
>
>   I am trying to update my build software to the current edk2-platforms layout and am running into some issues with the final part of the build.
>
>  It seems that the output is being generated under edk2/Build/Qdfxxxx_RBL/DEBUG_CLANG35/AARCH64/edk2-QDT-platforms-restricted/Silicon/QualcommDatacenter
>   But GenFds is looking under edk2/Build/Qdfxxxx_RBL/DEBUG_CLANG35/AARCH64/Silicon/QualcommDatacenter
>
> edk2-QDT-platforms-restricted is a path under PACKAGES_PATH
>
>
> I do have another directory that has build output from Silicon/QualcommDatacenter with some libraries
>
> Any ideas?

None of the references in your .dsc or .fdf files should include the
edk2-QDT-platforms-restricted prefix, can you check that?


  reply	other threads:[~2018-04-04 21:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <26519abafe2549879a44e1fb8680a17b@NASANEXM01B.na.qualcomm.com>
2018-04-04 17:00 ` GenFds issue with multiple paths in PACKAGES_PATH jbrasen.qdt
2018-04-04 21:06   ` Ard Biesheuvel [this message]
     [not found]     ` <fcd915ac48f5433e9498602995924ca0@NASANEXM01B.na.qualcomm.com>
2018-04-04 21:14       ` jbrasen.qdt
2018-04-08  2:21         ` Gao, Liming
2018-04-20 19:43           ` jbrasen.qdt

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='CAKv+Gu8=pL-co-G9nPvHv_ZR3DDj-R_Ddxmf=S+3n=N6dSDRYA@mail.gmail.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