Closed JoHuang closed 1 year ago
BTW, if I don't need this extension
Particle3D
, how can I skip it when building?
For future reference, just search the cmake files (*.txt
and *.cmake
) to find that information very quickly. In this case, a search for "particle3d" would have led you to this:
option(AX_ENABLE_EXT_PARTICLE3D "Build extension Particle3D" ON)
To turn it off, add this to the top of your project CMakeLists.txt
:
set(AX_ENABLE_EXT_PARTICLE3D OFF CACHE BOOL "Build extension Particle3D" FORCE)
Delete the file [build_folder_name]/CMakeCache.txt
if you've already generated the project, otherwise the cached value of AX_ENABLE_EXT_PARTICLE3D
may not be updated.
After several trials, it always stuck at 91%, but the last file shown on the logs was random. Not always the same file.
build wasm require large system resource, recommand use PC with high-performance mult-core and 32GB+ memory
close this not issue
I thought MacBook Pro with M1 Pro chip (10-core CPU) (RAM 16GB) is quite high-performance device. Is it normal that stuck for hours even for this device?
Steps to Reproduce:
axmol build -p wasm
Issue:
It stuck here, and CPU keep 100% (even mouse cursor is laggy). I waited it for more than half hour, and had to interrupt (ctrl + c) to stop it.
BTW, if I don't need this extension
Particle3D
, how can I skip it when building?Thanks