Skip to content

Remove support for generating mclib as a shared object #5188

Closed

Description

@zyv

Is there an existing request for this?

  • I have searched the existing issues

Is your feature request related to a problem?

See #4803 and #4806, specifically the following comments:

Describe the solution you'd like

--enable-mclib and all corresponding infrastructure to build a shared library should be removed.

Describe alternatives you've considered

No response

Additional context

No response

Activity

  1. added this to the 4.9.1 milestone on Oct 16, 2026
  2. added theissue type on Oct 16, 2026
  3. added
    prio: mediumHas the potential to affect progress
    needs triageNeeds triage by maintainers
    on Oct 16, 2026
  4. added
    area: buildBuild system and (cross-)compilation
    and removed
    needs triageNeeds triage by maintainers
    on Oct 16, 2026
  5. modified the milestones: Future Releases, 4.9.1 on Oct 16, 2026
  6. egmontkob commented on Oct 17, 2026

    @egmontkob
    Contributor

    I see you tagged it for release 4.9.1, whereas obviously 4.9.0 will be the big deal where we break compatibility at a couple of places.

    Any chance you could easily emit a big fat warning at least, or outright disable --enable-mclib for 4.9.0 already, whereas leaving the big cleanup for 4.9.1 or so?

  7. zyv commented on Oct 17, 2026

    @zyv
    MemberAuthor

    This was an arbitrary choice - only to keep a cleaner list of prioritized strategic todos, as opposed to an overfull list of tactical stuff already accepted for 4.9.0. I can also tag it for 4.9.0 if you want :) The problem is not tagging as such, but putting the work into it :( If I get a chance to work on making a release at all, I would absolutely prefer fixing it for 4.9.0... only I still have one last exam to put behind me by Christmas or "bad things will happen" (tm) so it's uncertain as to how and when I'll get back to it after this short break where I was sick after taking the last couple of exams.

  8. added a commit that references this issue on Oct 17, 2026
  9. modified the milestones: 4.9.1, 4.9.0 on Oct 17, 2026
  10. added a commit that references this issue on Oct 17, 2026
  11. added a commit that references this issue on Oct 18, 2026
  12. added a commit that references this issue on Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: buildBuild system and (cross-)compilationprio: mediumHas the potential to affect progress

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions