Closed GoogleCodeExporter closed 9 years ago
the experimental cutting simulation requires qt 4.7 which comes with Ubuntu
10.10.
You can delete your old CMakeCache.txt, then run
cmake -i
and select if you want to build the cutting simulation. if you select OFF, you
should be able to build without qt 4.7
the cutting simulation is currently very experimental and not useful for anyone
who is not a developer and wants to play with it and do programming.
Original comment by anders.e...@gmail.com
on 25 Apr 2011 at 2:00
Cutting simulation is off, but there are dependancys in ocl requiring it. These
seem to have been introduced in 720. My config lists that cutting simulation
will NOT be built, yet it does (and fails). Tested all releases up to 723.
Target seems to be ALL regardless of command to make. ("make ocl" vs "make
cutsim" vs "make all" build same.) Manually removing cutsim from Makefile2
fixes this but fails due to dependancies.
Something has happened, and I don't know the build system well enough to
pinpoint it, but it appears to start at 719->720.
Original comment by tha_krea...@hotmail.com
on 25 Apr 2011 at 7:04
could you try r724 which I just committed?
If you don't have Qt 4.7+ you should build with the setting "will NOT build ocl
cutting simulation"
most of the python scripts related to the old cutting simulation will not work
now. I hope to add some c++ examples for the new cutting sim eventually.
Original comment by anders.e...@gmail.com
on 26 Apr 2011 at 5:03
r724 builds correctly again on ubuntu 10.04 (shipped on EMC2 live cd) and it
seems like the zigzag paths are ok atleast. I was hoping for less leakage in
the waterlevel procedures from heeksCNC but I guess that's another story.
Will be looking into that later.
Original comment by tha_krea...@hotmail.com
on 26 Apr 2011 at 10:06
One thing: I really wish opencamlib would use tags so that other instructions
could say to check out a specific tag tested and known to work with their
respective releases. As-is most just say to check out trunk which is very
unstable...
A major-versioned tag that is moved up as development progresses, and
incremented whenever compatibility is broken would help a lot...
Original comment by tha_krea...@hotmail.com
on 26 Apr 2011 at 10:08
Yes, tags are probably a good idea. I will have to learn how they work and how
to transfer stuff from trunk to the 'stable' tag.
Original comment by anders.e...@gmail.com
on 27 Apr 2011 at 7:10
closing issue.
my cutsim experiments are now on github as separate projects.
https://github.com/aewallin/cutsim
and
https://github.com/aewallin/libcutsim
also see the OpenSCAM work by Joseph Coffland
http://openscam.com/
Original comment by anders.e...@gmail.com
on 19 Apr 2012 at 5:33
Original issue reported on code.google.com by
tha_krea...@hotmail.com
on 24 Apr 2011 at 11:59