[poppler] Compiling under Windows 7

[Stefano Emilio Campanini]

On 18 March 2011 11:44, Maarten Bosmans <mkbosmans at gmail.com> wrote:
> 2011/3/18 Stefano Emilio Campanini <stefano.campanini at tinvention.net>:
>> On 17 March 2011 13:40, Maarten Bosmans <mkbosmans at gmail.com> wrote:
>>> Stefano Emilio Campanini <stefano.campanini <at> tinvention.net> writes:
>>>> To make it easy, I've made those dependencies available as pre-compiled
>>>> files. You need to download http://windevlibs.googlecode.com/files/ext.zip
>>>> and unzip under 'ext' directory. Those are header files and static libraries
>>>> for freetype, libjpeg and zlib. "
>>>>
>>>> I cannot understand where to put the ext.zip contents ? Where I put
>>>> these contents ando/or how can I tell the compiler to use these
>>>> contents ?
>>>
>>> Not wanting to sound rude, but you don't seem to understand the basics of
>>> building software using the GNU autotools. In that case the above comment about
>>> prefering the ready-build packages seems relevant.
>>
>> You are right, I have not experience using these tools, my background
>> is Java/PHP ... no C, C++  and GNU tools.
>>
>>> In any case, my experience is that building using mingw on windows is a pain and
>>> that cross-compiling (using the same mingw32+autotools+gcc toolchain) on Linux
>>> is much easier, everything just works.
>>
>> Unfortunately I need to have poppler ( or something similar ) working
>> on M$ windows machine.
>> Do you mean that I can compile on Linux a package that runs on windows
>> ? It sound strange for me...
>
> That's exactly what I meant. Cross-compiling open source software on
> Linux is easy, because the whole toolchain is just there. Compare that
> with the difficulty to get mingw/msys running on Windows. I usually
> set the configure prefix to a samba mount of my windows pc, so that
> after a make install the binaries are ready on the windows pc to be
> tested.
>

Well, I will try this way.
Thank you very much Maarten !!

Bye
Stefano