Subversion Repositories filter_foundry

Rev

Rev 192 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
190 dmarschall 1
 
2
BUILDING FILTER FOUNDRY ON VISUAL STUDIO
3
by Daniel Marschall
4
 
192 daniel-mar 5
Most recently tested with Visual Studio 2019 and Adobe Photoshop SDK CC 2017.
190 dmarschall 6
 
7
 
192 daniel-mar 8
Prerequisites
9
-------------
190 dmarschall 10
 
192 daniel-mar 11
1) Visual Studio (Visual C++)
190 dmarschall 12
   There is a free "Community Edition" available here:
192 daniel-mar 13
   https://visualstudio.microsoft.com/de/vs/community/
190 dmarschall 14
 
15
2) Flex and Bison
16
   Download the tools here:
192 daniel-mar 17
   https://sourceforge.net/projects/winflexbison/
18
   Extract the contents of the package in the directory "..\win_flex_bison"
190 dmarschall 19
 
20
3) Adobe Photoshop SDK
21
   Available on some Photoshop CDs, or can be downloaded at
192 daniel-mar 22
   https://www.adobe.com/devnet/photoshop/sdk.html
23
   Extract the contents of the package in the directory "..\photoshop_sdk"
190 dmarschall 24
 
193 daniel-mar 25
4) Windows SDK
190 dmarschall 26
   Download the Windows SDK here:
192 daniel-mar 27
   https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/
190 dmarschall 28
   and install the following components:
192 daniel-mar 29
   - Windows SDK for Desktop C++ x86 Apps
30
   - Windows SDK for Desktop C++ amd64 Apps
31
   For some reason, you only need to install the Windows SDK if you
32
   build using the IDE, but not if you build using command-line (*.mak files).
190 dmarschall 33
 
34
 
192 daniel-mar 35
Build setup using the IDE
36
-------------------------
190 dmarschall 37
 
192 daniel-mar 38
1. Open the visual_studio\FilterFoundry.sln with Visual Studio
190 dmarschall 39
 
192 daniel-mar 40
2. Go to the project settings and change the Windows SDK version to the one you have installed.
190 dmarschall 41
 
192 daniel-mar 42
3. You can now compile the x86 and x64 plugins inside the IDE.
190 dmarschall 43
	The output files are:
192 daniel-mar 44
	C:\FilterFoundry\Source\visual_studio\Win32\(Release|Debug)\FilterFoundry.8bf
45
	C:\FilterFoundry\Source\visual_studio\Win64\(Release|Debug)\FilterFoundry64.8bf
190 dmarschall 46
 
47
 
192 daniel-mar 48
Build setup using command line/nmake
49
------------------------------------
190 dmarschall 50
 
192 daniel-mar 51
1. Check/Edit visual_studio\vc_make_3264.bat: Change the Visual Studio path to the one you have on your system.
190 dmarschall 52
 
192 daniel-mar 53
2. You can now use the script visual_studio\vc_make_3264.bat to build both x86 and x64 with one click.
190 dmarschall 54
	The output files are:
192 daniel-mar 55
	...\visual_studio\FilterFoundry.8bf
56
	...\visual_studio\FilterFoundry64.8bf
190 dmarschall 57
 
58
 
192 daniel-mar 59
Troubleshooting
60
---------------
190 dmarschall 61
 
62
- If "rc" can't be found, install the Windows 10 SDK, and then copy
192 daniel-mar 63
  C:\Program Files (x86)\Windows Kits\10\bin\...\x64 to
64
  C:\Program Files (x86)\Windows Kits\10\bin\x86
190 dmarschall 65
  see also https://stackoverflow.com/questions/43847542/rc-exe-no-longer-found-in-vs-2015-command-prompt
66
 
192 daniel-mar 67
- If lex.yy.c can't be found, check the flex command (it generates lex.yy.c)
68
  in the project properties or the mak-file, respectively.
190 dmarschall 69
 
70
- If nmake gives the error message "makefile(28) : fatal error U1000: Syntax error: ")" missing in macro invocation"
71
  then run nmake with the parameter "/f nmake.mak" or "/f nmake64.mak"
72
  (nmake calls Makefile by default, which is written for the 'normal' "make" and not "nmake")
73
 
74
- If you run into any problems, try "nmake /f nmake.mak clean" followed by "nmake /f nmake.mak",
75
  or for 64 bit: "nmake /f nmake64.mak clean" followed by "nmake /f nmake64.mak"
192 daniel-mar 76
  It is necessary to run the "clean" command when switching between 32-bit and 64-bit builds.
190 dmarschall 77
 
78
- Since the RC files have a complex structure, you cannot edit the resources inside the IDE.
79
  You need to edit the *.rc files manually.
192 daniel-mar 80
 
81
- If the winflex/bison prebuild commands fail, Visual Studio will just show the message
82
            'The command "cd ..'
83
  because the command contains line breaks and so you will only see the first command "cd ..".
84
  Hover the mouse over the error message to display the whole message (commands),
85
  or copy it using Ctrl+C and paste it into a text editor.