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 :
>> 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 -040
I have disabled scripting.
2017-03-17 15:04 GMT+01:00 Chris Pavlina :
> 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 scr
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 L
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
On Fri, Mar 17, 2017 at 09:56:14AM -0400, 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/
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.
> >
Well unfortunately we can't do much until python build is fixed.
On 18 March 2017 at 01:11, Wayne Stambaugh wrote:
> Thanks Adam and Simon for taking care of this!
>
> On 3/16/2017 6:24 PM, Adam Wolf wrote:
>> I have some time to do testing on this now that the stable package is
>> finished.
>>
>
Thanks Adam and Simon for taking care of this!
On 3/16/2017 6:24 PM, Adam Wolf wrote:
> I have some time to do testing on this now that the stable package is
> finished.
>
> Simon, please resend if possible and I'll take a look this weekend.
>
> Adam Wolf
>
> On Thu, Mar 16, 2017, 5:05 PM Simon
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 u
I have some time to do testing on this now that the stable package is
finished.
Simon, please resend if possible and I'll take a look this weekend.
Adam Wolf
On Thu, Mar 16, 2017, 5:05 PM Simon Wells wrote:
> the problem is most of the python bundling crap is in patches (and
> yeah it is a bit
the problem is most of the python bundling crap is in patches (and
yeah it is a bit hackish) wwas passed off to adam for testing but he
never came back. but its also reliant on the python build not being
broken. It is also as unhackish as it will get due to how cmake works,
althought we MAY be able
As I said before, I plan to work on the whole python packaging stuff as
discussed below if no one else volunteers to do before.
I had some look around on how to do this, but I didn’t find any out-of-the-box
solution which could be integrated quickly.
Unfortunately, I am still busy with other (non
I'm of two minds on this. On one hand, I'd like to disable scripting on
the macOS nightlies until it's fixed, so macOS users still *have*
nightlies. On the other hand, I worry that doing so will remove
motivation to actually fix it.
Is anyone actually _actively working on a fix_? I keep seeing cha
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.
Just my $0.02,
Jean-Paul
N1JPL
> On Mar 16, 2017, at 2:06 PM, Bernhard Stegmaier
> wrote:
>
> I have just seen people on the forum
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
That's exactly why we did it that way on windows. It was the least
painful option. It sounds like it may be a better option on osx as well.
On 2/21/2017 12:56 PM, Simon Wells wrote:
> I have previously sent a patch to adam for testing that bundled
> python. but it was a bit hackish as since pyth
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
wrote:
>
> On 21 Feb 2017, at 00:31, Wayne Stambaugh wrote:
>
> On 2/20/2017 6:27 PM, N
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 suppo
> On 21 Feb 2017, at 00:31, Wayne Stambaugh wrote:
>
> On 2/20/2017 6:27 PM, Nick Østergaard wrote:
>> 2017-02-20 23:48 GMT+01:00 Bernhard Stegmaier :
>>> 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 plac
When i looked into this a while ago, that is actually what Apple strongly
recommended/required.
Adam Wolf
On Feb 20, 2017 5:31 PM, "Wayne Stambaugh" wrote:
> On 2/20/2017 6:27 PM, Nick Østergaard wrote:
> > 2017-02-20 23:48 GMT+01:00 Bernhard Stegmaier :
> >> Hi Wayne,
> >>
> >> if you really w
On 2/20/2017 6:27 PM, Nick Østergaard wrote:
> 2017-02-20 23:48 GMT+01:00 Bernhard Stegmaier :
>> Hi Wayne,
>>
>> if you really want to have this commited soon, I’d suggest to completely
>> disable KICAD_SCRIPTING_MODULES stuff on macOS.
>>
>> I just had a look at the KICAD_SCRIPTING_MODULES stuff
On 2/20/2017 5:48 PM, Bernhard Stegmaier wrote:
> Hi Wayne,
>
> if you really want to have this commited soon, I’d suggest to completely
> disable KICAD_SCRIPTING_MODULES stuff on macOS.
It is disabled by default so it would be up to our package devs to build
with Python scripting disabled. Did
2017-02-20 23:48 GMT+01:00 Bernhard Stegmaier :
> Hi Wayne,
>
> if you really want to have this commited soon, I’d suggest to completely
> disable KICAD_SCRIPTING_MODULES stuff on macOS.
>
> I just had a look at the KICAD_SCRIPTING_MODULES stuff as it is now and I
> think it is broken anyway (back
Hi Wayne,
if you really want to have this commited soon, I’d suggest to completely
disable KICAD_SCRIPTING_MODULES stuff on macOS.
I just had a look at the KICAD_SCRIPTING_MODULES stuff as it is now and I think
it is broken anyway (back then when I changed the bundle stuff I just took what
was
Did Dick have look at the log and patched patch that Simon replied with?
Any comments on it or?
Den 20/02/2017 19.32 skrev "Wayne Stambaugh" :
> Simon,
>
> I'm going to commits Dick's original patch as soon as possible. I want
> to know if you (or anyone else who can fix the osx part of this) w
Hi Wayne,
I have already sent my concerns and what i am stuck on and have had no
response so at this point i am unable to help sorry
On 21 February 2017 at 07:28, Wayne Stambaugh wrote:
> Simon,
>
> I'm going to commits Dick's original patch as soon as possible. I want
> to know if you (or anyo
Simon,
I'm going to commits Dick's original patch as soon as possible. I want
to know if you (or anyone else who can fix the osx part of this) will be
available to fix the osx part of this before I commit it to minimize the
amount of time we have broken builds for osx.
Thanks,
Wayne
On 2/13/20
well i don't actually know what needs to be done, i just sent a chunk
to pass onto dick, i am not fussed if the whole commit is attributed
to dick
On 14 February 2017 at 09:32, Wayne Stambaugh wrote:
> Simon,
>
> This isn't going to work as patch that I can commit because the proper
> credit cann
Simon,
This isn't going to work as patch that I can commit because the proper
credit cannot be attributed to the correct author. I will commit Dick's
original patch this evening so you can send me patch for the osx fix
which will be attributed to you as the commit author. I don't really
want to
Error copying file "_pcbnew.kiface" to "_pcbnew.so".
attached is dicks patch with my changes
On 14 February 2017 at 03:15, Wayne Stambaugh wrote:
> On 2/12/2017 5:15 PM, Bernhard Stegmaier wrote:
>>
>>> On 12 Feb 2017, at 22:18, Wayne Stambaugh wrote:
>>>
>>> On 2/12/2017 5:37 AM, Simon Wells w
On 2/12/2017 5:15 PM, Bernhard Stegmaier wrote:
>
>> On 12 Feb 2017, at 22:18, Wayne Stambaugh wrote:
>>
>> On 2/12/2017 5:37 AM, Simon Wells wrote:
>>> i am stuck on the below as i do not understand whats trying to be
>>> achieved doing this
>>>
>>> # For phase 1, copy _pcbnew.kiface to the pyth
> On 12 Feb 2017, at 22:18, Wayne Stambaugh wrote:
>
> On 2/12/2017 5:37 AM, Simon Wells wrote:
>> i am stuck on the below as i do not understand whats trying to be
>> achieved doing this
>>
>> # For phase 1, copy _pcbnew.kiface to the python module. line onward
>> (line 733ish)
>>
>> until th
On 2/12/2017 5:37 AM, Simon Wells wrote:
> i am stuck on the below as i do not understand whats trying to be
> achieved doing this
>
> # For phase 1, copy _pcbnew.kiface to the python module. line onward
> (line 733ish)
>
> until the end of the if, and its broken for me.
It should just be a cop
i am stuck on the below as i do not understand whats trying to be
achieved doing this
# For phase 1, copy _pcbnew.kiface to the python module. line onward
(line 733ish)
until the end of the if, and its broken for me.
also can we please formalize a policy in the CMakeLists.txt files that
do_th
Simon,
Have you made any progress on this yet? I would really like to get this
committed but I don't want to break osx builds.
Thanks,
Wayne
On 2/2/2017 8:57 PM, Wayne Stambaugh wrote:
> Thanks Simon. Please send a patch against Dicks work so I can commit
> this at the same time. I don't wan
Thanks Simon. Please send a patch against Dicks work so I can commit
this at the same time. I don't want to break osx builds.
Thanks,
Wayne
On 2/2/2017 7:28 PM, Simon Wells wrote:
> its not good on osx, I will take a look over the weekend, There are a
> few things i would like to change in tha
its not good on osx, I will take a look over the weekend, There are a
few things i would like to change in that cmakelists, esspecially in
regards to OSX and the order of things/when things are done
On 3 February 2017 at 07:28, Wayne Stambaugh wrote:
> Did anyone of our osx devs get a chance to t
Did anyone of our osx devs get a chance to test this patch yet? I would
like to get it merged. It saves a nice chunk of time from builds.
Cheers,
Wayne
On 1/26/2017 11:42 AM, Wayne Stambaugh wrote:
> Would one of our osx devs please test the attached patch? Dick sent me
> this patch to fix th
Would one of our osx devs please test the attached patch? Dick sent me
this patch to fix the long standing issue of building _pcbnew.kiface
twice. It works fine on windows and linux but the fix requires copying
_pcbnew.kiface with the correct python extension and I'm not so sure
this isn't going
39 matches
Mail list logo
