-
Notifications
You must be signed in to change notification settings - Fork 81
Make 64bit compliant #21
Comments
It should be easy enough to upgrade. I don’t think Superdb is actively maintained any more, but feel free to toss in a pull request and I’ll review it. |
Just tried adding 64bit to architectures in SuperDBCore I get a bunch of these errors: for example on this line: adding sel_getName... fixes the warning I don't really understand what is going on under the hood is this the right path??? |
@Sohojoe Unfortunately I’m not sure, as most of the F-Script stuff wasn’t written by me. A lot of it was written before the ObjC 2.x runtime functions were made available so my guess is it might take more effort. I take back my earlier statement this morning about this being an easier task. I’d forgotten about the arm64 Also note there were already lots of warnings in the project (due to F-Script) before arm64, unfortunately. |
I was able to make some progress using object_getClass() - this was simple... I've hit a new problem with some assembly code - it doesn't like the @ (used for comments) - I found [see html link at bottom of post] on SO I'm not sure if it just needs a different syntax for comments of if the whole of the assembly language changed for 64bit - I don't have experience of assembly in arm - do you have insight?? these are the errors /Users/apple/development/superdb/SuperDBCore/SuperDBCore/iphone-sysv.S:62:1: error: unexpected token at start of statement |
any word on this? |
@mralexgray Sorry no not really. The project hasn’t been maintained in a while, unfortunately. |
I'm also interested in 64-bit version, we'll wait for it. |
Since it has been such a long time since the project is not updated, and there are no plan for the developers to add support for 64 bits architecture, I would suggest to make this quickly known in the readme so that people do not waste too much time in trying to make this run. Thanks for the effort in any case. |
The library requires the main app to be NON 64 bit...
The text was updated successfully, but these errors were encountered: