You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have one build script for each platform, they are under `build/platform{ios/mac/android/tizen}` directory.
69
+
We have one build script for each platform, they are under `build` directory.
70
70
71
71
All of them share the same usage:
72
72
@@ -81,15 +81,15 @@ All of them share the same usage:
81
81
- use comma separated library names, for example, `png,lua,jpeg,webp`, no space between the comma.
82
82
83
83
- param2:
84
-
- use `all` to build all the supported arches. For iOS, they are "armv7, arm64, i386, x86_64", for Android, they are "armeabi, armeabi-v7a, x86, arm64", for Mac, they are "x86_64", for Tizen, they are "armv7"
84
+
- use `all` to build all the supported arches. For iOS, they are "armv7, arm64, i386, x86_64", for Android, they are "arm,armv7,arm64,x86", for Mac, they are "x86_64", for Tizen, they are "armv7"
85
85
- use comma separated arch name, for example, `armv7, arm64`, no space between the comma.
86
86
87
87
- param3:
88
88
- release: Build library on release mode. This is the default option. We use `-O3 -DNDEBUG` flags to build release library.
89
89
- debug: Build library on debug mode. we use `-O0 -g -DDEBUG` flag to build debug library.
90
90
91
91
- list:
92
-
- Use these option to list all the supported libraries.
92
+
- Use these option to list all the supported library names and versions.
93
93
94
94
### Build png on iOS platform
95
95
For building libpng fat library with all arch x86_64, i386, armv7, arm64 on release mode:
@@ -126,15 +126,17 @@ cd build
126
126
127
127
3. Pass `--arch=64` to build the libraries with arm64 support.
128
128
129
-
130
-
For other platforms and other libraries, it is more or less the same way except for some minor changes in `--arch` parameter and `-p` parameter.
129
+
Note:
130
+
If you build `webp` with arm64, you will get `cpu-features.h` header file not found error. This is a known issue of Android NDK r10c. You could simply create a empty header file
131
+
named `cpu-features.h` under `{ANDROID_NDK}/platforms/android-21/arch-arm64/usr/include`.
131
132
132
133
133
134
## How to build a DEBUG and RELEASE version
134
135
You can add flag "--mode=[debug | release]" for building DEBUG and RELEASE version.
135
136
136
137
## How to do build clean?
137
-
If you use `./build.sh` to build static libraries, there is no need to do clean. After generating the static library, script will delete the intermediate files.
138
+
You could simply turn on the flag `cfg_is_cleanup_after_build` to "yes" in `main.ini` file.
139
+
After each build, you could also delete the generated folders under `contrib` directory.
0 commit comments