Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Afshin Pir <Afshin.Pir@gallagher.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Define dependency package only in staging
Date: Tue, 14 Feb 2023 23:20:10 +0200	[thread overview]
Message-ID: <87v8k40wok.fsf@tarshish> (raw)
In-Reply-To: <SY2PR01MB277812C5F0180DAA6B2A1D2994A29@SY2PR01MB2778.ausprd01.prod.outlook.com>

Hi Afshin,

On Tue, Feb 14 2023, Afshin Pir wrote:
> I wonder if it is possible that to force the dependant package to be
> installed only in staging folder. For example, I have written package
> A which depend on Package B like this:
>
> config BR2_PACKAGE_A
>                bool "my-a-provider"
>                select BR2_PACKAGE_B
>                help
>                        Test A Package
>
> The problem is that the above configuration installs B in the target,
> but in reality, it is enough to be installed in staging directory
> (since it provides a header-only version). In there anyway to define a
> dependency for staging only?

'<PKG>_INSTALL_TARGET = NO' might help you.

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-02-14 21:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 21:13 [Buildroot] Define dependency package only in staging Afshin Pir
2023-02-14 21:20 ` Baruch Siach via buildroot [this message]
     [not found]   ` <SY2PR01MB27785A7F0A589B49D0ABE42994A29@SY2PR01MB2778.ausprd01.prod.outlook.com>
2023-02-15  5:20     ` Baruch Siach via buildroot

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-all 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=87v8k40wok.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=Afshin.Pir@gallagher.com \
    --cc=baruch@tkos.co.il \
    /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