[Tutorial] SketchUp Ruby C Extension
-
Added a new example with basic functions. Will start on the tutorial text and images next.
Btw, does anyone know how one can make extconf.rb and make/nmake output their files to a given folder? I'd like to make it so that each platform outputs its generated files to separate directories.
-
What C++ compiler or development environment are you going to write this for so I can go download it and start poking around in it?
-
I am writing the extensions in C. But under windows I installed Visual C++ Express 2010 because it has the required Windows headers and
nmaketo compile it. I have some crude notes in the README.txt in the repo. Under OSX you need X Tools from the OSX DVD. -
Note that I never use the Visual C++ IDE editor.
-
Just wondering if there's any reason that MinGW instead of MSVC++ could not be used to compile c extensions. I assume the c extension is a libaray and doesn't require any Windows-specific GUI stuff - it's just a library of functions, right?
-
@thomthom said:
Btw, does anyone know how one can make extconf.rb and make/nmake output their files to a given folder? I'd like to make it so that each platform outputs its generated files to separate directories.
Did you check the methods defined in "mkmf.rb" ?
(You can also see "Appendix C. Functions Available in extconf.rb" in the "README.EXT" file.).. also check our the "extmk.rb" file in the ext dir.
-
@jim said:
Just wondering if there's any reason that MinGW instead of MSVC++ could not be used to compile c extensions. I assume the c extension is a libaray and doesn't require any Windows-specific GUI stuff - it's just a library of functions, right?
Dunno. I'd think it'd be possible. But I really have no clue when it comes to compiling. It'd be nice to have tutorials for different compilers. So please feel free to jump on the bandwagon
) -
@dan rathbun said:
Did you check the methods defined in "mkmf.rb" ?
(You can also see "Appendix C. Functions Available in extconf.rb" in the "README.EXT" file.).. also check our the "extmk.rb" file in the ext dir.
Yea, got a wee bit lost...
-
@thomthom said:
Yea, got a wee bit lost...
I know (insert head-spinning emoticon here).
Lets try these:
A Simple Makefile TutorialI think the constant you want is
DESTDIRor$(DESTDIR) -
Will have a look. Currently when I use nmake I get some warning about some of the compiler flags. Maybe I can eliminate them. I'd prefer that so there's less noise coming from the compiler. Easier to spot other warnings.
( That first link is sightly messed up though, as they didn't escape angle brackets inside the code examples:
#include <hellomake.h>eaten by the browser - at least under Firefox.I've come across a partial documentation of mkmf: http://www.ensta-paristech.fr/~diam/ruby/online/ruby-doc-stdlib/libdoc/mkmf/rdoc/index.html
-
@thomthom said:
Dunno. I'd think it'd be possible. But I really have no clue when it comes to compiling. It'd be nice to have tutorials for different compilers. So please feel free to jump on the bandwagon )
I could not get MinGW working using Ruby 1.8.6. I could get the examples to compile using Ruby 1.9.3, but they just crashed SketchUp.
But both example seem to compile and work just fine in SketchUp using VC++ Express and Ruby 1.8.6 per your instructions in the Readme file.
-
@jim said:
I could not get MinGW working using Ruby 1.8.6.
Ruby v1.8.6-p287 was the last 'distro' to be compiled with MSVC. (.. which is likely why the GSUDT released SU8 with this patch level, even though their were newer v1.8.6 patch levels available.)
All patch levels above p287 were distro'd (via Windows One-Click Installer,) compiled with MinGW.
That is not to say, however that someone (including Google,) could build the newer patch levels with MSVC, or do a manual install by downloading precompiled binaries from:
ftp;//ftp.ruby-lang.org/pub/ruby/binaries/mswin32/
(.. However not all patch levels are available.) -
Shouldn't the C extension be protected by a sort of a "namespace"? I mean shouldn't
Point3d {};beSX_Ext_Point3D {};? If we have two diffetent DLL's, do their functions exist in a same 'space'
? -
@unknownuser said:
Shouldn't the C extension be protected by a sort of a "namespace"? I mean shouldn't
Point3d {};beSX_Ext_Point3D {};? If we have two diffetent DLL's, do their functions exist in a same 'space' ?No - only the Ruby modules, classes and methods you define - like in a normal Ruby Script. Everything else is isolated.
As you see in the init function:
<span class="syntaxdefault"><br />void Init_SX_Basics</span><span class="syntaxkeyword">( </span><span class="syntaxdefault">void </span><span class="syntaxkeyword">)<br />{<br /> </span><span class="syntaxcomment">// Modules<br /> </span><span class="syntaxdefault">mSUExtTest </span><span class="syntaxkeyword">= </span><span class="syntaxdefault">rb_define_module</span><span class="syntaxkeyword">( </span><span class="syntaxstring">"SUExtTest" </span><span class="syntaxkeyword">);<br /> <br /> </span><span class="syntaxcomment">// Constants<br /> // > SUExtTest;;SX_BASIC_VERSION<br /> </span><span class="syntaxdefault">rb_define_const</span><span class="syntaxkeyword">( </span><span class="syntaxdefault">mSUExtTest</span><span class="syntaxkeyword">, </span><span class="syntaxstring">"SX_BASIC_VERSION"</span><span class="syntaxkeyword">, </span><span class="syntaxdefault">rb_str_new2</span><span class="syntaxkeyword">( </span><span class="syntaxstring">"0.1.0" </span><span class="syntaxkeyword">) );<br /> <br /> </span><span class="syntaxcomment">// Methods<br /> // > SUExtTest.foo<br /> </span><span class="syntaxdefault">rb_define_module_function</span><span class="syntaxkeyword">( </span><span class="syntaxdefault">mSUExtTest</span><span class="syntaxkeyword">, </span><span class="syntaxstring">"foo"</span><span class="syntaxkeyword">, </span><span class="syntaxdefault">h_foobar</span><span class="syntaxkeyword">, </span><span class="syntaxdefault">0 </span><span class="syntaxkeyword">);<br /> </span><span class="syntaxcomment">// > SUExtTest.multiply( number1, number2 )<br /> </span><span class="syntaxdefault">rb_define_module_function</span><span class="syntaxkeyword">( </span><span class="syntaxdefault">mSUExtTest</span><span class="syntaxkeyword">, </span><span class="syntaxstring">"multiply"</span><span class="syntaxkeyword">, </span><span class="syntaxdefault">h_multiply</span><span class="syntaxkeyword">, </span><span class="syntaxdefault">2 </span><span class="syntaxkeyword">);<br /> </span><span class="syntaxcomment">// > SUExtTest.pi_array( array )<br /> </span><span class="syntaxdefault">rb_define_module_function</span><span class="syntaxkeyword">( </span><span class="syntaxdefault">mSUExtTest</span><span class="syntaxkeyword">, </span><span class="syntaxstring">"pi_array"</span><span class="syntaxkeyword">, </span><span class="syntaxdefault">h_pi_array</span><span class="syntaxkeyword">, </span><span class="syntaxdefault">1 </span><span class="syntaxkeyword">);<br /> </span><span class="syntaxcomment">// > SUExtTest.random_points( size )<br /> </span><span class="syntaxdefault">rb_define_module_function</span><span class="syntaxkeyword">( </span><span class="syntaxdefault">mSUExtTest</span><span class="syntaxkeyword">, </span><span class="syntaxstring">"random_points"</span><span class="syntaxkeyword">, </span><span class="syntaxdefault">h_random_points</span><span class="syntaxkeyword">, </span><span class="syntaxdefault">1 </span><span class="syntaxkeyword">);<br /> </span><span class="syntaxcomment">// > SUExtTest.closest_distance( point_set1, point_set2 )<br /> </span><span class="syntaxdefault">rb_define_module_function</span><span class="syntaxkeyword">( </span><span class="syntaxdefault">mSUExtTest</span><span class="syntaxkeyword">, </span><span class="syntaxstring">"closest_distance"</span><span class="syntaxkeyword">, </span><span class="syntaxdefault">h_closest_distance</span><span class="syntaxkeyword">, </span><span class="syntaxdefault">2 </span><span class="syntaxkeyword">);<br />}<br /> </span><span class="syntaxdefault"></span>It's the
rb_define_*that will make the extension share anything with the Ruby environment - everything else is isolated. -
Hi Guys.
First, I want to say that this project you have started is awesome. I had just decided I needed a ruby extension to get a speed boost for a plug-in project. I found a lot of tutorials on making extensions, but most were for either linux or for MS Visual Studio 6 on Windows. I'm not using either environment. I am on Windows 7 (64bit).
Sooooo, I have followed TBD's example program the best I can.
- I have downloaded the SUExt files.
- I have downloaded the Ruby Installer and Source per the SUExt readme file and installed Ruby.
- I have installed Pelles C.
I tried to open suext.ppj file and Pelles C kept throwing an error about "suext.obj is wrongly located in -path_to_project-". So I tried suext6.ppj and it seemed to be fine. It even seemed to build once I pointed Pelles C to where my Ruby installation was at.
From here I'm a little lost. Am I done? I brought up the irb and typed in: require 'path_to_project/suext.so'
The results were as follows:LoadError: 127: The specified procedure could not be found. - Init_path_to_project\suext
path_to_project\suext.so
from path_to_project\suext.so
from path_to_ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from (irb):1
from :0What am I missing?
Thanks
-Chyn -
When you require a C Extension, do not include the file extension.
So instead of:
require 'path_to_project/suext.so'do:
require 'path_to_project/suext' -
Ok. That certainly changed things a little.
I type:
irb(main):002:0> require 'path_to_project\suext'and get back:
LoadError: 127: The specified procedure could not be found. - Init_path_to_project\suext
path_to_project\suext.so
from path_to_project\suext.so
from path_to_ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from (irb):2
from :0 -
or
/
? -
Both. The '/'s and ''s that are in the post were copied and pasted. I didn't change any of them. Let me know if you want the original output. I just shortened the paths for readability.
-Chyn
-
TIG means try using this --> / <-- instead of that --> ** <-- in your
requirestatement.
Advertisement