[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: udunits and Windows
- Subject: Re: udunits and Windows
- Date: Mon, 13 Feb 2006 17:09:56 -0700
David,
>Date: Tue, 14 Feb 2006 13:03:47 +1300
>From: David Rupp <address@hidden>
>Organization: NIWA, New Zealand
>To: Steve Emmerson <address@hidden>
>Subject: Re: udunits and Windows
The above message contained the following:
> I see that udalloc.c has the statement #include "udposix.h", while
> utscan.c has #include <udposix.h>. Udalloc.h compiles fine, but
> udposix.h can't be found when I attempt to compile utscan.c. I could
> replace the <> with "" and place udposix.h in the same directory as
> utscan.c, but somehow I don't think that's what you had in mind.
The C compiler needs to be told where to find the "udposix.h" file. On
UNIX systems, this is done via the "-I" option, e.g.,
c89 -I ../port/misc utscan.c
The Windows C compiler should have a similar option.
> I wish I could save the big picture questions for you and not bother you
> with little things like this that a software developer could figure out
> on their own.
Actually, the little things are easier. :-)
Don't worry about it.
Regards,
Steve Emmerson