1INSTRUCTIONS for installing Coco/R for C versions 1.08 - 1.17 2------------------------------------------------------------- 3 4Here are the basic steps to install and build Coco/R for C/C++ : 5 61. Set up the CRFRAMES environment variable to the path where the frame 7 files can be found: 8 9 DOS: Give a command llike 10 SET CRFRAMES=C:\COCOR\FRAMES 11 12 UNIX: Give a command like 13 CRFRAMES=/usr/local/cocor/frames;export CRFRAMES 14 15 (The exact form of this will depend on the shell you are using, and on 16 the directory set up. You can also set the values of the variables on 17 the command line) 18 192. Run the proper make file: 20 21 DOS: Give the command 22 make -f borlandc.mk 23 24 This will compile the Coco/R sources and some examples. 25 26 UNIX: 27 First uudecode the "dos2unix.uue" file to create the file 28 "dos2unix.sh". In this way we can be sure that dos2unix.sh is 29 correct; it contains a critical ASCII 13 (^M or CR) character in 30 its code. Give the command 31 32 uudecode dos2unix.uue 33 34 Make this file executable. Give the command 35 chmod +x dos2unix.sh 36 37 Execute dos2unix.sh as a shell script to correct the file unix.mk. 38 Give the command 39 ./dos2unix.sh unix.mk 40 41 Convert all files to "unix" format. Give the command 42 make -f unix.mk dos2unix 43 44 Finally build the distribution. Give the command 45 make -f unix.mk 46 47 ++++ You may have to edit the makefiles to select the correct compiler 48 for your system. If "make -f unix.mk" does not work properly, study 49 the make files and edit them appropriately. You may need to invoke 50 "gmake" rather than "make". 51 52Use of the Borland C++ IDE 53========================== 54 55If you are a DOS user, you can also use the Borland C++ integrated 56development environment to build the programs. Create a .prj file, and 57remember to change the include directories to have the correct include 58directories for you. (Menu: Options, Directories) 59 60 61File extension conventions 62========================== 63 64The C++ source files in the kit have been supplied with ".cpp" and ".hpp" 65extensions. 66 67These work well with Borland C++, Linux g++, and several other C++ compilers. 68However, some UNIX C++ compilers (like GNU C on Sun's Solaris) use a ".cpp" 69extension to mean "c preprocessed files", so that the compiler will NOT 70preprocess the file. To fix this problem, you have to 71 72 (1) Rename the files to have a valid C++ extension for your compiler, for 73 example, ".C" or ".cxx". 74 75 In all the directories that have C++ sources, the "unix.mk" makefiles 76 have 2 entry points, named "fix_2_cpp" and "fix_2_cxx". These will 77 help you rename the files in the distribution. 78 79 From the main Coco/R directory, to change all the C++ file extensions 80 from ".cpp" to ".cxx", give the command: 81 82 make -f unix.mk fix_2_cxx 83 84 (2) Do not forget to set the "CRCEXT" environment variable to "cxx". 85 Rebuild the distribution if necessary. 86 87You can tell Coco/R to use a customized file extension for your own 88applications by using the CRCEXT and CRHEXT environment variables. 89 90For example, suppose you need to use ".cxx" extensions for C++ files and 91".hxx" for the header files 92 93 DOS: Give the commands 94 SET CRCEXT=cxx 95 SET CRHEXT=hxx 96 UNIX: Give the command 97 CRCEXT=cxx;CRHEXT=hxx;export CRCEXT CRHEXT 98 99In this way, Coco/R will generate files with these extensions. It would 100probably be useful to set all the Coco/R environment variables in your 101AUTOEXEC.BAT, .profile or .login file, so that each time you login these 102variables will be correctly set up. 103 104As from version 1.08 you can also set these options using a command line 105option, for example 106 107 -DCRFRAMES=/usr/lib/coco/frames 108 109=end= 110 111