Date: Tue, 10 Sep 1996 14:09:19 +0200 (IST) From: Eli Zaretskii To: DJ Delorie Cc: djgpp-workers AT delorie DOT com Subject: Re: V2 alpha 980908 -- readme.1st In-Reply-To: <199609090348.XAA28882@delorie.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII README.1ST mentions csdpmi3p.zip: there are no such thing. CWSPARAM.EXE is in csdpmi3b.zip. Here are some more changes: *** readme.~1~ Mon Sep 9 21:33:54 1996 --- readme.1st Mon Sep 9 21:47:48 1996 *************** *** 1,6 **** ! This is the README.1ST file for DJGPP Version 2.00 ! DJGPP v2.0 is a free environment for developing 32-bit protected mode software in C/C++ under MS-DOS. Status and other information (online docs, FAQ, mail archives) are --- 1,6 ---- ! This is the README.1ST file for DJGPP Version 2.01 ! DJGPP is a free environment for developing 32-bit protected mode software in C/C++ under MS-DOS. Status and other information (online docs, FAQ, mail archives) are *************** *** 108,118 **** To build C programs, you'll need djdev201.zip, gcc2721b.zip, and bnu27b.zip. For C++, also get gpp2721b.zip and lgp271b.zip. To read the online manuals, get txi370b.zip and run "info". If you don't have ! a DPMI server installed, you'll need csdpmi1b.zip. (Windows, QDPMI, 386Max, NWDOS, OS/2, Win/NT and Linux DOSEmu all provide DPMI services, so you don't need CWSDPMI in those environments.) For more ! details, download either faq201b.zip (the hypertext version) or FAQ ! (the text version) and read Chapter 4 of the FAQ. Installation --- 108,118 ---- To build C programs, you'll need djdev201.zip, gcc2721b.zip, and bnu27b.zip. For C++, also get gpp2721b.zip and lgp271b.zip. To read the online manuals, get txi370b.zip and run "info". If you don't have ! a DPMI server installed, you'll need csdpmi3b.zip. (Windows, QDPMI, 386Max, NWDOS, OS/2, Win/NT and Linux DOSEmu all provide DPMI services, so you don't need CWSDPMI in those environments.) For more ! details, download faq201b.zip (the full FAQ list) and read Chapter 4 ! there. Installation *************** *** 150,156 **** on you system, like this: DPMI memory available: 8020 Kb ! DPMI swap space available: 240 Kb (The actual numbers will vary according to amount of RAM installed on your system, the available disk space and the DPMI server.) If --- 150,156 ---- on you system, like this: DPMI memory available: 8020 Kb ! DPMI swap space available: 39413 Kb (The actual numbers will vary according to amount of RAM installed on your system, the available disk space and the DPMI server.) If *************** *** 169,176 **** gcc myfile.c -o myfile.exe -lm The -lm links in the lib/libm.a library (trig math) if needed. (Link ! order is significant, so always put `-lm' at the end of the command ! line.) To compile a C or C++ source file into an object file, use this command line: --- 169,176 ---- gcc myfile.c -o myfile.exe -lm The -lm links in the lib/libm.a library (trig math) if needed. (Link ! order is significant, so if you need libm.a, always put `-lm' at the ! end of the command line.) To compile a C or C++ source file into an object file, use this command line: *************** *** 187,206 **** To link several C object files into an executable program, use a command line such as this: ! gcc -o myprog.exe mymain.o mysub1.o mysub2.o -lm This produces `myprog.exe' which can be run from the DOS prompt. To link a C++ program, use gxx instead of gcc, like this: ! gxx -o myprog.exe mymain.o mysub1.o mysub2.o -lm This will automatically search the C++ libraries, so you won't need to mention them on the command line. You can also combine the compilation and link steps, like this: ! gcc -Wall -o myprog.exe mymain.c mysub1.c mysub2.c -lm Further info about the plethora of GCC switches can be found in the GCC on-line documentation. To begin reading it, install the Texinfo --- 187,206 ---- To link several C object files into an executable program, use a command line such as this: ! gcc -o myprog.exe mymain.o mysub1.o mysub2.o This produces `myprog.exe' which can be run from the DOS prompt. To link a C++ program, use gxx instead of gcc, like this: ! gxx -o myprog.exe mymain.o mysub1.o mysub2.o This will automatically search the C++ libraries, so you won't need to mention them on the command line. You can also combine the compilation and link steps, like this: ! gcc -Wall -o myprog.exe mymain.c mysub1.c mysub2.c Further info about the plethora of GCC switches can be found in the GCC on-line documentation. To begin reading it, install the Texinfo *************** *** 214,230 **** Development environment (aka IDE) --------------------------------- ! DJGPP doesn't come with an integrated development environment of its ! own. (That might change, if you decide to sit down and write such a ! program, then donate it to DJGPP.) You are free to choose any editor, ! that can launch DOS programs and catch their output, to act as an ! IDE. Many people who work with DJGPP use a DOS port of GNU Emacs ! (it's available on SimTel mirrors) which can be compiled with DJGPP. ! Emacs is a very powerful editor (for example, it has a built-in Info ! reader, so you can read DJGPP documentation without leaving the ! editor), but many other free editors can serve as an IDE. The only ! task that these editors (including Emacs) cannot do is to run a ! debugger in a full-screen session. --- 214,232 ---- Development environment (aka IDE) --------------------------------- ! Currently, DJGPP doesn't come with an integrated environment of its ! own. You are free to choose any editor that can launch DOS programs ! and catch their output, to act as an IDE. Many people who work with ! DJGPP use a DOS port of GNU Emacs (it's available from the same place ! you got DJGPP) which can be compiled with DJGPP. Emacs is a very ! powerful editor (for example, it has a built-in Info reader, so you ! can read DJGPP documentation without leaving the editor), but many ! other free editors can serve as an IDE. The only task that these ! editors (including Emacs) cannot do is to run a debugger in a ! full-screen session. ! ! A DJGPP-specific IDE called RHIDE is in beta testing and should be ! available in the near future. *************** *** 241,247 **** and then link with `-g', but give the linker the name of the output file with no .exe extension: ! gcc -g -o myprog mymain.o mysub1.o mysub2.o -lm (note the `-o myprog' as opposed to `-o myprog.exe'). This will produce the COFF output named `myprog' as well as the DOS executable --- 243,249 ---- and then link with `-g', but give the linker the name of the output file with no .exe extension: ! gcc -g -o myprog mymain.o mysub1.o mysub2.o (note the `-o myprog' as opposed to `-o myprog.exe'). This will produce the COFF output named `myprog' as well as the DOS executable