[Podofo-users] compiling podofo manually?

[Yuliana Zigangirova]

Hi everyone!
I am trying to compile podofo static lib manually on my C++ Builder XE6
compiler (Borland).
I have edited podofo_config.h manually, setting a minimum of reasonable
options and have
just added all (except outdated) files from src/base and src/doc to
get a static library. Overall, it compiles nicely
and I can use the library functionality (what I needed so far), but the
problem is some strange
debug information in the stdout, like:

<</ID[<30F72A3B2DF1C95D1F98A45F860B6A44><30F72A3B2DF1C95D1F98A45F860B6A44>]/Info
2 0 R/Root 1 0 R/Size 4>>
<</ID[<44C8F037B421F0B019424E9F7DD8AC44><44C8F037B421F0B019424E9F7DD8AC44>]/Info
2 0 R/Root 3 0 R/Size 122
Fixing references in 4 0 R by 3
Fixing references in 5 0 R by 3
Fixing references in 6 0 R by 3
Fixing references in 7 0 R by 3
Fixing references in 8 0 R by 3
Fixing references in 9 0 R by 3
Fixing references in 10 0 R by 3
Fixing references in 11 0 R by 3
Fixing references in 12 0 R by 3
Fixing references in 13 0 R by 3
Fixing references in 14 0 R by 3
Fixing references in 15 0 R by 3

I have tried to unset precompiler defines in "podofo_config.h" like
"DEBUG" and "PODOFO_VERBOSE_DEBUG" but
this output is still here. So, where should I set precompiler defines
(like DEBUG|, PODOFO_EXTRA_CHECKS etc.)
|when compiling manually? How is correct error verbosity set? What
would be correct options for production build? I have used Borland
options for
release build.

Thank you very much in advance,
Yuliana

[zyx]

Post by Yuliana Zigangirova
I have tried to unset precompiler defines in "podofo_config.h" like
"DEBUG" and "PODOFO_VERBOSE_DEBUG" but
this output is still here. So, where should I set precompiler
defines (like DEBUG, PODOFO_EXTRA_CHECKS etc.)
when compiling manually? How is correct error verbosity set? What
would be correct options for production build? I have used Borland
options for
release build.

Hi,
try, somewhere in main(), to call:
PdfError::EnableLogging(false);
PdfError::EnableDebug(false);
It'll mute those messages, if I recall correctly.
Bye,
zyx

[Yuliana Zigangirova]

Thank you, this has muted the messages indeed.
But I would very much like to be sure, that extra checks
anddebugging were not enabled during compilation and that I got
the most possible efficient and quick library build.
Do you may be know which configuration file is commonly
read in all respectful sources?
Thank you very much,
Yuliana

Post by zyx

Post by Yuliana Zigangirova
I have tried to unset precompiler defines in "podofo_config.h" like
"DEBUG" and "PODOFO_VERBOSE_DEBUG" but
this output is still here. So, where should I set precompiler
defines (like DEBUG, PODOFO_EXTRA_CHECKS etc.)
when compiling manually? How is correct error verbosity set? What
would be correct options for production build? I have used Borland
options for
release build.

Hi,
PdfError::EnableLogging(false);
PdfError::EnableDebug(false);
It'll mute those messages, if I recall correctly.
Bye,
zyx

[zyx]

Post by Yuliana Zigangirova
Thank you, this has muted the messages indeed.
But I would very much like to be sure, that extra checks
anddebugging were not enabled during compilation and that I got the
most possible efficient and quick library build.
Do you may be know which configuration file is commonly
read in all respectful sources?

Hi,
it's the podofo_config.h you filled manually. It is included in
PdfCompilerCompat.h. Looking into this file gives you some hints on
DEBUG and _DEBUG differences, which this file defines for PoDoFo in a
way it is used in sources.

In any case, I would not edit the PdfCompilerCompat.h file, your main
place for customization is the podofo_config.h and compiler flags,
where you can also declare the desired defines. Search the code for
the DEBUG macro, then you'll see how often it's used. And to get the
most efficient code, just turn on the compiler optimizations.
Bye,
zyx