Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mruby
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Libraries
mruby
Commits
b7911ad1
Commit
b7911ad1
authored
Nov 23, 2012
by
Daniel Bovensiepen
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improve documentation to latest changes
parent
e32077fe
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
7 deletions
+8
-7
doc/mrbgems/README.md
doc/mrbgems/README.md
+8
-7
No files found.
doc/mrbgems/README.md
View file @
b7911ad1
...
...
@@ -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 build a
*
gem.a*
file during this build process. How you are going
to do this is up to you.
have to build a
*
mrb-GEMNAME-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
...
...
@@ -52,8 +52,8 @@ The *Makefile* is used for building a C extension. You should
define
*GEM*
(GEM name),
*GEM_C_FILES*
(all C files) and
*GEM_OBJECTS*
(all Object files). Pay also attention that your
*Makefile*
has to build the object files. You can use
*gem-c-files*
to build a
*
gem.a*
out of your Object code and use
*gem-clean-c-files*
to clean the object files.
*gem-c-files*
to build a
*
mrb-GEMNAME-gem.a*
out of your
Object code and use
*gem-clean-c-files*
to clean the object files.
### Pre-Conditions
...
...
@@ -100,7 +100,7 @@ folder.
The
*Makefile*
is used for building a Ruby extension. You should define
*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-rb-files*
to build a
*
mrb-GEMNAME-
gem.a*
out of your Ruby code and use
*gem-clean-rb-files*
to clean the generated C files.
### Pre-Conditions
...
...
@@ -137,8 +137,9 @@ into the *mrblib* folder and all C files into the *src* folder.
The
*Makefile*
is used for building a C and Ruby extension. You should
define
*GEM*
(GEM name),
*GEM_C_FILES*
(all C files),
*GEM_OBJECTS*
(all Object files) and
*GEM_RB_FILES*
(all Ruby files). You can use
*gem-c-and-rb-files*
to build a
*gem.a*
out of your Object and Ruby code
and use
*gem-clean-c-and-rb-files*
to clean the generated C files.
*gem-c-and-rb-files*
to build a
*mrb-GEMNAME-gem.a*
out of your Object
and Ruby code. Use
*gem-clean-c-and-rb-files*
to clean the generated
C files.
### Pre-Conditions
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment