WWW-www.enlightenment.org pushed a commit to branch master.
http://git.enlightenment.org/website/www-content.git/commit/?id=635eeb48cb09ebaca1396342b579b87b8341ddbe
commit 635eeb48cb09ebaca1396342b579b87b8341ddbe
Author: Felipe Magno de Almeida <felipe.m.alme...@gmail.com>
Date: Wed Sep 9 19:52:13 2020 -0700
Wiki page Compiling_the_native_Windows_EFL changed with summary [] by
Felipe Magno de Almeida
---
pages/Compiling_the_native_Windows_EFL.txt | 29 ++++++++++++-----------------
1 file changed, 12 insertions(+), 17 deletions(-)
diff --git a/pages/Compiling_the_native_Windows_EFL.txt
b/pages/Compiling_the_native_Windows_EFL.txt
index 0e8546ea1..96cd06c6d 100644
--- a/pages/Compiling_the_native_Windows_EFL.txt
+++ b/pages/Compiling_the_native_Windows_EFL.txt
@@ -109,9 +109,17 @@ To manage dependencies with vcpkg:
This way vcpkg will download, setup and install all of those dependencies.
-4.3. Set vcpkg toolchain file for meson
+----
+
+=== 7 - Compiling EFL ===
+
+Clone the [[https://github.com/expertisesolutions/efl.git|EFL Native Windows
Repository]] repository.
+
+<note>
+The cmake found by meson still has to find the dependencies, but vcpkg's
installed libraries aren't found by default. For that, [vcpkg's
docummentation](https://github.com/microsoft/vcpkg#using-vcpkg-with-cmake)
recommends using the cmake argument ''CMAKE_TOOLCHAIN_FILE'' to point to
vcpkg's toolchain file.
-The cmake found by meson still has to find the dependencies, but vcpkg's
installed libraries aren't found by default. For that, [vcpkg's
docummentation](https://github.com/microsoft/vcpkg#using-vcpkg-with-cmake)
recommends using the cmake argument ''CMAKE_TOOLCHAIN_FILE'' to point to
vcpkg's toolchain file. In current EFL build, to do that, you may set the
variable ''VCPKG_TOOLCHAIN_FILE'' which is automatically sent to meson when
calling ''configure.bat''.
+''configure.bat'' uses the ''vcpkg_toolchain_file'' environment variable to
pass the toolset as parameter to CMake from Meson.
+</note>
Create an environment ''env.bat'' file in EFL's root (e.g.
''C:/Users/Someone/efl/env.bat'') before calling ''configure.bat'', containing
for example (considering vcpkg is installed in ''C:/Users/Someone/vcpkg''):
@@ -121,18 +129,5 @@ path-to-efl> echo "set
vcpkg_toolchain_file=C:/Users/Someone/vcpkg/scripts/build
This file is run everytime by ''configure.bat'' as a special way to set local
custom environment variables.
-----
-
-=== 7 - Compiling EFL ===
-
- * Choose a directory to clone **EFL** repository;
- * Clone the [[https://github.com/expertisesolutions/efl.git|EFL Native
Windows Repository]] repository.
- * Open Visual Studio's **Developer Command Prompt** in the EFL directory
and run the following command:
- * <code>> configure.bat</code>
- * 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:
- - Delete the ''build'' directory;
- - Delete every subdirectory inside ''subprojects'' (**NOTE: Do NOT
delete the .wrap files!**)
- * After you finish, rerun **configure.bat**, execute **build.bat**:
- * <code>> build.bat</code>
\ No newline at end of file
+<code>efl-path> configure.bat --prefix=C:\efl</code>
+<code>efl-path> build.bat</code>
--
