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.

Sign up for GitHub

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

Jump to bottom

Better support for non-default mappings #58

Open
3 of 19 tasks
makamys opened this issue Feb 11, 2024 · 0 comments
Open
3 of 19 tasks

Better support for non-default mappings #58

makamys opened this issue Feb 11, 2024 · 0 comments

Comments

@makamys
Copy link
Collaborator

makamys commented Feb 11, 2024 •
edited
Loading

RFG already supports custom mappings (or does it), but they are generally difficult to use in practice due to several issues. Here is a list of what could be improved:

  • Properly support customizing the output directory of generateForgeSrgMappings (see Fix generateForgeSrgMappings always using default location in onlyIf #61)
  • Migrate mod source
    • Migrate Java code and mixins
    • Migrate string constants (reflection/ASM)
  • Remap dependencies
    • Remap bytecode
      • For non-maven deps
      • For maven deps
    • Remap string constants (reflection/ASM)
      • API users
      • API non-users
    • Remap sources(?)
    • Remap ATs
    • Remap CCC ASM
    • Remap reflection at runtime in dev
  • API for remappable string constants
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@makamys