Forum: Ruby How to generate local API documentation?

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
1924957eee03ddf35a65a3e8337f7f20?d=identicon&s=25 Stephan Dale (stephan)
on 2007-06-17 18:37
Hi all.

I'm fairly new to Ruby and I'm trying to generate a local copy of the
docs for the core and standard API, as shown online at

I ran rdoc in my ruby installation directory (/usr/lib/ruby) but it ate
all my memory so I had to kill it.

Next, I ran rdoc in /usr/lib/ruby/1.8, which worked but produced
documentation that doesn't contain details of certain parts of the
language. For example, searching for "kind_of" reveals that the
assert_kind_of (Test::Unit::Assertions) method is documented, but the
kind_of? (Object) method isn't.

How can I generate local documentation?

Many thanks.


P.S. Note that I installed ruby with a doc use flag, so ri works
properly, but I couldn't find any html documentation on my system.
1924957eee03ddf35a65a3e8337f7f20?d=identicon&s=25 Stephan Dale (stephan)
on 2007-06-18 11:10
Well I've found out why I can't generate core API docs using rdoc -
because Ruby is installed as a .so library, hence there are no .rb or .c
for rdoc to parse.

I've downloaded the documentation from but the ruby version is not exactly
the same as the one I've got installed, which could obviously lead to
problems in the future.

Does anyone know whether there's any way I can generate html
documentation from the ri docs or the .so libraries?
97550977337c9f0a0e1a9553e55bfaa0?d=identicon&s=25 Jano Svitok (Guest)
on 2007-06-18 11:27
(Received via mailing list)
On 6/18/07, Stephan Dale <> wrote:
> documentation from the ri docs or the .so libraries?
Download source package (either one for your distribution or the
"upstream" source tar from Unpack anywhere (e.g. you
home dir, /usr/src, /tmp,...). From the top directory (where all the
.c and .h files are located) run rdoc -o output_path, or add more
arguments to finetune the output. When it's finished, you will have
the docs in output_path. The -o argument is important, because rdoc by
default creates directory "doc" but here the one is already created,
so you have to point rdoc to some other place.

1924957eee03ddf35a65a3e8337f7f20?d=identicon&s=25 Stephan Dale (stephan)
on 2007-06-18 12:14
Thank you Jano, that worked a treat!
This topic is locked and can not be replied to.