Ruby 1.8.6
-
RUBY_VERSION responds with 1.8.6 in SU 8 and 1.8.5 in SU 7
We build C-code which interfaces to SketchUp using Ruby 1.8.5. If we upgrade to 1.8.6 as well, will our apps still work with SU 6 and SU 7?
Has anyone else tried this?
-
Vertex Tools where I built a Ruby C Extension works fine without any problems in SU8. (Didn't even think of that until you mentioned it.)
-
Oh - sorry. You mean if you build the C in 1.8.6. - no, haven't tried that.
-
Actually, I've had Ruby 1.8.6 installed all the time - it was never matching SU's version. So I guess the answer is, yes it should work.
-
@al hart said:
RUBY_VERSION responds with 1.8.6 in SU 8 and 1.8.5 in SU 7
Careful Al, prior to v8, the Ruby versions on Mac and PC differed.
For SU 7.x --
PC/WIN: Ruby v 1.8.0 (initial) RUBY_RELEASE_DATE = 2003-08-04
Mac/OSX: Ruby v 1.8.5 (initial) RUBY_RELEASE_DATE = 2006-08-25Both of these releases predated the constant RUBY_PATCHLEVEL, but you can still use RUBY_VERSION, and RUBY_RELEASE_DATE.
Nowadays they (the Ruby Core folks,) are calling the initial releases PATCHLEVEL "p0" (or integer 0.)@al hart said:
We build C-code which interfaces to SketchUp using Ruby 1.8.5. If we upgrade to 1.8.6 as well, will our apps still work with SU 6 and SU 7?
For simplicity, you may hope so. Be aware some techies.. update their Ruby DLLs on PC to higher patch levels, I've even run 7.1 and 8 with the highest v 1.8.7 patchlevel.
However... if they are competant enough to know how to change it for their own use.. they are competant enough to change it back to conform to any requirement of Twilight when they wish to run your renderer.So.. you will need to become more aware of the Ruby version and Patch Level... in the short term, in order to not be deluged with complaints.. you can trap unsupported Ruby Versions and Patch Levels, and display a warning dialog. You can add a "No Support" clause to the documentation, for Ruby versions above 1.8.6 and Patch Level such and such.
Or Find a modular way to support these by loading certain DLLs based on tesing RUBY_VERSION, and RUBY_RELEASE_DATE (and RUBY_PATCHLEVEL if release after 2006-12-25)
Many of us users and developers want to catch up to the rest of the world, and use a Ruby in the 1.9.x branch. Ruby 1.9.1 is up to p430, and v 1.9.2-p0 has just been released.
It's way past time Sketchup became Ruby Version Agile ! -
Using SketchUp Pro (Version 8.0.3161) on Mac OS X, I'm seeing a RUBY_VERSION of "1.8.5". Wazzup?
-r
-
@richmorin said:
Using SketchUp Pro (Version 8.0.3161) on Mac OS X, I'm seeing a RUBY_VERSION of "1.8.5". Wazzup?
I really hope this is not true. (Not that I wish you to be wrong Rich,) but we were led to believe v8 had updated Ruby to 1.8.6-p287 and no mention was made that the OSX edition was left "in the dust" with Ruby at 1.8.5(initial).
-
I thought SU under OSX used the version installed in the OS...?
-
No, its uses the Ruby that is specified in the Framework of the SU8 Package.
On OSX using SU8, I too get 1.8.5
-
Oh, just looking at the files in the OSX SU8 package I see Google dropped support for PowerPC Macs...
Oh well
-
@adamb said:
... I see Google dropped support for PowerPC Macs...
Yes.. that was in the Release Notes.
They didn't say why... but it may have been an endian issue.
-
@dan rathbun said:
@adamb said:
... I see Google dropped support for PowerPC Macs...
Yes.. that was in the Release Notes.
They didn't say why... but it may have been an endian issue.
"The PPC decision was driven by Apple - they're done with PPC, so we are, too. It greatly decreased the size of our installer."
from this thread:
http://forums.sketchucation.com/viewtopic.php?p=270078 -
Hmmmm.. so when Microsoft stops supporting XP SP3 soon will SU end support as well?
What about about when Microsoft only supports 64bit Windows ?
(Yes I'm being a bit sarcastic.)
Advertisement