Skip to content

MRUBY_PACKAGE_DIR does not always have a value. #6064

@pyama86

Description

@pyama86

Hello,

I have a concern regarding the changes below. It seems that some of the builds may not work with the following modification:

Link to the changes

Since MRUBY_PACKAGE_DIR does not always have a value, it appears that builds used by projects relying on libmruby.a might be affected. If possible, I would appreciate it if we could revert to using libmruby_static as it was done in versions prior to 3.2, instead of utilizing libmruby_static.replace_prefix_by(build_dir => "$(MRUBY_PACKAGE_DIR)").

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions