Closed gavanderhoorn closed 9 years ago
Oops, sorry. I had tested it on Hydro on a0a7a15c, and it worked. The problems you describe are one commit later, on 3ee8460d. Apparently, that commit uses some new features from Indigo.
I've fixed the Indigo problems in the indigo
branch and then did a very evil thing and force-pushed hydro to be at a0a7a15c, where it compiles.
Since I force-pushed, you need to do a git checkout hydro && git fetch && git reset --hard origin/hydro
instead of a git pull
, assuming you have no local changes. Sorry for the mess, but I think this is better than a git revert, especially now before people actually start using the package.
I guess we will just abandon hydro and leave it at a0a7a15c? If we do that, I guess we also don't publish it to debs for hydro? Any thoughts, @hdeeken @jspricke ?
Actually we can keep hydro. Just another stupidity on my side, I instantiated the property pointers in the declarations, not in the constructor. seems to work nowadays but not on the old setup. anyways e1b5464c7398be1e2f00869fdb1f8b990d6a6007 fixes that ;) both distros now support the latest version.
As mentioned in #4, compilation currently fails because of
include/fps_motion_tool.h
still includingfps_motion_widget.h
.After commenting that particular include, I can compile under Indigo fine, but on Hydro, I get the following error(s) (I've shortened the paths):
and:
Afaict, the
hydro
andindigo
branches are identical, right?Some more info (apart from the (Indigo, Trusty) vs (Hydro, Precise) differences):
Hydro system: gcc 4.6.4, Qt 4.8.1 Indigo system: gcc 4.8.2, Qt 4.8.6