[gdal-dev] building with PDF driver on Windows

[Joaquim Luis]

On 14-10-2010 18:32, Even Rouault wrote:
> Le jeudi 14 octobre 2010 17:01:06, Joaquim Luis a écrit :
>    
>> Hi,
>>
>> I tried to build GDAL on Win with PDF support and CV2010
>>
>> Well that's an adventure.
>>      
> I trust you and didn't even try this way.
>
> Instead I just downloaded the kde-win32 installer, used the "packager mode"
> (or whatever it is called. I'm just quoting from my memory of doing this a few
> weeks ago), and selected the poppler, freetype and lcms packages and their
> developement packages. The only requirement for GDAL is poppler, freetype and
> lcms appears to be poppler requirements on this KDE build. But those lib only
> work with MSVC 2008 if I remember.
>    

Even,

Hmm, on a further check those symbols are from poppler so it's not a 
lcms fault.
I get another error building poppler referring iconv.h that I ignore 
either but selected as a no dependency in CMake, but this affect the 
creation of a poppler-cpp.lib, not poppler.lib so I'm not sure it 
relates to the GDAL error.
I would like to build these dependencies myself because:

1. I don't want to use anything that dares to create manifests dependencies
2. I want to be able to build 64 bits versions too.

Anyway, I found these warnings too that are unrelated to this PDF driver 
issue

json_util.c
json_util.c(62) : warning C4013: 'open' undefined; assuming extern 
returning int
json_util.c(71) : warning C4013: 'read' undefined; assuming extern 
returning int
json_util.c(74) : warning C4013: 'close' undefined; assuming extern 
returning int
json_util.c(109) : warning C4013: 'write' undefined; assuming extern 
returning int

ogrsf_frmts.lib(resolvexlinks.obj) : warning LNK4221: This object file 
does not define any previously undefined public symbols, so it will not 
be used by any link operation that consumes this library

and many "blabla ... possible loss of data" warnings.