Re: Building EPICS base with Yocto

[Lucas Magalhães via Tech-talk <tech-talk@aps.anl.gov>]

Hi Marcio,

Here at ESS we are using e3 so we build them separate and not on bitbake recipes.

Are you going for a vanilla epics experience where you build the ioc as a single binary artifact? IMO, this would be quite a challenge to achieve in a recipe, but possible still.

Maybe having all components (base and modules) as git submodules and a single Makefile to build everything would make it easier.

Now with a solution like e3 it would be possible to build each module in a recipe and have them installed as libraries that could be used with require later.

Lucas A. M. Magalhães

________________________________________

From: Tech-talk <tech-talk-bounces@aps.anl.gov> on behalf of Han Lee via Tech-talk <tech-talk@aps.anl.gov>

Sent: Thursday, August 28, 2025 8:24 PM

To: EPICS tech-talk

Subject: Re: Building EPICS base with Yocto

Hi Marcio,

This information might be outdated, but it could offer some guidance for your Yocto Linux configuration. Please check the old legacy repository at the following link:

https://github.com/icshwi/e3-base/tree/master/configure/os<https://urldefense.us/v3/__https://github.com/icshwi/e3-base/tree/master/configure/os__;!!G_uCfscf7eWS!ZkoLP57PPBUunPKjvn8_Gqz30eXysd8EEkLhWoacK57VOi2r48HexKrpIbyLzrQUHp1K_tVIQ1x8giq8g0re2aI$>

You'll find three examples there, which you should place in your base source folder. Additionally, Yocto toolchain names are defined in this file:

https://github.com/icshwi/e3-base/blob/master/configure/CONFIG_BASE<https://urldefense.us/v3/__https://github.com/icshwi/e3-base/blob/master/configure/CONFIG_BASE__;!!G_uCfscf7eWS!ZkoLP57PPBUunPKjvn8_Gqz30eXysd8EEkLhWoacK57VOi2r48HexKrpIbyLzrQUHp1K_tVIQ1x8giq8tsmtrMg$>

The ESS teams might have the up-to-date version if they are still using Yocto Linux for their embedded solution.

HTH,

Han

On Thu, Aug 28, 2025 at 9:42 AM Johnson, Andrew N. via Tech-talk <tech-talk@aps.anl.gov<mailto:tech-talk@aps.anl.gov>> wrote:

Hi Marcio,

I can’t help you specifically with Yocto or Bitbake, but for embedded IOC builds I would recommend turning off shared libraries for that target architecture and doing a static build of the IOC executable. You could even try whole-program-optimization if you know how.

That way you don’t have to worry about configuring shared library search paths since all the EPICS code will have been linked into the executable, and the IOC will probably start very slightly quicker as the OS doesn’t have to resolve all the internal symbols at load-time.

HTH,

- Andrew

--

Complexity comes for free, Simplicity you have to work for.

On 8/28/25, 11:10 AM, "Tech-talk" <tech-talk-bounces@aps.anl.gov<mailto:tech-talk-bounces@aps.anl.gov>> wrote:

Hello.

I’m familiar with the approach of building EPICS base in a host machine, selecting different architectures, and then configuring Yocto to access the EPICS libraries that are installed in the host. But was anyone able to build EPICS base using a Bitbake recipe inside Yocto?

Cheers,

Marcio

--

Jeong Han Lee, Dr.rer.nat.

Lawrence Berkeley National Laboratory

https://orcid.org/0000-0002-1699-2660<https://urldefense.us/v3/__https://orcid.org/0000-0002-1699-2660__;!!G_uCfscf7eWS!ZkoLP57PPBUunPKjvn8_Gqz30eXysd8EEkLhWoacK57VOi2r48HexKrpIbyLzrQUHp1K_tVIQ1x8giq8QS5Gvfc$>