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
make install no longer respects lib_binary_dir_path #196
Comments
Also I did modify rake-compiler to use |
Is the your gem https://github.com/konsolebox/digest-xxhash-ruby ? |
One way to reproduce this is by cloning the repo to a temporary directory, checkout the v0.2.1 tag, install rake-compiler 1.1.3 or 1.1.4, then run rake test.
The significant output lines should be something like this:
You can see that Here's also a failing log in AppVeyor: https://ci.appveyor.com/project/konsolebox/digest-xxhash-ruby/builds/41851529/job/9st82d9etf11w5q9 |
Could you try 1.1.5? |
I tested it locally and also in AppVeyor. It looks fixed: https://ci.appveyor.com/project/konsolebox/digest-xxhash-ruby/builds/41857053 |
Thanks a lot! |
So I have a gem with a tree structure looking like this:
And before #191 was merged, I was able to configure rake-compiler like this:
This is because
binary_path
is generated fromname
which contains the partial directory pathdigest
, and the old install command,install tmp_binary_path, "#{lib_path}/#{binary_path}"
refers to it.But now I have to manually specify directories:
I'm not sure but maybe it has to do with the line
siteconf.puts "dest_path = mkintpath(#{File.expand_path(lib_path).dump})"
. Instead oflib_path
, it should specifylib_binary_dir_path
instead.Maybe specifying
name
with a subdirectory is illegal but if that's the case, what's the point of calculating and usinglib_binary_dir_path
as an argument todirectory
, and as a requirement argument instead of just usinglib_path
.The text was updated successfully, but these errors were encountered: