Rev 69 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 69 | Rev 106 | ||
|---|---|---|---|
| Line 83... | Line 83... | ||
| 83 | 83 | ||
| 84 | The finished binary, which contains executables for Classic and Carbon, |
84 | The finished binary, which contains executables for Classic and Carbon, |
| 85 | is left in the "dist" directory. |
85 | is left in the "dist" directory. |
| 86 | 86 | ||
| 87 | 87 | ||
| - | 88 | Windows notes |
|
| - | 89 | ------------- |
|
| - | 90 | ||
| - | 91 | To build with Visual Studio, you have to use nmake. |
|
| - | 92 | Currently, there is not Visual Studio project file. |
|
| - | 93 | ||
| - | 94 | To compile: |
|
| - | 95 | 1. First download Flex and Bison from https://sourceforge.net/projects/winflexbison/ |
|
| - | 96 | and unpack them on your disk. |
|
| - | 97 | 2. Download the Adobe Photoshop SDK from https://www.adobe.com/devnet/photoshop/sdk.html |
|
| - | 98 | and unpack it on your disk. |
|
| - | 99 | 3. Download the telegraphics common library from http://telegraphics.com.au/svn/common/trunk/ |
|
| - | 100 | and unpack it on your disk. |
|
| - | 101 | 4. Adjust paths in the nmake.mak file of Filter Foundry. |
|
| - | 102 | 5. Run "Visual Studio Developer Command Prompt" from the start menu |
|
| - | 103 | 6. Navigate to the Filter Foundry dir and run |
|
| - | 104 | nmake /f nmake.mak clean |
|
| - | 105 | nmake /f nmake.mak |
|
| - | 106 | ||
| - | 107 | Troubleshooting: |
|
| - | 108 | - If "rc" can't be found, install the Windows 10 SDK, and then copy |
|
| - | 109 | C:\Program Files (x86)\Windows Kits\10\bin\...\x64 to C:\Program Files (x86)\Windows Kits\10\bin\x86 |
|
| - | 110 | see also https://stackoverflow.com/questions/43847542/rc-exe-no-longer-found-in-vs-2015-command-prompt |
|
| - | 111 | - If lex.yy.c can't be found, check the flex command (it generates lex.yy.c) |
|
| - | 112 | - If nmake gives the error message "makefile(28) : fatal error U1000: Syntax error: ")" missing in macro invocation" |
|
| - | 113 | then run nmake with the parameter "/f nmake.mak" (nmake calls Makefile by default, which is not optimized for nmake) |
|
| - | 114 | - If you run into any problems, try "nmake /f nmake.mak clean" followed by "nmake /f nmake.mak" |
|
| - | 115 | ||
| - | 116 | ||
| - | 117 | To build in Windows with the OpenWatcom IDE, see the wpj |
|
| - | 118 | subdirectory and notes kindly provided by Peter Heckert. |
|
| - | 119 | Please note that there might be problems with calling conventions; |
|
| - | 120 | the plugin might not work after the building process. |
|
| - | 121 | ||
| - | 122 | ||
| 88 | Development systems |
123 | Development systems |
| 89 | ------------------- |
124 | ------------------- |
| 90 | While a CodeWarrior 7 project is provided, MPW and mingw32 are recommended |
125 | While a CodeWarrior 7 project is provided, MPW and mingw32 are recommended |
| 91 | as they produce much smaller executables. |
126 | as they produce much smaller executables. |
| 92 | 127 | ||
| 93 | Mingw32 (http://www.mingw.org/) can be hosted on virtually any UNIX or |
128 | Mingw32 (http://www.mingw.org/) can be hosted on virtually any UNIX or |
| 94 | Linux system, or under Windows. |
129 | Linux system, or under Windows. |
| 95 | 130 | ||
| 96 | MPW (http://developer.apple.com/tools/mpw-tools/) runs on PowerPC and |
131 | MPW (http://developer.apple.com/tools/mpw-tools/) runs on PowerPC and |
| 97 | 68K Macs under Mac OS 9 or earlier, or Classic under OS X. |
132 | 68K Macs under Mac OS 9 or earlier, or Classic under OS X. |
| 98 | - | ||
| 99 | To build in Windows with the OpenWatcom IDE, see the wpj subdirectory |
- | |
| 100 | and notes kindly provided by Peter Heckert. |
- | |