[Gdal-dev] Re: Building GDAL with eVC++ 4.0
Andrey Kiselev
dron at ak4719.spb.edu
Tue May 31 01:23:16 EDT 2005
On Mon, May 30, 2005 at 11:02:55PM +0200, Mateusz Łoskot wrote:
> I don't think that main problem is with the compiler determination.
> For now, I see there are some libraries/files missed in C standard
> library used by eVC++. But it is also possible to work wih this.
>
> eVC++ IDE prvides similar BAT file as "big" Visual Studi to
> reconfigure build environment (INCLUDE/LINK path, etc.)
>
> What do you mean as "heade guards placement"?
Guards are the special preprocessor definitions used to enable/disable
compilation of the various program blocks. For example, look at the
cpl_port.h module, it contains constructions like
#ifdef HAVE_LOCALE_H
# include <locale.h>
#endif
HAVE_LOCALE_H guard is defined in the cpl_config.h file. We can define a
symbol for Embedded VC in nmake.opt and use it as a guard in the various
modules to include the right headers. The first candidates are
cpl_port.h and cpl_vsisimple.cpp. That symbol will be manually enabled
in nmake.opt when appropriate.
Regards,
Andrey
--
Andrey V. Kiselev
Home phone: +7 812 5970603 ICQ# 26871517
More information about the Gdal-dev
mailing list