Post Reply 
Complex Lock mode for WP-34s
05-03-2015, 09:43 PM
Post: #56
RE: Complex Lock mode for WP-34s
(05-03-2015 12:53 AM)BarryMead Wrote:  I just tried to apply the latest version of cmode.patch to the latest source tree svn revision 3782, and the Qt Emulator will no-longer compile. The calc.bin REALBUILD image compiles, but the Qt Emulator does not. After applying the "svn patch cmode.patch" command from the primary checkout directory then changing to the trunk/QtGui directory and typing make, I get the following errors:
Code:
ED -o Linux_qt/obj/stopwatch.o stopwatch.c
In file included from stopwatch.c:22:0:
keys.h:64:13: error: ‘finish_cpx_entry’ declared ‘static’ but never defined [-Werror=unused-function]
keys.h:66:12: error: ‘process_cmplx’ declared ‘static’ but never defined [-Werror=unused-function]
keys.h:67:13: error: ‘stack_restore’ declared ‘static’ but never defined [-Werror=unused-function]
cc1: all warnings being treated as errors
make[2]: *** [Linux_qt/obj/stopwatch.o] Error 1
make[2]: Leaving directory `/home/barry/wp34s-3782-Comp/trunk'
make[1]: *** [qt_gui] Error 2
make[1]: Leaving directory `/home/barry/wp34s-3782-Comp/trunk'
make: *** [all] Error 2

I tried recompiling with make clean and make after commenting out the #define INCLUDE STOPWATCH in the features.h and it still would not compile. Do you see the same result when trying to compile the Qt emulator after applying the latest cmode.patch to the latest svn 3782 release ? The previous version of cmode.patch applied to either the 3769 or 3782 release of the source tree has no trouble compiling the Qt emulator. Something in the new cmode.patch broke the Qt emulator's ability to compile.

Thank you for pointing this out; the latest patch file (I hope) corrects it. I have to confess that I do not have the qt tools installed on my system but with the latest patch the errors I receive are related to missing tools (qmake, etc) rather than the errors about unused static functions that you report above.

I'm sorry about the delay in the separate branch; I have to confess that I wasn't sure how to go about this, but reading the svn documentation has given me the confidence to try. It should happen real soon now! (I'm aiming for tomorrow.)

Nigel (UK)
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Complex Lock mode for WP-34s - Nigel (UK) - 03-16-2015, 08:03 PM
RE: Complex Lock mode for WP-34s - Jeff O. - 03-16-2015, 08:22 PM
RE: Complex Lock mode for WP-34s - Jeff O. - 03-17-2015, 11:48 AM
RE: Complex Lock mode for WP-34s - Jeff O. - 03-17-2015, 11:50 PM
RE: Complex Lock mode for WP-34s - Bit - 03-18-2015, 02:50 AM
RE: Complex Lock mode for WP-34s - Jeff O. - 03-19-2015, 05:41 PM
RE: Complex Lock mode for WP-34s - Bit - 03-23-2015, 12:40 AM
RE: Complex Lock mode for WP-34s - Jeff O. - 03-23-2015, 12:03 PM
RE: Complex Lock mode for WP-34s - emece67 - 03-23-2015, 05:12 PM
RE: Complex Lock mode for WP-34s - emece67 - 04-22-2015, 12:17 AM
RE: Complex Lock mode for WP-34s - emece67 - 04-22-2015, 10:44 AM
RE: Complex Lock mode for WP-34s - Jeff O. - 04-24-2015, 05:44 PM
RE: Complex Lock mode for WP-34s - Jeff O. - 04-29-2015, 12:18 PM
RE: Complex Lock mode for WP-34s - Jeff O. - 04-13-2015, 01:55 PM
RE: Complex Lock mode for WP-34s - Jeff O. - 04-14-2015, 11:42 AM
RE: Complex Lock mode for WP-34s - emece67 - 04-29-2015, 02:02 PM
RE: Complex Lock mode for WP-34s - Nigel (UK) - 05-03-2015 09:43 PM
RE: Complex Lock mode for WP-34s - emece67 - 05-05-2015, 06:21 PM
RE: Complex Lock mode for WP-34s - emece67 - 05-06-2015, 07:13 AM
RE: Complex Lock mode for WP-34s - Jeff O. - 02-23-2019, 01:26 AM



User(s) browsing this thread: 2 Guest(s)