aboutsummaryrefslogtreecommitdiff
path: root/emlink.py
diff options
context:
space:
mode:
authorAlon Zakai <alonzakai@gmail.com>2013-06-28 16:43:34 -0700
committerAlon Zakai <alonzakai@gmail.com>2013-07-03 15:31:04 -0700
commit91e27ccadac6b37826a1a9fc07264597527a18f2 (patch)
tree5495f72a088655259ab9fda1c8d1aa294ecfa80b /emlink.py
parentf5c71a90e79a645ef9e44d6685907b86f8cf3c00 (diff)
link docs
Diffstat (limited to 'emlink.py')
-rw-r--r--emlink.py12
1 files changed, 12 insertions, 0 deletions
diff --git a/emlink.py b/emlink.py
index f37e8253..5985dceb 100644
--- a/emlink.py
+++ b/emlink.py
@@ -10,6 +10,18 @@ Usage: emlink.py [main module] [side module] [output name]
Note that the output file can be used as a main module, so you can link multiple
side modules into a main module that way.
+
+Limitations:
+
+ * Modules cannot be minified (but can be minified after linking)
+ * We duplicate code in some cases, like overlapping names in different modules, and function aliases
+ * We do not handle sharing of global constants across modules, only code (you can make a function to
+ access a constant, if you need that)
+
+Overall, this linking approach should be fast to perform, but generate less-optimal results than
+to link all the bitcode together and build to JS as a single project. Final builds should be
+done in that approach, but during development static linking can avoid recompiling your entire
+project all the time.
'''
import os, subprocess, sys, re