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
Upgrade SQLite #5302
Comments
PR #5348 updates to SQLite 3.39.3 |
fix(#5302): update wxsqlite3 submodule
Are we missing the encryption support? On building I get....
|
Same iss would seem to apply to Linux builds: https://app.circleci.com/pipelines/github/moneymanagerex/moneymanagerex/200/workflows/ef739925-40dd-41ec-a8ec-9b3a028db07d/jobs/199 |
Hmm. Not seeing this in Windows and the AppVeyor builds completed successfully. Might be a CMake issue? |
Ah, perhaps this is why:
Seems we need more work for Mac and Linux. |
Ulrich has just committed wxSQLite3 4.9.1 based on the very latest SQLite release. Perhaps ugrade to this version or is that too bleeding edge ? |
If I change the Mac build to build just for M1 ARM64 then it builds OK. |
You did some work on upgrading wxSQLite3 a few years ago in #3275. Looks like you made more changes in CMakeLists.txt than I did for this update. I admit I'm not a CMake expert. Anything you can see that is missing here? |
I can get it building by forcing in Obviously not optimal, and seemingly no way of doing this without tweaking code. |
I'm also not sure what happens if at compile time it sets this to AES_HARDWARE_NI and the code ultimately executes on a CPU that does not have the instruction set extension. |
@n-stein |
Yes, I will do that. |
No, just a compiler issue.
More work? Not really. Just add the compile time options
when compiling for x86/x86_64 platforms. That should solve the issue.
Disabling AES support when it is actually available is not such a good idea. AES hardware support should be enabled if possible to accelerate the code execution. There is no harm in enabling the AES hardware support, even if the executable later runs on a processor without AES hardware support - the code checks at runtime whether AES hardware support is actually available.
There were only very minor changes to wxSQLite3 and SQLite3 Multiple Ciphers. The underlying SQLite library is thoroughly tested by the SQLite developer team. Therefore upgrading to wxSQLite3 4.9.1 (based on SQLite3 Multiple Ciphers 1.5.4 and SQLite 3.40.0) should not impose noteworthy risks. If critical bugs are detected either in SQLite, SQLite3 Multiple Ciphers, or wxSQLite3, I usually provide new releases fixing them in a timely manner. |
@utelle Thanks for the speedy and concise response. All good, now builds. |
Based on Ulrich's comment I updated to 4.9.1. Shouldn't be any major difference. |
Should look to update SQLite to latest version.
See #1447
Can we update to SQLite >= 3.35.0? Would be nice to be able to use the 'ALTER TABLE ... DROP COLUMN ...' syntax which is not available prior to that version.
The text was updated successfully, but these errors were encountered: