Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!ceres.physics.uiowa.edu!news.iastate.edu!ux1.cso.uiuc.edu!csrd.uiuc.edu!sp66.csrd.uiuc.edu!petersen From: petersen@sp66.csrd.uiuc.edu (Paul Petersen) Newsgroups: comp.sys.amiga.programmer Subject: Re: HELP! Installing PDC _or_ NorthC!!! Message-ID: <1991Mar14.172638.17727@csrd.uiuc.edu> Date: 14 Mar 91 17:26:38 GMT References: <1991Mar13.210258.40179@eagle.wesleyan.edu> Sender: news@csrd.uiuc.edu (news) Organization: UIUC Center for Supercomputing Research and Development Lines: 144 As far as I know the most recent version of PDC that has been released is 3.33 on ux1.cso.uiuc.edu:amiga/misc/PDC. It should be relatively trivial to compile the programs. PDC comes in three archives. You should get all three and de-zoo (x//) them each on separate floppies or in separate directories on the hard-disk. PDC currently requires AmigaDOS 1.3 If you have de-zooed the pdc-program.zoo file into the directory dh0:PDC-3.33, then 1> cd dh0:PDC-3.33 2> execute s/start 3> path add PDC:bin 4> cd sample 5> ccx hello.c 6> hello Please read the documentation about Using_PDC and the Release_Notes. These instructions are really only approximate as I do not have my amiga in front of me at this moment. If they do not work, please try to report why, and maybe I can figure out what went wrong. PDC has LOTS of bugs/differences from K&R and ANSI C. However it works most of the time, is free and includes ALL source code. If you want to make it better, be my guest. ... Use the source Luke ... --------------------------- FILE: s/start ------------------------------------ ; This script is meant to be run from the top of your PDC directory hierarchy. ; It will set the necessary environment variables and will assign the logical ; device "pdc:" to a common point for referencing PDC-related files. ; assign pdc: "" setenv PDCLibs "PDC.Lib; Amiga.lib; Math.lib" setenv PDCLibDirs "PDC:lib" setenv PDCIncDirs "PDC:include" ------------------------------------------------------------------------------ Due to changes since the release Lionel and I do not have as much time available to do snail-mail distributions of PDC. There is no guarantee that any requests received will be processed in a timely manner, so it might be better NOT to ask for PDC by mail. However, it is still available by anonymous FTP. --------------------------- FILE: Using_PDC ---------------------------------- README - Some remarks and words of advice on using PDC ------------------------------------------------------ The major pieces of this distribution are the compiler (PDC), the assembler (A68k), the linker (BLink), and the libraries and header files. Tying everything together is a "front-end" program (CCX), which takes care of a lot of the drudgery behind creating an executable program. Things to do before invoking CCX -------------------------------- CCX requires that the following environment variables be set: PDCLibs - Lists the libraries with which to link PDCLibDirs - Lists the directories to search for libraries PDCIncDirs - Lists the directories to search for include files Multiple entries for an environment variable are delimited by semicolons. See the file s/start on this disk and the documentation to CCX in the doc directory on this disk for examples of how to use the environment variables. As for your search path, at the very least you ought to have in it the directory containg CCX, PDC, A68k, and BLink. This is necessary if you plan to use CCX. Stack size for running PDC should be above the CLI's default of 4K. 20000 bytes is the lowest recommended size. 32000 bytes is sufficient for most things, up to and including recompiling PDC and its libraries. To be safe, it is best to set a good large stack size in your startup-sequence, because forgetting later on usually results in a visit from the Guru. Should PDC ever guru on you, the first step to take is bump up the stack. In summary: - Set the environment variables PDCLibs, PDCLibDirs, and PDCIncDirs. - CCX requires that PDC, A68k, and Blink be in your search path. - PDC needs a MINIMUM of 20K of stack space to run safely. Headers, Libraries, and Startup code ------------------------------------ Standard C headers can be found in the directory "include" on this disk. See below for more information on Amiga-specific headers. The PDC Software Distribution includes the three library files necessary to compile programs written for the Amiga. Here are some short descriptions of them: * Amiga.lib Amiga.lib contains the hundreds of assembly language stubs, or "stub-routines", that allow programs written in C to call the Amiga's standard set of shared libraries. It also contains a few functions to aid in the construction and destruction of some common entities (eg, CreateTask, DeletePort, NewList, etc.). The version of Amiga.lib included with PDC can be built automatically by invoking the makefile contained in the "lib/src" directory on this disk and providing your Workbench 1.3 Extras disk. * PDC.lib: PDC.lib contains a large subset of the ANSI C functions, as well as some runtime support functions and other extensions. A (currently, partial) list of the functions provided in PDC.lib and Math.lib can be found in the file MANIFEST in the LibSrc directory on the Libs and Utils disk. * Math.lib: Math.lib contains library and runtime support functions for performing floating point math. Currently, PDC supports only IEEE double precision math via the Amiga's shared libraries, ieeedoubbas.library and ieeedoubtrans.library. As you may realize, this default requires that Workbench 1.3 be available at runtime in order use the transcendental functions. The source code for the transcendental functions is provided, though, if you care to use it. Most programs written specifically for the Amiga, including much source code to this distribution, require the Amiga header files in order to compile. Those who also own one of the commercial C compilers can generally get away with using the headers that come with those compilers [1]. In any case, I recommend that you obtain the Native Developer Update (NDU) from Commodore-Amiga Technical Support (CATS). The NDU includes commented and stripped versions of the Amiga C and assembly language headers, the fabled Autodocs, a healthy batch of README files, and Commodore's standard libraries and utilities. Altogether, you get four disks for US$20; an excellent deal. -- University of Illinois, Urbana-Champaign Center for Supercomputing Research and Development UUCP: {uunet,convex}!uiucuxc!uicsrd!petersen INTERNET: petersen@uicsrd.csrd.uiuc.edu