gnupic: Re: [gnupic] [PIC] piklab now supports ICD2 and PICkit 2 programmer under Linux
Subject:
Re: [gnupic] [PIC] piklab now supports ICD2 and PICkit 2 programmer under Linux
From:
Xiaofan Chen ####@####.####
Date:
16 Feb 2006 12:23:30 +0000
Message-Id: <a276da400602160423v1726aabaj42badfbf4f148c24@mail.gmail.com>
On 2/16/06, Scott Dattalo ####@####.#### wrote:
> Thanks for posting this announcement. My ancient PicStart+ finally died
> after nearly 10 years of service (RIP), so I upgraded to an ICD2. (I also
> bought the dsPICDEM 1.1 eval board!). The bad news is that piklab is a KDE
> app and it's a pain in the ass to build KDE apps on Fedora. But I managed
> to finally figure it out, so maybe someone else can benefit.
>
> I've recently upgraded from FC3 to FC4, and my system is an Athlon64.
>
> Like with pikdev, when I configure piklab I get this error when I
> ./configure:
>
> ...
> checking for KDE... libraries /usr/lib, headers /usr/include/kde
> checking if UIC has KDE plugins available... no
> configure: error: you need to install kdelibs first.
>
>
> Now, this is a lie, because kdelibs and kdelibs-devel are both installed.
> After searching around on google, I found you can get around this
> ./configure bug by editing the ./configure script and changing the line
>
> from:
>
> if test -f actest.cpp && grep klineedit actest.cpp > /dev/null; then
>
> to:
>
> if test -f actest.cpp && grep KLineEdit actest.cpp > /dev/null; then
>
> This is on line 29856. I found the solution here:
> http://www.skepticats.com/linlog/entries/2005/08/14_1024/
>
> This gets me through the configure script. But now, "make" gives this error:
>
> Making all in devices
> make[3]: Entering directory `/home/scott/tars/piklab-0.4.1/src/devices'
> /bin/sh ../../libtool --silent --mode=link --tag=CXX g++
> -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500
> -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W
> -Wpointer-arith -Wwrite-strings -O2 -Wformat-security
> -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common
> -o xml_to_data_device xml_device_parser.o
> ../../src/xml_to_data/libxmltodata.la ../../src/devices/libmisc.la
> -lkdecore -lusb
> g++: /usr/lib/libidn.so: No such file or directory
>
> This isn't a lie, because on 64bit machines this library is located in
> /usr/lib64/ ! So reading between the lines and picking up a hint here and
> there I deduced you need to actually configure like this:
>
> ./configure --enable-libsuffix=64 --with-qt-dir=/usr/lib64/qt-3.3/
> --with-qt-libraries=/usr/lib64/qt-3.3/lib/
>
> Success! I can now configure. But compiling is another story. There are
> thousands of QT warnings and one piklab error. Line 324 of
> DirectPrgConfigWidget.cpp reads:
>
> Direct::ConfigWidget::ConfigWidget(QWidget *parent)
> : ProgConfigWidget(Device::User::DirectProgrammer, parent,
> "direct_prog_config_widget")
>
> But should be:
>
> Direct::ConfigWidget::ConfigWidget(QWidget *parent)
> : ProgConfigWidget(Device::User::DirectProgrammer, parent,
> "direct_prog_config_widget")
>
> After this fix I *finally* built a KDE app on an Fedora Distribution!
> Piklab does indeed run too. However I did have to run as root to allow
> connection:
Hi Scott,
My 32-bit FC4 building process is much easier. I only need to do one thing:
export QTDIR=/usr/lib/qt-3.3
Other than this, there is nothing to change for FC4. Could you check
again with this change and your 64-bit lab fix?
It is also recommemded to use --enable-debug=full so that quite some
useful debug message can be shown under the GUI and the command
line piklab-prog tool.
However I still have some problems with USB connections under FC4
with 2.6.14 kernel.
Regards,
Xiaofan
