Difference between revisions of "Plugin Publish Process"

Latest revision as of 09:43, 9 April 2015

Use standard waf, make, cmake or autotools projects.
Can't replace CFLAGS, CXXFLAGS and LDFLAGS
Do not use -march=native, -sse etc
If you want to optimize for certain architecture, use the proper #ifdef
If in doubt, just don't mess with compilation flags.
If you have a good reason for not using waf, make or cmake, tell us. The system is being developed.
We need a way to compile the bundle without UI
After building, plugin will be tested for basic errors, any errors found will be reported back
The output ttl will be validated.
The final bundles must have the exact same structure on all architectures

@@ Line 5: / Line 5: @@
 == REST API ==
-- Upload source code to build sytem
+* Upload source code to build sytem
 == Build System ==
-- Use standard waf, make or cmake projects.
+* Use standard waf, make, cmake or autotools projects.
-- Can't replace CFLAGS, CXXFLAGS and LDFLAGS
+* Can't replace CFLAGS, CXXFLAGS and LDFLAGS
-- Do not use -march=native, -sse etc
+* Do not use -march=native, -sse etc
-- If you want to optimize for certain platform, use the proper #ifdef
+* If you want to optimize for certain architecture, use the proper #ifdef
-- If in doubt, just don't mess with compilation flags.
+* If in doubt, just don't mess with compilation flags.
-- If you have a good reason for not using waf, make or cmake, tell us. The system is being developed.
+* If you have a good reason for not using waf, make or cmake, tell us. The system is being developed.
-- We need a way to compile the bundle without UI
+* We need a way to compile the bundle without UI
+* After building, plugin will be tested for basic errors, any errors found will be reported back
+* The output ttl will be validated.
+* The final bundles must have the exact same structure on all architectures
 == Repository ==