From: eregontp@... Date: 2017-05-29T15:33:11+00:00 Subject: [ruby-core:81455] [Ruby trunk Feature#13570] Using mkmf for ruby/spec C API specs Issue #13570 has been updated by Eregon (Benoit Daloze). File spec_helper.rb added I attach here the current version of the spec_helper.rb doing the compilation of extensions. It seems to now work correctly for out-of-source builds, and with an extra hack uses the right ruby in the Makefile (RbConfig.ruby in ./rbconfig.rb is just incorrect for built but not installed ruby). I found very confusing the effect that $extmf can have, I wished MRI used a simpler mechanism to detect if ruby was installed or not. Is it so important nowadays to be able to test without "make install"? Could I ask some help for making this run correctly on Windows? I would like if possible something not too hacky. The old way to compile extensions was un-maintainable due to its complexity. ---------------------------------------- Feature #13570: Using mkmf for ruby/spec C API specs https://bugs.ruby-lang.org/issues/13570#change-65157 * Author: Eregon (Benoit Daloze) * Status: Closed * Priority: Normal * Assignee: * Target version: ---------------------------------------- Hello all, I am thinking to use mkmf to compile the C API specs. https://github.com/ruby/ruby/blob/trunk/spec/rubyspec/optional/capi/spec_helper.rb is getting pretty complex and hard to maintain. I have a few questions: * Does mkmf works well on Windows? * What is a good way to compile a single .c file with mkmf to a given library file in another directory? I tried this but I am not sure it's correct: ~~~ ruby def compile_extension(name) objdir = object_path ext = "#{name}_spec" lib = "#{objdir}/#{ext}.#{RbConfig::CONFIG['DLEXT']}" require 'mkmf' # TODO: probably best to use a subprocess to avoid polluting the namespace Dir.chdir(objdir) do $srcs = ["#{extension_path}/#{ext}.c"] $objs = ["#{extension_path}/#{ext}.o"] # should probably be in objdir but that does not seem to work create_makefile(ext) system "make" end lib end ~~~ Alternatively, we can copy the needed files to a temporary directory, build there and copy the shared library back. It's a bit more work but not a big deal either. ---Files-------------------------------- spec_helper.rb (2.22 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: