[Podofo-users] build error
hi everyone, i have downloaded the latest podofo-0.9.6-rc1 and want to build it on a win10 machine using the visual studio 2017 command prompt. i have cmake 3.11.1 and all the nescessary libs installed/built. i created a build.cmd as described in the readme file, first in an empty subdirectory, then after the same error in the podofo root dir: del cmakecache.txt set FTDIR=C:\ecworks_mep\freetype-2.8.1 set FTLIBDIR=C:\ecworks_mep\freetype-2.8.1\objs set JPEGDIR=C:\ecworks_mep\jpeg-9b set ZLIBDIR=C:\ecworks_mep\zlib-1.2.11 cmake -G "Visual Studio 15 2017" .\src -DCMAKE_INCLUDE_PATH="%FTDIR%\include;%JPEGDIR%\include;%JPEGDIR%;%ZLIBDIR%\include" the command output shows: C:\ecworks_mep\podofo-0.9.6-rc1>build.cmd C:\ecworks_mep\podofo-0.9.6-rc1>del cmakecache.txt C:\ecworks_mep\podofo-0.9.6-rc1>set FTDIR=C:\ecworks_mep\freetype-2.8.1 C:\ecworks_mep\podofo-0.9.6-rc1>set FTLIBDIR=C:\ecworks_mep\freetype-2.8.1\objs C:\ecworks_mep\podofo-0.9.6-rc1>set JPEGDIR=C:\ecworks_mep\jpeg-9b C:\ecworks_mep\podofo-0.9.6-rc1>set ZLIBDIR=C:\ecworks_mep\zlib-1.2.11 C:\ecworks_mep\podofo-0.9.6-rc1>cmake -G "Visual Studio 15 2017" .\src -DCMAKE_INCLUDE_PATH="C:\ecworks_mep\freetype-2.8.1\include;C:\ecworks_mep\jpeg-9b\include;C:\ecworks_mep\jpeg-9b;C:\ecworks_mep\zlib-1.2.11\include" -- The C compiler identification is MSVC 19.14.26428.1 -- The CXX compiler identification is MSVC 19.14.26428.1 -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/Tools/MSVC/14.14.26428/bin/Hostx86/x86/cl.exe -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/Tools/MSVC/14.14.26428/bin/Hostx86/x86/cl.exe -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/Tools/MSVC/14.14.26428/bin/Hostx86/x86/cl.exe -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/Tools/MSVC/14.14.26428/bin/Hostx86/x86/cl.exe -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Error at CMakeLists.txt:4 (MESSAGE): Run cmake on the CMakeLists.txt in the project root, not the one in the 'src' directory. You will need to delete CMakeCache.txt from the current directory. -- Configuring incomplete, errors occurred! See also "C:/ecworks_mep/podofo-0.9.6-rc1/CMakeFiles/CMakeOutput.log". this output log does not show any errors, all the entries end with "0 warnings, 0 errors". i do run cmake in the project root, so what is wrong? thank you! -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
[Podofo-users] image extract
hi everyone, i think the imageextract tool is very outdated. i tried it with a pdf that i created from a single jpg (see attachment), resulting in a distorted version of that jpg. a png triggered an exception that i was unable to debug. my final goal is to extract all the images in a pdf and store them in a std::vector for further processing. I wanted to start from the imgextract code but it does not work. could someone update this tool so it works with different kinds of image types? or point me in the right direction otherwise? thank you! shell_logo_30645.pdf Description: Adobe PDF document -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
Re: [Podofo-users] image extract
okay, it works now, i had to rebuild everything and also include libpng although it is supposed to be optional. Am 22.05.2018 um 12:56 schrieb Joerg Sonnenberger: On Tue, May 22, 2018 at 12:48:50PM +0200, M. Froese wrote: thank you joerg, so what might be wrong with my podofo build? the resulting image is included in the attachment. Windows problem. The file is not written as binary, so \n gets messed up. Joerg -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
Re: [Podofo-users] image extract
thank you joerg, so what might be wrong with my podofo build? the resulting image is included in the attachment. in the cmake stage of building i have included jpeg-9c, but i had to adjust some things to build everything from the resulting .sln file in visual studio. unfortunately it is some days ago and i do not remember specifics. maybe the linker command line from visual studio shows a problem? /OUT:"C:\ecworks_mep\podofo-0.9.6-rc1\martinBuild\tools\podofoimgextract\Debug\podofoimgextract.exe" /MANIFEST /NXCOMPAT /PDB:"C:/ecworks_mep/podofo-0.9.6-rc1/martinBuild/tools/podofoimgextract/Debug/podofoimgextract.pdb" /DYNAMICBASE "podofo.lib" "kernel32.lib" "user32.lib" "gdi32.lib" "winspool.lib" "comdlg32.lib" "advapi32.lib" "shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "ws2_32.lib" /IMPLIB:"C:/ecworks_mep/podofo-0.9.6-rc1/martinBuild/tools/podofoimgextract/Debug/podofoimgextract.lib" /DEBUG /MACHINE:X86 /SAFESEH /INCREMENTAL /PGD:"C:\ecworks_mep\podofo-0.9.6-rc1\martinBuild\tools\podofoimgextract\Debug\podofoimgextract.pgd" /SUBSYSTEM:CONSOLE",5.01" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /ManifestFile:"podofoimgextract.dir\Debug\podofoimgextract.exe.intermediate.manifest" /ERRORREPORT:PROMPT /NOLOGO /LIBPATH:"C:/ecworks_mep/podofo-0.9.6-rc1/martinBuild/src" /LIBPATH:"C:/ecworks_mep/podofo-0.9.6-rc1/martinBuild/src/Debug" /TLBID:1 Am 22.05.2018 um 12:23 schrieb Joerg Sonnenberger: On Mon, May 21, 2018 at 03:15:44PM +0200, M. Froese wrote: i think the imageextract tool is very outdated. i tried it with a pdf that i created from a single jpg (see attachment), resulting in a distorted version of that jpg. It works perfectly fine here with the attached document. Joerg -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
