Re: components_4_64 python Test_Class Build Fails

[Simon Wright <simon@pushface.org>]

Roger Mc <rogermcm2@gmail.com> writes:

> Mac OSX Monterey
> Trying to build Test_Class fails with
> /System/Volumes/Data/Ada_Source/components_4_64/python-examples/class/test_class
> dyld[89915]: Library not loaded:
> '/Library/Frameworks/Python.framework/Versions/3.8/Python'
>   Referenced from:
> '/System/Volumes/Data/Ada_Source/components_4_64/python-examples/class/test_class'
>   Reason: tried:
> '/Library/Frameworks/Python.framework/Versions/3.8/Python' (no such
> file),
> '/System/Library/Frameworks/Python.framework/Versions/3.8/Python' (no
> such file)
>
> I have set the gpr Linker item to
> -F/usr/local/Cellar/python@3.10/3.10.5/Frameworks
> but this does not fix th problem

Not sure I've ever seen /System/Volumes/Data at the start of a path
before! would have expected just /Ada_Source.

Which compiler are you using?

I don't know what triggers that message about
/Library/Frameworks/Python.framework/Versions/3.8/Python,
you'd need to be running a fairly old compiler - if it's one of mine
it'd have to be GCC 10.1.0, otherwise it won't look in
/Library/Frameworks at all.

If your homebrew setup is like mine, you could just say
-F/usr/local/Frameworks, but you have to say _which_ framework, i.e.
-framework python (or maybe -framework Python, probably better).

I built this using GNATstudio, GCC 12.1.0, x86_64 Monterey 12.6,
Atomic_Access auto,
Development Debug,
Legacy Ada2012,
Object_Dir nested,
Target_OS OSX,
Tasking Multiple,
Traced_Objects Off,
arch x86_64

and it linked without issue. Didn't run,
Error: raised ADA.IO_EXCEPTIONS.USE_ERROR : Failed to load Python DLL "libpython3.so"