|
290
|
1 Building the VC++ Windows Configuration Tool |
|
|
2 ============================================ |
|
|
3 |
|
|
4 NOTE: this tool is no longer supported. Users wanting a graphical |
|
|
5 configuration tool under Windows should instead consider the |
|
|
6 wxWindows-based tool, ../wxwin/ReadMe. |
|
|
7 |
|
|
8 The graphical configuration tool can be built using a Developer Studio |
|
|
9 project, tools/ecosconfig/standalone/win32/Configtool.dsw |
|
|
10 Even if building the host tools from Visual Studio, it is still |
|
|
11 necessary to install Cygwin and Tcl 8.x. Additionally, there is a |
|
|
12 dependency on either the Microsoft Platform SDK or the Microsoft HTML |
|
|
13 Help Workshop. The latter is available at: |
|
|
14 http://msdn.microsoft.com/library/tools/htmlhelp/wkshp/download.htm |
|
|
15 |
|
|
16 To prepare the machine for the build, it is necessary to: |
|
|
17 |
|
|
18 1) Set the TCLHOME environment variable to the root of the Tcl |
|
|
19 installation. (For example, TCLHOME=C:\tcl) This can be set from the |
|
|
20 Enviroment Variables dialog on the Advanced tab of the System |
|
|
21 Properties dialog. |
|
|
22 |
|
|
23 2) It is also necessary to add several directories to Visual Studio's |
|
|
24 default file search paths. This is set from the Directories tab in the |
|
|
25 Options menu. |
|
|
26 |
|
|
27 The following entries will need to be added (full paths are shown for |
|
|
28 clarity, the actual path may be different): |
|
|
29 |
|
|
30 a) Executable Files |
|
|
31 c:\cygwin\bin |
|
|
32 b) Include Files |
|
|
33 c:\tcl\include |
|
|
34 c:\program files\microsoft platform sdk\include _OR_ |
|
|
35 c:\program files\html help workshop\include |
|
|
36 c) Library Files |
|
|
37 c:\tcl\lib |
|
|
38 c:\program files\microsoft platform sdk\lib _OR_ |
|
|
39 c:\program files\html help workshop\lib |
|
|
40 |
|
|
41 3) The build process as setup by default in the sources available from |
|
|
42 CVS is setup to build the host tools on the DOS v:\ drive. If this |
|
|
43 drive doesn't exist, it may be preferable to do a "subst v:\ c:\temp" |
|
|
44 command from a Windows command shell. This will effectively create a |
|
|
45 virtual disk which is located at c:\temp, and the build process will |
|
|
46 place all intermediate and build files in this location. |
|
|
47 (Alternatively, it is possible to go through the project settings in |
|
|
48 Visual Studio and adjust the drive letters manually.) |
|
|
49 |
|
|
50 4) If you have installed a version of Tcl other than version 8.2, it |
|
|
51 will be necessary to change the names of libraries linked with the |
|
|
52 projects. This can be done by: |
|
|
53 |
|
|
54 a) Selecting "Settings..." on the ChangeLog file in the cdl project in |
|
|
55 the Configtool workspace, you will see the custom build step for the |
|
|
56 project. At the end of the first line of the custom build step, there |
|
|
57 is an option --with-tcl_version=82. Change this value (82) to |
|
|
58 correspond to the version of Tcl installed on the machine. |
|
|
59 |
|
|
60 b) Selecting "Settings..." on the Configtool project in the workspace, |
|
|
61 you should go to the Link tab in the right-hand pane. In this pane you |
|
|
62 will see a line listing all the Libraries with which the project is |
|
|
63 being linked. Change the tcl82.lib entry to the name appropriate for |
|
|
64 the version of Tcl installed. |
|
|
65 |
|
|
66 (NOTE: These settings must be applied to all configurations you intend |
|
|
67 to build separately. The eCos host tools as shipped by RedHat were |
|
|
68 built using the "Win32 ANSI Release" Configuration. If you build the |
|
|
69 "Win32 Release" Configuration, you will also need to have the Unicode |
|
|
70 version of the MFC libraries and DLLs.) |
|
|
71 |
|
|
72 5) Click "Build... (F7)". The compiled binaries will be located in the |
|
|
73 Configtool folder on the V:\ drive. |
|
|
74 |
|
|
75 |
|
|
76 NOTES: |
|
|
77 |
|
|
78 1) When using WinCVS, make sure to use the default Windows mode to get |
|
|
79 the tools. Using UNIX mode will break the Visual Studio project files |
|
|
80 and you won't be able to open them. (It is preferable, in general, to |
|
|
81 use Windows mode for all eCos files.) |
|
|
82 |
|
|
83 2) There will be many warnings related to STL header compilation. |
|
|
84 These are benign. There are also some warnings related to missing help |
|
|
85 files at the beginning of the Configtool project compilation. These |
|
|
86 can also be ignored. |
|
|
87 |
|
|
88 3) To build the other Win32 projects in the host tools, it may be |
|
|
89 necessary to repeat step 4.b) above. (Again, this depends on which |
|
|
90 version of Tcl is in use.) |
