← Back to team overview

kicad-developers team mailing list archive

Re: adamwolf-kicad-scripting-testing-daily ppa - import pcbnew not working

 

Hi Hans,

I don't know how it worked for me.  I am not sure how the new system
finds pcbnew.py, however, it is most definitely not in the list of
packaged files.  I will add it, and test that tomorrow. Thanks Hans!

Adam Wolf
Wayne and Layne, LLC

On Mon, Oct 29, 2012 at 4:31 PM, Hans Henry von Tresckow
<hvontres@xxxxxxxxx> wrote:
> I wonder if you somehow still had a copy of pcbnew.py laying around
> when you did the testing. I noticed it is not in the list of installed
> files for the package and putting a copy in same dir as the pcbnew
> executable seemed to help with loading the module inside of pcbnew.
>
>
>
> On Sat, Oct 27, 2012 at 7:01 AM, Adam Wolf
> <adamwolf@xxxxxxxxxxxxxxxxxxxx> wrote:
>> I'll have to look into it further.  You said you're on 12.04 right
>> now?  I definitely tested the 12.04 64 bit packages and they worked
>> fine for me.
>>
>> Adam Wolf
>>
>> On Fri, Oct 26, 2012 at 11:23 PM, Hans Henry von Tresckow
>> <hvontres@xxxxxxxxx> wrote:
>>> Ok, here is what I get from today's install:
>>>
>>> henry@Dr-Bunsen:~/kicad/LCD Driver$ pcbnew
>>> Traceback (most recent call last):
>>>   File "<string>", line 3, in <module>
>>> ImportError: No module named pcbnew
>>> henry@Dr-Bunsen:~/kicad/LCD Driver$
>>>
>>> It looks like the pcbnew module is not getting packaged somehow.
>>>
>>> Here is the version Info from pcbnew:
>>>
>>> Application: Pcbnew
>>> Version: (2012-oct-18)-testing
>>> Build: wxWidgets 2.8.12 (no debug,Unicode,compiler with C++ ABI
>>> 1002,GCC 4.6.3,wx containers,compatible with 2.6)
>>> Platform: Linux 3.2.0-33-generic x86_64, 64 bit, Little endian, wxGTK
>>> Boost version: 1.49.0
>>> Options: USE_PCBNEW_SEXPR_FILE_FORMAT=OFF
>>>          USE_PCBNEW_NANOMETRES=ON
>>>          USE_PCBNEW_SEXPR_FOOTPRINT_LIBS=OFF
>>>          KICAD_GOST=OFF
>>>          USE_WX_GRAPHICS_CONTEXT=OFF
>>>          USE_WX_OVERLAY=OFF
>>>          USE_BOOST_POLYGON_LIBRARY=OFF
>>>          KICAD_SCRIPTING=ON
>>>          KICAD_SCRIPTING_MODULES=OFF
>>>          KICAD_SCRIPTING_WXPYTHON=ON
>>>
>>>
>>> Anything else I should try?
>>>
>>> On Thu, Oct 25, 2012 at 8:35 AM, Adam Wolf
>>> <adamwolf@xxxxxxxxxxxxxxxxxxxx> wrote:
>>>> Hi Hans,
>>>>
>>>> Could you try again?  I tested the kicad from
>>>> kicad-scripting-testing-daily for Ubuntu 12.04.  I put the footprint
>>>> wizard python file in ~/.kicad_plugins, and I was able to open pcbnew,
>>>> click the module editor, and see the footprint wizard button.  I
>>>> clicked it, and a new window opened saying Footprint Wizard with a
>>>> bunch of wizardy stuff.  From that, it seems that it's working (at
>>>> least mostly!)
>>>>
>>>> It builds on the Launchpad servers for 12.04, 12.10, and 13.04.  I
>>>> have added investigating why it doesn't build for 11.10 and 11.04 to
>>>> my list of things to do.  For Ubuntu 12.10 and 13.04, they have
>>>> changed the Kicad versioning.  The official Ubuntu package in their
>>>> repository has a version number of 0.20120526..., which is "newer"
>>>> than 0.0.201210... which are the ones I'm creating now.  There are
>>>> also a few assumptions in the packaging that were correct in the past,
>>>> but are not correct now, regarding the documentation and a few things
>>>> about dependencies.  Cleaning those up so we are a great example of
>>>> how to package for Debian and Ubuntu is also on my list of things to
>>>> do. (Along with seeing if people can have kicad-with-scripting
>>>> installed next to kicad-without, which would be a great template for
>>>> any other feature branches we get in the future, and looking into the
>>>> package name changing that someone asked about on the list a few days
>>>> ago.)
>>>>
>>>> However, all those caveats being said, if any brave souls want to try
>>>> it, here are the instructions.
>>>>
>>>> If you are on Ubuntu 12.04:
>>>>
>>>> If you already have kicad installed, from either a PPA or from the
>>>> official repo, uninstall it first.
>>>> sudo apt-get remove kicad kicad-common
>>>>
>>>> Add the tentative kicad-scripting-testing ppa:
>>>> sudo add-apt-repository ppa:adamwolf/kicad-scripting-testing-daily
>>>>
>>>> Update your package list:
>>>> sudo apt-get update
>>>>
>>>> Install the new packages:
>>>> sudo apt-get install kicad
>>>>
>>>> To go back to how you had it before, if these packages don't work for you.
>>>> Remove the current packages
>>>> sudo apt-get remove kicad kicad-common
>>>>
>>>> Remove the new PPA
>>>> sudo rm /etc/apt/sources.list.d/adamwolf-kicad-scripting-testing-daily-*.list
>>>>
>>>> Optional: add my PPA back if you used to use it, otherwise skip this
>>>> step if you want the stock Ubuntu packages
>>>> sudo add-apt-repository ppa:adamwolf/kicad-testing-daily
>>>>
>>>> Update your package list:
>>>> sudo apt-get update
>>>>
>>>> Install the other packages:
>>>> sudo apt-get install kicad
>>>>
>>>> If you are on Ubuntu 12.10 or an alpha release of 13.04:
>>>>
>>>> If you already have kicad installed, from either a PPA or from the
>>>> official repo, uninstall it first.
>>>> sudo apt-get remove kicad kicad-common
>>>>
>>>> Add the tentative kicad-scripting-testing ppa:
>>>> sudo add-apt-repository ppa:adamwolf/kicad-scripting-testing-daily
>>>>
>>>> Update your package list:
>>>> sudo apt-get update
>>>>
>>>> Find out the options for kicad:
>>>> sudo apt-cache showpkg kicad
>>>>
>>>> Read to see which one comes from my PPA. Its version will start
>>>> 0.0.201210... (until October is over)  Note that version number
>>>>
>>>> Install the new packages:
>>>> sudo apt-get install kicad=0.0.201210...
>>>>
>>>> To revert, do the same thing as you would if you were on 12.04.
>>>>
>>>> Question:
>>>> Should I change my PPA versioning to match the newer Ubuntus?  I don't
>>>> see this hurting anything on the older Ubuntu releases, and it will
>>>> make my PPA be less hassle on 12.10 (the "current" Ubuntu) as well as
>>>> future releases.  If I don't hear objections, I'll make this change
>>>> over the weekend.  No one should notice anything, as far as I know.
>>>>
>>>> Do you follow this list and use an Ubuntu older than 12.04?  12.04 is
>>>> the latest Long Term Support release, which should have updates for 5
>>>> years.  I'll probably be sticking with 12.04 on my main development
>>>> machine for a while, but I use the current release at work.  If no one
>>>> here uses an Ubuntu older than 12.04, I will put compatibility with
>>>> those releases lower priority than some of the other packaging tasks.
>>>>
>>>> This PPA is still definitely experimental, and please assume that
>>>> issues you run into with it are the fault of the package, not the
>>>> scripting support.
>>>>
>>>> Adam Wolf
>>>> Wayne and Layne
>>>>
>>>>
>>>>
>>>> On Tue, Oct 23, 2012 at 3:48 PM, Adam Wolf
>>>> <adamwolf@xxxxxxxxxxxxxxxxxxxx> wrote:
>>>>> I think it's more that the dependencies are named differently in the
>>>>> older versions.  There's a special tool that chroots the compilaton so
>>>>> you can check for obscure dependencies.
>>>>>
>>>>> 12.04 and 12.10, as well as the two newer versions beyond that,
>>>>> "compile" on the remote system, but they have the issue you mentioned.
>>>>>
>>>>> I'll let you know when I get it working--it should be soon, but I've
>>>>> never seen this issue before.
>>>>>
>>>>> On Tue, Oct 23, 2012 at 2:57 PM, Hans Henry von Tresckow
>>>>> <hvontres@xxxxxxxxx> wrote:
>>>>>> I'm on 12.04 for now, but I think in another week or so I'll switch
>>>>>> over to 12.10. I wonder if there might be some obscure dependancy you
>>>>>> have locally but that does not get pulled in on the build server.
>>>>>>
>>>>>> On Tue, Oct 23, 2012 at 7:15 AM, Adam Wolf
>>>>>> <adamwolf@xxxxxxxxxxxxxxxxxxxx> wrote:
>>>>>>> I'm able to compile using my recipe and packaging stuff on my local machine,
>>>>>>> and it works, but when I upload the recipe to the PPA build servers, it
>>>>>>> produces crashy programs.
>>>>>>>
>>>>>>> What OS version are you using?  I'm having issues getting it to work on any
>>>>>>> Ubuntu version older than 12.04. I had this description on the recipe, but
>>>>>>> not the PPA. "This is a testing build of KiCad, with scripting enabled.
>>>>>>> Scripting support works, but may crash. This package might not work."  I
>>>>>>> have since added it to the PPA as well.
>>>>>>>
>>>>>>> I was able to get the footprint wizard to work fine, which imports from
>>>>>>> pcbnew.
>>>>>>>
>>>>>>> I'm running into a variety of small issues, including the fact that with
>>>>>>> 12.10, the Ubuntu package number has changed from 0.0.date to 0.date.  I
>>>>>>> think it may be prudent for me to change my PPA versioning to match,
>>>>>>> otherwise I think we'll see some weird issues. (The old kicad in the
>>>>>>> official repo will always be a higher version than my current generated
>>>>>>> packages, for 12.10 and newer.)
>>>>>>>
>>>>>>> I'll certainly post here when I feel the packages are ready to be tested.
>>>>>>> After that, starting the middle of November, I hope to spend an hour a week
>>>>>>> on KiCad packaging for Ubuntu/Debian until it's where I like.
>>>>>>>
>>>>>>> Adam Wolf
>>>>>>> Wayne and Layne, LLC
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Oct 23, 2012 at 12:58 AM, Hans Henry von Tresckow
>>>>>>> <hvontres@xxxxxxxxx> wrote:
>>>>>>>>
>>>>>>>> I just tried the first build of Adam's scripting PPA, but it seems I
>>>>>>>> can't import the pcbnew module. Is this an issue with sys.path or do
>>>>>>>> we still have a packaging issue?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> --
>>>>>>>> Henry von Tresckow (hvontres)
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Henry von Tresckow (hvontres)
>>>
>>>
>>>
>>> --
>>> Henry von Tresckow (hvontres)
>
>
>
> --
> Henry von Tresckow (hvontres)


Follow ups

References