[Buildroot] Define dependency package only in staging

[Buildroot] Define dependency package only in staging

[Afshin Pir]

[-- Attachment #1.1: Type: text/plain, Size: 1057 bytes --]

Hi All

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?

Best Regards,
Afshin
________________________________
This email is confidential and may contain information subject to legal privilege. If you are not the intended recipient please advise us of our error by return e-mail then delete this email and any attached files. You may not copy, disclose or use the contents in any way. The views expressed in this email may not be those of Gallagher Group Ltd or subsidiary companies thereof.
________________________________

[-- Attachment #1.2: Type: text/html, Size: 3251 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] Define dependency package only in staging

[Baruch Siach via buildroot]

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

Re: [Buildroot] Define dependency package only in staging

[Baruch Siach via buildroot]

Hi Afshin,

Please keep the list on Cc.

On Tue, Feb 14 2023, Afshin Pir wrote:
> You mean will it work if I add that in package "A" configuration like this:
>         B_INSTALL_TARGE = NO
> Because normally each package its own configuration.

That should be

  B_INSTALL_TARGET = NO

But now I see that you want B out of target only when A selects B, not
for the general case, right? There is no direct support for that in
Buildroot. You can always use a post build script to remove whatever you
like from your target.

Alternatively you can add a blind config symbol to package B Config.in
that adds 'B_INSTALL_TARGET = NO', and then select this symbol from
package A.

baruch

> -----Original Message-----
> From: Baruch Siach <baruch@tkos.co.il>
> Sent: Wednesday, 15 February 2023 10:20 am
> To: Afshin Pir <Afshin.Pir@gallagher.com>
> Cc: buildroot@buildroot.org
> Subject: Re: [Buildroot] Define dependency package only in staging
>
> 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