[digiKam-users] Extracting thumbnails

Maik Qualmann metzpinguin at gmail.com
Thu May 21 04:56:12 BST 2020


Oh, sorry. I was wrong. The facial database blobs are compressed. The 
thumbnails are pure PGF data. Gilles has to adapt the tool again.

Maik

Am Donnerstag, 21. Mai 2020, 00:17:01 CEST schrieb Wesley Smith:
> Gilles, I'll try one more time.  But, honestly the photos are quite
> private.  Is there a way you recommend for me to extract them?  I have used
> a python script I found to do it and then I also tried extracting a single
> blob using dbBrowser for SQLite.  Neither has given me a blob that can be
> read using the pgf tool.
> 
> On Wed, May 20, 2020 at 8:34 AM Wesley Smith <wss7932 at gmail.com> wrote:
> > Gilles, I'm going to drop this endevor.  Merci beaucoup for all of your
> > help.  The blobs are of a rather sensitive nature and I've just decided to
> > let it go.  Sorry for the bother.
> > 
> > On Tue, May 19, 2020 at 9:09 AM Gilles Caulier <caulier.gilles at gmail.com>
> > 
> > wrote:
> >> Please share me the Thumbnails_row_*_data.blob files, i will take a
> >> look...
> >> 
> >> Use a cloud web service, it's more simple than private email.
> >> 
> >> Gilles
> >> 
> >> Le mar. 19 mai 2020 à 15:59, Wesley Smith <wss7932 at gmail.com> a écrit :
> >> > I did and thank you very much.  I will have to re-extract the blobs.  I
> >> 
> >> got an error trying to use the exe on them.  Here is what I get 
currently:
> >> >> F:\dump>pgfdatabase.exe Thumbnails_row_1_data.blob
> >> >> qUncompress: Z_DATA_ERROR: Input data is corrupted
> >> >> PGFUtils: PGF image data to decode : size is null
> >> >> loadPGFScaled failed...
> >> >> 
> >> >> F:\dump>pgfdatabase.exe Thumbnails_row_2_data.blob
> >> >> Cannot open PGF file to read...
> >> >> 
> >> >> F:\dump>pgfdatabase.exe Thumbnails_row_3_data.blob
> >> >> qUncompress: Z_DATA_ERROR: Input data is corrupted
> >> >> PGFUtils: PGF image data to decode : size is null
> >> >> loadPGFScaled failed...
> >> > 
> >> > On Tue, May 19, 2020 at 3:58 AM Gilles Caulier <
> >> 
> >> caulier.gilles at gmail.com> wrote:
> >> >> Wesley,
> >> >> 
> >> >> Did you seen my last message ? You have now a Windows executable ready
> >> >> to use "as well" for your problem. I would to receive a feedback
> >> >> about.
> >> >> 
> >> >> Also can your share me some database thumbnail blobs to test here,
> >> >> just to be sure that all will work as expected ?
> >> >> 
> >> >> Thanks in advance
> >> >> 
> >> >> Gilles Caulier
> >> >> 
> >> >> Le dim. 17 mai 2020 à 20:53, Gilles Caulier <caulier.gilles at gmail.com>
> >> 
> >> a écrit :
> >> >> > Done.
> >> >> > 
> >> >> > The tool is now cross compiled for Windows under Linux. It's a
> >> >> > static
> >> >> > executable which do not require external dependency.
> >> >> > 
> >> >> > Program is here :
> >> >> > 
> >> >> > https://github.com/cgilles/digikam-pgf-database/tree/master/bin
> >> >> > 
> >> >> > Gilles Caulier
> >> >> > 
> >> >> > Le sam. 16 mai 2020 à 16:48, Gilles Caulier <
> >> 
> >> caulier.gilles at gmail.com> a écrit :
> >> >> > > Ok lets me one day, I will cross compile the tool under Linux for
> >> 
> >> windows
> >> 
> >> >> > > Gilles Caulier
> >> >> > > 
> >> >> > > Le sam. 16 mai 2020 à 15:05, Wesley Smith <wss7932 at gmail.com> a
> >> 
> >> écrit :
> >> >> > >> I've tried all of the shortcuts for msvc and they all give me a
> >> 
> >> similar result.  Not sure what to do.  It's frustrating being so close
> >> but,
> >> unable to obtain the goal.
> >> 
> >> >> > >> On Fri, May 15, 2020 at 11:10 AM Gilles Caulier <
> >> 
> >> caulier.gilles at gmail.com> wrote:
> >> >> > >>> This is strange.  It sound like your don't use the right MSVC
> >> 
> >> terminal
> >> 
> >> >> > >>> which set the PATH to compiler.
> >> >> > >>> 
> >> >> > >>> You don't need to play with build dir. bootstrap script will do
> >> 
> >> it for you.
> >> 
> >> >> > >>> Gilles
> >> >> > >>> 
> >> >> > >>> Le ven. 15 mai 2020 à 09:59, Wesley Smith <wss7932 at gmail.com> a
> >> 
> >> écrit :
> >> >> > >>> > I appreciate your patience and help.  Forgive me if I'm not
> >> 
> >> making this easy.
> >> 
> >> >> > >>> > Here is what I get using the bootstrap.bat
> >> 
> >> **********************************************************************
> >> 
> >> >> > >>> >> ** Visual Studio 2019 Developer Command Prompt v16.5.5
> >> >> > >>> >> ** Copyright (c) 2019 Microsoft Corporation
> >> 
> >> **********************************************************************
> >> 
> >> >> > >>> >> C:\Program Files (x86)\Microsoft Visual
> >> 
> >> Studio\2019\Community>cd \Users\wss79\git\digikam-pgf-database
> >> 
> >> >> > >>> >> C:\Users\wss79\git\digikam-pgf-database>dir
> >> >> > >>> >> 
> >> >> > >>> >>  Volume in drive C is Windows
> >> >> > >>> >>  Volume Serial Number is B439-C954
> >> >> > >>> >>  
> >> >> > >>> >>  Directory of C:\Users\wss79\git\digikam-pgf-database
> >> >> > >>> >> 
> >> >> > >>> >> 05/14/2020  04:52 PM    <DIR>          .
> >> >> > >>> >> 05/14/2020  04:52 PM    <DIR>          ..
> >> >> > >>> >> 05/14/2020  04:49 PM    <DIR>          .vs
> >> >> > >>> >> 05/14/2020  04:29 PM               264 bootstrap.bat
> >> >> > >>> >> 05/14/2020  04:52 PM    <DIR>          build
> >> >> > >>> >> 05/14/2020  07:27 AM            15,620 CMakeCache.txt
> >> >> > >>> >> 05/14/2020  07:27 AM    <DIR>          CMakeFiles
> >> >> > >>> >> 05/13/2020  09:05 AM               921 CMakeLists.txt
> >> >> > >>> >> 05/14/2020  04:13 PM               504 CMakeSettings.json
> >> >> > >>> >> 05/13/2020  09:05 AM             2,137 loadpgfblob.cpp
> >> >> > >>> >> 05/14/2020  04:12 PM    <DIR>          out
> >> >> > >>> >> 05/13/2020  09:05 AM    <DIR>          pgfutils
> >> >> > >>> >> 
> >> >> > >>> >>                5 File(s)         19,446 bytes
> >> >> > >>> >>                7 Dir(s)  235,184,947,200 bytes free
> >> >> > >>> >> 
> >> >> > >>> >> C:\Users\wss79\git\digikam-pgf-database>rmdir build
> >> >> > >>> >> The process cannot access the file because it is being used
> >> 
> >> by another process.
> >> 
> >> >> > >>> >> C:\Users\wss79\git\digikam-pgf-database>rmdir build
> >> >> > >>> >> The process cannot access the file because it is being used
> >> 
> >> by another process.
> >> 
> >> >> > >>> >> C:\Users\wss79\git\digikam-pgf-database>rmdir build
> >> >> > >>> >> The directory is not empty.
> >> >> > >>> >> 
> >> >> > >>> >> C:\Users\wss79\git\digikam-pgf-database>rmdir /s /q build
> >> >> > >>> >> 
> >> >> > >>> >> C:\Users\wss79\git\digikam-pgf-database>dir
> >> >> > >>> >> 
> >> >> > >>> >>  Volume in drive C is Windows
> >> >> > >>> >>  Volume Serial Number is B439-C954
> >> >> > >>> >>  
> >> >> > >>> >>  Directory of C:\Users\wss79\git\digikam-pgf-database
> >> >> > >>> >> 
> >> >> > >>> >> 05/14/2020  04:56 PM    <DIR>          .
> >> >> > >>> >> 05/14/2020  04:56 PM    <DIR>          ..
> >> >> > >>> >> 05/14/2020  04:49 PM    <DIR>          .vs
> >> >> > >>> >> 05/14/2020  04:29 PM               264 bootstrap.bat
> >> >> > >>> >> 05/14/2020  07:27 AM            15,620 CMakeCache.txt
> >> >> > >>> >> 05/14/2020  07:27 AM    <DIR>          CMakeFiles
> >> >> > >>> >> 05/13/2020  09:05 AM               921 CMakeLists.txt
> >> >> > >>> >> 05/14/2020  04:13 PM               504 CMakeSettings.json
> >> >> > >>> >> 05/13/2020  09:05 AM             2,137 loadpgfblob.cpp
> >> >> > >>> >> 05/14/2020  04:12 PM    <DIR>          out
> >> >> > >>> >> 05/13/2020  09:05 AM    <DIR>          pgfutils
> >> >> > >>> >> 
> >> >> > >>> >>                5 File(s)         19,446 bytes
> >> >> > >>> >>                6 Dir(s)  235,184,984,064 bytes free
> >> >> > >>> >> 
> >> >> > >>> >> C:\Users\wss79\git\digikam-pgf-database>bootstrap.bat
> >> >> > >>> >> -- The C compiler identification is unknown
> >> >> > >>> >> -- The CXX compiler identification is unknown
> >> >> > >>> >> 
> >> >> > >>> >> CMake Error at CMakeLists.txt:7 (project):
> >> >> > >>> >>   The CMAKE_C_COMPILER:
> >> >> > >>> >>     C:/Program Files (x86)/Microsoft Visual
> >> 
> >> Studio/2019/Community/VC/Tools/MSVC/14.24.28314/bin/Hostx86/x86/cl.exe
> >> 
> >> >> > >>> >>   is not a full path to an existing compiler tool.
> >> >> > >>> >>   
> >> >> > >>> >>   To use the NMake generator with Visual C++, cmake must be
> >> 
> >> run from a shell
> >> 
> >> >> > >>> >>   that can use the compiler cl from the command line.  This
> >> 
> >> environment is
> >> 
> >> >> > >>> >>   unable to invoke the cl compiler.  To fix this problem, run
> >> 
> >> cmake from the
> >> 
> >> >> > >>> >>   Visual Studio Command Prompt (vcvarsall.bat).
> >> >> > >>> >>   
> >> >> > >>> >>   Tell CMake where to find the compiler by setting either the
> >> 
> >> environment
> >> 
> >> >> > >>> >>   variable "CC" or the CMake cache entry CMAKE_C_COMPILER to
> >> 
> >> the full path to
> >> 
> >> >> > >>> >>   the compiler, or to the compiler name if it is in the PATH.
> >> >> > >>> >> 
> >> >> > >>> >> CMake Error at CMakeLists.txt:7 (project):
> >> >> > >>> >>   The CMAKE_CXX_COMPILER:
> >> >> > >>> >>     C:/Program Files (x86)/Microsoft Visual
> >> 
> >> Studio/2019/Community/VC/Tools/MSVC/14.24.28314/bin/Hostx86/x86/cl.exe
> >> 
> >> >> > >>> >>   is not a full path to an existing compiler tool.
> >> >> > >>> >>   
> >> >> > >>> >>   To use the NMake generator with Visual C++, cmake must be
> >> 
> >> run from a shell
> >> 
> >> >> > >>> >>   that can use the compiler cl from the command line.  This
> >> 
> >> environment is
> >> 
> >> >> > >>> >>   unable to invoke the cl compiler.  To fix this problem, run
> >> 
> >> cmake from the
> >> 
> >> >> > >>> >>   Visual Studio Command Prompt (vcvarsall.bat).
> >> >> > >>> >>   
> >> >> > >>> >>   Tell CMake where to find the compiler by setting either the
> >> 
> >> environment
> >> 
> >> >> > >>> >>   variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER
> >> 
> >> to the full path
> >> 
> >> >> > >>> >>   to the compiler, or to the compiler name if it is in the
> >> 
> >> PATH.
> >> 
> >> >> > >>> >> -- Configuring incomplete, errors occurred!
> >> >> > >>> >> See also
> >> 
> >> "C:/Users/wss79/git/digikam-pgf-database/CMakeFiles/CMakeOutput.log".
> >> 
> >> >> > >>> >> See also
> >> 
> >> "C:/Users/wss79/git/digikam-pgf-database/CMakeFiles/CMakeError.log".
> >> 
> >> >> > >>> >> '-DCMAKE_BUILD_TYPE' is not recognized as an internal or
> >> 
> >> external command,
> >> 
> >> >> > >>> >> operable program or batch file.
> >> >> > >>> >> '-DCMAKE_PREFIX_PATH' is not recognized as an internal or
> >> 
> >> external command,
> >> 
> >> >> > >>> >> operable program or batch file.
> >> >> > >>> >> '-Wno-dev' is not recognized as an internal or external
> >> 
> >> command,
> >> 
> >> >> > >>> >> operable program or batch file.
> >> >> > >>> >> '..' is not recognized as an internal or external command,
> >> >> > >>> >> operable program or batch file.
> >> >> > >>> >> 
> >> >> > >>> >> C:\Users\wss79\git\digikam-pgf-database>
> >> >> > >>> > 
> >> >> > >>> > And this is what I get when trying manually:
> >> >> > >>> >>  C:\Users\wss79\git\digikam-pgf-database>mkdir build
> >> >> > >>> > 
> >> >> > >>> > C:\Users\wss79\git\digikam-pgf-database>copy CMakeLists.txt
> >> 
> >> build
> >> 
> >> >> > >>> >         1 file(s) copied.
> >> >> > >>> > 
> >> >> > >>> > C:\Users\wss79\git\digikam-pgf-database>cd build
> >> >> > >>> > 
> >> >> > >>> > C:\Users\wss79\git\digikam-pgf-database\build>cmake ..
> >> >> > >>> > -- The C compiler identification is unknown
> >> >> > >>> > -- The CXX compiler identification is unknown
> >> >> > >>> > 
> >> >> > >>> > CMake Error at CMakeLists.txt:7 (project):
> >> >> > >>> >   The CMAKE_C_COMPILER:
> >> >> > >>> >     C:/Program Files (x86)/Microsoft Visual
> >> 
> >> Studio/2019/Community/VC/Tools/MSVC/14.24.28314/bin/Hostx86/x86/cl.exe
> >> 
> >> >> > >>> >   is not a full path to an existing compiler tool.
> >> >> > >>> >   
> >> >> > >>> >   To use the NMake generator with Visual C++, cmake must be
> >> 
> >> run from a shell
> >> 
> >> >> > >>> >   that can use the compiler cl from the command line.  This
> >> 
> >> environment is
> >> 
> >> >> > >>> >   unable to invoke the cl compiler.  To fix this problem, run
> >> 
> >> cmake from the
> >> 
> >> >> > >>> >   Visual Studio Command Prompt (vcvarsall.bat).
> >> >> > >>> >   
> >> >> > >>> >   Tell CMake where to find the compiler by setting either the
> >> 
> >> environment
> >> 
> >> >> > >>> >   variable "CC" or the CMake cache entry CMAKE_C_COMPILER to
> >> 
> >> the full path to
> >> 
> >> >> > >>> >   the compiler, or to the compiler name if it is in the PATH.
> >> >> > >>> > 
> >> >> > >>> > CMake Error at CMakeLists.txt:7 (project):
> >> >> > >>> >   The CMAKE_CXX_COMPILER:
> >> >> > >>> >     C:/Program Files (x86)/Microsoft Visual
> >> 
> >> Studio/2019/Community/VC/Tools/MSVC/14.24.28314/bin/Hostx86/x86/cl.exe
> >> 
> >> >> > >>> >   is not a full path to an existing compiler tool.
> >> >> > >>> >   
> >> >> > >>> >   To use the NMake generator with Visual C++, cmake must be
> >> 
> >> run from a shell
> >> 
> >> >> > >>> >   that can use the compiler cl from the command line.  This
> >> 
> >> environment is
> >> 
> >> >> > >>> >   unable to invoke the cl compiler.  To fix this problem, run
> >> 
> >> cmake from the
> >> 
> >> >> > >>> >   Visual Studio Command Prompt (vcvarsall.bat).
> >> >> > >>> >   
> >> >> > >>> >   Tell CMake where to find the compiler by setting either the
> >> 
> >> environment
> >> 
> >> >> > >>> >   variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER
> >> 
> >> to the full path
> >> 
> >> >> > >>> >   to the compiler, or to the compiler name if it is in the
> >> 
> >> PATH.
> >> 
> >> >> > >>> > -- Configuring incomplete, errors occurred!
> >> >> > >>> > See also
> >> 
> >> "C:/Users/wss79/git/digikam-pgf-database/CMakeFiles/CMakeOutput.log".
> >> 
> >> >> > >>> > See also
> >> 
> >> "C:/Users/wss79/git/digikam-pgf-database/CMakeFiles/CMakeError.log".
> >> 
> >> >> > >>> > C:\Users\wss79\git\digikam-pgf-database\build>
> >> >> > >>> > 
> >> >> > >>> > On Thu, May 14, 2020 at 3:34 PM Gilles Caulier <
> >> 
> >> caulier.gilles at gmail.com> wrote:
> >> >> > >>> >> No i use VS community everywhere and it work like a charm...
> >> >> > >>> >> 
> >> >> > >>> >> Let's me see the full console backtrace from the moment where
> >> 
> >> you
> >> 
> >> >> > >>> >> start the terminal and the error message
> >> >> > >>> >> 
> >> >> > >>> >> Gilles Caulier
> >> >> > >>> >> 
> >> >> > >>> >> Le jeu. 14 mai 2020 à 21:13, Wesley Smith <wss7932 at gmail.com>
> >> 
> >> a écrit :
> >> >> > >>> >> > Would this be a result of using VS Community 2019?  I've
> >> 
> >> launched the prompt from VS and still get the same errors.
> >> 
> >> >> > >>> >> > On Thu, May 14, 2020 at 7:40 AM Gilles Caulier <
> >> 
> >> caulier.gilles at gmail.com> wrote:
> >> >> > >>> >> >> In fact i know well the error, as i devel with Qt in my
> >> 
> >> office under
> >> 
> >> >> > >>> >> >> Windows and MSVC.
> >> >> > >>> >> >> 
> >> >> > >>> >> >> You need to launch the MSVC terminal, not the standard
> >> 
> >> Windows
> >> 
> >> >> > >>> >> >> terminal (aka "cmd").
> >> >> > >>> >> >> 
> >> >> > >>> >> >> This MSVC terminal init a lots of variables to be able to
> >> 
> >> use the CLI
> >> 
> >> >> > >>> >> >> compiler from Microsoft (i hope that you install the CLI
> >> 
> >> MSVC tools
> >> 
> >> >> > >>> >> >> with the Mircost compiler installer).
> >> >> > >>> >> >> 
> >> >> > >>> >> >> You will found the MSVC terminal in Run Windows menu, MSVC
> >> 
> >> section,
> >> 
> >> >> > >>> >> >> and advanced tools (or something like that). There are
> >> 
> >> many version,
> >> 
> >> >> > >>> >> >> to cross compile to ARM or in 32bits. for get these ones,
> >> 
> >> and take the
> >> 
> >> >> > >>> >> >> native 64 bits version.
> >> >> > >>> >> >> 
> >> >> > >>> >> >> Voilà.
> >> >> > >>> >> >> 
> >> >> > >>> >> >> Gilles Caulier
> >> >> > >>> >> >> 
> >> >> > >>> >> >> Le jeu. 14 mai 2020 à 14:31, Wesley Smith <
> >> 
> >> wss7932 at gmail.com> a écrit :
> >> >> > >>> >> >> > Thank you for that.  I did run it and ran into some
> >> 
> >> issues.  I then ran a command prompt from within Visual Studio Community
> >> edition 2019 and tried again.  Here is the output.  It is looking for a
> >> path I'm not familiar with.
> >> 
> >> >> > >>> >> >> >> C:\Users\wss79\git\digikam-pgf-database\build>cmake ..
> >> >> > >>> >> >> >> -- The C compiler identification is MSVC 19.24.28315.0
> >> >> > >>> >> >> >> -- The CXX compiler identification is MSVC
> >> >> > >>> >> >> >> 19.24.28315.0
> >> >> > >>> >> >> >> -- Check for working C compiler: C:/Program Files
> >> 
> >> (x86)/Microsoft Visual
> >> Studio/2019/Community/VC/Tools/MSVC/14.24.28314/bin/Hostx86/x86/cl.exe
> >> 
> >> >> > >>> >> >> >> -- Check for working C compiler: C:/Program Files
> >> 
> >> (x86)/Microsoft Visual
> >> Studio/2019/Community/VC/Tools/MSVC/14.24.28314/bin/Hostx86/x86/cl.exe -
> >> broken
> >> 
> >> >> > >>> >> >> >> CMake Error at C:/Program
> >> 
> >> Files/CMake/share/cmake-3.17/Modules/CMakeTestCCompiler.cmake:60 
(message):
> >> >> > >>> >> >> >>   The C compiler
> >> >> > >>> >> >> >>   
> >> >> > >>> >> >> >>     "C:/Program Files (x86)/Microsoft Visual
> >> 
> >> Studio/2019/Community/VC/Tools/MSVC/14.24.28314/bin/Hostx86/x86/cl.exe"
> >> 
> >> >> > >>> >> >> >>   is not able to compile a simple test program.
> >> >> > >>> >> >> >>   
> >> >> > >>> >> >> >>   It fails with the following output:
> >> >> > >>> >> >> >>     Change Dir:
> >> C:/Users/wss79/git/digikam-pgf-database/CMakeFiles/CMakeTmp
> >> 
> >> >> > >>> >> >> >>     Run Build Command(s):nmake /nologo cmTC_7b893\fast
> >> 
> >> &&       "C:\Program Files (x86)\Microsoft Visual
> >> Studio\2019\Community\VC\Tools\MSVC\14.24.28314\bin\HostX86\x86\nmake.exe
> >> "
> >> -f CMakeFiles\cmTC_7b893.dir\build.make /nologo -L
> >> CMakeFiles\cmTC_7b893.dir\build
> >> 
> >> >> > >>> >> >> >>     Building C object
> >> 
> >> CMakeFiles/cmTC_7b893.dir/testCCompiler.c.obj
> >> 
> >>  C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1424~1.283\bin\Hostx86\
> >>  x86\cl.exe>> 
> >> @C:\Users\wss79\AppData\Local\Temp\nmC021.tmp
> >> 
> >> >> > >>> >> >> >>     testCCompiler.c
> >> >> > >>> >> >> >>     Linking C executable cmTC_7b893.exe
> >> >> > >>> >> >> >>     
> >> >> > >>> >> >> >>         "C:\Program Files\CMake\bin\cmake.exe" -E
> >> 
> >> vs_link_exe --intdir=CMakeFiles\cmTC_7b893.dir
> >> --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100183~1.0\x86\rc.exe
> >> --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100183~1.0\x86\mt.exe --manifests  --
> >> C:\TDM-GCC-64\bin\ld.exe /nologo @CMakeFiles\cmTC_7b893.dir\objects1.rsp
> >> @C:\Users\wss79\AppData\Local\Temp\nmC62D.tmp
> >> 
> >> >> > >>> >> >> >>     LINK Pass 1: command "C:\TDM-GCC-64\bin\ld.exe
> >> 
> >> /nologo @CMakeFiles\cmTC_7b893.dir\objects1.rsp /out:cmTC_7b893.exe
> >> /implib:cmTC_7b893.lib
> >> /pdb:C:\Users\wss79\git\digikam-pgf-database\CMakeFiles\CMakeTmp\cmTC_7b8
> >> 93.pdb /version:0.0 /machine:X86 /debug /INCREMENTAL /subsystem:console
> >> kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib
> >> oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST
> >> /MANIFESTFILE:CMakeFiles\cmTC_7b893.dir/intermediate.manifest
> >> CMakeFiles\cmTC_7b893.dir/manifest.res" failed (exit code 1) with the
> >> 
> >> following output:
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find /nologo: No
> >> 
> >> such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find
> >> 
> >> /out:cmTC_7b893.exe: No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find
> >> 
> >> /implib:cmTC_7b893.lib: No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find
> >> 
> >> /pdb:C:\Users\wss79\git\digikam-pgf-database\CMakeFiles\CMakeTmp\cmTC_7b8
> >> 93.pdb: Invalid argument
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find /version:0.0:
> >> No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find /machine:X86:
> >> No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find /debug: No
> >> 
> >> such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find /INCREMENTAL:
> >> No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find
> >> 
> >> /subsystem:console: No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find kernel32.lib:
> >> No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find user32.lib:
> >> No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find gdi32.lib: No
> >> 
> >> such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find winspool.lib:
> >> No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find shell32.lib:
> >> No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find ole32.lib: No
> >> 
> >> such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find oleaut32.lib:
> >> No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find uuid.lib: No
> >> 
> >> such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find comdlg32.lib:
> >> No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find advapi32.lib:
> >> No such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find /MANIFEST: No
> >> 
> >> such file or directory
> >> 
> >> >> > >>> >> >> >>     C:\TDM-GCC-64\bin\ld.exe: cannot find
> >> 
> >> /MANIFESTFILE:CMakeFiles\cmTC_7b893.dir/intermediate.manifest: Invalid
> >> argument
> >> 
> >> >> > >>> >> >> >>     CMakeFiles\cmTC_7b893.dir/manifest.res: file not
> >> 
> >> recognized: File format not recognized
> >> 
> >> >> > >>> >> >> >>     NMAKE : fatal error U1077: '"C:\Program
> >> 
> >> Files\CMake\bin\cmake.exe"' : return code '0xffffffff'
> >> 
> >> >> > >>> >> >> >>     Stop.
> >> >> > >>> >> >> >>     NMAKE : fatal error U1077: '"C:\Program Files
> >> 
> >> (x86)\Microsoft Visual
> >> Studio\2019\Community\VC\Tools\MSVC\14.24.28314\bin\HostX86\x86\nmake.exe
> >> "'
> >> 
> >> : return code '0x2'
> >> : 
> >> >> > >>> >> >> >>     Stop.
> >> >> > >>> >> >> > 
> >> >> > >>> >> >> > On Thu, May 14, 2020 at 2:35 AM Gilles Caulier <
> >> 
> >> caulier.gilles at gmail.com> wrote:
> >> >> > >>> >> >> >> Hi,
> >> >> > >>> >> >> >> 
> >> >> > >>> >> >> >> I just add a bootstrap.bat script for Windows. Take a
> >> 
> >> look, you can
> >> 
> >> >> > >>> >> >> >> customize the Qt5_DIR variable, which is the root
> >> 
> >> install path to Qt5.
> >> 
> >> 
> >> https://github.com/cgilles/digikam-pgf-database/blob/master/bootstrap.bat
> >> 
> >> >> > >>> >> >> >> Gilles Caulier
> >> >> > >>> >> >> >> 
> >> >> > >>> >> >> >> Le jeu. 14 mai 2020 à 04:28, Gilles Caulier <
> >> 
> >> caulier.gilles at gmail.com> a écrit :
> >> >> > >>> >> >> >> > Le jeu. 14 mai 2020 à 02:08, Wesley Smith <
> >> 
> >> wss7932 at gmail.com> a écrit :
> >> >> > >>> >> >> >> > > I hate not being able to figure this out but, I
> >> 
> >> have an issue.  I'm not at all familiar with QT.  I'm using Windows 10
> >> (latest stable build) and I just installed cmake and Qt.  I followed the
> >> instructions but, cmake is not able to find some things.  Here is the
> >> 
> >> output:
> >> >> > >>> >> >> >> > >> -- Selecting Windows SDK version 10.0.18362.0 to
> >> 
> >> target Windows 10.0.18363.
> >> 
> >> >> > >>> >> >> >> > >> -- Could NOT find Qt5 (missing: Qt5_DIR)
> >> >> > >>> >> >> >> > >> -- Configuring done
> >> >> > >>> >> >> >> > >> 
> >> >> > >>> >> >> >> > >> CMake Error at CMakeLists.txt:21 (add_executable):
> >> >> > >>> >> >> >> > >>   Target "pgfdatabase" links to target "Qt5::Core"
> >> 
> >> but the target was not
> >> 
> >> >> > >>> >> >> >> > >>   found.  Perhaps a find_package() call is missing
> >> 
> >> for an IMPORTED target, or
> >> 
> >> >> > >>> >> >> >> > >>   an ALIAS target is missing?
> >> >> > >>> >> >> >> > 
> >> >> > >>> >> >> >> > How did you get this trace ? From a windows terminal
> >> 
> >> with MSVC setup ?
> >> 
> >> >> > >>> >> >> >> > Did you install Qtcreator ? I need to know more
> >> 
> >> details about the
> >> 
> >> >> > >>> >> >> >> > install from your system.
> >> >> > >>> >> >> >> > 
> >> >> > >>> >> >> >> > Gilles Caulier
> >> >> > > 
> >> >> > > --
> >> >> > > Send with Gmail Mobile






More information about the Digikam-users mailing list