[Tutorial] SketchUp Ruby C Extension
-
Uploaded my WIP at: https://bitbucket.org/thomthom/sketchup-ruby-c-extension/
Working on OSX 10.5.
-
-
Think I got one step further. This thread mentions that vcvars32.bat needs to be run from the prompt: http://social.msdn.microsoft.com/Forums/en-US/Vsexpressvc/thread/325b5459-c469-40d0-bf6d-e3356a2f14cd/
And this (http://stackoverflow.com/questions/6622869/problem-with-nmake)
So after I did that I got a different error. Missing crt file...
-
( Apologies for those with the know-how - I will be posting lots of silly stuff as I work through this. Posting to make a record of what I am doing. "Thinking out loud". )
-
Got it working!
Uncommented a
#pragma comment(lib, "crt.lib");I had. TBD's SUExt project had a reference to it. Which is what I based my project on. Seeing how it also referred to#pragma comment(lib, "msvcrt-ruby18.lib");I just tried to see what happened if I removed the ref to crt.lib. Everything worked fine after that point.Now I wonder what the other lines do:
#pragma comment(lib, "kernel32.lib") #pragma comment(lib, "gdi32.lib") #pragma comment(lib, "user32.lib") #pragma comment(lib, "shell32.lib")I'm looking at this tutorial: http://blogs.law.harvard.edu/hoanga/2006/12/14/getting-a-ruby-c-extension-to-compile-on-windows/
It made no reference to any of this. ( what is it? Is it really required? )I'm guessing
#include <windows.h>is required though. -
Now... I'd like to find a way to make any output from extconf.rb and make/nmake put everything is a separate directory - for each platform.
-
Huh... I removed all of that stuff completely, as http://blogs.law.harvard.edu/hoanga/2006/12/14/getting-a-ruby-c-extension-to-compile-on-windows/ made no reference to it at all. Worked fine without. Guess it was required due to the way the Pelles C project was set up...
-
Hey Chris, when we get around to writing up the step by step instructions, are you willing to be a guinea pig?
-
Absolutely!
-
Great!
I'm writing up a Basic example that shows a little more than Hello World.
Then I start on making the step by step Wiki tutorial. I hope people with more know how can fill the in the "why" to much of it. And that people will try it and give feedback on what is unclear and what turns out not to work.
-
@thomthom said:
Though I have a suspicion I need to specify the path to where windows.h is located... Though I don't know where to do so...
To do so via the IDE... from the menu Tools > Options...
.. brings up the "Options" dialog.
Choose "VC++ Directories" from the "Projects and Solutions" branch in the nav tree.
You can see the dirs for catagories by selecting the cat from the "Show directories for:" dropdown control:Executable files:
Include files:
-
Don't forget the "help" topic here:
[Info] C/C++ Ruby extensions & SketchUp plugins
.. and read Adan Nelson's posts (links on the above list.) -
from the info file "win32.readme" in the Ruby C source:
@unknownuser said:You can NOT use a path name [that] contains any white space characters as
the ruby source directory, this restriction comes from the behavior of include directives of NMAKE.
(- you may call it a bug. -) -
Thom:
#pragma comment(lib, "*.lib")adds the libraries to the link phase (that hold imports and functions code)it was a way to make sure that it will compile even if you create a new project and don't use in mine in PellesC.
-
Right'o! Gotcha. Been reading more up on C and GCC.
-
Thanks Thomas for the example.
I do not understand what is 'extconf.rb' for. I have compiled my extension under VC++ 2008 without running the file and without using any makefile... Is it bad ?
-
extconf.rb - external configuration, it generates the makefile to create the extension. using makefile you can automate builds and tests.
-
extconf.rbgenerates a make file you can use withmakeunder OSX andnmakeunder Windows.
http://ruby-doc.org/docs/ProgrammingRuby/html/ext_ruby.html#UG -
@unknownuser said:
I have compiled my extension under VC++ 2008
How big difference is making a Ruby Extension in C++ as oppose to C? ...seeing how Ruby is built in C...
-
@unknownuser said:
extconf.rb - external configuration, it generates the makefile to create the extension. using makefile you can automate builds and tests.
Got it! In VC++ I have to configure it on my own.
@thomthom said:
How big difference is making a Ruby Extension in C++ as oppose to C? ...seeing how Ruby is built in C...
You certainly would need to enclose declaration of the extension initialization with
extern "C":extern "C" { void Init_SX_HelloWorld(); }I am not really an expert, but I guess all the rest would stay same.
Advertisement