# Copyright (C) 1990-1995 The Santa Cruz Operation, Inc. # # The information in this file is provided for the exclusive use of # the licensees of The Santa Cruz Operation, Inc. Such users have # the right to use, modify, and incorporate this code into other # products for purposes authorized by the SCO license agreement, # without fee. # # THE SANTA CRUZ OPERATION (SCO) DISCLAIMS ALL WARRANTIES WITH REGARD TO # THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND # FITNESS, IN NO EVENT SHALL SCO BE LIABLE FOR ANY SPECIAL, INDIRECT OR # CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF # USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR # OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR # PERFORMANCE OF THIS SOFTWARE. # # SCCSID: @(#) README 1.3 96/01/24 (SCO) This distribution provides an example of how to use SCO OpenServer development system create a CDMT distribution of a product, in this case it is the hypothetical "lep" product. This distribution contains the following files: README cut clean cdmt/LEP.files cdmt/LEPDS.export cdmt/LEPDS.files cdmt/LEPRT.CLIENT cdmt/LEPRT.export cdmt/LEPRT.files cdmt/LEPRT_ccs.sh cdmt/LEPRT_cqs.sh cdmt/SharedControl.files cdmt/cdmt.config cdmt/lep_ccs.sh cdmt/lep_cqs.sh src/Driver.c src/Makefile src/Master src/Node src/System src/lep.conf src/lep.h src/leptst.c src/liblep1.c src/liblep2.c The files in the "src" directory compile and build a small product, which is installed into a "dist" directory that "make install" creates. The files in the "cdmt" directory control the operation of the CDMT cutting tools, in particular, cdmtConvert, cdmtParse, cdmtCompress, and cdmtArchive. The building and cutting process have been automated in the "cut" script which calls all the tools in the correct order to build and cut the product. To create the installable images, which are left in the directory archives/FLOPPY/*, just run "./cut". The "clean" script removes all files created during the build and cut process, and returns the tree to a pristine state. The distribution after installation will comprise the following files: /usr/include/lep.h /usr/bin/leptst /usr/lib/liblep.a /etc/lep.conf as well, the "lep" driver files will not be exported (ie. made visible to users), but will be left in /opt/K/VDR/lep/1.0.0a/usr/lib/lep/Driver.o /opt/K/VDR/lep/1.0.0a/usr/lib/lep/Driver.c /opt/K/VDR/lep/1.0.0a/usr/lib/lep/Master /opt/K/VDR/lep/1.0.0a/usr/lib/lep/Node /opt/K/VDR/lep/1.0.0a/usr/lib/lep/System During the installation, this driver will be installed into the link kit via the "idinstall" command. You should also at least peruse the Chapter 12 of the SCO OpenServer Development System Release 5 Developer's Topics book, entitled "Custom Distribution Mastering Toolkit". It introduces many concepts which are necessary to understand why things are done in the following example. In particular, the sections on "Software management phases", and "About component scripts" should be read. I have tried to heavily comment the cqs and ccs scripts so that it is clear what is being done at each step and why. I am also including here a couple of "tricks" that you can use with custom to speed the debugging of your scripts. 1) You can use command line arguments to custom to automate the installation and removal process of the software. The format of these commands is: Installation: custom -p : -i -z Removal: custom -p : -r So for this example, in which the media images are in the archives/FLOPPY directory, the commands would be: Installation: custom -p VDR:LEP -i -z archives/FLOPPY Removal: custom -p VDR:LEP -r 2) You can also "disable" and then "enable" your product once it is installed. After the "disable", you can edit your ccs scripts in the /opt heirarchy, and have the modified versions rerun when you "enable" the product again. The format of these commands is: Disable: custom -p : -d Enable: custom -p : -e So for this example, the sequence of events would be: custom -p VDR:LEP -d vi /opt/K/VDR/LEP/1.0.0a/cntl/ccs vi /opt/K/VDR/LEP/1.0.0a/cntl/packages/LEPRT/ccs custom -p VDR:LEP -e I hope this is useful in getting you started. Comments are welcome. Larry Philps (larryp@sco.com) SCO January 24, 1995