Restore some files and fix minor issues of SGX platform (#144)

Author: Weining2019

CODE_OF_CONDUCT.md

@@ -1,23 +1,14 @@
-+++
-version = "1.4"
-aliases = ["/version/1/4"]
-+++
-
 # Contributor Covenant Code of Conduct
 
+*Note*: this Code of Conduct pertains to individuals' behavior. Please also see the [Organizational Code of Conduct][OCoC].
+
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to make participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
 ## Our Standards
 
-Examples of behavior that contributes to creating a positive environment
-include:
+Examples of behavior that contributes to creating a positive environment include:
 
 * Using welcoming and inclusive language
 * Being respectful of differing viewpoints and experiences
@@ -27,55 +18,32 @@ include:
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
 * Trolling, insulting/derogatory comments, and personal or political attacks
 * Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ## Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
 
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies within all project spaces, and it also applies when
-an individual is representing the project or its community in public spaces.
-Examples of representing a project or community include using an official
-project e-mail address, posting via an official social media account, or acting
-as an appointed representative at an online or offline event. Representation of
-a project may be further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at otc.community.care@intel.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Bytecode Alliance CoC team at [report@bytecodealliance.org](mailto:report@bytecodealliance.org). The CoC team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The CoC team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the Bytecode Alliance's leadership.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
 
+[OCoC]: ORG_CODE_OF_CONDUCT.md
 [homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+[version]: https://www.contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -36,5 +36,4 @@ We use GitHub issues to track public bugs. Report a bug by [open a new issue](ht
 Code of Conduct
 ===============
 
-This project is governed by the [Contributor Covenant](CODE_OF_CONDUCT.md).
-All contributors and participants agree to abide by its terms.
+WAMR is a [Bytecode Alliance](https://bytecodealliance.org/) project, and follows the Bytecode Alliance's [Code of Conduct](CODE_OF_CONDUCT.md) and [Organizational Code of Conduct](ORG_CODE_OF_CONDUCT.md).

README.md

@@ -1,5 +1,10 @@
 WebAssembly Micro Runtime
 =========================
+
+**A [Bytecode Alliance][BA] project**
+
+[BA]: https://bytecodealliance.org/
+
 WebAssembly Micro Runtime (WAMR) is a standalone WebAssembly (WASM) runtime with small footprint. It includes a few parts as below:
 - A WebAssembly VM core (namely iwasm)
 - The supporting API's for the WASM applications
@@ -57,7 +62,7 @@ Embed WAMR
 
 WAMR can be built into a standalone executable which takes the WASM application file name as input, and then executes it. In some other situations, the WAMR source code is embedded the product code and built into the final product. 
 
-WAMR provides a set of C API for loading the WASM module, instantiating the module and invoking a WASM  function from a native call. 
+WAMR provides a set of C API for loading the WASM module, instantiating the module and invoking a WASM function from a native call. 
 
 See the [doc/embed_wamr.md](./doc/embed_wamr.md) for the details.
 
@@ -66,7 +71,7 @@ WAMR application programming library
 
 WAMR defined event driven programming model:
 - Single thread per WASM app instance
-- App must implement system callbacks: on_init, on_destrory
+- App must implement system callbacks: on_init, on_destroy
 
 
 In general there are a few API classes for the WASM application programming:
@@ -112,7 +117,7 @@ See the [major features releasing history and contributor names](./doc/release_a
 Roadmap
 =======
 
-See the [roadmap](./doc/roadmap.md) to understand what major features are planed or under development.
+See the [roadmap](./doc/roadmap.md) to understand what major features are planned or under development.
 
 Please submit issues for any new feature request, or your plan for contributing new features.
 

core/iwasm/products/linux-sgx/enclave-sample/Makefile

@@ -170,7 +170,7 @@ Enclave/%.o: Enclave/%.cpp
 	@$(CXX) $(Enclave_Cpp_Flags) -c $< -o $@
 	@echo "CXX  <=  $<"
 
-$(Enclave_Name): Enclave/Enclave_t.o $(Enclave_Cpp_Objects)
+$(Enclave_Name): Enclave/Enclave_t.o $(Enclave_Cpp_Objects) libvmlib.a libextlib.a
 	@$(CXX) $^ -o $@ $(Enclave_Link_Flags)
 	@echo "LINK =>  $@"
 

core/shared-lib/platform/linux-sgx/bh_platform.h

@@ -14,7 +14,6 @@
 #include <assert.h>
 #include <time.h>
 #include <string.h>
-#include <strings.h>
 #include <stdio.h>
 #include <stdlib.h>
 #include <math.h>
@@ -66,6 +65,7 @@ typedef void* (*thread_start_routine_t)(void*);
 #define wa_strdup bh_strdup
 
 int snprintf(char *buffer, size_t count, const char *format, ...);
+int strncasecmp(const char *s1, const char *s2, size_t n);
 double fmod(double x, double y);
 float fmodf(float x, float y);
 double sqrt(double x);