* How to handle custom fetcher? #yocto
@ 2020-01-13 13:56 Bill.Kulp
2020-01-13 14:12 ` [yocto] " Philip Balister
0 siblings, 1 reply; 2+ messages in thread
From: Bill.Kulp @ 2020-01-13 13:56 UTC (permalink / raw)
To: yocto
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
Hello! I'm creating a Yocto BSP layer that depends on an external binary. This binary is large, so it is stored on an external server. (it's an HDF file for a Xilinx ZynqMP device).
The binary is retrieved using a shell script that can
(1) retrieve a string representing the version of the latest build, and
(2) download a build corresponding to a specific version.
I am trying to figure out how to integrate step (1) with Bitbake. Ideally, Bitbake should treat the version string like a version control identifier, querying it and rebuilding the package if it has changed.
Do you have advice on the best practice to do this? Do I need custom code in the do_fetch step? Can I dynamically set something like SRCPV or SRCREV?
[-- Attachment #2: Type: text/html, Size: 804 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [yocto] How to handle custom fetcher? #yocto
2020-01-13 13:56 How to handle custom fetcher? #yocto Bill.Kulp
@ 2020-01-13 14:12 ` Philip Balister
0 siblings, 0 replies; 2+ messages in thread
From: Philip Balister @ 2020-01-13 14:12 UTC (permalink / raw)
To: Bill.Kulp, yocto
On 1/13/20 8:56 AM, Bill.Kulp@azuresummit.com wrote:
> Hello! I'm creating a Yocto BSP layer that depends on an external binary. This binary is large, so it is stored on an external server. (it's an HDF file for a Xilinx ZynqMP device).
>
> The binary is retrieved using a shell script that can
> (1) retrieve a string representing the version of the latest build, and
This sounds very close to what setting SRCREV = ${AUTOREV} does. You
might see how that is implemented. As a note, we avoid recipes setting
AUTOREV since they need networkd access during a build and we try to
avoid that being a requirement for people doing builds from local sources.
Philip
> (2) download a build corresponding to a specific version.
>
> I am trying to figure out how to integrate step (1) with Bitbake. Ideally, Bitbake should treat the version string like a version control identifier, querying it and rebuilding the package if it has changed.
>
> Do you have advice on the best practice to do this? Do I need custom code in the do_fetch step? Can I dynamically set something like SRCPV or SRCREV?
>
>
>
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-01-13 14:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-13 13:56 How to handle custom fetcher? #yocto Bill.Kulp
2020-01-13 14:12 ` [yocto] " Philip Balister
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.