From a76647ead7d8af214de46a2eb4185b979964c88b Mon Sep 17 00:00:00 2001 From: Daniel Bovensiepen Date: Thu, 22 Nov 2012 20:44:34 +0800 Subject: Clean build documentation for mrbgems a bit more --- doc/mrbgems/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/mrbgems/README.md b/doc/mrbgems/README.md index 480e034a5..e1de425f1 100644 --- a/doc/mrbgems/README.md +++ b/doc/mrbgems/README.md @@ -33,8 +33,8 @@ All GEMs have to be located under *$(MRUBY_ROOT)/mrbgems/g/*. ## Build process mrbgems will call *make* to build and *make clean* to clean your GEM. You -have to create *gem.a* file during the build process. How you are going -to do this is you decision. +have to build a *gem.a* file during this build process. How you are going +to do this is up to you. To make your build process more easier and more standardized we suggest to include *mrbgems/Makefile4gem* which defines some helper rules. In @@ -99,7 +99,7 @@ classes or add new ones in this way. Put all Ruby files into the *mrblib* folder. The *Makefile* is used for building a Ruby extension. You should define -define *GEM* (GEM name) and *GEM_RB_FILES* (all Ruby files). You can use +*GEM* (GEM name) and *GEM_RB_FILES* (all Ruby files). You can use *gem-rb-files* to build a *gem.a* out of your Ruby code and use *gem-clean-rb-files* to clean the generated C files. -- cgit v1.2.3