Thread: [Rubycocoa-talk] [ANN] RubyCocoa 0.4.1 for Tiger (10.4)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi all,

RubyCocoa 0.4.1 binary package (dmg) for Tiger (Mac OS X 10.4) is here:

  http://prdownloads.sourceforge.net/rubycocoa/RubyCocoa-0.4.1-tiger.dmg

thanks,
-- 
FUJIMOTO Hisa

On 1 Jun 2005, at 13:33, FUJIMOTO Hisa wrote:

> RubyCocoa 0.4.1 binary package (dmg) for Tiger (Mac OS X 10.4) is  
> here:
>
>   http://prdownloads.sourceforge.net/rubycocoa/RubyCocoa-0.4.1- 
> tiger.dmg
>

What will happen if this framework is used on Panther?

My script that bundles up RubyCocoa inside an application copies the  
installed RubyCocoa framework for distribution. Will it mean the  
application won't work on Panther?

Thanks
Jonathan

At Wed, 1 Jun 2005 13:51:18 +0100,
Jonathan Paisley wrote:
> On 1 Jun 2005, at 13:33, FUJIMOTO Hisa wrote:
> 
> > RubyCocoa 0.4.1 binary package (dmg) for Tiger (Mac OS X 10.4) is  
> > here:
> >
> >   http://prdownloads.sourceforge.net/rubycocoa/RubyCocoa-0.4.1- 
> > tiger.dmg
> >
> 
> What will happen if this framework is used on Panther?

Rubycocoa of the current Tiger binary package is (dynamic) linked to
/usr/lib/libruby.dylib. So it may be depend on /usr/lib/libruby.dylib
on target environment:

  $ cd /tmp && mkdir foo && cd foo
  $ gzcat /Volumes/RubyCocoa-0.4.1-tiger/RubyCocoa-0.4.1.pkg/Contents/Archive.pax.gz | \
      pax -r ./Library/Frameworks/RubyCocoa.framework/Versions/A/RubyCocoa
  $ otool -L ./Library/Frameworks/RubyCocoa.framework/Versions/A/RubyCocoa
  ./Library/Frameworks/RubyCocoa.framework/Versions/A/RubyCocoa:
	@executable_path/../Frameworks/RubyCocoa.framework/Versions/A/RubyCocoa \
           (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa \
           (compatibility version 1.0.0, current version 11.0.0)
	/usr/lib/libruby.1.dylib (compatibility version 1.8.0, current version 1.8.2)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.0.0)

It's difficult to decide which (and how) libruby is linked for *binary
package* when different requirement exists. It may be better that you
build rubycocoa by yourself tuned for your purpose.

thanks,
-- 
FUJIMOTO Hisa

On 1 Jun 2005, at 15:54, FUJIMOTO Hisa wrote:
>
> It's difficult to decide which (and how) libruby is linked for *binary
> package* when different requirement exists. It may be better that you
> build rubycocoa by yourself tuned for your purpose.
>

Thanks for the info.

Thinking about it further, I realise my question was more like this:

I know that during the build process the installed AppKit header  
files are parsed to generate wrappers. Will the built RubyCocoa be  
susceptible to (Cocoa, not Ruby) link failures on 10.3 if compiled on  
Tiger? If so, is there a way to persuade it to build against the  
10.3.9 SDK?

Thanks.
Jonathan

Thread: [Rubycocoa-talk] [ANN] RubyCocoa 0.4.1 for Tiger (10.4)

rubycocoa-talk