xace 0.4 Ubuntu Compile problems.

[Steve]

I think maybe we could do with a 'How to compile..' for Windows users who
use Linux on and off.

I cannot get xace to compile with

make -f makefile.org

I have the source code in a folder in the ../User/Documents/xace

when in command prompt mode navigate to code folder.

type make -f makefile.org then I get a load of errors such as expect '='

any thoughts on what I doing wrong? (I have a screenshot of the window if
that's any help!)

I know to be of any use, I must learn how to compile the code, I don't want
to wait for a MS Windows code!

thanks.
Steve

[Lawrence Woodman]

Steve,

Steve wrote:
> I think maybe we could do with a 'How to compile..' for Windows users who
> use Linux on and off.
>

I agree it needs to be easier. The README needs to be clearer and I'm
also thinking of improving the automated build tool to shed more light.

> I cannot get xace to compile with
>
> make -f makefile.org
>
>
> I have the source code in a folder in the ../User/Documents/xace
>
> when in command prompt mode navigate to code folder.
>
> type make -f makefile.org then I get a load of errors such as expect '='
>
> any thoughts on what I doing wrong? (I have a screenshot of the window if
> that's any help!)
>

If you type the following it will redirect all output of make to a file
called make.out:

make -f makefile.org &>make.out

Could you post this make.out file to the mailing list and I'll have a look.

> I know to be of any use, I must learn how to compile the code, I don't want
> to wait for a MS Windows code!
>

It's actually quite handy that you aren't so familiar, so that these
sort of problems can be sorted out for the majority of people who also
aren't too used to compiling code.

Thanks for the feedback.

bfn

Lorry

--
vLife Systems Ltd
Registered Office: The Meridian, 4 Copthall House, Station Square, Coventry, CV1 2FL
Registered in England and Wales No. 06477649
http://vlifesystems.com

[ste...@jupiter-ace.co.uk]

 

Here is the make.out file hope this makes scene to you?

 

 

 

 

cc -I/usr/X11R6/include -DWHITE_ON_BLACK -DSCALE=2 -DMITSHM   -c -o xmain.o xmain.c
xmain.c:33:22: error: X11/Xlib.h: No such file or directory
xmain.c:34:23: error: X11/Xutil.h: No such file or directory
xmain.c:35:24: error: X11/keysym.h: No such file or directory
xmain.c:36:27: error: X11/Intrinsic.h: No such file or directory
xmain.c:41:33: error: X11/extensions/XShm.h: No such file or directory
xmain.c:436: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
xmain.c:437: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
xmain.c:439: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘root’
xmain.c:440: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cmap’
xmain.c:441: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘maingc’
xmain.c:442: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘fggc’
xmain.c:443: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘borderwin’
xmain.c:444: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
xmain.c:451: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘xshminfo’
xmain.c:481: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
xmain.c:484: error: expected identifier or ‘(’ before ‘{’ token
xmain.c: In function ‘image_init’:
xmain.c:521: error: ‘ximage’ undeclared (first use in this function)
xmain.c:521: error: (Each undeclared identifier is reported only once
xmain.c:521: error: for each function it appears in.)
xmain.c:521: error: ‘display’ undeclared (first use in this function)
xmain.c:522: error: ‘ZPixmap’ undeclared (first use in this function)
xmain.c:522: error: ‘xshminfo’ undeclared (first use in this function)
xmain.c: In function ‘notify’:
xmain.c:584: error: ‘Pixmap’ undeclared (first use in this function)
xmain.c:584: error: expected ‘;’ before ‘icon’
xmain.c:585: error: ‘XWMHints’ undeclared (first use in this function)
xmain.c:585: error: expected ‘;’ before ‘xwmh’
xmain.c:586: error: ‘XSizeHints’ undeclared (first use in this function)
xmain.c:586: error: expected ‘;’ before ‘xsh’
xmain.c:587: error: ‘XClassHint’ undeclared (first use in this function)
xmain.c:587: error: expected ‘;’ before ‘xch’
xmain.c:588: error: ‘XTextProperty’ undeclared (first use in this function)
xmain.c:588: error: expected ‘;’ before ‘appname’
xmain.c:593: error: ‘icon’ undeclared (first use in this function)
xmain.c:593: error: ‘display’ undeclared (first use in this function)
xmain.c:593: error: ‘root’ undeclared (first use in this function)
xmain.c:600: error: ‘xsh’ undeclared (first use in this function)
xmain.c:600: error: ‘PSize’ undeclared (first use in this function)
xmain.c:600: error: ‘PMinSize’ undeclared (first use in this function)
xmain.c:600: error: ‘PMaxSize’ undeclared (first use in this function)
xmain.c:605: error: ‘appname’ undeclared (first use in this function)
xmain.c:609: error: ‘iconname’ undeclared (first use in this function)
xmain.c:613: error: ‘xwmh’ undeclared (first use in this function)
xmain.c:613: error: ‘NormalState’ undeclared (first use in this function)
xmain.c:616: error: ‘StateHint’ undeclared (first use in this function)
xmain.c:616: error: ‘IconPixmapHint’ undeclared (first use in this function)
xmain.c:616: error: ‘InputHint’ undeclared (first use in this function)
xmain.c:617: error: ‘xch’ undeclared (first use in this function)
xmain.c:619: error: ‘borderwin’ undeclared (first use in this function)
xmain.c: In function ‘startup’:
xmain.c:642: error: ‘display’ undeclared (first use in this function)
xmain.c:649: error: ‘scrptr’ undeclared (first use in this function)
xmain.c:650: error: ‘root’ undeclared (first use in this function)
xmain.c:658: error: ‘maingc’ undeclared (first use in this function)
xmain.c:661: error: ‘fggc’ undeclared (first use in this function)
xmain.c:664: error: ‘bggc’ undeclared (first use in this function)
xmain.c:667: error: ‘cmap’ undeclared (first use in this function)
xmain.c:681: error: ‘borderwin’ undeclared (first use in this function)
xmain.c:683: error: ‘mainwin’ undeclared (first use in this function)
xmain.c:686: error: ‘KeyPressMask’ undeclared (first use in this function)
xmain.c:686: error: ‘KeyReleaseMask’ undeclared (first use in this function)
xmain.c:687: error: ‘ExposureMask’ undeclared (first use in this function)
xmain.c:687: error: ‘EnterWindowMask’ undeclared (first use in this function)
xmain.c:687: error: ‘LeaveWindowMask’ undeclared (first use in this function)
xmain.c:688: error: ‘StructureNotifyMask’ undeclared (first use in this function)
xmain.c: In function ‘process_keypress’:
xmain.c:715: error: expected declaration specifiers before ‘XKeyEvent’
xmain.c:718: error: ‘KeySym’ undeclared (first use in this function)
xmain.c:718: error: expected ‘;’ before ‘ks’
xmain.c:729: error: ‘ks’ undeclared (first use in this function)
xmain.c:732: error: ‘XK_Escape’ undeclared (first use in this function)
xmain.c:747: error: ‘XK_F12’ undeclared (first use in this function)
xmain.c:754: error: ‘XK_Return’ undeclared (first use in this function)
xmain.c:757: error: ‘XK_Shift_R’ undeclared (first use in this function)
xmain.c:758: error: ‘XK_Shift_L’ undeclared (first use in this function)
xmain.c:759: error: ‘XK_Alt_L’ undeclared (first use in this function)
xmain.c:760: error: ‘XK_Alt_R’ undeclared (first use in this function)
xmain.c:761: error: ‘XK_Meta_L’ undeclared (first use in this function)
xmain.c:762: error: ‘XK_Meta_R’ undeclared (first use in this function)
xmain.c:764: error: ‘XK_F4’ undeclared (first use in this function)
xmain.c:768: error: ‘XK_F9’ undeclared (first use in this function)
xmain.c:772: error: ‘XK_Control_L’ undeclared (first use in this function)
xmain.c:773: error: ‘XK_Control_R’ undeclared (first use in this function)
xmain.c:777: error: ‘XK_F1’ undeclared (first use in this function)
xmain.c:781: error: ‘XK_BackSpace’ undeclared (first use in this function)
xmain.c:782: error: ‘XK_Delete’ undeclared (first use in this function)
xmain.c:786: error: ‘XK_Up’ undeclared (first use in this function)
xmain.c:790: error: ‘XK_Down’ undeclared (first use in this function)
xmain.c:794: error: ‘XK_Left’ undeclared (first use in this function)
xmain.c:798: error: ‘XK_Right’ undeclared (first use in this function)
xmain.c:803: error: ‘XK_space’ undeclared (first use in this function)
xmain.c:806: error: ‘XK_exclam’ undeclared (first use in this function)
xmain.c:810: error: ‘XK_quotedbl’ undeclared (first use in this function)
xmain.c:814: error: ‘XK_numbersign’ undeclared (first use in this function)
xmain.c:818: error: ‘XK_dollar’ undeclared (first use in this function)
xmain.c:822: error: ‘XK_percent’ undeclared (first use in this function)
xmain.c:826: error: ‘XK_ampersand’ undeclared (first use in this function)
xmain.c:830: error: ‘XK_apostrophe’ undeclared (first use in this function)
xmain.c:834: error: ‘XK_parenleft’ undeclared (first use in this function)
xmain.c:838: error: ‘XK_parenright’ undeclared (first use in this function)
xmain.c:842: error: ‘XK_asterisk’ undeclared (first use in this function)
xmain.c:846: error: ‘XK_plus’ undeclared (first use in this function)
xmain.c:850: error: ‘XK_comma’ undeclared (first use in this function)
xmain.c:854: error: ‘XK_minus’ undeclared (first use in this function)
xmain.c:858: error: ‘XK_period’ undeclared (first use in this function)
xmain.c:862: error: ‘XK_slash’ undeclared (first use in this function)
xmain.c:866: error: ‘XK_0’ undeclared (first use in this function)
xmain.c:869: error: ‘XK_1’ undeclared (first use in this function)
xmain.c:872: error: ‘XK_2’ undeclared (first use in this function)
xmain.c:875: error: ‘XK_3’ undeclared (first use in this function)
xmain.c:878: error: ‘XK_4’ undeclared (first use in this function)
xmain.c:881: error: ‘XK_5’ undeclared (first use in this function)
xmain.c:884: error: ‘XK_6’ undeclared (first use in this function)
xmain.c:887: error: ‘XK_7’ undeclared (first use in this function)
xmain.c:890: error: ‘XK_8’ undeclared (first use in this function)
xmain.c:893: error: ‘XK_9’ undeclared (first use in this function)
xmain.c:896: error: ‘XK_colon’ undeclared (first use in this function)
xmain.c:900: error: ‘XK_semicolon’ undeclared (first use in this function)
xmain.c:904: error: ‘XK_less’ undeclared (first use in this function)
xmain.c:908: error: ‘XK_equal’ undeclared (first use in this function)
xmain.c:912: error: ‘XK_greater’ undeclared (first use in this function)
xmain.c:916: error: ‘XK_question’ undeclared (first use in this function)
xmain.c:920: error: ‘XK_at’ undeclared (first use in this function)
xmain.c:924: error: ‘XK_A’ undeclared (first use in this function)
xmain.c:926: error: ‘XK_a’ undeclared (first use in this function)
xmain.c:929: error: ‘XK_B’ undeclared (first use in this function)
xmain.c:931: error: ‘XK_b’ undeclared (first use in this function)
xmain.c:934: error: ‘XK_C’ undeclared (first use in this function)
xmain.c:936: error: ‘XK_c’ undeclared (first use in this function)
xmain.c:939: error: ‘XK_D’ undeclared (first use in this function)
xmain.c:941: error: ‘XK_d’ undeclared (first use in this function)
xmain.c:944: error: ‘XK_E’ undeclared (first use in this function)
xmain.c:946: error: ‘XK_e’ undeclared (first use in this function)
xmain.c:949: error: ‘XK_F’ undeclared (first use in this function)
xmain.c:951: error: ‘XK_f’ undeclared (first use in this function)
xmain.c:954: error: ‘XK_G’ undeclared (first use in this function)
xmain.c:956: error: ‘XK_g’ undeclared (first use in this function)
xmain.c:959: error: ‘XK_H’ undeclared (first use in this function)
xmain.c:961: error: ‘XK_h’ undeclared (first use in this function)
xmain.c:964: error: ‘XK_I’ undeclared (first use in this function)
xmain.c:966: error: ‘XK_i’ undeclared (first use in this function)
xmain.c:969: error: ‘XK_J’ undeclared (first use in this function)
xmain.c:971: error: ‘XK_j’ undeclared (first use in this function)
xmain.c:974: error: ‘XK_K’ undeclared (first use in this function)
xmain.c:976: error: ‘XK_k’ undeclared (first use in this function)
xmain.c:979: error: ‘XK_L’ undeclared (first use in this function)
xmain.c:981: error: ‘XK_l’ undeclared (first use in this function)
xmain.c:984: error: ‘XK_M’ undeclared (first use in this function)
xmain.c:986: error: ‘XK_m’ undeclared (first use in this function)
xmain.c:989: error: ‘XK_N’ undeclared (first use in this function)
xmain.c:991: error: ‘XK_n’ undeclared (first use in this function)
xmain.c:994: error: ‘XK_O’ undeclared (first use in this function)
xmain.c:996: error: ‘XK_o’ undeclared (first use in this function)
xmain.c:999: error: ‘XK_P’ undeclared (first use in this function)
xmain.c:1001: error: ‘XK_p’ undeclared (first use in this function)
xmain.c:1004: error: ‘XK_Q’ undeclared (first use in this function)
xmain.c:1006: error: ‘XK_q’ undeclared (first use in this function)
xmain.c:1009: error: ‘XK_R’ undeclared (first use in this function)
xmain.c:1011: error: ‘XK_r’ undeclared (first use in this function)
xmain.c:1014: error: ‘XK_S’ undeclared (first use in this function)
xmain.c:1016: error: ‘XK_s’ undeclared (first use in this function)
xmain.c:1019: error: ‘XK_T’ undeclared (first use in this function)
xmain.c:1021: error: ‘XK_t’ undeclared (first use in this function)
xmain.c:1024: error: ‘XK_U’ undeclared (first use in this function)
xmain.c:1026: error: ‘XK_u’ undeclared (first use in this function)
xmain.c:1029: error: ‘XK_V’ undeclared (first use in this function)
xmain.c:1031: error: ‘XK_v’ undeclared (first use in this function)
xmain.c:1034: error: ‘XK_W’ undeclared (first use in this function)
xmain.c:1036: error: ‘XK_w’ undeclared (first use in this function)
xmain.c:1039: error: ‘XK_X’ undeclared (first use in this function)
xmain.c:1041: error: ‘XK_x’ undeclared (first use in this function)
xmain.c:1044: error: ‘XK_Y’ undeclared (first use in this function)
xmain.c:1046: error: ‘XK_y’ undeclared (first use in this function)
xmain.c:1049: error: ‘XK_Z’ undeclared (first use in this function)
xmain.c:1051: error: ‘XK_z’ undeclared (first use in this function)
xmain.c:1054: error: ‘XK_bracketleft’ undeclared (first use in this function)
xmain.c:1058: error: ‘XK_backslash’ undeclared (first use in this function)
xmain.c:1062: error: ‘XK_bracketright’ undeclared (first use in this function)
xmain.c:1066: error: ‘XK_asciicircum’ undeclared (first use in this function)
xmain.c:1070: error: ‘XK_underscore’ undeclared (first use in this function)
xmain.c:1074: error: ‘XK_grave’ undeclared (first use in this function)
xmain.c:1078: error: ‘XK_braceleft’ undeclared (first use in this function)
xmain.c:1082: error: ‘XK_bar’ undeclared (first use in this function)
xmain.c:1086: error: ‘XK_braceright’ undeclared (first use in this function)
xmain.c:1090: error: ‘XK_asciitilde’ undeclared (first use in this function)
xmain.c: In function ‘process_keyrelease’:
xmain.c:1102: error: expected declaration specifiers before ‘XKeyEvent’
xmain.c:1105: error: ‘KeySym’ undeclared (first use in this function)
xmain.c:1105: error: expected ‘;’ before ‘ks’
xmain.c:1107: error: ‘ks’ undeclared (first use in this function)
xmain.c:1110: error: ‘XK_Return’ undeclared (first use in this function)
xmain.c:1113: error: ‘XK_Shift_L’ undeclared (first use in this function)
xmain.c:1114: error: ‘XK_Shift_R’ undeclared (first use in this function)
xmain.c:1115: error: ‘XK_Alt_L’ undeclared (first use in this function)
xmain.c:1116: error: ‘XK_Alt_R’ undeclared (first use in this function)
xmain.c:1117: error: ‘XK_Meta_L’ undeclared (first use in this function)
xmain.c:1118: error: ‘XK_Meta_R’ undeclared (first use in this function)
xmain.c:1119: error: ‘XK_Escape’ undeclared (first use in this function)
xmain.c:1120: error: ‘XK_Tab’ undeclared (first use in this function)
xmain.c:1123: error: ‘XK_F4’ undeclared (first use in this function)
xmain.c:1127: error: ‘XK_F9’ undeclared (first use in this function)
xmain.c:1131: error: ‘XK_Control_L’ undeclared (first use in this function)
xmain.c:1132: error: ‘XK_Control_R’ undeclared (first use in this function)
xmain.c:1136: error: ‘XK_F1’ undeclared (first use in this function)
xmain.c:1140: error: ‘XK_BackSpace’ undeclared (first use in this function)
xmain.c:1141: error: ‘XK_Delete’ undeclared (first use in this function)
xmain.c:1145: error: ‘XK_Up’ undeclared (first use in this function)
xmain.c:1149: error: ‘XK_Down’ undeclared (first use in this function)
xmain.c:1153: error: ‘XK_Left’ undeclared (first use in this function)
xmain.c:1157: error: ‘XK_Right’ undeclared (first use in this function)
xmain.c:1162: error: ‘XK_space’ undeclared (first use in this function)
xmain.c:1165: error: ‘XK_exclam’ undeclared (first use in this function)
xmain.c:1169: error: ‘XK_quotedbl’ undeclared (first use in this function)
xmain.c:1173: error: ‘XK_numbersign’ undeclared (first use in this function)
xmain.c:1177: error: ‘XK_dollar’ undeclared (first use in this function)
xmain.c:1181: error: ‘XK_percent’ undeclared (first use in this function)
xmain.c:1185: error: ‘XK_ampersand’ undeclared (first use in this function)
xmain.c:1189: error: ‘XK_apostrophe’ undeclared (first use in this function)
xmain.c:1193: error: ‘XK_parenleft’ undeclared (first use in this function)
xmain.c:1197: error: ‘XK_parenright’ undeclared (first use in this function)
xmain.c:1201: error: ‘XK_asterisk’ undeclared (first use in this function)
xmain.c:1205: error: ‘XK_plus’ undeclared (first use in this function)
xmain.c:1209: error: ‘XK_comma’ undeclared (first use in this function)
xmain.c:1213: error: ‘XK_minus’ undeclared (first use in this function)
xmain.c:1217: error: ‘XK_period’ undeclared (first use in this function)
xmain.c:1221: error: ‘XK_slash’ undeclared (first use in this function)
xmain.c:1225: error: ‘XK_0’ undeclared (first use in this function)
xmain.c:1228: error: ‘XK_1’ undeclared (first use in this function)
xmain.c:1231: error: ‘XK_2’ undeclared (first use in this function)
xmain.c:1234: error: ‘XK_3’ undeclared (first use in this function)
xmain.c:1237: error: ‘XK_4’ undeclared (first use in this function)
xmain.c:1240: error: ‘XK_5’ undeclared (first use in this function)
xmain.c:1243: error: ‘XK_6’ undeclared (first use in this function)
xmain.c:1246: error: ‘XK_7’ undeclared (first use in this function)
xmain.c:1249: error: ‘XK_8’ undeclared (first use in this function)
xmain.c:1252: error: ‘XK_9’ undeclared (first use in this function)
xmain.c:1255: error: ‘XK_colon’ undeclared (first use in this function)
xmain.c:1259: error: ‘XK_semicolon’ undeclared (first use in this function)
xmain.c:1263: error: ‘XK_less’ undeclared (first use in this function)
xmain.c:1267: error: ‘XK_equal’ undeclared (first use in this function)
xmain.c:1271: error: ‘XK_greater’ undeclared (first use in this function)
xmain.c:1275: error: ‘XK_question’ undeclared (first use in this function)
xmain.c:1279: error: ‘XK_at’ undeclared (first use in this function)
xmain.c:1283: error: ‘XK_A’ undeclared (first use in this function)
xmain.c:1285: error: ‘XK_a’ undeclared (first use in this function)
xmain.c:1288: error: ‘XK_B’ undeclared (first use in this function)
xmain.c:1290: error: ‘XK_b’ undeclared (first use in this function)
xmain.c:1293: error: ‘XK_C’ undeclared (first use in this function)
xmain.c:1295: error: ‘XK_c’ undeclared (first use in this function)
xmain.c:1298: error: ‘XK_D’ undeclared (first use in this function)
xmain.c:1300: error: ‘XK_d’ undeclared (first use in this function)
xmain.c:1303: error: ‘XK_E’ undeclared (first use in this function)
xmain.c:1305: error: ‘XK_e’ undeclared (first use in this function)
xmain.c:1308: error: ‘XK_F’ undeclared (first use in this function)
xmain.c:1310: error: ‘XK_f’ undeclared (first use in this function)
xmain.c:1313: error: ‘XK_G’ undeclared (first use in this function)
xmain.c:1315: error: ‘XK_g’ undeclared (first use in this function)
xmain.c:1318: error: ‘XK_H’ undeclared (first use in this function)
xmain.c:1320: error: ‘XK_h’ undeclared (first use in this function)
xmain.c:1323: error: ‘XK_I’ undeclared (first use in this function)
xmain.c:1325: error: ‘XK_i’ undeclared (first use in this function)
xmain.c:1328: error: ‘XK_J’ undeclared (first use in this function)
xmain.c:1330: error: ‘XK_j’ undeclared (first use in this function)
xmain.c:1333: error: ‘XK_K’ undeclared (first use in this function)
xmain.c:1335: error: ‘XK_k’ undeclared (first use in this function)
xmain.c:1338: error: ‘XK_L’ undeclared (first use in this function)
xmain.c:1340: error: ‘XK_l’ undeclared (first use in this function)
xmain.c:1343: error: ‘XK_M’ undeclared (first use in this function)
xmain.c:1345: error: ‘XK_m’ undeclared (first use in this function)
xmain.c:1348: error: ‘XK_N’ undeclared (first use in this function)
xmain.c:1350: error: ‘XK_n’ undeclared (first use in this function)
xmain.c:1353: error: ‘XK_O’ undeclared (first use in this function)
xmain.c:1355: error: ‘XK_o’ undeclared (first use in this function)
xmain.c:1358: error: ‘XK_P’ undeclared (first use in this function)
xmain.c:1360: error: ‘XK_p’ undeclared (first use in this function)
xmain.c:1363: error: ‘XK_Q’ undeclared (first use in this function)
xmain.c:1365: error: ‘XK_q’ undeclared (first use in this function)
xmain.c:1368: error: ‘XK_R’ undeclared (first use in this function)
xmain.c:1370: error: ‘XK_r’ undeclared (first use in this function)
xmain.c:1373: error: ‘XK_S’ undeclared (first use in this function)
xmain.c:1375: error: ‘XK_s’ undeclared (first use in this function)
xmain.c:1378: error: ‘XK_T’ undeclared (first use in this function)
xmain.c:1380: error: ‘XK_t’ undeclared (first use in this function)
xmain.c:1383: error: ‘XK_U’ undeclared (first use in this function)
xmain.c:1385: error: ‘XK_u’ undeclared (first use in this function)
xmain.c:1388: error: ‘XK_V’ undeclared (first use in this function)
xmain.c:1390: error: ‘XK_v’ undeclared (first use in this function)
xmain.c:1393: error: ‘XK_W’ undeclared (first use in this function)
xmain.c:1395: error: ‘XK_w’ undeclared (first use in this function)
xmain.c:1398: error: ‘XK_X’ undeclared (first use in this function)
xmain.c:1400: error: ‘XK_x’ undeclared (first use in this function)
xmain.c:1403: error: ‘XK_Y’ undeclared (first use in this function)
xmain.c:1405: error: ‘XK_y’ undeclared (first use in this function)
xmain.c:1408: error: ‘XK_Z’ undeclared (first use in this function)
xmain.c:1410: error: ‘XK_z’ undeclared (first use in this function)
xmain.c:1413: error: ‘XK_bracketleft’ undeclared (first use in this function)
xmain.c:1417: error: ‘XK_backslash’ undeclared (first use in this function)
xmain.c:1421: error: ‘XK_bracketright’ undeclared (first use in this function)
xmain.c:1425: error: ‘XK_asciicircum’ undeclared (first use in this function)
xmain.c:1429: error: ‘XK_underscore’ undeclared (first use in this function)
xmain.c:1433: error: ‘XK_grave’ undeclared (first use in this function)
xmain.c:1437: error: ‘XK_braceleft’ undeclared (first use in this function)
xmain.c:1441: error: ‘XK_bar’ undeclared (first use in this function)
xmain.c:1445: error: ‘XK_braceright’ undeclared (first use in this function)
xmain.c:1449: error: ‘XK_asciitilde’ undeclared (first use in this function)
xmain.c: In function ‘check_events’:
xmain.c:1464: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘xev’
xmain.c:1464: error: ‘xev’ undeclared (first use in this function)
xmain.c:1465: error: ‘XConfigureEvent’ undeclared (first use in this function)
xmain.c:1465: error: ‘conf_ev’ undeclared (first use in this function)
xmain.c:1466: error: ‘XCrossingEvent’ undeclared (first use in this function)
xmain.c:1466: error: ‘cev’ undeclared (first use in this function)
xmain.c:1468: error: ‘display’ undeclared (first use in this function)
xmain.c:1468: error: ‘QueuedAfterReading’ undeclared (first use in this function)
xmain.c:1471: error: ‘Expose’ undeclared (first use in this function)
xmain.c:1473: error: ‘ConfigureNotify’ undeclared (first use in this function)
xmain.c:1474: error: expected expression before ‘)’ token
xmain.c:1475: error: ‘mainwin’ undeclared (first use in this function)
xmain.c:1478: error: ‘MapNotify’ undeclared (first use in this function)
xmain.c:1478: error: ‘UnmapNotify’ undeclared (first use in this function)
xmain.c:1478: error: ‘ReparentNotify’ undeclared (first use in this function)
xmain.c:1480: error: ‘EnterNotify’ undeclared (first use in this function)
xmain.c:1481: error: expected expression before ‘)’ token
xmain.c:1482: error: ‘NotifyInferior’ undeclared (first use in this function)
xmain.c:1485: error: ‘LeaveNotify’ undeclared (first use in this function)
xmain.c:1486: error: expected expression before ‘)’ token
xmain.c:1490: error: ‘KeyPress’ undeclared (first use in this function)
xmain.c:1490: error: ‘XKeyEvent’ undeclared (first use in this function)
xmain.c:1490: error: expected expression before ‘)’ token
xmain.c:1492: error: ‘KeyRelease’ undeclared (first use in this function)
xmain.c:1492: error: expected expression before ‘)’ token
xmain.c: In function ‘refresh’:
xmain.c:1535: error: ‘display’ undeclared (first use in this function)
xmain.c:1535: error: ‘borderwin’ undeclared (first use in this function)
xmain.c:1633: error: ‘mainwin’ undeclared (first use in this function)
xmain.c:1633: error: ‘maingc’ undeclared (first use in this function)
xmain.c:1633: error: ‘ximage’ undeclared (first use in this function)
xmain.c: In function ‘closedown’:
xmain.c:1651: error: ‘display’ undeclared (first use in this function)
xmain.c:1651: error: ‘xshminfo’ undeclared (first use in this function)
xmain.c:1652: error: ‘ximage’ undeclared (first use in this function)
make: *** [xmain.o] Error 1

