kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

On 2/23/2016 3:44 PM, Nick Østergaard wrote:
> Hi Wayne
> 
> Let me explain the confusion. The current scripts to build the windows
> installer is found at:
> https://github.com/nickoe/KiCad-Winbuilder
> 
> It initially started becaue now one or few people cared to package for
> windows. No one was using the msys2 environment at the time for builds
> IIRC.  Anyway, the packing job was basically just taking the nsis
> script in the kicad source. This was sort of broken an not that good.
> Then I created a script to package it "properly". (Still a work in
> progress.) And Brian created some cmake stuff for it too, such that
> you could just make sure that you had cmake on your commandline, and
> that creates a working msys2 installation for building kicad.
> 
> I don't actually use the cmake stuff for packaging, I only use
> makepkg-mingw and the copydlls.sh script.
> 
> And after that seemed to work Brian decided to abandon his
> kicad-winbuilder on lp. So in a sense this is the new
> kicad-winbuilder. We might want to move the repo under the kicad org
> on github, because this is what is used for the official windows
> installers.

Moving this to the KiCad project on github is probably a good idea.  I
can't remember how I transferred Marco's KiCad doc repo.  I think I gave
him temporary admin privileges on the KiCad project page until he
transferred it to the kicad project.  Let me know if you want to do this
and I will go ahead and give you admin privileges so you can do the
transfer.

> 
> On a sort of side note, but related. I have determined that since the
> enhanced python shell was comitted (at least it seems so so far), then
> the python console in pcbnew did not start up anymore. I am still
> trying to figure out what might be missing. I can just confirm that it
> works when executed from the msys2 environment, but not when
> installed.
> 
> Nick
> 
> 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