Hello,
There is something strange in the CMake report about OpenSSL...
I've compiled myself OpenSSL release 1.0.2o as a shared library and let
the install process in the makefile do his job.
So I've defined the CMake variables for LIBCRYPTO (aka libeay32) and
SSL_EAY (aka ssleay32) the same
Hello Matthew and zyx,
Sorry for the delay, I was called on another project until now.
If I've used $(EXTERN_DEV), it's because it's the way VS projects use
macros.
I've tried many solutions like :
set( EXTERN_DEV "$ENV{EXTERN_DEV}")
and use ${EXTERN_DEV} in the definitions of paths.
Hello,
My name is Patrice and I'm new with Podofo.
I was able to build Podofo 0.9.5 on Linux Debian 7 without problem but
it's a little bit more complicated on Windows with Visual Studio 2013.
I've build the dependent libraries (jpeg9c, png1634, tiff 4.0.9,
freetype 2.9, zlib 1.2.11) without
Hello Patrice, hello all,
> On 13 July 2018 at 10:48 Patrice Guérin wrote:
>
> Hello,
>
> My name is Patrice and I'm new with Podofo.
> I was able to build Podofo 0.9.5 on Linux Debian 7 without problem but it's
> a little bit more complicated on Windows with Visual Studio 2013.
>
Hello Dmitry,
It's the way I do, except that all the dependent library paths are
expressed relative to the environment variable not with absolute paths.
In the case of moving libraries elsewhere, I've just to change the env
variable and re-generate the VS solution.
In the case of absolute
Hello, Patrice.
Your configuration seems a bit complicated to me. Why not to specify all
of the required paths using CMake GUI and generate a VS project?
Regards,
Dmitry
--
Check out the vibrant tech community on one of
Hello,
My name is Patrice and I'm new with Podofo.
I was able to build Podofo 0.9.5 on Linux Debian 7 without problem but
it's a little bit more complicated on Windows with Visual Studio 2013.
I've build the dependent libraries (jpeg9c, png1634, tiff 4.0.9,
freetype 2.9, zlib 1.2.11) without
