| Deutsch English Français Italiano |
|
<vemfc9$1qphf$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: news.eternal-september.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Brian Schenkenberger <mail@SendSpamHere.ORG> Newsgroups: comp.os.vms Subject: Re: Can C #includes like this be made to work onVMS? Date: Tue, 15 Oct 2024 15:21:46 -0400 Organization: Tmesis Software Lines: 41 Message-ID: <vemfc9$1qphf$1@dont-email.me> References: <vemd23$1qdt1$1@dont-email.me> <memo.20241015201538.19028q@jgd.cix.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Tue, 15 Oct 2024 21:21:46 +0200 (CEST) Injection-Info: dont-email.me; posting-host="8c0b8f6f0929c169bed5d22865ec2f83"; logging-data="1926703"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19Nf10ahJmjiVfnWWI2Uy+m" User-Agent: Unison/2.2 Cancel-Lock: sha1:LduqDoAitOS5UXIyXLpyJ8RCG+o= On 2024-10-15 19:15:00 +0000, John Dallman said: > In article <vemd23$1qdt1$1@dont-email.me>, mail@SendSpamHere.ORG (Brian > Schenkenberger) wrote: > >> I want to port a freeware package. It's C code is littered with >> includes like: >> >> #include "package_name/include_file.h" >> >> I've tried the DECC$***_INCLUDE logicals, the CC command quilifier >> /INCLUDE_DIRECTORY and logicals, rooted and otherwise, defining >> "package_name". Can't get the C compiler to find include_file.h. > > Don't try to define "package name". General C practice is to regard that > as a directory name that the compiler should look for, used to collect > specific headers together. > > Instead, try using the various ways of specifying where you want include > files to be read from to indicate the directory that holds the > "package_name" directory. > > The compiler should look for the directory called "package_nane" and the > "include_file.h" within it. > > John In the distribution, the includes are in a directory: [package_name.INCLUDE] and the source is in [package_name.SRC] I am hoping not to have to edit all of the sources to change the #include "..."s.