Enable auto lightfuncs in ROM example build

svaarala · svaarala · commit d74bc118ae0b · 2016-08-24T04:20:29.000+03:00
diff --git a/util/example_rombuild.sh b/util/example_rombuild.sh
@@ -12,6 +12,7 @@ PYTHON=`which python2 python | head -1`
 make clean
 $PYTHON util/make_dist.py \
 	--rom-support \
+	--rom-auto-lightfunc \
 	--user-builtin-metadata util/example_user_builtins1.yaml \
 	--user-builtin-metadata util/example_user_builtins2.yaml
 
@@ -37,6 +38,7 @@ make duk dukd  # XXX: currently fails to start, DUK_CMDLINE_LOGGING_SUPPORT, DUK
 $PYTHON config/genconfig.py \
 	--metadata config \
 	--output dist/src/duk_config.h \
+	--option-file config/examples/low_memory.yaml \
 	-DDUK_USE_ROM_STRINGS \
 	-DDUK_USE_ROM_OBJECTS \
 	-DDUK_USE_ROM_GLOBAL_INHERIT \
diff --git a/util/example_user_builtins1.yaml b/util/example_user_builtins1.yaml
@@ -139,8 +139,8 @@ objects:
 
   # Example of plain value types supported at the moment:
   #
-  # - Object, function, and accessor types not illustrated here
-  #   (see src/builtins.yaml for examples of those).
+  # - Object, function, lightfunc, and accessor types not illustrated
+  #   here (see src/builtins.yaml for examples of those).
   #
   # - Duktape buffer and pointer types cannot be used by built-in
   #   objects at the moment.
@@ -187,6 +187,16 @@ objects:
         value: "foobar"               # Encode string as UTF-8, then map bytes to U+0000...U+00FF
         attributes: wec
 
+      #- key: "lightfuncType"
+      #  value:
+      #    type: lightfunc
+      #    native: duk_bi_math_object_random
+      #    nargs: 0
+      #    varargs: false
+      #    length: 13
+      #    magic: 0
+      #  attributes: wec
+
   # Object IDs are only resolved when metadata loading is complete, so it's
   # OK to create reference loops or refer to objects defined later (even in
   # a separate YAML file not yet loaded).
