From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Pankaj Bansal <pankaj.bansal@nxp.com>
Cc: "Gao, Liming" <liming.gao@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
Michael D Kinney <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Udit Kumar <udit.kumar@nxp.com>, Varun Sethi <V.Sethi@nxp.com>
Subject: Re: PACKAGES_PATH in !include path in Dsc files
Date: Tue, 16 Oct 2018 11:11:12 +0800 [thread overview]
Message-ID: <CAKv+Gu9MJERpkk3aWKr=xh3yLmKNBKPaxVZdB4Q5TW=OvJ7UOA@mail.gmail.com> (raw)
In-Reply-To: <HE1PR0402MB3323F9A729C56EB3A2303A1DF1FE0@HE1PR0402MB3323.eurprd04.prod.outlook.com>
On 16 October 2018 at 10:40, Pankaj Bansal <pankaj.bansal@nxp.com> wrote:
> +edk2-platforms maintainers in To list
>
>
>
> Thank you Liming for replying.
>
>
>
> Our entire code is in edk2-platforms
> (https://github.com/tianocore/edk2-platforms) which is denoted by
> PACKAGES_PATH.
>
> The PACKAGES_PATH directory can be anywhere in WORKSPACE depending on the
> sync directory defined by user.
>
> i.e. it can be $(WORKSPACE)/edk2-platforms or $(WORKSPACE)/<any directory
> name that user can define during git sync>
>
> As our dsc files are relative to PACKAGES_PATH, I want to specify their path
> in dsc file like this:
>
>
>
> !include $(PACKAGES_PATH)/Silicon/NXP/<Silicon Name>.dsc
>
>
>
> Using $(WORKSPACE), I cannot specify above path, as it can be at place other
> than $(WORKSPACE)/edk2-platforms
>
But why do you need to !include things in the first place?
Can you explain how you are trying to organize the files, and which
file includes which?
next prev parent reply other threads:[~2018-10-16 3:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 9:00 PACKAGES_PATH in !include path in Dsc files Pankaj Bansal
2018-10-16 1:35 ` Gao, Liming
2018-10-16 2:40 ` Pankaj Bansal
2018-10-16 3:11 ` Ard Biesheuvel [this message]
2018-10-16 5:23 ` Pankaj Bansal
2018-10-16 5:28 ` Gao, Liming
2018-10-16 6:00 ` Pankaj Bansal
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+Gu9MJERpkk3aWKr=xh3yLmKNBKPaxVZdB4Q5TW=OvJ7UOA@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