[GSoC 2020]: Doubts in building RSB Recipe for EPICS for multiple architectures

Chris Johns chrisj at rtems.org
Mon Jul 27 00:01:28 UTC 2020

On 27/7/20 4:17 am, Mritunjay Sharma wrote:
> Hello everyone,
> Meanwhile, I publish a couple of blogs of the learnings I made in this phase,
> tonight, 

Thanks. I cannot find in your blog [1] where you have documented building the PC
BSP with the legacy stack for EPICS by hand? This is an important step.

> I will request you all to kindly review the patches so that I can send the next
> version of them. 
> Also kindly guide, so that the RSB recipe which works only on pc-386 can also
> work for other BSP targets for EPICS7+RTEMS5
> Thanks
> Mritunjay
> On Fri, Jul 24, 2020 at 7:20 PM Mritunjay Sharma <mritunjaysharma394 at gmail.com
> <mailto:mritunjaysharma394 at gmail.com>> wrote:
>     Hello all, 
>     To update you all, I have sent the first version of PATCHES that
>     implement an RSB recipe for EPICS7 building with RTEMS5 for pc-386. 
>     While the build was successful for pc-386, I have doubts and need 
>     suggestions on how to make it work across different BSP targets.
>     I will request Chris to show me the path and if possible then also review
>     the patches. 
>     Gedare has suggested using sed but it will be really nice if I can get a
>     a more clear idea on how to implement it. 
>     The existing changes in the file can be seen here: 
>     https://github.com/RTEMS/rtems-source-builder/compare/master...mritunjaysharma394:epics-support

I have no idea how to comment in the specific files. I could not see how to do
this in github so I will put my comments here:

1) Why have you not include rtems-bsp.bset? I do not know how compatible EPICS
is to the GNU configure type build settings. In epics-base.bset you have the
RTEMS version forced to 5. I suggest you review the config/rtems bset files and
see what they have.

2) I am using base64 encoded hash values these days as they are smaller. There
is a script called `sha512-base64` that generates the hash.

3) Please do not reference a personal repo in the source-builder/config tree.
Those files only reference the upstream project. You can specialise in a config
file in the RTEMS config tree with a config file name that hints at the difference.


More information about the devel mailing list