-
-
Notifications
You must be signed in to change notification settings - Fork 901
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
precompiled gems should not have a runtime dependency on mini_portile2
#1991
Comments
It's already there #1989 ! |
I've merged in @larskanis's PR at #1989. Will be in v1.11.0.rc2. |
Reopening, see my comments in #1989. |
@larskanis Cross-posting here (from #1989) that the change in that PR doesn't seem to work for me. I don't see the |
I tested this but probably only with the Windows gems. I'll check this issue this weekend. |
Currently the cross_compiling block isn't called when cross compiling for the build platform. This is due to the fact that define_native_tasks() is called first for the build platform and later on for the cross platforms. The task "native:<gemname>:<platform>" is defined only once and therefore only without the callback. The callback is therefore not called for the cross platform that equals the build platform. OMHO the root issue is that rake-compiler doesn't has a clear separation between native and cross tasks. However I think calling cross_compiling for any binary gem (native or cross) is a suitable workaround. This fixes bug sparklemotion/nokogiri#1991 (comment)
The cross_compiling block wasn't called for the x86_64-linux platform leading to an additional dependency to mini_portile2 and missing post install message. Patch to rake-compiler is here: rake-compiler/rake-compiler#171 Fixes sparklemotion#1991
As pointed out by @voxik in #1983, any gems that are precompiled don't need
mini_portile2
and so we should remove that as a dependency from those gemspecs.The text was updated successfully, but these errors were encountered: