This is an automated email from the git hooks/post-receive script.
git pushed a commit to branch master
in repository www-content.
View the commit online.
commit 7d4ab6b1ececa4accf05c0df139de55fb8317fc4
Author: nekobit <hylandb...@gmail.com>
AuthorDate: Tue Oct 8 08:52:03 2024 -0700
Wiki page Compiling_the_native_Windows_EFL changed with summary [Add/remove some notes] by nekobit
---
pages/Compiling_the_native_Windows_EFL.txt | 30 ++++++++++++++----------------
1 file changed, 14 insertions(+), 16 deletions(-)
diff --git a/pages/Compiling_the_native_Windows_EFL.txt b/pages/Compiling_the_native_Windows_EFL.txt
index bb059b683..18ac928c1 100644
--- a/pages/Compiling_the_native_Windows_EFL.txt
+++ b/pages/Compiling_the_native_Windows_EFL.txt
@@ -3,12 +3,6 @@
The steps below correspond to the preparation of the **EFL native windows** compilation environment.
-<note important>
-**[Note!]**
-
-These steps were tested on Windows server 2019 64bit and Windows 10 64bit.
-</note>
-
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
@@ -78,7 +72,7 @@ If the command is not recognized, finish the environment variables step and try
3.2. When installing, it is important to select at least one of the options below:
>[x] Add LLVM to the system PATH for all users.
->[x] Add LLVM to thr system PATH for current user.
+>[x] Add LLVM to the system PATH for current user.
In this tutorial, we install it in ''C:\Program Files\LLVM''.
@@ -86,7 +80,11 @@ In this tutorial, we install it in ''C:\Program Files\LLVM''.
=== 4. VCPKG ===
-Vcpkg is not strictly necessary, since you could install each of the dependencies separately and make sure cmake finds it, but it is a more convenient way to do so and it is supported by EFL's current build system.
+<note important>
+You must manually install Vcpkg using the installation guide linked below. Manifest support is required when using the Visual Studio 2022 Vcpkg build, which won't let you install all the packages in one line.
+</note>
+
+Vcpkg is not strictly necessary, but highly recommended. You could install each of the dependencies separately and make sure cmake finds it, but it is more convenient way to let Vcpkg handle this, as it is supported by EFL's current build system.
To manage dependencies with vcpkg:
@@ -96,13 +94,13 @@ To manage dependencies with vcpkg:
4.2. Install the following dependencies for x64 windows:
- - Curl;
- - OpenSSL;
- - Freetype;
- - Check;
- - Libpng;
- - Libjpeg-turbo;
- - Zlib.
+ - Curl;
+ - OpenSSL;
+ - Freetype;
+ - Check;
+ - Libpng;
+ - Libjpeg-turbo;
+ - Zlib.
<code>
c:\vcpkg-path> vcpkg install openssl:x64-windows freetype:x64-windows check:x64-windows libpng:x64-windows zlib:x64-windows libjpeg-turbo:x64-windows curl:x64-windows
@@ -119,7 +117,7 @@ Check that all dependencies were installed at ''installed\x64-windows\bin''.
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, [[https://github.com/microsoft/vcpkg#using-vcpkg-with-cmake|vcpkg's docummentation]] recommends using the cmake argument ''CMAKE_TOOLCHAIN_FILE'' to point to vcpkg's toolchain file.
''configure.bat'' uses the ''vcpkg_toolchain_file'' environment variable to pass the toolset as parameter to CMake from Meson.
</note>
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
