Machine:
Operating System Type : GNU/Linux
OS Name : Kubuntu
OS Version : 14.04.2 LTS, Trusty Tahr
Architecture : AMD64
Kernel Release : 3.13.0-53-generic
Hostname : kubuntu
Error Message:
tommy@kubuntu:~/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build$ cmake -DCMAKE_VERBOSE_MAKEFILE=ON ..
CMake Warning at /usr/share/cmake-2.8/Modules/FindQt4.cmake:659 (message):
/usr/bin/qmake reported QT_INSTALL_LIBS as "/usr/lib/x86_64-linux-gnu" but
QtCore could not be found there. Qt is NOT installed correctly for the
target build environment.
Call Stack (most recent call first):
CMakeLists.txt:6 (find_package)
CMake Error at /usr/share/cmake-2.8/Modules/FindQt4.cmake:664 (message):
Could NOT find QtCore. Check
/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build/CMakeFiles/CMakeError.log
for more details.
Call Stack (most recent call first):
CMakeLists.txt:6 (find_package)
CMake Warning (dev) in CMakeLists.txt:
No cmake_minimum_required command is present. A line of code such as
cmake_minimum_required(VERSION 2.8)
should be added at the top of the file. The version specified may be lower
if you wish to support older CMake versions for this project. For more
information run "cmake --help-policy CMP0000".
This warning is for project developers. Use -Wno-dev to suppress it.
-- Configuring incomplete, errors occurred!
See also "/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build/CMakeFiles/CMakeOutput.log".
Update on 2015.07.10: The basic issue is that if libglib2.0-dev is not found, then buildsystem generation fails.
Hi Tom,
thanks for the feedback.
Based on the error message, it looks like you don't have the Qt4 development package installed. You will also need kdelibs development packages, for compiling ktechlab. I recommend installing the KDElibs4 and Qt4 development packages first:
sudo apt-get install kdelibs5-dev
(this will allso install Qt4 development files; the package name is from ubuntu 14.04, don't ask why it has "5" in it).
Then, for compiling, I recommend to run the script included in the source directory:
ktechlab-0.3-port-0.3.8-kde4-v1$
bash ./build-simple.sh
If the script finishes with success, then you can run ktechlab by:
ktechlab-0.3-port-0.3.8-kde4-v1$
bash ./run-simple.sh
I know that the documentation doesn't specify this; it needs updating.
Hi, Zoltan,
I have attached some file for you to peruse to see what exactly is
going on. I did install the kdelibs5-dev file(s). Then followed
your instructions after deleting all the existing file/directories
and untarring them all over and doing the ./build-simple.sh.
It failed, hence, this reply with appropriate attached files.
Tom Bell
On 06/08/2015 10:10 AM, Zoltan P wrote:
Related
Bugs:
#25Hmm.. this is unexpected. Could you please also attach the
build-simple.log
file from the same directory as build-simple.sh ? This file should contain the output of build-simple.sh, and hopefully some clue about the cause of the build failure.The attachment you requested is included.
I don't know if you can receive the attachment
through the list, so I have sent it to your address
as well as "replying".
Thank you!
Tom Bell
On 06/09/2015 06:40 AM, Zoltan P wrote:
Related
Bugs:
#25I have got the attachement, in both locations: through email and also through the web interface here:
https://sourceforge.net/p/ktechlab/bugs/25/
Based on the log, it now is clear to me what is the issue: because of a bug in the cmake buildsystem files in ktechlab, if glib2 development files are not found, then buildsystem generation fails, and thus compilation fails.
A quick workaround is to install glib2 development files ( package name should be
libglib2.0-dev
), and try again compiling ktechlab.The longer way is to wait for me until I fix the build for the case when glib2 development files are not found -- they should be an optional dependency, needed for gpsim. Probably I will have time to fix this in the weekend.
Also note that you don't have the pic simulator development package is not installed (
gpsim-dev
), so pic simulation support for ktechlab will be disabled at compile-time (this is also an optional dependency, and it depends on glib2 ).Hope you manage to compile and run KTechLab, finally.
I installed libglib2.0-dev and gpsim, as well as gpsim-dev and got the
following results:
./build-simple.sh
+ readlink -f ./build-simple.sh
+ dirname
/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build-simple.sh
+ SCRIPTDIR=/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1
+
LOGFILE=/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build-simple.log
+ date
+ log_cmd echo == starting build at Wed Jun 10 13:46:42 EDT 2015 ==
+ echo == starting build at Wed Jun 10 13:46:42 EDT 2015 ==
+ tee -a
/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build-simple.log
== starting build at Wed Jun 10 13:46:42 EDT 2015 ==
+ mkdir -p
/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build-simple/
+ cd /home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build-simple/
+ [ -f
/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build-simple/CMakeCache.txt
]
+ echo buildsystem generated, using it
buildsystem generated, using it
+ log_cmd make -C
/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build-simple/src/core
+ tee -a
/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build-simple.log
+ make -C
/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build-simple/src/core
make: Entering directory
/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build-simple/src/core' make: *** No targets specified and no makefile found. Stop. make: Leaving directory
/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build-simple/src/core'+ log_cmd make install -j2
+ tee -a
/home/tommy/Downloads/ktechlab-0.3-port-0.3.8-kde4-v1/build-simple.log
+ make install -j2
make: *** No rule to make target `install'. Stop.
On 06/10/2015 04:21 AM, Zoltan P wrote:
--
"The only thing necessary for the triumph of evil
is for good men to do nothing" .- Edmund Burke
Related
Bugs:
#25It tries to reuse the build results ("buildsystem") from the previous
run of simple-build.sh. And it fails, because the previous run has
been incomplete, and the "buildsystem" part has not been generated
completely. Please delete the "build-simple" directory, and re-run the
simple-build.sh script.
A little technical note: CMake is a buildsystem generator, this being
is run first, and it creates a buildsystem inside the build-simple
directory. This has been failing. After CMake, make is needed to
actually perform the compilation / installing of the source code. All
of this is automated by the simple-build.sh script.
2015-06-10 21:03 GMT+03:00 Tom Bell old_timer@users.sf.net:
Related
Bugs:
#25I included the CMakeError.log, CMakeOutput.log and the output.log in the
attached .gz file.
In the output.log that is a copy of the CLI output, I added some lines
that start and end with 3 asterisks. The other two files came from the
build-simple/CMakeFiles/ directory as you requested.
Tom Bell
On 06/11/2015 04:08 AM, Zoltan P wrote:
--
"The only thing necessary for the triumph of evil
is for good men to do nothing" .- Edmund Burke
Zoltan,
When you are ready, I both the git copy of ktechlab
and the .deb files in different directories. I can
test them for you want me to try.
The .deb directory has the build-simple.sh file, while
the git directory has not.
Whenever you or someone else has a solution to try,
let me know.
Thank you!
Tom Bell
--
"The only thing necessary for the triumph of evil
is for good men to do nothing" .- Edmund Burke
Hi Tom,
I've just pushed a new update to github:
https://github.com/ktechlab/ktechlab-0.3/tree/port-0.3.8-kde4-v1
With this update, ktechlab should compile on Ubuntu 14.04.2, 64 bit.
Note that currently GPSim is not detected, thus PIC simulation will be
not available. Besides this limitation, ktechlab should compile and
run.
For testing, I recommend to get the sources from github, either with
git, or just downloading the latest version as a zip (
https://github.com/ktechlab/ktechlab-0.3/archive/port-0.3.8-kde4-v1.zip
).
Any feedback is welcome,
Zoltan
2015-07-05 13:52 GMT+03:00 Tom Bell old_timer@users.sf.net:
Related
Bugs:
#25On 07/05/2015 10:50 AM, Zoltan P wrote:
Zoltan,
Thanks. That did not work. When I did a git pull, it said
that the files were all up-to-date so I downloaded the .zip
file and deleted the old directory before unzipping the file.
My GIT clone is in a different directory, ktechlab, and not
affected by the download.
I have attached the appropriate files for your perusal.
I have also installed GPSIM and GPSIM-DEV (version 0.27.0).
Thank you!
Tom
--
"The only thing necessary for the triumph of evil
is for good men to do nothing" .- Edmund Burke
I'm supposing that you have used the
build-simple.sh
script. Couldyou please send me the log file of that script, named
build-simple.log
? Without that, the CMake*.log files are not usefulfor me.
2015-07-05 21:08 GMT+03:00 Tom Bell old_timer@users.sf.net:
Related
Bugs:
#25Zoltan,
build-simple.log attached as requested.
Tom
On 07/06/2015 04:25 AM, Zoltan P wrote:
--
"The only thing necessary for the triumph of evil
is for good men to do nothing" .- Edmund Burke
Thanks for the log.
I've pushed one more fix to github (
https://github.com/ktechlab/ktechlab-0.3/tree/port-0.3.8-kde4-v1 ).
With this fix, on my test virtual machine, on xubuntu 14.04.2, 64 bit,
ktechlab compiles relatively cleanly, without strange errors from
cmake.
If it still doesn't compile by using the
build-simple.sh
script,then please let me know, and please attach the
build-simple.log
build-log file.
2015-07-06 12:11 GMT+03:00 Tom Bell old_timer@users.sf.net:
Related
Bugs:
#25Zoltan,
That built just fine and run-simple.sh works good.
I have to download the .zip since this particular
build I don't have a git clone and can't do a pull.
However, at least, we know it works on a true AMD64.
Thank you!
I will await further builds while checking this one
out for problems and let you know.
Tom
On 07/06/2015 12:15 PM, Zoltan P wrote:
--
"The only thing necessary for the triumph of evil
is for good men to do nothing" .- Edmund Burke
This is great news. Thanks for the testing and have fun.
2015-07-06 22:41 GMT+03:00 Tom Bell old_timer@users.sf.net:
Related
Bugs:
#25I ran run-simple.sh and it does work.
However, the circuit attempted to build crashed at one
point and I filled out the crash info which was sent to
"Ktechlab-devel" list at SourceForge.org
If you would rather I send such reports to this address
I can do that.
Tom
"Facts do not cease to exist because they are ignored." -- Aldous Huxley
Hello Tom,
I have got your emails on the ktechlab-devel list. Only now I had time to
respond (probably they will be sent about the same time from my email
client). In my opinion that list is fine for discussing bug reports, or
anything related to ktechlab.
For keeping things organized, I propose that if you find new bugs, then
please open a new bug report for each specific issue, either on
sourceforge, or on github. I will get notifications from both location.
For non-private discussions I recommend ktechlab-devel mailing list from
sourceforge; for private discusssions feel free to send me emails.
Best regards,
Zoltan
On Thu, 09 Jul 2015 01:25:04 +0300, Tom Bell old_timer@users.sf.net
wrote:
Diff:
Zoltan,
I have been running some tests and have found it more efficient
to turn off simulation before changing the circuit in any way.
I also timed the clock circuit, 1 Hz, and found it cycled
approximately every 14.947 seconds.
I did this using the circuit setup in the photo attached.
A somewhat simple setup, but effective. Using a program called
stopwatch I was able to time when the clock cycled and when
the second cycle started and they are about the same, depending
on my reflexes starting and stopping the timer.
Just some observations so far.
Is anyone planning on adding a Hertz adjust for the clock circuit?
I can do some limited programming, mostly assembly, matlab, bash,
flowcode, java, C, C++, VHDL and Ada, but that is the limit of my
experience. I would love to help program, but, looking at your
code so far it is a little beyond me.
I have a BS in Electronics Engineering and can pretty well wring
out the bugs that appear and report them.
I have gotten in the habit of adding a component to the circuit
and then merely copy-and-paste additional of the same component.
It seems to help me. I also SAVE after every component/wire change
regardless of the tedium.
Anything you want to do, just let me know, especially, any new
changes you want tested.
Oh, and a new address to contact you at, so I don't keep adding to
this bug report.
Thank you!
Tom
"A government for protecting business only is but a carcass
and soon fails by its own corruption and decay."
-- Amos Bronson Alcott (1799-1888), Transcendentalist, writer
and philosopher.
Hello Tom,
please find my answers inline below.
On Fri, 10 Jul 2015 14:52:34 +0300, Tom Bell old_timer@users.sf.net
wrote:
The simulation doesn't actually run in real-time, but at something like
15*10^6 slower than the wall clock. I'm not sure about the actual figure.
For analog simulation I guess there doesn't exist a powerful enough CPU,
and I assume that the digital simulation is synchronized to the analog
one. I recommend to start a discussion about this topic on the
ktechlab-devel mailing list. There had been some discussion on this topic
a few years ago, but there was no conclusion.
I'm not planning currently because I prefer to fix the most urgent
porting-related bugs. I recommend to ask on the mailing list. It would be
nice to have a discussion about what would be the technically correct fix
for this timing delay.
KTechLab is written and C++ and uses Qt. If you would like to learn those,
then feel free to fix simple things. I can review your changes (or
somebody else on the mailing list).
If you don't feel like getting deep into C++ and Qt, then that's fine
also. Any help is welcome :)
Yes, unfortunately KTechLab crashes way to often to be useful. I really
want to change this (and already fixed a few things).
Usually after I commit some changes, I make an announcement on the mailing
list. The last one I sent had been at last Wednesday night.
I've got your emails, and responded.
Have fun,
Zoltan