AsmResolver.Elf
ds5678 opened this issue · 2 comments
ds5678 commented
What would be involved in supporting ELF? From a brief look online, the specification appears to be fully opensource. If I wanted to work on this, how would you want me to go about that?
Washi1337 commented
What's most important is that it should follow the same structure and API design as the other libraries related to the PE file format to keep things consistent and predictable.
In practical terms that would probably mean something in the lines of the following as a start:
- An
ElfFile
class for low level ELF file access (i.e., basic headers and sections). - An
ElfImage
class for higher level representations (i.e., interpretation of sections). - Use the same model for "normal" and "serialized" versions of the classes, and use the lazy loading for non-trivial properties.
- Ideally, an
ElfFileBuilder
class if feasible, however this can be difficult to make generically (which is why there also does not exist one yet for PE).
I would say we do not need IElfFile
and IElfImage
. The equivalent ones for PE will very likely be removed in the future (see #445).