Select Git revision
block_alloc.h
-
Fredrik Hübinette (Hubbe) authored
Rev: src/Makefile.in:1.207 Rev: src/backend.c:1.56 Rev: src/block_alloc.h:1.24 Rev: src/builtin_functions.c:1.300 Rev: src/compilation.h:1.20 Rev: src/docode.c:1.80 Rev: src/interpret.c:1.166 Rev: src/interpret.h:1.66 Rev: src/interpret_functions.h:1.31 Rev: src/las.c:1.192 Rev: src/main.c:1.100 Rev: src/object.c:1.145 Rev: src/program.c:1.265 Rev: src/program.h:1.105 Rev: src/testsuite.in:1.323 Rev: src/threads.c:1.139
Fredrik Hübinette (Hubbe) authoredRev: src/Makefile.in:1.207 Rev: src/backend.c:1.56 Rev: src/block_alloc.h:1.24 Rev: src/builtin_functions.c:1.300 Rev: src/compilation.h:1.20 Rev: src/docode.c:1.80 Rev: src/interpret.c:1.166 Rev: src/interpret.h:1.66 Rev: src/interpret_functions.h:1.31 Rev: src/las.c:1.192 Rev: src/main.c:1.100 Rev: src/object.c:1.145 Rev: src/program.c:1.265 Rev: src/program.h:1.105 Rev: src/testsuite.in:1.323 Rev: src/threads.c:1.139
.how_to_create_modules 893 B
o You need a name for your module, for our purposes, let us assume you
want to create the module "modulen".
o Create the dir src/modules/modulen
o Copy the Makefile.src from src/modules/files and modify it.
The Makefile.src need not contain any dependencies.
o You need a testsuite.in, even if it is just an empty one.
o You want a doc dir with BMML or HTML documenation.
o You need a configure.in
Your configure.in should test for ALL features you need.
Do not trust the global configure tests to do things for you.
o All c/c++ files should include "global.h"
o The makefile should create a file called linker_options in the build dir
that contains the needed -l<lib> directives.
o When building the your module the first time you need to:
1) run autoconf
2) do 'make depend' from your build dir
3) re-run configure from your build dir
4) make (in your build dir)