enlightenment/www-content
enlightenment
/
www-content
6
0
Fork 2
Code Issues Pull Requests Projects Releases Wiki Activity

Wiki page Compiling_the_native_Windows_EFL changed with summary [Minor typos] by Joo Paulo Taylor Ienczak Zanette

This commit is contained in:
João Paulo Taylor Ienczak Zanette 2020-08-18 12:30:27 -07:00 committed by www-data
parent 01bf639b12
commit 38f13b7c8f
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
pages/Compiling_the_native_Windows_EFL.txt
View File

@ -3,10 +3,12 @@
The steps below correspond to the preparation of the **EFL native windows** compilation environment.
> [Note!]
> These steps were tested on Windows server 2019 64bit and Windows 10 64bit.
<note important>
**[Note!]**
These steps were tested on Windows server 2019 64bit and Windows 10 64bit.
</note>
Except for topic 7 (Environment variables) that can be consulted during the process of preparing the environment, the ideal is that the steps are fulfilled in the proposed order.
Except for topic 6 (Environment variables) that can be consulted during the process of preparing the environment, the ideal is that the steps are fulfilled in the proposed order.
- Visual studio installation
- Meson
@ -15,7 +17,6 @@ Except for topic 7 (Environment variables) that can be consulted during the proc
- Environment variables
- Compiling the EFL
----
=== 1 - Visual studio installation ===
@ -124,7 +125,7 @@ In case you're using a custom OpenSSL installation (not the one from vcpkg), you
----
===8 - Compiling the EFL===
=== 7 - Compiling EFL ===
* Choose a directory to clone **EFL** repository;
* Clone the [[https://github.com/expertisesolutions/efl.git|EFL Native Windows Repository]] repository.
@ -133,7 +134,7 @@ In case you're using a custom OpenSSL installation (not the one from vcpkg), you
* If an error occurs in this step, it is generally due to opening a regular Command Prompt (instead of VS's Developer Command Prompt). In that case, you may manually setup the developer prompt by entering the following command:
* <code> > "C:\Program Files (x86)\Microsoft Visual Studio\<VS version>\<VS edition>\VC\Auxiliary\Build\vcvars64.bat"</code>
* If it still does not work, try to:
1. Delete the ''build'' directory;
2. Delete every subdirectory inside ''subprojects'' (**NOTE: Do NOT delete the .wrap files!**)
- Delete the ''build'' directory;
- Delete every subdirectory inside ''subprojects'' (**NOTE: Do NOT delete the .wrap files!**)
* After you finish executing **configure.bat** execute **build.bat**:
* <code>>build.bat</code>