5 If you need to modify the InstallShield project files, follow these steps:
7 0) Go to the src dir version of the install files.
9 1) Run the batch file CreateISDirs.bat
10 This will create the directories that IS needs. We can't store these
11 dirs in CML because the directory names contain spaces.
13 2) Run the batch file ScatterFiles.bat
14 This will copy the IS files that are in the main install dir to the
17 3) Run the batch file CreateGeneratedFiles.bat
18 This will run other batch files that will generate certain IS files that
19 we can't use directly. This is because the IS IDE puts paths in those
20 files that are relative to the machine the IDE is running on. If some
21 other person doing a build used a different drive mapping to get at the
22 build tree, the IS build would fail. These batch files will generate the
23 IS files such that the paths will be relative to the person doing the
26 4) Run InstallShield and load the InstallShield5.ipr project file.
27 It is called InstallShield5.ipr, and not something more appropriate like
28 TransarcAFS.ipr, because IS requires that the project name match the
29 name of the directory in which the project lives.
31 5) Do whatever it is you need to do to the IS5 project.
33 6) CML edit the files in the main install dir.
35 7) If you changed the file groups, you must go into the File Groups dir and
36 modify the GenFileGroups.bat file. If you changed an existing file group,
37 then you must make the change again in the batch file. If you have deleted
38 a file group, then you must delete it from the batch file. If you added a
39 group, then add it to the batch file.
41 7) Run the batch file GatherFiles.bat.
42 This will get all the IS5 files out of their IS5 dirs and copy them into
45 8) If you have added or deleted file groups, edit the batch file DelISDirTree.bat.
46 It removes the file group files, so modify its list to match what currently
49 9) Run the batch file DelISDirTree.bat.
50 This will delete all of the IS dirs. Some of the dirs, like the media build
51 report dirs, are always removed. Most other dirs are removed only if they
52 are empty. Any dirs not removed after running the batch file contain files
53 that we previously didn't know about, so IS had some reason to create them
54 for the first time. You will have to determine if the file should be added
55 to cml. If it should be added, then check to see if it contains path names.
56 If it does, then you must create a batch file to generate this new file.
57 Look at GenFileGroups.bat for an example of how to do that. In either case
58 you have a new file to add to the build tree, either the new file IS made or
59 your batch file that generates the IS file. Copy this file to the main
60 install dir (rename it if it clashes with a file already there), and modify
61 ScatterFiles.bat, GatherFiles.bat, and DelISDirTree.bat to include the new
64 Also, if you had to create a batch file to generate the IS file, then modify
65 CreateGeneratedFiles.bat to include a call to your batch file.
67 10) Do a cml close. If you want to diff the IS5 files, do so only on the setup.rul
68 file. IS5 reoriganizes most other files more or less randomly each time
69 they are saved. It's easist to just edit all the files and then check in all
70 of them. However, if you know IS well and you know which files your changes
71 have affected, then only check in those files.
75 HOW TO BUILD THE SETUP PROJECT
77 0) Go to the obj dir version of the install files.
79 1) To build the distribution type:
80 nmake /f NTMakfile install
82 If the build fails, you may not have the environment variable IS5ROOT
83 defined. Define it and try again.
85 If it still fails, then you're on your own. Use your excellent debugging
86 skills to fix the problem.