kicad-developers team mailing list archive

[Bernhard Stegmaier <stegmaier@xxxxxxxxxxxxx>]

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, with default settings CMake bails out complaining about not finding python-2.6 packages although default interpreter is python-2.7 (and wxPython was built with the 2.7)… I don’t know where the 2.6 comes from.

This can be fixed by using suitable DPYTHON_EXECUTABLE and DPYTHON_SITE_PACKAGE_PATH settings, but (to be honest) until now I don’t know if this gets things done right just because it compiles and seems to run my machine (although on console there is a warning about not matching python versions).
Especially, when the generated package will be run on a different machine with probably a completely different python version (the python used to compile is not contained in the application bundle, but only libs/modules of wxPython).

However, this may be only because of my setup and is not representative.

The strategy for python and the application bundle needs to be discussed I guess… if the bundle should be 100% self contained, then I almost guess that the python version used to build the bundle would also have to be included in there.
Unfortunately, I am not so familiar with python right now to be able to judge that in detail. 


Regards,
Bernhard

> On 02 Oct 2015, at 20:32, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
> 
> 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 would prefer that packagers enable scripting
> on a case by case basis.  We certainly can discuss turning it on by
> default after the stable release and dumping support for the old
> msys1/mingw32 platform.
> 
> On 10/2/2015 2:24 PM, Nick Østergaard wrote:
>> Hello
>> 
>> Since we have been discussing the python scripting stuff recently, I
>> would like to hear if it is supposed to be officially supported or
>> not.
>> 
>> The thing is that it is by default OFF in the build scripts. This is
>> choice likely to affect many linux distributions build configuraiton.
>> 
>> I would actually suggest that we enable it by default. Any comments?
>> 
>> Regards
>> Nick
>> 
>> _______________________________________________
>> 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