← Back to team overview

kicad-developers team mailing list archive

Re: Patch to compile _pcbnew.kiface only once

 

Thank you Nick!

On 3/17/2017 10:17 AM, Nick Østergaard wrote:
> I have disabled scripting.
> 
> 2017-03-17 15:04 GMT+01:00 Chris Pavlina <pavlina.chris@xxxxxxxxx>:
>> On Fri, Mar 17, 2017 at 10:01:20AM -0400, Wayne Stambaugh wrote:
>>> On 3/17/2017 9:56 AM, Chris Pavlina wrote:
>>>> On Fri, Mar 17, 2017 at 08:08:28AM -0400, Wayne Stambaugh wrote:
>>>>> Would someone please disable python scripting on OSX builds so we can
>>>>> provide nightly builds until we can find a solution for the python issue.
>>>>>
>>>>> On 3/16/2017 4:56 PM, Jean-Paul Louis wrote:
>>>>>> I agree 150% with Bernhard.
>>>>>>
>>>>>> A disabled Python is 150% better than no new build at all.
>>>>>>
>>>>>> I do not understand why OS X users are considered second class citizens.
>>>>>
>>>>> I'm sorry you feel this way but this has nothing to do with OSX being
>>>>> second class and every thing to do with the simple fact that there are
>>>>> far more windows and linux devs so things tend to get fixed faster on
>>>>> those platforms.
>>>>
>>>> In his defense, that's kinda the definition of a second class citizen.
>>>> Not that it's our _fault_, we don't have many developers for macOS. But
>>>> that doesn't make it not true. :\
>>>
>>> I wish I had a better answer to this issue but I don't.
>>
>> Same here. In fact I have the hardware/software resources to do macOS
>> development but not the time. Hell, my own *main* kicad work has been
>> delayed for weeks, and it'd take me ages just to get to the bottom of
>> what's going on here and understand it all, let alone find a fix :(
>>
>>>
>>>>
>>>> Wayne, would you be okay with disabling scripting on the macOS builds
>>>> until scripting is fixed for them?
>>>
>>> I replied to an email earlier to request that we disable python
>>> scripting on osx until the python build issues are a resolved.  Did it
>>> not make it through?
>>
>> Nah, there's just been enough discussion on this issue that I've managed
>> to miss and/or forget some.
>>
>>>
>>>>
>>>>> Your comments doe nothing to encourage the few OSX
>>>>> devs that we do have.  Perhaps a better way to motivate them would be to
>>>>> thank them for their efforts.
>>>>>
>>>>>>
>>>>>> Just my $0.02,
>>>>>> Jean-Paul
>>>>>> N1JPL
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Mar 16, 2017, at 2:06 PM, Bernhard Stegmaier <stegmaier@xxxxxxxxxxxxx> wrote:
>>>>>>>
>>>>>>> I have just seen people on the forum complaining that OSX nightlies still don’t build.
>>>>>>>
>>>>>>> @Simon:
>>>>>>> Do you intend to push your changes, no matter how hackish?
>>>>>>> Might at least be a start to work with.
>>>>>>>
>>>>>>> Or, just disable python scripting at all until the whole python bundling has been sorted out?
>>>>>>> Having no python scripting is better than having no build or a build where it doesn’t work right...
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>> Bernhard
>>>>>>>
>>>>>>>> On 21 Feb 2017, at 18:56, Simon Wells <swel024@xxxxxxxxx> wrote:
>>>>>>>>
>>>>>>>> I have previously sent a patch to adam for testing that bundled
>>>>>>>> python. but it was a bit hackish as since python is a system lib
>>>>>>>> bundleutilies doesn't copy it.
>>>>>>>>
>>>>>>>> On 21 February 2017 at 21:28, Bernhard Stegmaier
>>>>>>>> <stegmaier@xxxxxxxxxxxxx> wrote:
>>>>>>>>>
>>>>>>>>> On 21 Feb 2017, at 00:31, Wayne Stambaugh <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>:
>>>>>>>>>
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Mailing list: https://launchpad.net/~kicad-developers
>>>>>>>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>>>>>>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>>>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Mailing list: https://launchpad.net/~kicad-developers
>>>>>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>>>>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Mailing list: https://launchpad.net/~kicad-developers
>>>>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>>>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~kicad-developers
>>>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp



References