-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Project does not build #662
Comments
Xcode Version 6.4 (6E35b) |
Try installing Carthage.pkg from https://github.com/Carthage/Carthage/releases ./checkout.sh after installing necessary dependencies open the Client.xcodeproj file from finder with XCode. |
Same issue here. Where does the sqlite3.c file dependency comes from? The Sqlite Cipher project does not seem to contain any sqlite3.c file nor does the firefox for iOS repository. By the way, but this is more related to Carthage, I had to manually fetch dependencies as Carthage segfaults on my machine with the Firefox for iOS Cartfile. |
I managed to make it compile: I first opened the sqlcipher Xcode project, built the sqlcipher target then reopened the Firefox for iOS project and it passed. |
I forgot to mention that I used the latest sqlcipher project for that. However, the default configuration seems to not be good for Firefox. I got back to the version delivered with Firefox. I had to build the sqlcipher dependency (amalgamation) manually. In a Terminal, in the ThirdParty/sqlcipher directory, type: ./configure --enable-tempstore=yes --with-crypto-lib=commoncrypto CFLAGS="-DSQLITE_HAS_CODEC -DSQLITE_TEMP_STORE=2"
make sqlite3.c The command is taken from the amalgamation target Run Script build phase of the sqlcipher Xcode project. |
This was fixed: https://bugzilla.mozilla.org/show_bug.cgi?id=1182620. |
I get compiler errors (missing file) when trying to build the project for a real device:
I have tried to build it exactly as said on the GitHub page, and I'm building using Xcode.
If I try to run on the simulator instead I get a very similar error, just using another location:
Did anybody else have this problem?
The text was updated successfully, but these errors were encountered: