|
Notes |
|
|
(0029060)
|
|
Felix Schwitzer
|
|
2012-04-02 16:11
|
|
The problem exists not only on Mac OSX, but also on linux and windows (cygwin and mingw).
I dug into ruby's own build system and makefile generator (generate_makefile in mkmf.rb) and found, that the name for the extension module is
"$(TARGET).#{CONFIG['DLEXT']}", so the library name is the module name
without prefix and the extension(suffix) is platform dependent
(.so on linux/cygwin/wingw, .bundle on mac).
I believe the best is to ask the ruby-interpreter for the extension, like
FindRuby.cmake it does for RUBY_ARCH and others.
I implemented this approach in the attached patch.
The patch generates a dependency to FindRuby, but when building a ruby extension
the assumption that a ruby interpreter is installed on the build machine is
reasonable, or isn't it? |
|
|
|
(0034607)
|
|
jschueller
|
|
2013-11-28 04:28
|
|
|
|
|
(0034612)
|
|
Felix Schwitzer
|
|
2013-11-28 16:16
|
|
Great. I tested your patch and it works fine for me, thanks.
I checked also the naming convention for ruby 2.0 and it seems that nothing
changed here.
Maybe my initial approach was a little bit too intrusive... |
|
|
|
(0034680)
|
|
jschueller
|
|
2013-12-02 13:06
|
|
|
|
|
(0036097)
|
|
Robert Maynard
|
|
2014-06-02 08:39
|
|
|
Closing resolved issues that have not been updated in more than 4 months. |
|
0001-UseSWIG-adjust-module-name-for-ruby.patch (4,807) 2012-04-02 16:03