kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

On 2/23/2016 3:53 PM, Nick Østergaard wrote:
> As far as I can se, we need python2w.exe, that should be easy to add.
> But what I worry about is if we include pip, it might not work as
> expeced for the user, beacause when he upgrades he might get into
> trouble if he uninstalls kicad and then installs. The user will have
> to reinstall the modules that he uses. An other thing is if kicad is
> installed to %PROGRAMFILES%, then you will likely have trouble
> modifying stuff there, because of the user access control. But I have
> not tested this.

This was my concern.  Providing a full Python implementation is outside
the scope of the project.  If someone needs this, they should install
msys2 and either build kicad from source or create pacman packages.  If
you don't mind, I would like to cherry pick your changes to PKGBUILD and
push them to the msys2 kicad-git package repo.  I'll also create a kicad
PKGBUID for the stable version of kicad using your PKGBUILD-STABLE so
the msys2 project can provide both git mirror and stable version kicad
packages.

Thanks,

Wayne

> 
> 2016-02-23 20:32 GMT+01:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
>> AFAIK kicad-winbuilder is no longer used or maintained.  KiCad is now
>> built using msys2/mingw32 and msys2/mingw64 and the appropriate python
>> run time requirements are installed in the same path as kicad.  Package
>> devs correct me if I'm wrong but this is a partial install of the
>> mingw32 or mingw64 python system containing only the run time
>> requirements to use the python console and the Pcbnew Python modules and
>> scripts.
>>
>> If you want to maintain kicad-winbuilder, feel free to modify it any way
>> you see fit but the windows installers will still continue to use msys2
>> as the build environment.  We are using msys2/mingw32/64 because all of
>> the dependency libraries required to build kicad are supplied by the
>> msys2 project.  There is no need to build wxwidgets, boost, cairo, etc.
>> from source to build kicad.
>>
>> On 2/23/2016 1:51 PM, Константин Барановский wrote:
>>> I'm confused. I'm not understand what is your point of view about
>>> integration python to the installation of kicad on Windows. Will it
>>> still done with kicad-winbuilder or you planning to separate python from
>>> kicad installation and to use system-wide?
>>> As I see (thank you xarx and Torsten Hüter), simplest way to include
>>> full-featured python - it modify kicad-winbuilder. If you do not mind,
>>> I'll try to do it.
>>>
>>> Regards, Konstantin.
>>>
>>>
>>> _______________________________________________
>>> 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