FUJIMOTO Hisa
hisa****@fobj*****
Mon Jun 25 10:34:42 JST 2007
Hi the committers
This week I'll do some important work for the source tree and
build/packaging process. So, sorry to please be less commit your code
the repository, if it's not important.
Currently, Eloy may be able to explain about my idea/thinking about it
by English, because he made good effort to read my blog and the ML in
japanese (my native lang) about it last week, and I discussed about it
with him.
Well, Current RubyCocoa has complex dependency of several parts
especially the build and packaging process. The cause of it may be
that the project was started as just extension library as historical
reason, before version 0.4. Now I strongly thought that now is the
time to reconstruct the source tree for make lots of things more
simple. Current RubyCocoa is constructed by the following
moudles/components in fact:
runtime (or core, it's like JRE in Java maybe):
core/framework # RubyCocoa.framework as shared library
core/extlib # ruby libraries for the ruby command
core/tests # testing for the framework depend on extlib
# for a developer of RubyCocoa itself
external (runtime depends on):
external/bridgesupport
external/libffi
devel (for a developer *using* RubyCocoa):
devel/xcode-templates
devel/examples
tools (for a developer *using* RubyCocoa maybe):
tools/standalonify
tools/rb_nibtool
tools/gen_bridge_doc
tools/rubycocoa
# this tree is current idea, it's very mutable at now.
Tools may be embed the framework at the packaging phase rather than
build process. I guess it's better for orthogonality.
the point; boost up the orthogonality of each module/component for
build and packaging process. I'm going to start reconstructing soon on
the branches/rubycocoa-reconstruct-20070625 on the repository.
Maybe I can't reply enough, because The wrting, especially by
English, may decrease down sometimes my concentration. sorry ;)
thanks
--
hisa