kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

I pushed Dick's original patch so I expect to see some autobuilders
complaining about osx build errors any minute.  Please try disabling the
python scripting to see if that resolves the issue on osx builds.  It
sounds like that should be the default until we can resolve the issues
with python support on osx.

Thanks,

Wayne

On 2/21/2017 3:28 AM, Bernhard Stegmaier wrote:
> 
>> On 21 Feb 2017, at 00:31, Wayne Stambaugh <stambaughw@xxxxxxxxx
>> <mailto:stambaughw@xxxxxxxxx>> wrote:
>>
>> On 2/20/2017 6:27 PM, Nick Østergaard wrote:
>>> 2017-02-20 23:48 GMT+01:00 Bernhard Stegmaier
>>> <stegmaier@xxxxxxxxxxxxx <mailto:stegmaier@xxxxxxxxxxxxx>>:
>>>> How is this done on Windows?
>>>> You also don’t have a global filesystem with one Python there where
>>>> you just
>>>> copy it into the right place… where does the Windows installer put those
>>>> files and how do you use them from some installed Python? Are there
>>>> issues
>>>> with library paths of the library dependencies that come with KiCAD when
>>>> used from an external Python?
>>>>
>>>
>>> I am not aware of any issues with it on windows, but I don't really
>>> use windows.
>>>
>>> People have requested to include pip with the windows install, and
>>> that is done now, so I assume that at least something works.
>>>
>>> I am not sure if the user uses the shell inside pcbnew or calls the
>>> python bundled with the installer. The file system layout is basically
>>> as on linux, just inside the install destination folder.
>>
>> Would something like this work on osx rather than trying to fit into an
>> existing python install?  It might prove to be more reliable.  At least
>> you would always have a known python build.
> 
> Yes, that’s probably the only way to do it in a safe way for the bundle
> (and, as Adam said how Apple requires it).
> Currently only wxPython packages and the pcbnew .so are copied into the
> bundle.
> There is no (matching) python installation contained/copied.
> 
> This seems to be sufficient to at least run the python console from
> inside pcbnew with some external python installation - if the python
> version used to build the bundle and the one on the target system are
> compatible. 
> However, the last time I tried it the python console was really unusable
> for me, because you couldn’t even type some keys (menu hotkeys always
> trigger the menu action).
> Don’t know if that has been fixed meanwhile.
> 
> So, I think this whole python stuff needs a big overhaul on macOS for
> both types of scripting.
> I will work on it when I have some spare time.
> If someone else is going to work on that please drop me a note, so that
> we don’t do it twice…
> 
> 
> Regards,
> Bernhard
> 
>