Re: [Kicad-developers] KiCad scripting supported in the release or not

Hi Collin, If you have any of the docs/scripting around packaging Python along with it, I urge you to post it somewhere. After the stable release, I'm going to see how much work/if it'd be worth anything for me to get KiCad in the Mac App Store. Adam Wolf On Wed, Oct 7, 2015 at 8:49 AM, Collin

Re: [Kicad-developers] KiCad scripting supported in the release or not

Hi, this is kind of an old message, but I posted about this some time ago, before there were even OS X nightlies. I mentioned that this would rear its head eventually - as to when, that's for Apple to not tell us until far too short a time before it happens, as they tend to do. The worry of

Re: [Kicad-developers] KiCad scripting supported in the release or not

Rather than doing this at compile time, can it be done at run or install time instead. ie: if the relevant python support is available enable the scripting features dynamically, otherwise leave them disabled. This could be done using 2 shared libraries (.so or .dll etc) one has all of the

Re: [Kicad-developers] KiCad scripting supported in the release or not

Shamelessly pilfered from the movie "Karate Kid", build config tools rule #1: Always check for features, not platforms. build config tools rule #2: go back and learn rule #1. Yes we could check for msys but it is possible (however painful) that someone may have actually patched, built, and

Re: [Kicad-developers] KiCad scripting supported in the release or not

2015-10-03 5:12 GMT+02:00 David Godfrey : > Surely it would be possible to detect which msys version is available, and > automatically enable scripting if msys2 is found? Nah, either way, it should be up to they guy building in the environment. Making theese kind of

Re: [Kicad-developers] KiCad scripting supported in the release or not

This cannot be done because of the old msys1/mingw32 builds which require Brian's kicad-winbuilder in order to build all of the dependencies correctly. Build python and wxpython on msys1/mingw32 is a major hassle which has been eliminated with the new msys2/mingw32/64. For the stable release, I

Re: [Kicad-developers] KiCad scripting supported in the release or not

For me, on OS X the default build settings do not work correctly - at least when just used out of the box. I didn’t investigate further, but I think this is due to multiple python versions being installed in parallel natively by OS X and packet managers like MacPorts (in my case). For example,

Re: [Kicad-developers] KiCad scripting supported in the release or not

Is there any way to use the bundle to check for a valid python installation and download and install it if it's not? Why is it the open source distros can pull this off (apt, yum, pacman, etc.) but the wealthiest companies on the planet can't seem to get this right? On 10/2/2015 3:06 PM,

Re: [Kicad-developers] KiCad scripting supported in the release or not

It is just a concept thing I guess. You can either use some sort of package manager to pull in dependencies. Or, you can put all dependencies into one single package and you don’t need any package manager. Each approach has pros and cons… I think it is useless to discuss that. I think you have

Re: [Kicad-developers] KiCad scripting supported in the release or not

OS X has a builtin Python (on 10.10 it's Python 2.7.10, located at /usr/bin/python). Can't you just use that, as it's provided by the system already and (almost) guaranteed to be there? Particularly on 10.11 since SIP would prevent it from being touched... Most Linux distributions also

Re: [Kicad-developers] KiCad scripting supported in the release or not

Ok, I am ok with that, but does that mean that we should motivate packagers to enable it in the release notes when that time comes? 2015-10-02 20:32 GMT+02:00 Wayne Stambaugh : > This cannot be done because of the old msys1/mingw32 builds which > require Brian's

Re: [Kicad-developers] KiCad scripting supported in the release or not

Ian, That's what I'm doing already (and have already been doing for months). Please note: right now we say we support 10.7-10.10, and soon I'll switch it over to say 10.7 to 10.11. Adam Wolf Cofounder and Engineer W On Fri, Oct 2, 2015 at 2:45 PM, Ian Woloschin wrote: >

Re: [Kicad-developers] KiCad scripting supported in the release or not

2015-10-02 21:45 GMT+02:00 Ian Woloschin : > OS X has a builtin Python (on 10.10 it's Python 2.7.10, located at > /usr/bin/python). Can't you just use that, as it's provided by the system > already and (almost) guaranteed to be there? Particularly on 10.11 since > SIP would

Re: [Kicad-developers] KiCad scripting supported in the release or not

I'm hoping our linux packagers are enabling the scripting since that is the one place we know it works well. If not, please do. Windows and OSX are a lot more work to get Python scripting working but we seem to have that in pretty good shape. On 10/2/2015 3:44 PM, Nick Østergaard wrote: > Ok, I

Re: [Kicad-developers] KiCad scripting supported in the release or not

> On Oct 2, 2015, at 12:32 PM, Bernhard Stegmaier > wrote: > > Of course, we could switch back to some package manager like home-brew or > MacPorts on OS X, but you would lose the ability to just download and run an > app bundle (everyone would have to “build” his

Re: [Kicad-developers] KiCad scripting supported in the release or not

I know there are a variety of applications that come with Python extensions--I think finding the docs on how we're supposed to do it will probably solve this problem. On Fri, Oct 2, 2015 at 2:16 PM, Wayne Stambaugh wrote: > Is there any way to use the bundle to check for a

Re: [Kicad-developers] KiCad scripting supported in the release or not

Don't worry, Andy, I'm not going to stop the OS X dmg releases! If no one else gets to this soon, I will dig into this. I need to find out why my build isn't working for Bernhard, and figure out the matrix of OS X release and Python version that is currently supported, and figure out if there's

Re: [Kicad-developers] KiCad scripting supported in the release or not

I think your build didn’t work correctly for me because the paths were just wrong before my patch, so no plugins were found. I’ll retest when a new build has been made with the new paths. I guess it is not a problem for now. The rest about incompatibilities is just speculation, maybe also just

Re: [Kicad-developers] KiCad scripting supported in the release or not

> On Oct 2, 2015, at 3:30 PM, Bernhard Stegmaier > wrote: > > I think your build didn’t work correctly for me because the paths were just > wrong before my patch, so no plugins were found. > I’ll retest when a new build has been made with the new paths. > I guess it

Re: [Kicad-developers] KiCad scripting supported in the release or not

I definitely see that there can be problems there. I hope we can get most users without a lot more work. It would not be a huge amount of work for me to make a different build for each OS X version every night. Adam Wolf Cofounder and Engineer Wayne and Layne, LLC On Fri, Oct 2, 2015 at 5:30