<div dir="ltr">On 18 December 2017 at 11:28, Burton, Ross <span dir="ltr"><<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class="">On 18 December 2017 at 11:06, Olof Johansson <span dir="ltr"><<a href="mailto:olof.johansson@axis.com" target="_blank">olof.johansson@axis.com</a>></span> wrote:<br></span><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm so sorry, I missed your email; I am, but maybe not as quickly<br>
as you are able to(?). My is_stripped looks kind of like yours,<br>
but without the ShType.progbits. Thanks for the suggestion! I<br>
were able to hackishly integrate the Elf class it with<br>
staging.bbclass and package.bbclass.<br>
<br>
I did have a couple of questions; if I were to add an is_stripped<br>
method, would that fit best in the Elf class itself or in some<br>
wrapper? Would renaming the elf class to "ElfParser" class make<br>
more sense, and have an ELF class that wraps it? I can publish a<br>
draft somewhere later today.<br></blockquote><div><br></div></span><div>The Elf class is generated with kaitai struct so I'm trying to reduce the number of changes to it, but we can definitely move it into a subpackage like oe.parsers.elf and then have oe.elf for just the utility method.</div></div></div></div></blockquote><div><br></div><div>Just pushed ross/elf with this change. The next obvious step is to turn lib/oe/qa.py into a new lib/oe/elf.py which has a better API and includes the stripped function.</div><div><br></div><div>Ross</div></div></div></div>