Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support using as a library #12

Open
5 tasks
puff opened this issue Jun 11, 2023 · 0 comments
Open
5 tasks

Support using as a library #12

puff opened this issue Jun 11, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@puff
Copy link
Owner

puff commented Jun 11, 2023

Currently, everything is built into a standalone executable. It would be nice to be able to use the project as a library to allow a more extensible pipeline.

Tasks to be done:

  • Split Core into separate projects.
  • Make Core completely separated from the pipeline.
    - For example, IO namespace uses DevirtualizationContext from the pipeline. We should move IO away from the Core namespace.
  • Fix the internal access modifier spam.
  • Split MethodDevirtualizer stage into MethodDisassembler and MethodRecompiler stages.
    - Decouple VMMethod and other VM architecture from CIL and keep them more VMIL.
    - Allows other stages to modify instructions before recompilation (i.e. Fixers or Data Devirtualization)
  • Move Devirtualization namespace to its own project and implement an IPipeline.
    - Decentralizes the pipeline and allow for more pipelines to be created and used.
@puff puff added the enhancement New feature or request label Jun 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant