Norberto Ortigoza
norbe****@gmail*****
Sat Jan 20 14:23:15 JST 2007
Hi,
I think the right place for the ri documentation is under /usr/share/ri/1.8/
*site*/OSX.
system is for Ruby´s standard libraries.
I did some changes to the rubycocoa-unstable/pre-install.rb
# frameworks RI documentation
basedstdir =
"#{Config::CONFIG['datadir']}/ri/#{Config::CONFIG['ruby_version']}/site"
unless File.exist?(basedstdir)
command "mkdir -p '#{basedstdir}'"
end
command "cp -R 'framework/bridge-doc/ri/doc/ri/OSX' '#{basedstdir}'"
I also check if the site directory already exist.
I hope this help. Thanks for the documentation!
NoM
On 1/19/07, Fujimoto Hisa <hisa****@fobj*****> wrote:
>
> Hi guys,
>
> Excellent work! This must be applied to creating development
> environments of rubycocoa great improved.
> Eloy, thanks a lot!
>
> On 2007/01/20, at 9:17, Laurent Sansonetti wrote:
> > On Jan 19, 2007, at 1:52 AM, Eloy Duran wrote:
> >
> >> Hello guys,
> >>
> >> I just committed the final patches for AppKit support.
> >> Foundation should be a breeze with the new exceptions module support.
> >>
> >> So AppKit rdoc weighs in a hefty....... 26,3MB :p
> >>
> >> As always suggestions, bugs etc are very welcome.
> >
> > Eloy, this is excellent. I played with it at the end of the afternoon
> > and it's very fun.
>
> > I created a new install.rb phase, 'doc', and attached your script from
> > there (in framework/pre-doc.rb). I also modified gen_bridge_doc.rb to
> > also generate RI documentation.
>
> excellent!
>
> > Some points regarding gen_bridge_doc.rb:
> >
> > - would it be possible to "exit 1" when failure?
> >
> > - would it be possible to not spawn another ruby interpreter process?
> > The problem being that the user may have run install.rb using a custom
> > ruby interpreter, and we may want to use it for all ruby tasks during
> > the build process.
> >
> > I modified the installation phase to copy the HTML files in /
> > Developer/
> > Documentation/RubyCocoa/Frameworks. I didn't copy the RI files yet
> > because I didn't find the right place to put them yet (ri(1) doesn't
> > discover them if they are in /usr/share/ri/1.8/RubyCocoa).
>
> I'm naive about ri. But it works fine by putting the OSX dir into
> /usr/share/ri/1.8/system/, e.g. /usr/bin/ri OSX::NSView
> --
> hisa
>
>
>
> _______________________________________________
> Rubycocoa-devel mailing list
> Rubyc****@lists*****
> http://lists.sourceforge.jp/mailman/listinfo/rubycocoa-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
ダウンロード