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
e9f87368
Commit
e9f87368
authored
Nov 24, 2012
by
Daniel Bovensiepen
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add usage documentation for mrbgems
parent
b6a10248
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
2 deletions
+14
-2
doc/mrbgems/README.md
doc/mrbgems/README.md
+14
-2
No files found.
doc/mrbgems/README.md
View file @
e9f87368
...
...
@@ -3,6 +3,20 @@
mrbgems is a library manager to integrate C and Ruby extension in an easy and
standardised way into mruby.
## Usage
By default mrbgems is currently deactivated. As long as mrbgems is deactivated
there is no overhead inside of the mruby interpreter.
To activate you have to make the following changes:
*
set
*ENABLE_GEMS*
to
*true*
in
*$(MRUBY_ROOT)/Makefile*
*
define
*ENABLE_GEMS*
in
*$(MRUBY_ROOT)/include/mrbconf.h*
*
activate GEMs in
*$(MRUBY_ROOT)/mrbgems/GEMS.active*
Every activated GEM has to be listed with his absolute path in
*GEMS.active*
. It
is possible to point to an alternative activate file:
*
set
*ACTIVE_GEMS*
to your customized GEM list in
*$(MRUBY_ROOT)/Makefile*
## GEM Structure
The maximal GEM structure looks like this:
...
...
@@ -28,8 +42,6 @@ rules to build a *gem.a* file inside of the GEM directory. Which will be used
for integration into the normal mruby build process.
*README.md*
is a short
description of your GEM.
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
...
...
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