[Lawrence Woodman]

Steve,

ste...@jupiter-ace.co.uk wrote:
>
>
>
> Here is the make.out file hope this makes scene to you?
>
>
>
>
>
> cc -I/usr/X11R6/include -DWHITE_ON_BLACK -DSCALE=2 -DMITSHM -c -o
> xmain.o xmain.c
> xmain.c:33:22: error: X11/Xlib.h: No such file or directory
> xmain.c:34:23: error: X11/Xutil.h: No such file or directory
> xmain.c:35:24: error: X11/keysym.h: No such file or directory
> xmain.c:36:27: error: X11/Intrinsic.h: No such file or directory
> xmain.c:41:33: error: X11/extensions/XShm.h: No such file or directory
>

Thanks for posting that. DuLac is right, you need to add certain
libraries. I have made the requirements section of the README clearer
and pushed an update to the repo. If you download the latest source, I
am hoping that this should be clearer. I have not gone into too much
detail in this post as I want to see if the new requirements section
explains enough (hope you don't mind).

Compilation can at times be a little awkward and in the longer term I
would like a a deb package created for each release to ease things. Who
knows, maybe we could get a Jupiter Ace emulator into the Debian and
Ubuntu repositories.

[ste...@jupiter-ace.co.uk]

after installing 'libx11' and 'libxext'- i think I install the correct files there are so many libx11 files.

 

I was not sure if the code had compiled as I still got a few warnings.

 

I did see an xace execute file so I guess the code did compile.

 

On quickly running the new xace exe file I got the xace window up and a VLIST.

That's are fare as I have had time for this morning.

 

Its a bit different that compiling code on a Windows machine, but with the help of DuLac and Lawrence I got a positive result.

 

New Linux uses (I include myself, as I use some apps and do not compile code yet) might find it confusing with the large number of libx11 files which one do you install or do you need all.

 

A bit more detail is needed to confirm which lib files are needed.

 

I will post a screen shot on the Ace Forums.

 

thanks,

everyone.

[DuLac]

The following are the Ubuntu library Synaptic finds:

On May 28, 11:57 am, "ste...@jupiter-ace.co.uk" <ste...@jupiter-

ace.co.uk> wrote:
> after installing 'libx11' and 'libxext'- i think I install the correct files
> there are so many libx11 files.
>  
> I was not sure if the code had compiled as I still got a few warnings.

LIBX11-DEV
(apparently optional is LIBX11-6-DEV)
I have also installed LIBXEXT6 (do not know if really needed)
(I also have the DBG libraries for the above (I shouldn't but did
download them at the time)

The library containing xmkmf is X11-UTILS
This one should be avoided to be sure xACE can be compiled in a close
future

[DuLac]

> Compilation can at times be a little awkward and in the longer term I
> would like a a deb package created for each release to ease things.  

I would suggest to do it AFTER the TAP files are loading nicely.

REPORT:
- MAKE compiles well
- External TAP files error:

»Reading from file 'test.tap'
(internal TAP)

»Couldn't open file 'vida_32x24.tap'
(External TAP)

»Couldn't open file 'stack.tap'
(External TAP)

I would suggest that when writing a TAP a XOR with each new byte be
processed in parallel to be placed in the TAP.
I'm not sure but that may be the checksum used in a TAP (as is on the
TAPE format).
Anyway, the actual algorithm is buried in 81's code. It's worth
checking it (81's code)

> Who knows, maybe we could get a Jupiter Ace emulator into the Debian
> and Ubuntu repositories.

Certainly a thing to do when due time. xACE deserves it.
Most people will only load what is referenced by it's synaptic tool.
And frankly, that is quite understandable.

[Lawrence Woodman]

Steve,

ste...@jupiter-ace.co.uk wrote:
>
> after installing 'libx11' and 'libxext'- i think I install the correct
> files there are so many libx11 files.
>

Unfortunately finding just the right library has traditionally been
quite a pain with lots of compile processes.

>
>
>
> I was not sure if the code had compiled as I still got a few warnings.
>

I have just looked at the image you posted on your site, the warnings
are nothing to worry about for the moment. I have however fixed one of
them and pushed an update. The others will have to be fixed at a later
stage. For now I have created an issue to make sure it doesn't get
forgotten: http://github.com/LawrenceWoodman/xAce/issues#issue/4

>
>
>
> I did see an xace execute file so I guess the code did compile.
>
>
>
> On quickly running the new xace exe file I got the xace window up and
> a VLIST.
>
> That's are fare as I have had time for this morning.
>
>
>
> Its a bit different that compiling code on a Windows machine, but with
> the help of DuLac and Lawrence I got a positive result.
>

Great to hear that you got it working. I noticed from the screen shot
that you had some trouble running xace from the command line. To run a
program in the current directory that isn't in the PATH, you prefix it
with ./ so to run xace you type ./xace I have updated the README to
reflect this.

>
>
>
> New Linux uses (I include myself, as I use some apps and do not
> compile code yet) might find it confusing with the large number of
> libx11 files which one do you install or do you need all.
>

I agree it is a bit confusing. Once you are used to compiling code, it
isn't that hard, but until then it is a bit of a pain. That is why I am
keen to investigate creating some packages such as 'deb' files to make
things simple. For the moment, if you install the two or three
mentioned in the README it should bring in any other necessary ones.
Now that this is done, until there are changes to the libraries that
xAce uses, it should be fairly plain sailing.

>
>
>
> A bit more detail is needed to confirm which lib files are needed.
>

At this point I'm not sure what extra detail can be added to the README;
have you seen that latest update to this? One of the big problems with
Linux is that unfortunately there are small differences between
distributions which makes clarifying things such as this quite
difficult. Again another reason why I am so keen to get some packages
built. There are other automated build tools which can simplify things
and when I get a chance I want to look into these as well.

>
>
> I will post a screen shot on the Ace Forums.
>

The screen shot was really useful and it was nice to see it up on your
system.

[Lawrence Woodman]

DuLac,

DuLac wrote:
>> Compilation can at times be a little awkward and in the longer term I
>> would like a a deb package created for each release to ease things.
>>
>
> I would suggest to do it AFTER the TAP files are loading nicely.
>

I agree sorting out the TAP files are more important for the moment.

> REPORT:
> - MAKE compiles well
> - External TAP files error:
>
> �Reading from file 'test.tap'
> (internal TAP)
>
> �Couldn't open file 'vida_32x24.tap'
> (External TAP)
>
> �Couldn't open file 'stack.tap'
> (External TAP)
>
>

Were the .tap files above produced by xAce or by another emulator?

> I would suggest that when writing a TAP a XOR with each new byte be
> processed in parallel to be placed in the TAP.
> I'm not sure but that may be the checksum used in a TAP (as is on the
> TAPE format).
>

I think that is right, however I will check with Marcos if it isn't
obvious when I look at a hex dump of a correct file. I know that he has
already worked out this one.

>> Who knows, maybe we could get a Jupiter Ace emulator into the Debian
>> and Ubuntu repositories.
>>
>
> Certainly a thing to do when due time. xACE deserves it.
> Most people will only load what is referenced by it's synaptic tool.
> And frankly, that is quite understandable.
>

The other good thing about packages is that people can then easily track
updates.

[DuLac]

Internal = made by xACE
External = from another emulator

Hope it's only a checksum absence.

Cheers.

On May 29, 7:41 am, Lawrence Woodman <lwood...@vlifesystems.com>
wrote:

[Lawrence Woodman]

DuLac,

Sorry, my question wasn't very clear. What I meant to ask was whether
the files that couldn't be opened were failing when being read on xAce
or were failing when being read by a different emulator. I guess the
latter, but thought I should check.

[DuLac]

Just in case...

On May 29, 3:39 pm, Lawrence Woodman <lwood...@vlifesystems.com>
wrote:

> What I meant to ask was whether the files that couldn't be opened were failing
> when being read on xAce or were failing when being read by a different emulator.

xACE files are read by xACE.
Other TAP files from other software (like those in the Resource) are
not loaded by xACE.

81's TAP files are NOT read...
I suppose this leave 2 chances in the open:
- If a checksum is being used then we see a checksum incompatibility
when reading TAPs
- If the checksum is ignored, then there is a structural
incompatibility reading/writing TAPs

I guess this covers all immediate chances.
Cheers

[Steve]

would it be a case of comparing the code between xace and 81 emulator to see
if a checksum is used?

I have also made a note to make sure all .TAP files are renamed to .tap in
the archive.
I hope to get this done in the next few days.

Steve

[DuLac]

On May 29, 6:49 pm, "Steve" <ste...@jupiter-ace.co.uk> wrote:
> would it be a case of comparing the code between xace and 81 emulator to see
> if a checksum is used?

Yes, absolutely.
Considering to be a "standard", the related '81' code expresses HOW it
should be implemented. Also serves as example and finally most of the
code can be cut-and-paste. The language is the same but the code
interface most likely is different and needs to be adapted to xACE
calls. Trivial but you must be a C coder.

> I have also made a note to make sure all .TAP files are renamed to .tap in the archive.
> I hope to get this done in the next few days.

No need.
1 - Not loading is not a question of extension, I've tried both.
2 - It could be considered as a standard that *.TAP is an upcase
extension.
3 - Every TAP file past and future will always be in upcase.
4 - It is the program that should load an upcase .TAP file so not to
broke the standard.
5 - In C, as any other language, there is an upcase function. So
there's no problem.

Cheers.

[Lawrence Woodman]

Hello,

I renamed the thread for clarity.

Hopefully it is only some of the .tap files from the archive that are
not able to load. There is a structural difference in the format which
I would like to see resolved. 81's .TAP format supports multiple files
inside the .TAP file. Therefore you have to connect the .TAP file to
the emulator. Whereas xAce uses a slightly different model that
accesses .TAP files individually on the basis that each one only
contains a single file. It would be good to be able to connect a .TAP
file to the emulator and therefore allow multiple files to be accessed
through it. That said, there should be no problem for the software in
the archive that only has one file per .TAP, such as those listed on the
Compatibility page of the wiki:
http://wiki.github.com/LawrenceWoodman/xAce/compatibility

As far as the checksum of the .TAP file is concerned, xAce just ignores
this field at the moment.

[Lawrence Woodman]

Steve,

Steve wrote:
> I have also made a note to make sure all .TAP files are renamed to .tap in
> the archive.
> I hope to get this done in the next few days.
>

It would probably be worth holding off for the moment until we decide
the best course of action as far as which to go for.

[Lawrence Woodman]

DuLac,

DuLac wrote:
>> I have also made a note to make sure all .TAP files are renamed to .tap in the archive.
>> I hope to get this done in the next few days.
>>
>
> No need.
> 1 - Not loading is not a question of extension, I've tried both.
> 2 - It could be considered as a standard that *.TAP is an upcase
> extension.
> 3 - Every TAP file past and future will always be in upcase.
> 4 - It is the program that should load an upcase .TAP file so not to
> broke the standard.
> 5 - In C, as any other language, there is an upcase function. So
> there's no problem.
>

Actually the problem is a little more subtle than that. Under Windows
something.TAP and something.tap are ways of referring to the same file
as Windows' filenames are case-insensitive. Whereas on Unix they are
two separate files as Unix is case-sensitive.

This therefore creates the problem that if we use upcase to load a .TAP
file and then save as a .tap file, there will now be two files, so which
should be loaded next time?

I have also noticed that not every file in the archive uses .TAP, plenty
use .tap, just to complicate the issue.

I personally favour using solely .tap for loading and saving, as under
Windows this will make no difference and under Unix lower case filenames
and extensions in particular are the standard. The worst case is that
.TAP files will need renaming to .tap

If we decide to move over to a model where we are attaching .TAP/.tap
files to the emulator then all of this will become a non-issue.
Therefore I think that as long as xAce is loading .tap files which
contain just one file, then we should leave this for the moment, get the
release out so that people don't have to patch the current version and
then we can start increasing the pace and sort this problem out properly.

[DuLac]

On May 30, 7:28 am, Lawrence Woodman <lwood...@vlifesystems.com>
wrote:

> I personally favour using solely .tap for loading and saving, as under
> Windows this will make no difference and under Unix lower case filenames
> and extensions in particular are the standard.  The worst case is that
> .TAP files will need renaming to .tap

Hum... Had no idea that there was some TAPs in lower case.
Having no idea how the loading is implemented, may I suggest the
upper, or lower case, conversion of the extension when reading the
files? That would solve that minor problem and ease xACE usage.

> Therefore I think that as long as xAce is loading .tap files which

> contain just one file, <...>

"IS" loading .TAPs with one file?!?
All files I tried to load contain just one file. I've checked with
ACE32.
Anyway I tried my own vida_32x24 and the 5 TAPs from the first Cantab
demo tape. None was loaded.

Is it possible that WHEN building a single file TAP, AND '81' has
several taps loaded, some unexpected difference appears in the new one
file TAP, like the preparation of a new block.
I found bizarre that, not checking the checksum, I was still unable to
load any of the files I tried. One file TAPs.

I'll try a different TAP, one where '81' most likely didn't face the
chance of having a second file available.
Any suggestion of a TAP to try?

'later.

[Lawrence Woodman]

DuLac,

DuLac wrote:
> On May 30, 7:28 am, Lawrence Woodman <lwood...@vlifesystems.com>
> wrote:
>
>
>> I personally favour using solely .tap for loading and saving, as under
>> Windows this will make no difference and under Unix lower case filenames
>> and extensions in particular are the standard. The worst case is that
>> .TAP files will need renaming to .tap
>>
>
> Hum... Had no idea that there was some TAPs in lower case.
> Having no idea how the loading is implemented, may I suggest the
> upper, or lower case, conversion of the extension when reading the
> files? That would solve that minor problem and ease xACE usage.
>
>

It depends on what you mean. If you mean a) That files are converted,
i.e. renamed automatically. I did consider this but think that would
rub people up the wrong way renaming their files without much warning.
or b) That xAce looks for either .tap or .TAP when loading, that would
be ok, unless they want to modify it and re-save as the problem then
would be which case to save the file as. This could lead to on-going
confusion, at least with renaming the pain is only once.

>> Therefore I think that as long as xAce is loading .tap files which
>> contain just one file, <...>
>>
>
> "IS" loading .TAPs with one file?!?
> All files I tried to load contain just one file. I've checked with
> ACE32.
> Anyway I tried my own vida_32x24 and the 5 TAPs from the first Cantab
> demo tape. None was loaded.
>
> Is it possible that WHEN building a single file TAP, AND '81' has
> several taps loaded, some unexpected difference appears in the new one
> file TAP, like the preparation of a new block.
> I found bizarre that, not checking the checksum, I was still unable to
> load any of the files I tried. One file TAPs.
>
> I'll try a different TAP, one where '81' most likely didn't face the
> chance of having a second file available.
> Any suggestion of a TAP to try?
>

Thanks for being so thorough with this. All the files on the wiki
compatibility page should work, you may want to give them a try:
http://wiki.github.com/LawrenceWoodman/xAce/compatibility

An '81' tap file consists of essentially multiple xAce .tap files
concatenated together with checksums between. Therefore when only one
file is in a .tap file, the 81 and xAce .tap files are identical, apart
from xAce not calculating the checksum, which for reading from xAce
doesn't matter as it ignores them.