From:	pjfarley AT banet DOT net (Peter J. Farley III)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Q: How to use Rhide to make a library?
Date:	Fri, 17 Mar 2000 16:35:12 GMT
Message-ID:	<38d25b74.1175697@news3.banet.net>
X-Newsreader:	Forte Free Agent 1.21/32.243
NNTP-Posting-Host:	32.100.250.89
X-Trace:	17 Mar 2000 16:28:37 GMT, 32.100.250.89
Organization:	Global Network Services - Remote Access Mail & News Services
Lines:	33
X-Complaints-To:	abuse AT prserv DOT net
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi all,

I've finally decided to try Rhide, and the first project I'd like to
use it for has an associated library in addition to a normal
executable.  I've read much of the Rhide docs, and I did not yet see
any instructions on how to set up a Rhide project for a library (which
is not to say they aren't there).

I did see the answer to almost the question I'm asking, but the answer
just says to look at the Rhide sources for examples.  I've done that,
and all I see so far is that the main target is specified as the
library name instead of an executable name.

Is that really all that is required?  (In addition to the usual
directory and other settings that may be required for the library code
to be compiled, of course.)

Second question:  Is it possible to include sub-projects as part of a
larger project file?  For example, in my case, do I include the
library *project* file name as part of the executable project?  Or
just the library name itself?

I am quite willing to assemble the answers to my questions (and the
inevitable follow-up questions) into an update for the Rhide
documentation (assuming I didn't simply miss the instructions in my
previous readings).

TIA for any help or info you can provide.  RTFM pointers gratefully
accepted.

----------------------------------------------------
Peter J. Farley III (pjfarley AT nospam DOT dorsai DOT org OR
                     pjfarley AT nospam DOT banet DOT net)

- Raw text -