-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mac M1 start ios compilation failed #25
Comments
i have the same problem, but cant click on the error message. |
Hey guys, can you try again with v0.7.4, which I just released? For me iOS builds were also working in previous versions, but while working on v0.7.4 I found and fixed a subtle bug in CMake config, which caused PCRE2 and Lighttpd libraries being built only for a single architecture (effectively, for the first one in the list of target archs specified by Xcode). I wonder that was causing problems for you. |
yes, it works for me. thanks :) |
Awesome! 🥳 Thanks for confirming, I'll close the issue then. |
@birdofpreyru And I just downgraded to 0.7.4, then can build the project without any issue
|
@owen800q I don't think I changed anything between v0.7.4 and v0.7.5 that could impact that part of the build; and also your logs read like PCRE2 and Lighttpd sources are just missing in the package. Can it be that v0.7.5 you tried to install directly from the Git repo, and you did not do |
@birdofpreyru yes, you are right, just because when I build the example project, missing running git submodule update --init --recursive ok now, thanks for your responsive feedback |
Yeah... I should update the example's README to mention this step is needed, as the example is setup differently from a real-world project, to use the library code from the parent folder, rather than from node modules installed from NPM. |
i have same issue when i have tried with example codes in this repo or useing v 0.15.1 in my project. device: Apple M1 Pro
|
There should be more specific error details somewhere in the log. Are you sure, it is not #111 you experience (the latest CMake v3.30.0 breaks library builds, because of a presumed regression on CMake side)? |
Thanks yes it was cmake issue. |
The text was updated successfully, but these errors were encountered: