Jump to content

PetrifiedDelhpi

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. PetrifiedDelhpi

    iOS 17

    Lagging behind? iOS 17 was released a year ago, and still no debugging support. My employer tries to move out from Delphi, but there is some 500 000 lines of Delphi code.
  2. PetrifiedDelhpi

    iOS 17

    Delphi on iOS could be called Deprecated. Had to buy an iPhone X, to enable debugging. (Apple doesn't support degrading to older versions of iOS, signing is removed within days.)
  3. I tried to go that way before I realized that FireDAC.Phys.SQLiteWrapper.Stat is totally unnecessary on iOS. I don't have Delphi at home, but there are somewhere in the units or inc files the linking of the static library used by Delphi. Delphi can also link statically to a "dynamic" library if it is available, at least on Windows. http://docwiki.embarcadero.com/RADStudio/Athens/en/Connect_to_SQLite_database_(FireDAC) btw, I don't believe that the dynamic linking of the proprietary iOS lib works, although it is mentioned on that page
  4. PetrifiedDelhpi

    Android - debugging

    Apple doesn't support reverting to an older version of iOS, usually they remove signing of older versions withing days of a new release.
  5. PetrifiedDelhpi

    Android - debugging

    Debugging an iOS app is a worse nightmare. For starters, debugging does not work at all with iOS 17. Had to buy an iPhone X, that is limited to version 16.8. Breakpoints in Delphi's own iOS units don't work,
  6. PetrifiedDelhpi

    Android - debugging

    Delphi (whater version since XEx) needs some magic (restart or killing.) Changing target usually leads to point that the background service that handles, for example, to going to the implementation, stops working properly. Or exception in bpl80.dll or something. The service works perfectly with Visual Studio Code, but that can't handle project settings, or compiling (that could be implemented.) One would wish a more stable editor.
  7. I had the same problem in an own application, and with Kastri FCMRebooted demo. I just removed FireDAC.Phys.SQLiteWrapper.Stat, and then FireDAC uses dynamic linking, and probably uses the native sqlite3 dylib. The database still works. ChatGPT suggested using TFDPhysSQLiteDriverLink.Create(nil).VendorLib := ''; to use the native library, but that didn't help with statical linking. Another option would to edit the linking of the static library in the unit, to use the iOS native lib. EDIT: on Android, you have to use the SQLiteWrapper.Stat unit, or deploy the dynamic lib..
  8. PetrifiedDelhpi

    What's the general opinion on v12?

    Delphi has been really unstable since XEx. No difference here. For example, if there is no connection to PAServer when saving preferences, instant freeze, only killing helps. Changing of target leads to instant unstability, at least debugging is killed. Not to speak of iOS 17... no debugging.
×