Package Details: piklab 0.16.2-3

Git Clone URL: (read-only)
Package Base: piklab
Description: IDE for applications based on Microchip PIC and dsPIC microcontrollers similar to the MPLAB environment
Upstream URL:
Licenses: GPL
Submitter: mouse256
Maintainer: ivanovp
Last Packager: ivanovp
Votes: 12
Popularity: 0.000000
First Submitted: 2006-04-25 15:53
Last Updated: 2016-11-23 17:43

Dependencies (9)

Required by (0)

Sources (1)

Latest Comments

fenugrec commented on 2018-01-31 20:41

Hi, just thought I'd mention I've added a Qt-only PKGBUILD for this (search for piklab-qt-svn), which is incomplete (no GUI ! apparently there's still some hard dependencies on KDE) but provides the very useful piklab-prog binary.

mah0x00 commented on 2017-11-20 11:05

Thank you for that but I already hade installed MPLABX but the reason for installing the piklab is that I have a clone for ICD2 and it doesn't work on MPLABX and piklab was the only software to operate it, I tried other programs but none of them seems to be working.

ivanovp commented on 2017-11-19 06:19

@mah0x00: There is Linux version of MPLABX, try to install that.

mah0x00 commented on 2017-11-13 20:11

is there is another program like piklab yesterday I tried to install it but there is a missing Dependencies (kdebase-katepart) if someone still working on it please tell me if there is a fix and how?

ivanovp commented on 2016-11-23 17:45

@jaracil: Thanks, fixed.

jaracil commented on 2016-11-11 12:58

It was needed to add (-D 'CMAKE_CXX_FLAGS=-Wno-narrowing') to cmake params to bypass narrowing conversion errors.


ivanovp commented on 2015-03-15 09:30

Fixed: it tried to use /lib directory, but it is a symlink to /usr/lib in Arch Linux. Consider using microchip-mplabx-bin, as it is actively developed.

pendor commented on 2015-03-15 00:16

Tried to compile. System up-to-date.
Error message when trying to install:

error: no se pudo realizar la operación (archivos en conflicto)
piklab: /lib existe en el sistema de archivos
Ocurrieron errores, por lo que no se actualizaron los paquetes

error: could not perform operation (conflicting files)
piklab: /lib exists in filesystem
Errors occurred, no packages were upgraded

I remember something like this with other packages some time ago... but don't know what to do right now.


bxs commented on 2012-09-01 12:38

I know that piklab is based of pikdev that is based on kate but didn't know that kdebase-katepart dependency was needed, I dropped the maintenance of piklab so you can adopt it and make the dependency change.

ivanovp commented on 2012-09-01 05:14

Please, add dependecy: kdebase-katepart

bxs commented on 2012-07-24 02:02

Updated to version 0.16.1, now uses Qt4.

Anonymous comment on 2011-08-30 13:38

Thanks to janserv for his patches.
For those who did not understand how to install piklab when the conversion error comes up when compiling with gcc 4.6:
Download the 2 packages that I made based on the comments bellow :
piklab-0.15.10-6-i686.pkg.tar.xz (1.68 MB)
qt3-3.3.8-20-i686.pkg.tar.xz (7.7 MB)

Then install them:
su -c 'pacman -U qt3-3.3.8-20-i686.pkg.tar.xz'
su -c 'pacman -U piklab-0.15.10-6-i686.pkg.tar.xz'

Anonymous comment on 2011-05-12 01:13

Now, why? who knows? Maybe the last yauourt -Syu, or the cleaning up, or your PKGBUILD, or the moon phase...
Nevertheless, thanx a whole lot for your help, pal!!!!

janserv commented on 2011-05-10 06:01

Clear the md5sums array in the PKGBUILD and create a new array.
makepkg -g >> PKGBUILD

Anonymous comment on 2011-05-09 23:06

Cleaned everything, using your PKGBUILD and now I got md5sum error for the patch... that was copied and paste from your link, or downloaded as raw data... Could this be related??

Anonymous comment on 2011-05-09 22:39

I did that. Twice.

janserv commented on 2011-05-09 22:00

I don't know what this can be.
Did you try a fresh build, meaning after you removed all the source files and the src dir in your piklab build dir?

Anonymous comment on 2011-05-09 20:08

I can see no differences between my PKGBUILD and yours.
Besides, the problem is with libqt-mt...
I´m flabbergasted (is that the correct word??).

I only built qt3 from ABS, are there any other qt related packages I should check???
Or, looking at the error messages again, can it be related to the xml_to_data patch?

janserv commented on 2011-05-09 04:27

Anonymous comment on 2011-05-09 00:21

Could you post the PKGBUILD with your corrections? just for checking...

Anonymous comment on 2011-05-09 00:17

Just built qt3 from ABS. Patched PKGBUILD with device_xml_to_data.h patch.
After makepkg I got the same error that reported previously, e. g.:

make[2]: *** No hay ninguna regla para construir el objetivo `/opt/qt/lib/libqt-mt', necesario para `src/devices/pic/xml/pic_xml_to_data'. Alto.
make[1]: *** [src/devices/pic/xml/CMakeFiles/pic_xml_to_data.dir/all] Error 2
make: *** [all] Error 2
==> ERROR: Se produjo un error en build().

It says (translating from spanish) "no rules to build libqt-mt" Error. Cancelling...
Googling about libqt-mt says something about some symbolic links to make. But I'm not sure about this.
I REALLY want this soft, any clues/ideas/hints??
By the way, my arch is x86_64, up to date.

janserv commented on 2011-05-07 21:06

Make sure you first build qt3 from ABS or grab the files from trunk.
Use my patch for piklab from the comment below.
Piklab builds fine here on x86_64.

construidor commented on 2011-05-07 18:48

On make:

/opt/qt/include/qvaluevector.h:244:13: error: ‘ptrdiff_t’ does not name a type
In file included from /opt/kde/include/kaboutdata.h:24:0,
from /home/construidor/src/pic16f84a/piklab/src/piklab-0.15.10/src/common/common/global.h:65,
from /home/construidor/src/pic16f84a/piklab/src/piklab-0.15.10/src/common/common/args.h:12,
from /home/construidor/src/pic16f84a/piklab/src/piklab-0.15.10/src/common/common/args.cpp:9:
/opt/qt/include/qimage.h: In member function ‘bool QImageTextKeyLang::operator<(const QImageTextKeyLang&) const’:
/opt/qt/include/qimage.h:58:61: warning: suggest parentheses around ‘&&’ within ‘||’ [-Wparentheses]
make[2]: ** [src/common/common/CMakeFiles/common.dir/args.o] Erro 1
make[1]: ** [src/common/common/CMakeFiles/common.dir/all] Erro 2
make: ** [all] Erro 2


construidor commented on 2011-05-07 11:57

==> Iniciando build()...
/tmp/yaourt-tmp-construidor/aur-piklab/./PKGBUILD: line 22: cmake: comando não encontrado

add cmake on dependency

Anonymous comment on 2011-05-01 23:26

After patching and compiling and installing qt3, patched piklab sources, when I try to compile I get this after a while

make[2]: *** No hay ninguna regla para construir el objetivo `/opt/qt/lib/libqt-mt', necesario para `src/devices/pic/xml/pic_xml_to_data'. Alto.
make[1]: *** [src/devices/pic/xml/CMakeFiles/pic_xml_to_data.dir/all] Error 2
make: *** [all] Error 2
==> ERROR: Se produjo un error en build().

Any ideas?

Anonymous comment on 2011-04-25 11:46

Thanx again!

janserv commented on 2011-04-25 06:59

I see now that qt3 is patched in trunk so you can wait for a new release or grep the build files from trunk and build it yourself.
For piklab get this patch and add it to the piklab build dir.
Put this line in the build() before cmake "patch -p1 -i ${srcdir}/device_xml_to_data.h.patch"

Anonymous comment on 2011-04-24 21:19

Thanx for the quick answer!
Would you please give more detailed instruction about the patching of qt3 and piklab??

janserv commented on 2011-04-24 16:32

If you are compiling with gcc 4.6 you first need to patch and rebuild qt3 with this patch
Then you need to patch and build piklab with this patch

If you don't want to rebuild qt3 than you have to build piklab with gcc 4.5.2

Anonymous comment on 2011-04-24 14:39

It does not compile

kevincox commented on 2011-03-07 21:37

How's this one?

tgoossens commented on 2011-03-07 19:03

The new PKGBUILD (from janerv's comment) works excellent!

The PKGBUILD from the AUR itself, doesn't build.

janserv commented on 2011-01-31 15:28

Again, here's a better PKGBUILD.

The wiki has an excellent article about creating PKGBUILD's, maybe you can read that first.

kevincox commented on 2011-01-25 01:40

Would you like me to maintain this???