From: jstacey AT plato DOT wadham DOT ox DOT ac DOT uk (J-P) Newsgroups: comp.os.msdos.djgpp Subject: Re: Linking in .a files from within RHIDE Date: 7 Apr 2000 11:29:42 +0100 Organization: Wadham College Oxford Lines: 22 Message-ID: <8ckdam$343$1@plato.wadham.ox.ac.uk> References: <8ciba7$ttq$1 AT plato DOT wadham DOT ox DOT ac DOT uk> <38ECD3B0 DOT FE8403F8 AT hotmail DOT com> NNTP-Posting-Host: plato.wadham.ox.ac.uk X-Trace: news.ox.ac.uk 955103383 28519 163.1.164.74 (7 Apr 2000 10:29:43 GMT) X-Complaints-To: newsmaster AT ox DOT ac DOT uk NNTP-Posting-Date: 7 Apr 2000 10:29:43 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com In article <38ECD3B0 DOT FE8403F8 AT hotmail DOT com>, Andrew Hakman wrote: >When linking a .a file using RHIDE, if the file has lib???.a, go to >OPTIONS->Libraries, type the name but chop the "lib" and ".a" parts off, then >click the checkbox beside it's name. It should now link in properly. >Example: to include libemu.a type emu and check the box to the left of >it. Thanks. Works like a charm. Out of interest, is there any way of stopping both gcc via RHIDE and command-line gcc from including all the POSIX stuff and thus speeding up compile time? I noticed two things - the hack mentioned in the FAQ about getting rid of some of gcc's automatically included functions, and the checkbox under OPTIONS\LIBRARIES that says "include default libraries." Can I happily run a non-POSIX program by removing libc.a linking? It's again me trying to convince my supervisor to move from Turbo C... :) His main complaint at the moment is compile time. J-P -- ghosts! // lake phonebooth // contact lens origami // ceramic teeth