buildroot-siteTodo
- In buildroot1 in git, create a minimal Makefile
- We need a high-level make that builds three buildroot images: LinuxRT 2019 64-bit and 32-bit and LinuxRT 2016 64-bit
- Fetch 2019 buildroot tarball and get it to actually build (did this for 64-bit, need to build 32-bit and try it)
- Fetch 2016 buildroot tarball and get it to actually build (and try it)
- We need to get Eric Gumtow's changes (i.e., encourage Eric to check the changes he made in)
- Incorporate/use Eric's changes to confirm that it works in the same way the RC3s he did worked (bug-per-bug)
- Figure out what broke between RC1 and RC3 (with respect to
chrt
) - Add unit tests for all of the new ("security patch") functionality
...
- Eric's instructions involve grabbing the buildroot-site repo on SLAC's GitHub area, slaclab, and checking out a particular branch; for buildroot-2019-08 it's br2019.08 and for buildroot-2016.11.1 it's br2016.11. I did that originally because I didn't want to change anything. These branches get checked out as "site-top" in their respective buildroot directories.
- Once I wanted to go in to start making changes, I created two new branches in buildroot-site named br2019.08-dev and br2016.11-dev.
- Question: At the moment, it appears that buildroot-site is essentially using specific branches as tags. So, I didn't want to alter those. Perhaps we should tag them?
- In order to attempt to start where Eric left off, I went into his buildroot directories and found the diffs (using git) in the site-top directories and applied them to mine (but I checked out the "-dev" variants I created, not to disturb the originals while working on this).
...
{"serverDuration": 50, "requestCorrelationId": "085d5af43ccc3938"}