Rev 404 | Rev 440 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log | RSS feed
Rev | Author | Line No. | Line |
---|---|---|---|
60 | peter | 1 | |
198 | daniel-mar | 2 | Building FilterFoundry with OpenWatcom |
3 | ====================================== |
||
60 | peter | 4 | |
437 | daniel-mar | 5 | Tested with OpenWatcom 1.9 and OpenWatcom 2.0 together with Adobe Photoshop SDK 2021. |
60 | peter | 6 | |
107 | dmarschall | 7 | |
192 | daniel-mar | 8 | Prerequisites |
9 | ------------- |
||
107 | dmarschall | 10 | |
11 | 1) Flex and Bison |
||
192 | daniel-mar | 12 | Available here: |
13 | https://sourceforge.net/projects/winflexbison/ |
||
107 | dmarschall | 14 | |
15 | 2) Adobe Photoshop SDK |
||
192 | daniel-mar | 16 | Available on some Photoshop CDs, or can be downloaded at |
17 | https://www.adobe.com/devnet/photoshop/sdk.html |
||
107 | dmarschall | 18 | |
61 | peter | 19 | 3) Watcom 1.6beta RC1 or later |
192 | daniel-mar | 20 | Available here: |
21 | http://www.openwatcom.org/ |
||
22 | After installing, do a reboot, or set the environment manually. |
||
60 | peter | 23 | |
24 | |||
193 | daniel-mar | 25 | Build setup |
26 | ----------- |
||
107 | dmarschall | 27 | |
193 | daniel-mar | 28 | There is no special build setup required. |
437 | daniel-mar | 29 | Just open **wpj\filterfoundry.wpj** in Watcom's IDE and click "Make target". |
60 | peter | 30 | |
437 | daniel-mar | 31 | Alternatively, run **wpj\make_watcom.bat** which should do the same. |
32 | |||
192 | daniel-mar | 33 | IMPORTANT: Your path must not contain whitespaces! |
34 | For example, you must not use "C:\Users\John Doe\SVN\Filter Foundry\". |
||
107 | dmarschall | 35 | |
60 | peter | 36 | |
192 | daniel-mar | 37 | Troubleshooting |
38 | --------------- |
||
107 | dmarschall | 39 | |
192 | daniel-mar | 40 | - Please make sure that you must not have whitespaces in the pathname. |
107 | dmarschall | 41 | |
204 | daniel-mar | 42 | - Missing **sdkddkver.h**: |
43 | * In OpenWatcom 1.9: |
||
44 | If you get the error message "Fatal Error! 62: Unable to open 'sdkddkver.h'", please open |
||
45 | pluginsdk\photoshopapi\photoshop\PITypes.h in your Adobe Photoshop SDK and |
||
46 | comment out the line "#include <sdkddkver.h> // for WINVER". |
||
384 | daniel-mar | 47 | Alternatively, you can create an empty sdkddkver.h file in your wpj folder. |
204 | daniel-mar | 48 | * In Open Watcom 2.0: |
49 | The error message has the error code E062. |
||
50 | Creating an empty sdkddkver.h does not work anymore. |
||
51 | You need to comment out the line in PITypes.h. |
||
437 | daniel-mar | 52 | (Bug will be fixed: https://github.com/open-watcom/open-watcom-v2/issues/770 ) |
107 | dmarschall | 53 | |
54 | - It is important that the correct calling convention is used. |
||
55 | The calling convention needs to be set in |
||
56 | Options -> C Compiler Switches -> Memory Model and Processor Switches. |
||
57 | There, select "Pentium Pro stack-based calling" (default is "Pentium Pro register based calling"). |
||
58 | The wpj project should already have this setting applied. |
||
59 | |||
60 | - If you receive the error message "lex.yy.c(580): Error! E1009: Expecting ';' but found '1'", |
||
61 | check if the compiler directive "YY_SKIP_YYWRAP" is set. |
||
192 | daniel-mar | 62 | Go to Options -> C Compiler Switches -> Source switches, and add YY_SKIP_YYWRAP=1 . |
107 | dmarschall | 63 | The wpj project should already have this setting applied. |
64 | |||
192 | daniel-mar | 65 | - The path to the Photoshop SDK and to Win Flex/Bison (PreBuild event) |
66 | is already set in the project file. Please note that changing these |
||
437 | daniel-mar | 67 | paths is a bit complicated. There are several bugs in older versions of OpenWatcom |
192 | daniel-mar | 68 | where you can only make the pre-build-events shorter, but not longer). |
69 | You have to edit the WPJ file with a text editor. |
||
70 | Remember how many characters you have added or deleted, |
||
437 | daniel-mar | 71 | and subtract or add them to the number written above the before-instructions. |
72 | This is the number of bytes of the commands. |
||
107 | dmarschall | 73 | |
198 | daniel-mar | 74 | - In the code, it is important that all variables are declared at the |
75 | top of the scope (curly brackets) and that there is no executable code or |
||
76 | assignments in between. |
||
192 | daniel-mar | 77 | |
437 | daniel-mar | 78 | Wrong: |
198 | daniel-mar | 79 | |
437 | daniel-mar | 80 | int a; |
81 | int b = GetXYZ(); |
||
82 | int c; |
||
83 | |||
84 | Correct: |
||
85 | |||
86 | int a; |
||
87 | int b; |
||
88 | int c; |
||
89 | b = GetXYZ(); |
||
90 | |||
91 | |||
404 | daniel-mar | 92 | Attention! Some optimizations break the code |
93 | -------------------------------------------- |
||
94 | |||
95 | Don't choose "Fastest possible code (-otexan)" for optimization! |
||
96 | |||
97 | As soon as "Disable stack depth checking" is enabled, the code crashes |
||
98 | on some combinations of machines and Photoshop versions. |
||
99 | |||
100 | Win98 VM + Photoshop 3.0.x: Clicking any button (Make, Load, Cancel) will cause SegFault. |
||
101 | Win10 PC + Photoshop 3.0.x: No problem. |
||
102 | |||
103 | "otexan" contains "s" (because "ox" is equal to "obmiler" and "s"). |
||
104 | |||
105 | So, "-otexan" means: |
||
106 | |||
107 | - Branch prediction (-ob) |
||
108 | - Loop optimizations (-ol) |
||
109 | - In-line intrinsic functions (-oi) |
||
110 | - Instruction scheduling (-or) |
||
111 | - Math optimizations (-om) |
||
112 | - Expand function in-line (-oe) |
||
113 | - Disable stack depth checking (-s) |
||
114 | |||
115 | The program works if "-ot" is enabled and all other optimizations (except "s") are enabled. |
||
116 | |||
117 | However, for now we just use the optimizations which "-otaxan" contains, except "s", |
||
118 | so we enabled: |
||
119 | |||
120 | - Time optimizations (-ot) |
||
121 | - Branch prediction (-ob) |
||
122 | - Loop optimizations (-ol) |
||
123 | - In-line intrinsic functions (-oi) |
||
124 | - Instruction scheduling (-or) |
||
125 | - Math optimizations (-om) |
||
126 | - Expand function in-line (-oe) |
||
127 | |||
128 | I haven't been able to detect why/where the stack is overloaded. |
||
129 | If anyone has an idea, please contact me. |
||
130 | Maybe the initial stack size is just too small? |
||
131 | Because the code should be OK - Application Verifier has not detected anything wrong. |
||
132 | |||
133 | https://open-watcom.github.io/open-watcom-v2-wikidocs/c_readme.html |
||
134 | http://www.azillionmonkeys.com/qed/watfaq.shtml (Q19) |
||
135 | |||
136 | |||
60 | peter | 137 | Remarks |
192 | daniel-mar | 138 | ------- |
60 | peter | 139 | |
192 | daniel-mar | 140 | flex and bison are currently invoked as a batch process. |
60 | peter | 141 | This is defined in the menu File->Before. |
192 | daniel-mar | 142 | The IDE fails to build the project when filenames contain more than one dot. |
61 | peter | 143 | Therefore the output files of bison and lex are renamed. |
60 | peter | 144 | There is no error checking done. |
145 | Probably it would be better to write a small wmake file for this purpose. |