-
Notifications
You must be signed in to change notification settings - Fork 167
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
Using Compiled version of JavascriptCore library/framework gives compile time error #25
Comments
+1 to this. Tried all kinds of variations of JavascriptCore and cannot compile. My issue is mainly around arm64, but tried armv7 with no success either |
All architectures (armv7, armv7s, arm64, i386, x86_64) compile cleanly for me with XCode 6.1 installed. Are you using the |
+1 the same issue. JavaScriptCore can be built successfully, but the problem lies in compiling working project using the pre-compiled JavaScriptCore library, with Xcode 6.1.1. No luck with one built by Xcode 6 or copied from Ejecta project. |
+1, same issue.
|
A workaround here. We built this project for arm64 slice in order to build our project for Standard architectures (armv7, arm64). But since Apple's arm64 devices all start at least iOS 7, we should be safe to drop this project in favor of iOS 7 built-in JavaScriptCore framework for arm64:
So this project could be retired. Thanks for the contribution so far. |
@denkeni: Nice solution, thanks. |
Sadly, we still need this custom JSC version for Ejecta, because the official JSC doesn't yet have an API to read/write Typed Arrays. See: https://bugs.webkit.org/show_bug.cgi?id=120112 No idea what's going wrong with compilation, though. Last time I tried it, everything compiled smoothly. |
I am able to successfully build JSC library and while trying to use it in my project gives below error
I have verified all the required architecture of JSC and my project and it is common. But still while using JSC library I am having above error. Can you please suggest what is problem in above errors?
The text was updated successfully, but these errors were encountered: