www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1995/10/26/14:25:53

Xref: news-dnh.mv.net comp.os.msdos.djgpp:2873
Newsgroups: comp.os.msdos.djgpp
Path: news-dnh.mv.net!mv!news.sprintlink.net!news.texas.net!news-out.internetmci.com!newsfeed.internetmci.com!EU.net!sun4nl!phcoms4.seri.philips.nl!newssvr!kunst
From: kunst AT natlab DOT research DOT philips DOT com (Pieter Kunst)
Subject: Re: Contrib headers and libraries.
Sender: news AT natlab DOT research DOT philips DOT com (USENET News System)
Organization: Philips Research Laboratories, Eindhoven, The Netherlands
References: <46mvr4$ds4 AT ds2 DOT acs DOT ucalgary DOT ca>
Date: Thu, 26 Oct 1995 15:13:14 GMT
Lines: 20
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

In article <46mvr4$ds4 AT ds2 DOT acs DOT ucalgary DOT ca> mrtrembl AT acs DOT ucalgary DOT ca (Marc Tremblay) writes:
>
>	I was just wondering what people familiar with DJGPP find is the best 
> way to access the contrib headers and libraries.  Do you put all of the copies
> of all of the headers into a single include directory and similarly with the 
> libraries or do you find it works better to add path information to djgpp.env?

There is a third option!

(3) specify the include directory at compile time (in the Makefile),
    and the library directory at link time, e.g.:

    gcc -c -O -I\djgpp\contrib\pdcurses testcurs.c
    gcc -o testcurs testcurs.o -L\djgpp\contrib\pdcurses -lcurses

This way you won't have to clobber the standard directories,
and also you don't have to mess with djgpp.env.
But either of the 3 methods works. Choose one that suits you best.

Pieter.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019