Menu
▾
▴
piklab-users — For Users
You can subscribe to this list here.
| 2012 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
(2) |
Jul
(3) |
Aug
(3) |
Sep
|
Oct
|
Nov
(7) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Alan C. <ala...@gm...> - 2016-08-28 14:34:59
|
I used Piklab last in 2008 under OpenBSD and was fairly happy with it. So when I had an application for a PIC again I downloaded the current version and tried to build it. It's looking for linux/hiddev.h and I don't see any simple way in CMakeCache.txt to turn that off or set a NOTFOUND. Of course only Linux is going to have that. I did get it to build under Raspbian on my Raspberry Pi. I can live without HID stuff, I'd just like to work around it. Has this been abandoned since 2012, or is it considered the final version, or has it moved? -- Credit is the root of all evil. - AB1JX |
|
From: Antonio T. B. <an...@bo...> - 2013-07-09 05:23:21
|
VERSION: SVN Trunk , this moment July, 9 , 2013 4:00 Z OS: Ubuntu 13.04 SITUATION: compiled ok, instaled ok. When open any window, as programmer config, or even a warning window, like that say about voltages at ICD2, when I close those windows, all PIKLAB crashes. Running from a terminal, says: piklab(10610)/konsole Konsole::TerminalDisplay::setVTFont: Using an unsupported variable-width font in the terminal. This may produce display errors. piklab(10610)/konsole Konsole::TerminalDisplay::setVTFont: Using an unsupported variable-width font in the terminal. This may produce display errors. The program 'piklab' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 1604 error_code 3 request_code 20 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) piklab(10610)/konsole Konsole::SessionManager::~SessionManager: Konsole SessionManager destroyed with sessions still alive Seems that konsoles font config is a bit confused. REMEDY (nasty): apt-get purge konsole I have no konsole into piklab, but no crashes using it anymore Regards, *Antonio Augusto Todo Bom Neto Boole Embedded* PMI Membership ID: 2548138 |
|
From: Baltazar B. <bal...@ya...> - 2013-03-14 08:21:26
|
Hello, I am using Piklab on Ubuntu, great tool. Recently I needed to use a new PIC - the PIC16F1518. With lots of effort I managed to create necessary files and recompile Piklab from source so I can now build projects for this target. However, when I try to program the PIC with my direct programmer, I get the message "The current programmer "Direct programmer" does not support device "16F1518"". How could I solve this (if switching to some other programmer is not an option at this stage)? Is it possible to add support of new devices in piklab-prog? Thanky for any suggenstions. |
|
From: Nicolas H. <ha...@kd...> - 2012-11-08 06:15:20
|
Hi Adriano, there is currently no package in Ubuntu because there is no active maintainer. The only solution at the moment is to compile piklab by hand. It's not that complicated. Please refer to the following page: https://sourceforge.net/apps/mediawiki/piklab/index.php?title=Compilation_for_Linux If you run into problems, do not hesitate to email me and the user list. Regards, Nicolas On Mon, Nov 5, 2012 at 4:42 PM, al.advocacia <al....@bo...>wrote: > Hi. > > I use PikLab for some time in Ubuntu. However, I can not install it in > Ubuntu 12.04, which I currently use. Can I install PikLab in Ubuntu 12.04? > If yes, what should I do? (If I'm no using the appropriate way to get the > information, please orient me how I can get it). > Thank you. > > Adriano - Brazil > |
|
From: Nicolas <aa...@gm...> - 2012-11-08 05:47:56
|
Hi, It should now be fixed in the svn repository. Thanks! Nicolas On Wed, Nov 7, 2012 at 11:19 AM, bitlord <bit...@gm...> wrote: > On Wed, 7 Nov 2012 20:10:44 +0100 > bitlord <bit...@gm...> wrote: > > > Hello, > > > > I built 0.16.2 for testing, and when I try to configure toolchain > > Settings > Configure Toolchains ... > > Tried with 'PICC Compiler' and 'PICC Lite Compiler' selecting > > executable directory (I installed it as user in home directory > > "/home/<user>/bin/hitech/picc/9.83/bin" ) the program crashes. > > I don't know how to enable debug and compile it with debugging > > symbols, tried adding '-ggdb' to C and CXX FLAGS (test machine > > running gentoo (mostly stable)), but still get this: > > > > Reading symbols from /usr/bin/piklab...(no debugging symbols > > found)...done. > > > > Here is a backtrace I get with '-ggdb' > > > > piklab: version 0.16.2 (rev. distribution) > > [New Thread 0x7fffe7c5f700 (LWP 14317)] > > [New Thread 0x7fffe70c4700 (LWP 14344)] > > piklab(14314) KSambaSharePrivate::isSambaInstalled: Samba is not > > installed! piklab(14314) KSambaSharePrivate::findSmbConf: KSambaShare: > > Could not find smb.conf! piklab(14314) > > KSambaSharePrivate::isSambaInstalled: Samba is not installed! Qt has > > caught an exception thrown from an event handler. Throwing exceptions > > from an event handler is not supported in Qt. You must reimplement > > QApplication::notify() and catch all exceptions there. > > > > Qt has caught an exception thrown from an event handler. Throwing > > exceptions from an event handler is not supported in Qt. You must > > reimplement QApplication::notify() and catch all exceptions there. > > > > terminate called after throwing an instance of 'std::bad_alloc' > > what(): std::bad_alloc > > > > Program received signal SIGABRT, Aborted. > > 0x00007ffff3d9fcc5 in raise () from /lib64/libc.so.6 > > (gdb) bt > > #0 0x00007ffff3d9fcc5 in raise () from /lib64/libc.so.6 > > #1 0x00007ffff3da0edf in abort () from /lib64/libc.so.6 > > #2 0x00007ffff41bbb45 in __gnu_cxx::__verbose_terminate_handler() () > > from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 > > #3 0x00007ffff41ba246 in ?? () > > from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #4 > > 0x00007ffff41ba268 in std::terminate() () > > from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #5 > > 0x00007ffff41ba391 in __cxa_rethrow () > > from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #6 > > 0x00007ffff5a5972f in > > QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () > > from /usr/lib64/qt4/libQtCore.so.4 #7 0x00007ffff5a5d561 in > > QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #8 > > 0x00007ffff3d8d474 in __libc_start_main () from /lib64/libc.so.6 #9 > > 0x000000000044a839 in _start () > > Oh, little update (I hope it will get to the right thread, I don't know > how this mailing list works, but it looks strange, don't get my > messages in inbox). Now I tested it adding a path directly to the > "textbox" and it works fine, so the problem only exists if I click on > the little icon and search for a path/location > > > ------------------------------------------------------------------------------ > LogMeIn Central: Instant, anywhere, Remote PC access and management. > Stay in control, update software, and manage PCs from one command center > Diagnose problems and improve visibility into emerging IT issues > Automate, monitor and manage. Do more in less time with Central > http://p.sf.net/sfu/logmein12331_d2d > _______________________________________________ > Piklab-users mailing list > Pik...@li... > https://lists.sourceforge.net/lists/listinfo/piklab-users > |
|
From: bitlord <bit...@gm...> - 2012-11-07 19:20:14
|
On Wed, 7 Nov 2012 20:10:44 +0100 bitlord <bit...@gm...> wrote: > Hello, > > I built 0.16.2 for testing, and when I try to configure toolchain > Settings > Configure Toolchains ... > Tried with 'PICC Compiler' and 'PICC Lite Compiler' selecting > executable directory (I installed it as user in home directory > "/home/<user>/bin/hitech/picc/9.83/bin" ) the program crashes. > I don't know how to enable debug and compile it with debugging > symbols, tried adding '-ggdb' to C and CXX FLAGS (test machine > running gentoo (mostly stable)), but still get this: > > Reading symbols from /usr/bin/piklab...(no debugging symbols > found)...done. > > Here is a backtrace I get with '-ggdb' > > piklab: version 0.16.2 (rev. distribution) > [New Thread 0x7fffe7c5f700 (LWP 14317)] > [New Thread 0x7fffe70c4700 (LWP 14344)] > piklab(14314) KSambaSharePrivate::isSambaInstalled: Samba is not > installed! piklab(14314) KSambaSharePrivate::findSmbConf: KSambaShare: > Could not find smb.conf! piklab(14314) > KSambaSharePrivate::isSambaInstalled: Samba is not installed! Qt has > caught an exception thrown from an event handler. Throwing exceptions > from an event handler is not supported in Qt. You must reimplement > QApplication::notify() and catch all exceptions there. > > Qt has caught an exception thrown from an event handler. Throwing > exceptions from an event handler is not supported in Qt. You must > reimplement QApplication::notify() and catch all exceptions there. > > terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc > > Program received signal SIGABRT, Aborted. > 0x00007ffff3d9fcc5 in raise () from /lib64/libc.so.6 > (gdb) bt > #0 0x00007ffff3d9fcc5 in raise () from /lib64/libc.so.6 > #1 0x00007ffff3da0edf in abort () from /lib64/libc.so.6 > #2 0x00007ffff41bbb45 in __gnu_cxx::__verbose_terminate_handler() () > from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 > #3 0x00007ffff41ba246 in ?? () > from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #4 > 0x00007ffff41ba268 in std::terminate() () > from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #5 > 0x00007ffff41ba391 in __cxa_rethrow () > from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #6 > 0x00007ffff5a5972f in > QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () > from /usr/lib64/qt4/libQtCore.so.4 #7 0x00007ffff5a5d561 in > QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #8 > 0x00007ffff3d8d474 in __libc_start_main () from /lib64/libc.so.6 #9 > 0x000000000044a839 in _start () Oh, little update (I hope it will get to the right thread, I don't know how this mailing list works, but it looks strange, don't get my messages in inbox). Now I tested it adding a path directly to the "textbox" and it works fine, so the problem only exists if I click on the little icon and search for a path/location |
|
From: bitlord <bit...@gm...> - 2012-11-07 19:11:08
|
Hello, I built 0.16.2 for testing, and when I try to configure toolchain Settings > Configure Toolchains ... Tried with 'PICC Compiler' and 'PICC Lite Compiler' selecting executable directory (I installed it as user in home directory "/home/<user>/bin/hitech/picc/9.83/bin" ) the program crashes. I don't know how to enable debug and compile it with debugging symbols, tried adding '-ggdb' to C and CXX FLAGS (test machine running gentoo (mostly stable)), but still get this: Reading symbols from /usr/bin/piklab...(no debugging symbols found)...done. Here is a backtrace I get with '-ggdb' piklab: version 0.16.2 (rev. distribution) [New Thread 0x7fffe7c5f700 (LWP 14317)] [New Thread 0x7fffe70c4700 (LWP 14344)] piklab(14314) KSambaSharePrivate::isSambaInstalled: Samba is not installed! piklab(14314) KSambaSharePrivate::findSmbConf: KSambaShare: Could not find smb.conf! piklab(14314) KSambaSharePrivate::isSambaInstalled: Samba is not installed! Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Program received signal SIGABRT, Aborted. 0x00007ffff3d9fcc5 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff3d9fcc5 in raise () from /lib64/libc.so.6 #1 0x00007ffff3da0edf in abort () from /lib64/libc.so.6 #2 0x00007ffff41bbb45 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #3 0x00007ffff41ba246 in ?? () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #4 0x00007ffff41ba268 in std::terminate() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #5 0x00007ffff41ba391 in __cxa_rethrow () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #6 0x00007ffff5a5972f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #7 0x00007ffff5a5d561 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #8 0x00007ffff3d8d474 in __libc_start_main () from /lib64/libc.so.6 #9 0x000000000044a839 in _start () |
|
From: Butuza T. <tbu...@fr...> - 2012-11-02 17:28:01
|
After installing kdelibs5-dev package, piklab compiles and runs successfully,Imre and Zsolt, thank you for help. Best regards,Tamas |
|
From: Péntek I. <pen...@gm...> - 2012-11-02 11:42:42
|
Hello, Maybe you didn't know, there's a command apt-file in Ubuntu: root@ubuntu:~# apt-file search FindKDE4Internal.cmake The program 'apt-file' is currently not installed. You can install it by typing: apt-get install apt-file Oops, fresh install, so: root@ubuntu:~# apt-get install apt-file [...] GUI might offer to run apt-file update for you, but I suggest to run it from the terminal as root instead: root@ubuntu:~# apt-file update [...] root@ubuntu:~# apt-file search FindKDE4Internal.cmake kdelibs5-dev: /usr/share/kde4/apps/cmake/modules/FindKDE4Internal.cmake root@ubuntu:~# so now you know that the file actually missing is shipped by the Ubuntu package named kdelibs5-dev Good luck! -- Üdvözlettel: Ifj. Péntek Imre E-Mail: pen...@gm... On Thursday 01 November 2012 11:26:56 Butuza Tamas wrote: > Dear piklab users and developers, I tried to compile and install Piklab > (latest source) on Ubuntu 12.04 but have no success.I got the following > error: -- Found LIBUSB -- LIBUSB version: 0.1.12 > CMake Error at /usr/share/cmake-2.8/Modules/FindKDE4.cmake:98 (MESSAGE): > ERROR: cmake/modules/FindKDE4Internal.cmake not found in > /home/tbutuza/.kde/share/apps;/usr/share/kde4/apps > Call Stack (most recent call first): > cmake/Piklab.cmake:57 (find_package) > CMakeLists.txt:21 (include) This is the point, where I cannot proceed.I > have no idea what should I do. Could you please help me what do I do, or > could somebody give me binary package for Ubuntu? Thanks in advance,Tamas |
|
From: Butuza T. <tbu...@fr...> - 2012-11-01 10:27:04
|
Dear piklab users and developers, I tried to compile and install Piklab (latest source) on Ubuntu 12.04 but have no success.I got the following error: -- Found LIBUSB -- LIBUSB version: 0.1.12 CMake Error at /usr/share/cmake-2.8/Modules/FindKDE4.cmake:98 (MESSAGE): ERROR: cmake/modules/FindKDE4Internal.cmake not found in /home/tbutuza/.kde/share/apps;/usr/share/kde4/apps Call Stack (most recent call first): cmake/Piklab.cmake:57 (find_package) CMakeLists.txt:21 (include) This is the point, where I cannot proceed.I have no idea what should I do. Could you please help me what do I do, or could somebody give me binary package for Ubuntu? Thanks in advance,Tamas |
|
From: Nicolas <aa...@gm...> - 2012-08-16 06:47:47
|
Hi,
I put your fix in the development tree.
Thanks!
Nicolas
On Wed, Aug 15, 2012 at 2:41 PM, bitlord <bit...@gm...> wrote:
> On Wed, 2012-08-15 at 23:02 +0200, bitlord wrote:
> > Hello, I'm new to this list, first I want to thank everyone who worked
> > on this software, it is great, and allows me to use my ICD2 on linux.
> >
> > I'm using fedora distribution, and now in fedora 17 we have
> > piklab-0.15.12, and I wanted a 0.16.1 and tried to update .spec file,
> > then tried to build a package.
> >
> > But I got some errors
> >
> > In file included
> > from
> /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/common/args.h:12:0,
> from
> /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/common/args.cpp:9:
> >
> /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/common/global.h:53:28:
> fatal error: kapplication.h: No such file or directory
> > compilation terminated.
> > In file included
> > from
> /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/port/port.h:12:0,
> from
> /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/port/port_base.h:12,
> from
> /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/port/parallel.h:14,
> from
> /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/port/parallel.cpp:11:
> >
> /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/common/global.h:53:28:
> fatal error: kapplication.h: No such file or directory
> > compilation terminated.
> >
> > I think I have all build dependencies installed, kapplication.h is from
> > kdelibs-devel package, and it is found at the beginning
> > -- Found KDE 4.8 include dir: /usr/include/kde4
> >
> > but probably missing -I/usr/include/kde4 later
> >
> > Few important things: I'm not a developer, know almost nothing about
> > build systems.
> > I got a small hint from someone with a lot more experience to add
> > include_directories(${KDE4_INCLUDES}) to CMakeLists.txt but I don't know
> > in which one, tried with this simple patch for
> > src/common/common/CMakeLists.txt
> > ...
> > @@ -1,4 +1,5 @@
> > include_directories(${CMAKE_CURRENT_SOURCE_DIR})
> > +include_directories(${KDE4_INCLUDES})
> >
> > SET(common_STAT_SRCS
> > args.cpp
> >
> > I think that helped for the first error.
> >
> >
> >
> >
> A lot of people from #fedora-kde on freenode helped me with building rpm
> package, and <Kevin_Kofler> found the problem and solution for it. Now
> it builds fine, just some minor tweaking needed in spec file I think
>
> Sorry if this reply doesn't get well combined in the thread, I didn't
> configured my account on mailing list to send me messages which I send
> to mailing list so I didn't know how to reply (I don't use mailing list
> much)
>
>
> Here is the patch
> --- cmake/Piklab.cmake_orig 2012-08-15 23:21:25.515511895 +0200
> +++ cmake/Piklab.cmake 2012-08-15 23:21:52.746171465 +0200
> @@ -27,7 +27,7 @@
> else(QT_ONLY)
> find_package(KDE4 REQUIRED)
> add_definitions(${QT_DEFINITIONS} ${KDE4_DEFINITIONS})
> - include_directories( ${KDE4_INCLUDE_DIRS})
> + include_directories( ${KDE4_INCLUDES})
> set(EXE_LIBS ${QT_LIBRARIES} ${KDE4_KDECORE_LIBS} ${KDE4_KIO_LIBS}
> kde)
> set(GUI_LIBS ${KDE4_KDEUI_LIBS} ${KDE4_KDE3SUPPORT_LIBS} ${EXE_LIBS}
> kde_gui ${KDE4_KTEXTEDITOR_LIBS} ${KDE4_KFILE_LIBS})
> endif(QT_ONLY)
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Piklab-users mailing list
> Pik...@li...
> https://lists.sourceforge.net/lists/listinfo/piklab-users
>
|
|
From: bitlord <bit...@gm...> - 2012-08-15 21:43:30
|
On Wed, 2012-08-15 at 23:02 +0200, bitlord wrote:
> Hello, I'm new to this list, first I want to thank everyone who worked
> on this software, it is great, and allows me to use my ICD2 on linux.
>
> I'm using fedora distribution, and now in fedora 17 we have
> piklab-0.15.12, and I wanted a 0.16.1 and tried to update .spec file,
> then tried to build a package.
>
> But I got some errors
>
> In file included
> from /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/common/args.h:12:0, from /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/common/args.cpp:9:
> /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/common/global.h:53:28: fatal error: kapplication.h: No such file or directory
> compilation terminated.
> In file included
> from /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/port/port.h:12:0, from /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/port/port_base.h:12, from /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/port/parallel.h:14, from /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/port/parallel.cpp:11:
> /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/common/global.h:53:28: fatal error: kapplication.h: No such file or directory
> compilation terminated.
>
> I think I have all build dependencies installed, kapplication.h is from
> kdelibs-devel package, and it is found at the beginning
> -- Found KDE 4.8 include dir: /usr/include/kde4
>
> but probably missing -I/usr/include/kde4 later
>
> Few important things: I'm not a developer, know almost nothing about
> build systems.
> I got a small hint from someone with a lot more experience to add
> include_directories(${KDE4_INCLUDES}) to CMakeLists.txt but I don't know
> in which one, tried with this simple patch for
> src/common/common/CMakeLists.txt
> ...
> @@ -1,4 +1,5 @@
> include_directories(${CMAKE_CURRENT_SOURCE_DIR})
> +include_directories(${KDE4_INCLUDES})
>
> SET(common_STAT_SRCS
> args.cpp
>
> I think that helped for the first error.
>
>
>
>
A lot of people from #fedora-kde on freenode helped me with building rpm
package, and <Kevin_Kofler> found the problem and solution for it. Now
it builds fine, just some minor tweaking needed in spec file I think
Sorry if this reply doesn't get well combined in the thread, I didn't
configured my account on mailing list to send me messages which I send
to mailing list so I didn't know how to reply (I don't use mailing list
much)
Here is the patch
--- cmake/Piklab.cmake_orig 2012-08-15 23:21:25.515511895 +0200
+++ cmake/Piklab.cmake 2012-08-15 23:21:52.746171465 +0200
@@ -27,7 +27,7 @@
else(QT_ONLY)
find_package(KDE4 REQUIRED)
add_definitions(${QT_DEFINITIONS} ${KDE4_DEFINITIONS})
- include_directories( ${KDE4_INCLUDE_DIRS})
+ include_directories( ${KDE4_INCLUDES})
set(EXE_LIBS ${QT_LIBRARIES} ${KDE4_KDECORE_LIBS} ${KDE4_KIO_LIBS}
kde)
set(GUI_LIBS ${KDE4_KDEUI_LIBS} ${KDE4_KDE3SUPPORT_LIBS} ${EXE_LIBS}
kde_gui ${KDE4_KTEXTEDITOR_LIBS} ${KDE4_KFILE_LIBS})
endif(QT_ONLY)
|
|
From: bitlord <bit...@gm...> - 2012-08-15 21:04:38
|
Hello, I'm new to this list, first I want to thank everyone who worked
on this software, it is great, and allows me to use my ICD2 on linux.
I'm using fedora distribution, and now in fedora 17 we have
piklab-0.15.12, and I wanted a 0.16.1 and tried to update .spec file,
then tried to build a package.
But I got some errors
In file included
from /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/common/args.h:12:0, from /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/common/args.cpp:9:
/home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/common/global.h:53:28: fatal error: kapplication.h: No such file or directory
compilation terminated.
In file included
from /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/port/port.h:12:0, from /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/port/port_base.h:12, from /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/port/parallel.h:14, from /home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/port/parallel.cpp:11:
/home/bitlord/rpmbuild/BUILD/piklab-0.16.1/src/common/common/global.h:53:28: fatal error: kapplication.h: No such file or directory
compilation terminated.
I think I have all build dependencies installed, kapplication.h is from
kdelibs-devel package, and it is found at the beginning
-- Found KDE 4.8 include dir: /usr/include/kde4
but probably missing -I/usr/include/kde4 later
Few important things: I'm not a developer, know almost nothing about
build systems.
I got a small hint from someone with a lot more experience to add
include_directories(${KDE4_INCLUDES}) to CMakeLists.txt but I don't know
in which one, tried with this simple patch for
src/common/common/CMakeLists.txt
...
@@ -1,4 +1,5 @@
include_directories(${CMAKE_CURRENT_SOURCE_DIR})
+include_directories(${KDE4_INCLUDES})
SET(common_STAT_SRCS
args.cpp
I think that helped for the first error.
|
|
From: Nicolas <aa...@gm...> - 2012-07-04 20:03:21
|
Hi Pal, On Wed, Jul 4, 2012 at 10:50 AM, Csanyi Pal <csa...@gm...> wrote: > After that I try to run piklab by running 'piklab' command on the > command line of an xterm window but get message: > > piklab: error while loading shared libraries: libkdecore.so.4: cannot > open shared object file: No such file or directory > > How can I solve this problem? > > As far as I know, libkdecore.so.4 is for KDE3. Are you sure you don't have another version of piklab installed? > > I tried to contact the Debian packager for Piklab but she has not > > answered me. I also just opened a packaging request for Ubuntu ( > > https://bugs.launchpad.net/ubuntu/+bug/1019705). We may need to open > > a bug for Debian too... > > So I can produce the piklab debian package but I'm not a Debian > Developer so I can't upload it to Debian Repository. What can I do > regardnig this issue? > > I am unsure how to proceed; note that there is most probably additional work to have a compliant package. Here is some documentation I found about contacting package maintainer: http://www.debian.org/doc/manuals/developers-reference/beyond-pkging.html#mia-qa You probably want to send an email to pi...@pa... to try to contact the maintainer again. Regards, Nicolas |
|
From: Csanyi P. <csa...@gm...> - 2012-07-04 17:50:20
|
Hi Nicolas, Sat, 30 Jun 2012 19:19:04 -0700 -n Nicolas <aa...@gm...> írta: > I don't know how to make a Debian package for Piklab. I find out how to make it. I made a piklab debian package with the following steps: tar -xvf piklab-0.16.0.tar.bz2 cd piklab-0.16.0/ dh_make -e csa...@gm... -c gpl2 --createorig Type of package: single binary, indep binary, multiple binary, library, kernel module, kernel patch? [s/i/m/l/k/n] s Done. Please edit the files in the debian/ subdirectory now. piklab uses a configure script, so you probably don't have to edit the Makefiles. dpkg-buildpackage -rfakeroot After I get the piklab_0.16.0-1_amd64.deb package and install it successfully with: sudo dpkg -i piklab_0.16.0-1_amd64.deb After that I try to run piklab by running 'piklab' command on the command line of an xterm window but get message: piklab: error while loading shared libraries: libkdecore.so.4: cannot open shared object file: No such file or directory How can I solve this problem? > I tried to contact the Debian packager for Piklab but she has not > answered me. I also just opened a packaging request for Ubuntu ( > https://bugs.launchpad.net/ubuntu/+bug/1019705). We may need to open > a bug for Debian too... So I can produce the piklab debian package but I'm not a Debian Developer so I can't upload it to Debian Repository. What can I do regardnig this issue? -- Regards from Pal |
|
From: Nicolas <aa...@gm...> - 2012-07-01 02:19:50
|
Hi Pal, I don't know how to make a Debian package for Piklab. I tried to contact the Debian packager for Piklab but she has not answered me. I also just opened a packaging request for Ubuntu ( https://bugs.launchpad.net/ubuntu/+bug/1019705). We may need to open a bug for Debian too... Regards, Nicolas On Sat, Jun 30, 2012 at 11:35 AM, Csanyi Pal <csa...@gm...> wrote: > Hi, > > my system is Debian GNU/Linux testing/sid. > > I have downloaded and unpacked the piklab-0.16.0.tar.bz2. > > I did the following so far: > $ cmake . > $ make > > It is left only to do > $ sudo make install > > but I would prefer to install this Piklab version as a debian package. > > Can I get somehow an installable debian package from this source: > piklab-0.16.0.tar.bz2 ? > > If can't then how can I build the Piklab source to get an > installable Piklab debian package? > > -- > Regards from Pal > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Piklab-users mailing list > Pik...@li... > https://lists.sourceforge.net/lists/listinfo/piklab-users > |
|
From: Csanyi P. <csa...@gm...> - 2012-06-30 18:36:00
|
Hi, my system is Debian GNU/Linux testing/sid. I have downloaded and unpacked the piklab-0.16.0.tar.bz2. I did the following so far: $ cmake . $ make It is left only to do $ sudo make install but I would prefer to install this Piklab version as a debian package. Can I get somehow an installable debian package from this source: piklab-0.16.0.tar.bz2 ? If can't then how can I build the Piklab source to get an installable Piklab debian package? -- Regards from Pal |
|
From: Péntek I. <pen...@gm...> - 2012-06-15 08:38:35
|
Hello! I am unable to program my pic18f4550 chip with an ICD2.5USB programmer (80x126x26mm white box with a telephone-like ICSP socket). The actual output is: user@host:~/pic/piklab/bin$ sudo ./piklab-prog --debug --port usb --programmer icd2 --device 18F4550 --firmware-dir /home/user/pic/MPLAB\ IDE/ICD2/ --target-self-powered true -c connect piklab-prog: version 0.16.0 (rev. distribution) Connecting ICD2 Programmer on USB Port with device 18F4550... Firmware id is 5 and we want 5 Firmware version is 1.4.5 Set target Set target self powered: true Hold reset Programmer Vpp = 11.7424 V Target Vdd = 0.62528 V Target Vpp = 11.982 V Self-test Warning: Self-test failed: Target Vdd=Low; Module Vpp=Pass; MCLR ground=Pass; MCLR Vdd=Low; MCLR Vpp=Pass Warning: Self-test failed (Target Vdd=Low; Module Vpp=Pass; MCLR ground=Pass; MCLR Vdd=Low; MCLR Vpp=Pass). Do you want to continue anyway? *no* user@host:~/pic/piklab/bin$ sudo ./piklab-prog --debug --port usb --programmer icd2 --device 18F4550 --firmware-dir /home/user/pic/MPLAB\ IDE/ICD2/ --target-self-powered true -c program /home/user/pic/t2/kimenet.hex piklab-prog: version 0.16.0 (rev. distribution) Connecting ICD2 Programmer on USB Port with device 18F4550... Firmware id is 5 and we want 5 Firmware version is 1.4.5 Set target Set target self powered: true Hold reset Programmer Vpp = 11.7424 V Target Vdd = 5.19764 V Target Vpp = 11.982 V Self-test Connected. Enter normal mode Already in requested mode. Warning: Unknown or incorrect device (Read id is 0xFFFF). Warning: Unknown device. *no* user@host:~/pic/piklab/bin$ sudo ./piklab-prog --debug --port usb --programmer icd2 --device 18F4550 --firmware-dir /home/user/pic/MPLAB\ IDE/ICD2/ --target-self-powered true -c run piklab-prog: version 0.16.0 (rev. distribution) Connecting ICD2 Programmer on USB Port with device 18F4550... Firmware id is 5 and we want 5 Firmware version is 1.4.5 Set target Set target self powered: true Hold reset Programmer Vpp = 11.7424 V Target Vdd = 5.19764 V Target Vpp = 11.982 V Self-test Connected. Enter normal mode Already in requested mode. Warning: Unknown or incorrect device (Read id is 0xFFFF). Warning: Unknown device. *no* It might be the Target Vdd=Low, but I have an external 5.00V supply attached, so I don't understand (maybe 5.00 is too low? I don't know) Also I wasn't able to find anything useful using google. Any sugestion would be appreciated. Thank you for your help in advance. -- Üdvözlettel: Ifj. Péntek Imre E-mail: pen...@gm... |
|
From: Alain P. <ala...@un...> - 2012-03-19 09:43:50
|
Hi Gál, Could you please try this patch ? Regards, Alain |
|
From: Alain P. <ala...@un...> - 2012-03-15 10:15:21
|
Hello world! |
|
From: Gál Z. <tra...@fr...> - 2012-03-15 09:25:57
|
I checked out the latest version of piklab from svn and I tried to compile it. I got this message: [ 64%] Built target misc_check Linking CXX executable save_load_memory_check ../../common/cli/libcli.a(cli_interactive.o): In function `Interactive': /home/zsolti/svn/trunk/piklab/src/common/cli/cli_interactive.cpp:36: undefined reference to `using_history' /home/zsolti/svn/trunk/piklab/src/common/cli/cli_interactive.cpp:36: undefined reference to `using_history' ../../common/cli/libcli.a(cli_interactive.o): In function `CLI::Interactive::redisplayPrompt()': /home/zsolti/svn/trunk/piklab/src/common/cli/cli_interactive.cpp:51: undefined reference to `rl_forced_update_display' ../../common/cli/libcli.a(cli_interactive.o): In function `CLI::Interactive::displayPrompt()': /home/zsolti/svn/trunk/piklab/src/common/cli/cli_interactive.cpp:61: undefined reference to `readline' /home/zsolti/svn/trunk/piklab/src/common/cli/cli_interactive.cpp:63: undefined reference to `add_history' collect2: ld returned 1 exit status make[2]: *** [src/piklab-test/save_load_memory/save_load_memory_check] Error 1 make[1]: *** [src/piklab-test/save_load_memory/CMakeFiles/save_load_memory_check.dir/all] Error 2 make: *** [all] Error 2 -- ~~~~~~~~~~~~~~~~ http://galzsolt.zzl.org |
