kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #08622
Re: Win32 compilation for kicad scripting
Hi Adam,
but <kicad_path>\lib\python\dist-packages doesn't seem like
the best place, right?, may be we should be able to discover where
python2.7 is installed, or may be just provide it within kicad Win32
installation, if it isn't too big :)
About the OS differences for the examples, may be it could make
sense to just forget about /tmp or C:\TEMP and let the user provide
the output filename with sys.argv to keep the examples as simple as
possible.
I will fix those examples to avoid any problem with that.
2012/7/22 Adam Vašíček <vasiceka@xxxxxxxxx>:
> Hi Mike,
>
> yes, now the _pcbnew.pyd is copied to
> <kiad_path>\lib\python\dist-packages by cmake.
>
> In order to get example scripts to run on Windows properly, platform
> differences should be taken into account (see attached diff for
> createPcb.py example script).
>
> Thanks for your valuable work Mike!
> Adam
>
> On Sun, Jul 22, 2012 at 2:25 PM, Miguel Angel Ajo Pelayo
> <miguelangel@xxxxxxx> wrote:
>> I've added a couple of fixes by Adam Vašíček that might get the
>> scripting part compiling
>> into WIN32 targets,
>>
>> http://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing/revision/3656
>>
>> He told me that he managed to get it compiled with:
>>
>> * compiler GCC (mingw32-gcc) version 4.5.2
>> * Python 2.7.3
>> * SWIG 2.0.7
>>
>> I'm not sure if the _pcbnew.pyd will get installed in the right place.
>>
>> --
>>
>> Miguel Angel Ajo Pelayo
>> http://www.nbee.es
>> +34 636 52 25 69
>> skype: ajoajoajo
--
Miguel Angel Ajo Pelayo
http://www.nbee.es
+34 636 52 25 69
skype: ajoajoajo
Follow ups
References