Embarcadero/python4delphi

Non-Windows FMX won't install on Community Edition

Closed this issue · 8 comments

[Moved here from main repo]

The Multi-Installer just throws up a dialog box saying there's no install directory when run

Installing via Delphi from project group compilation fails as the non-Windows targets try to compile source that includes the Windows unit

The result of this is that no down-stream projects (Python Environments, Lightweight wrappers, P4D Data Sciences can be installed on non-Wondows targets either).

I will stress that this is observed using Delphi 10 Sydney Community Edition so if you have a 'Real' Delphi on system this may result in different experiences.

Suggested replication - use a clean Windows install and Delphi Community Edition, easiest way to achieve this without spare kit is to use a VMWare Player with fresh install of Win10 + Delphi Community then this try to install this and dependant libraries.

If resolution is found very clear documentation would help (I'd write it myself if I could get the stuff to install)

@peardox,

please, can you update your stream and try again?

Better but still not perfect

MacOSX now appears OK with one warning...
[dccosx64 Warning] python.dpk(24): W1002 Symbol 'IMAGEBASE' is specific to a platform

Android, however, fails at PythonFMX causing the inability to build the branch labelled libPythonFmx270.a as Python can't be found. I notice that the generated lib directory has Python.o which remains after a Clean implying something is half-installed (Python.dcu doesn't make it to lib).

The branch labelled libPython270.a builds perfectly

I will go and try the down-stream components for MacOSX to see if they build (seems likely now)

Is the Android dcp folder included in your path?

image

image

The IMAGEBASE warning is expected, though.

OK - That fixed things - needs to be mentioned in docs in case not present...

This is more Delphi related, but sure, it worth mentioning.

Let me know when we can close this issue 💪

This is more Delphi related, but sure, it worth mentioning.

We're in a Embarcadero repo so it seems quite important here (less so in Main I guess)

Anyway - all seems OK so closed

Yes, you're right. I will provide this info in the docs.