Re: [Podofo-users] build error
On Tue, 2018-05-15 at 12:02 +0200, M. Froese wrote: > cmake -G "Visual Studio 15 2017" .\src > -DCMAKE_INCLUDE_PATH="%FTDIR%\include;%JPEGDIR%\include;%JPEGDIR%;%ZL > IBDIR%\include" > > the command output shows: > > C:\ecworks_mep\podofo-0.9.6-rc1>build.cmd Hi, I usually create a 'build' or '_build' directory in the checkout, cd into it and then run cmake as this: $ cmake -G "xxx" .. thus in your case you've the checkout at C:\ecworks_mep\podofo-0.9.6-rc1 create the directory C:\ecworks_mep\podofo-0.9.6-rc1\_build then: cd C:\ecworks_mep\podofo-0.9.6-rc1\_build cmake -G "xxx" .. which tells cmake where the main CMakeLists.txt file is. Note that there is an issue with the version on the Windows, the "-rc1" is not a number, as reported here [1], thus you might need to change the version in the main CMakeLists.txt slightly. Bye, zyx [1] https://sourceforge.net/p/podofo/mailman/message/36288545/ -- 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] build error
On Tue, May 15, 2018 at 12:02:30PM +0200, M. Froese wrote: > cmake -G "Visual Studio 15 2017" .\src > -DCMAKE_INCLUDE_PATH="%FTDIR%\include;%JPEGDIR%\include;%JPEGDIR%;%ZLIBDIR%\include" This tells cmake to configure the src directory, not the current directory. 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
[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] build error
Hi, I got this today: /home/pierre/system/src/podofo/src/PdfParser.cpp:483: error: integer constant is too large for ‘long’ type /home/pierre/system/src/podofo/src/PdfParser.cpp:484: error: integer constant is too large for ‘long’ type with: ../podofo/src/PdfDefines.h:#define PODOFO_MAX_OBJ_NUMBER 99 So, I don’t know exactly what’s the bizarre brain malfunction but I changed it into here[1] to have it compiling :) [1] OpenSuse 10.3 $ rpm -qi gcc-c++-4.2-24 Name: gcc-c++ Relocations: (not relocatable) Version : 4.2 Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany Release : 24Build Date: ven 21 sep 2007 20:23:17 CEST Install Date: sam 06 oct 2007 17:34:27 CEST Build Host: glinka.suse.de Group : Development/Languages/C and C++ Source RPM: gcc-4.2-24.src.rpm Size: 0License: GPL v2 or later Signature : DSA/SHA1, ven 21 sep 2007 20:26:44 CEST, Key ID a84edae89c800aca Packager: http://bugs.opensuse.org URL : http://gcc.gnu.org/ Summary : The system GNU C++ Compiler Description : The system GNU C++ Compiler. Distribution: openSUSE 10.3 (i586) $ uname -a Linux portable 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC i686 i686 i386 GNU/Linux $rpm -qi glibc-2.6.1-18.3 Name: glibcRelocations: (not relocatable) Version : 2.6.1 Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany Release : 18.3 Build Date: mar 23 oct 2007 14:57:03 CEST Install Date: mer 24 oct 2007 20:54:41 CEST Build Host: linux-r2dp Group : System/Libraries Source RPM: glibc-2.6.1-18.3.src.rpm Size: 4045566 License: BSD 3-Clause; GPL v2 or later; LGPL v2 or later Signature : DSA/SHA1, mar 23 oct 2007 17:36:16 CEST, Key ID a84edae89c800aca Packager: http://bugs.opensuse.org URL : http://www.gnu.org/software/libc/libc.html Summary : Standard Shared Libraries (from the GNU C Library) Description : The GNU C Library provides the most important standard libraries used by nearly all programs: the standard C library, the standard math library, and the POSIX thread library. A system is not functional without these libraries. Distribution: openSUSE 10.3 (i686) -- Pierre Marchand - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
Re: [Podofo-users] build error
Hmm, does this help? Making it explicitly a long? #define PODOFO_MAX_OBJ_NUMBER 99L AFAIK Craig is working on x86_64, too, as I am. So our 64bit longs should be definitely large enough, maybe we have to check MAX_INT or MAX_LONG on other platforms. This could solve your problem on Unix at least: #include limits.h #if 99L LONG_MAX #define PODOFO_MAX_OBJ_NUMBER 99L #else #define PODOFO_MAX_OBJ_NUMBER LONG_MAX #endif Ciao, Dom Am Dienstag, 15. April 2008 schrieb Pierre Marchand: Hi, I got this today: /home/pierre/system/src/podofo/src/PdfParser.cpp:483: error: integer constant is too large for ‘long’ type /home/pierre/system/src/podofo/src/PdfParser.cpp:484: error: integer constant is too large for ‘long’ type with: ../podofo/src/PdfDefines.h:#define PODOFO_MAX_OBJ_NUMBER 99 So, I don’t know exactly what’s the bizarre brain malfunction but I changed it into here[1] to have it compiling :) [1] OpenSuse 10.3 $ rpm -qi gcc-c++-4.2-24 Name: gcc-c++ Relocations: (not relocatable) Version : 4.2 Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany Release : 24Build Date: ven 21 sep 2007 20:23:17 CEST Install Date: sam 06 oct 2007 17:34:27 CEST Build Host: glinka.suse.de Group : Development/Languages/C and C++ Source RPM: gcc-4.2-24.src.rpm Size: 0License: GPL v2 or later Signature : DSA/SHA1, ven 21 sep 2007 20:26:44 CEST, Key ID a84edae89c800aca Packager: http://bugs.opensuse.org URL : http://gcc.gnu.org/ Summary : The system GNU C++ Compiler Description : The system GNU C++ Compiler. Distribution: openSUSE 10.3 (i586) $ uname -a Linux portable 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC i686 i686 i386 GNU/Linux $rpm -qi glibc-2.6.1-18.3 Name: glibcRelocations: (not relocatable) Version : 2.6.1 Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany Release : 18.3 Build Date: mar 23 oct 2007 14:57:03 CEST Install Date: mer 24 oct 2007 20:54:41 CEST Build Host: linux-r2dp Group : System/Libraries Source RPM: glibc-2.6.1-18.3.src.rpm Size: 4045566 License: BSD 3-Clause; GPL v2 or later; LGPL v2 or later Signature : DSA/SHA1, mar 23 oct 2007 17:36:16 CEST, Key ID a84edae89c800aca Packager: http://bugs.opensuse.org URL : http://www.gnu.org/software/libc/libc.html Summary : Standard Shared Libraries (from the GNU C Library) Description : The GNU C Library provides the most important standard libraries used by nearly all programs: the standard C library, the standard math library, and the POSIX thread library. A system is not functional without these libraries. Distribution: openSUSE 10.3 (i686) -- ** Dominik Seichter - [EMAIL PROTECTED] KRename - http://www.krename.net - Powerful batch renamer for KDE KBarcode - http://www.kbarcode.net - Barcode and label printing PoDoFo - http://podofo.sf.net - PDF generation and parsing library SchafKopf - http://schafkopf.berlios.de - Schafkopf, a card game, for KDE Alan - http://alan.sf.net - A Turing Machine in Java ** signature.asc Description: This is a digitally signed message part. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
Re: [Podofo-users] build error
Dominik Seichter wrote: Hmm, does this help? Making it explicitly a long? #define PODOFO_MAX_OBJ_NUMBER 99L AFAIK Craig is working on x86_64, too, as I am. So our 64bit longs should be definitely large enough, maybe we have to check MAX_INT or MAX_LONG on other platforms. That should never exceed max long, but does exceed max int. It should've been explicitly `long', because it's used with `long' data types. gcc 4.1 handles it silently, but newer versions appear to be stricter (good!). My bad. It should be fixed in SVN now. -- Craig Ringer - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
