Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. How can I open openexr image on qt widget
Forum Updated to NodeBB v4.3 + New Features

How can I open openexr image on qt widget

Scheduled Pinned Locked Moved Unsolved General and Desktop
49 Posts 5 Posters 10.9k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • VRoninV Offline
    VRoninV Offline
    VRonin
    wrote on last edited by VRonin
    #34

    I tried to build it myself but I must admit I too struggle with getting openexr to link. I will post my progress below anyway to make it more accessible to other people to try and fix this. The commands should create a zip file containing each dependency and a zip file containing the KDE API libraries but I can't get the final link over the line

    The series of commands I used can be replicated to build all the dependencies and the library (as you can see, I built with Qt5.12 on MSVC 2015):

    set cmake_path=C:\Program Files\CMake\bin
    set 7zip_path=C:\Program Files\7-Zip
    set git_path=C:\Program Files\Git\bin
    set qt_path=C:\Qt\5.12\msvc2015_64
    set curl_path=C:\libcurl\bin
    set compiler_path=C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC
    set comp_platform=amd64
    set use_mingw=false
    set originalWD=%CD%
    set PATH=%cmake_path%;%git_path%;%curl_path%;%7zip_path%;%PATH%
    call "%qt_path%\bin\qtenv2.bat"
    cd %originalWD%
    echo on
    if %use_mingw%==true set PATH=%compiler_path%;%PATH%
    if %use_mingw%==false call "%compiler_path%\vcvarsall.bat" %comp_platform%
    if %use_mingw%==true (set CMAKEGENERATOR="MinGW Makefiles") else (set CMAKEGENERATOR="NMake Makefiles")
    mkdir .\bzip2src && cd .\bzip2src
    curl -k -L https://sourceforge.net/projects/gnuwin32/files/bzip2/1.0.5/bzip2-1.0.5-src.zip --output bzip2.zip
    7z x bzip2.zip
    del /F /Q  bzip2.zip
    cd src\bzip2\1.0.5\bzip2-1.0.5\
    mkdir build && cd build
    echo cmake_minimum_required(VERSION 3.5) >> ..\CMakeLists.txt
    echo project(bzip2 C) >> ..\CMakeLists.txt
    echo set(bzip2_VERSION 1.0.5) >> ..\CMakeLists.txt
    echo set(bzip2_SRCS >> ..\CMakeLists.txt
    echo bzlib.c >> ..\CMakeLists.txt
    echo blocksort.c >> ..\CMakeLists.txt
    echo huffman.c >> ..\CMakeLists.txt
    echo crctable.c >> ..\CMakeLists.txt
    echo compress.c >> ..\CMakeLists.txt
    echo decompress.c >> ..\CMakeLists.txt
    echo randtable.c >> ..\CMakeLists.txt
    echo ) >> ..\CMakeLists.txt
    echo add_library(bzip2 SHARED ${bzip2_SRCS}) >> ..\CMakeLists.txt
    echo install(TARGETS bzip2 >> ..\CMakeLists.txt
    echo EXPORT bzip2 >> ..\CMakeLists.txt
    echo RUNTIME DESTINATION bin COMPONENT library >> ..\CMakeLists.txt
    echo LIBRARY DESTINATION lib COMPONENT library >> ..\CMakeLists.txt
    echo ARCHIVE DESTINATION lib COMPONENT library >> ..\CMakeLists.txt
    echo ) >> ..\CMakeLists.txt
    echo install(FILES bzlib.h >> ..\CMakeLists.txt
    echo DESTINATION include >> ..\CMakeLists.txt
    echo COMPONENT headers >> ..\CMakeLists.txt
    echo ) >> ..\CMakeLists.txt
    cmake -G %CMAKEGENERATOR% -DCMAKE_INSTALL_PREFIX=../../../../../../bzip2 -DCMAKE_BUILD_TYPE=RELEASE ../
    cmake --build .
    cmake --build . --target install
    cd ..\..\..\..\..\..\
    set PATH=%CD%\bzip2;%PATH%
    7z a -tzip bzip2.zip .\bzip2\*
    mkdir .\liblzma && cd .\liblzma
    curl -k -L https://tukaani.org/xz/xz-5.2.4-windows.zip --output liblzma.zip
    7z x liblzma.zip
    del /F /Q liblzma.zip
    if %use_mingw%==true (ren bin_i686 lib) else (mkdir lib && mkdir bin)
    if %use_mingw%==false curl -k -L https://tukaani.org/xz/xz-5.2.4.tar.gz --output liblzma.tar.gz
    if %use_mingw%==false 7z x liblzma.tar.gz
    if %use_mingw%==false del /F /Q liblzma.tar.gz
    if %use_mingw%==false 7z x liblzma.tar
    if %use_mingw%==false del /F /Q liblzma.tar
    if %use_mingw%==false cd xz-5.2.4\windows\vs2013
    if %comp_platform%==x86 if %use_mingw%==false msbuild xz_win.sln /property:Configuration=Release /property:Platform=Win32 && xcopy /Y /I /K Release\Win32\liblzma_dll\*.dll ..\..\..\bin && xcopy /Y /I /K Release\Win32\liblzma_dll\*.lib ..\..\..\lib
    if %comp_platform%==amd64 if %use_mingw%==false msbuild xz_win.sln /property:Configuration=Release /property:Platform=x64 && xcopy /Y /I /K Release\x64\liblzma_dll\*.dll ..\..\..\bin && xcopy /Y /I /K Release\x64\liblzma_dll\*.lib ..\..\..\lib
    if %use_mingw%==false cd ..\..\..\
    set PATH=%CD%;%PATH%
    cd ..\
    7z a -tzip liblzma.zip .\liblzma\include\
    7z a -tzip liblzma.zip .\liblzma\lib\
    if %use_mingw%==false 7z a -tzip liblzma.zip .\liblzma\bin\
    git clone https://github.com/madler/zlib.git zlibBuild
    cd zlibBuild
    mkdir .\build && cd .\build
    cmake -G %CMAKEGENERATOR% -DCMAKE_INSTALL_PREFIX=../../zlib -DCMAKE_BUILD_TYPE=RELEASE ../
    cmake --build .
    cmake --build . --target install
    cd ..\..\
    7z a -tzip zlib.zip .\zlib\*
    set PATH=%CD%\zlib;%PATH%
    git clone https://github.com/openexr/openexr.git OpenEXRsrc
    cd OpenEXRsrc
    mkdir .\build && cd .\build
    cmake -G %CMAKEGENERATOR% -DOPENEXR_NAMESPACE_VERSIONING=OFF -DOPENEXR_BUILD_PYTHON_LIBS=OFF -DCMAKE_DEBUG_POSTFIX=d -DOPENEXR_BUILD_TESTS=OFF -DCMAKE_INSTALL_PREFIX=../../OpenEXR -DCMAKE_BUILD_TYPE=DEBUG ../
    cmake --build .
    cmake --build . --target install
    cmake -G %CMAKEGENERATOR% -DOPENEXR_NAMESPACE_VERSIONING=OFF -DOPENEXR_BUILD_PYTHON_LIBS=OFF -DOPENEXR_BUILD_TESTS=OFF -DCMAKE_INSTALL_PREFIX=../../OpenEXR -DCMAKE_BUILD_TYPE=RELEASE ../
    cmake --build .
    cmake --build . --target install
    cd ..\..\
    7z a -tzip OpenEXR.zip .\OpenEXR\*
    set PATH=%CD%\OpenEXR;%PATH%
    git clone git://anongit.kde.org/extra-cmake-modules ECM
    cd ECM
    mkdir .\build && cd .\build
    cmake -G %CMAKEGENERATOR% -DBUILD_TESTING=OFF -DCMAKE_INSTALL_PREFIX=../../ECMbuild -DCMAKE_BUILD_TYPE=RELEASE ../
    cmake --build .
    cmake --build . --target install
    cd ..\..\
    set PATH=%CD%\ECMbuild;%PATH%
    git clone git://anongit.kde.org/karchive.git KArchive
    cd KArchive
    mkdir .\build && cd .\build
    cmake -G %CMAKEGENERATOR% -DBUILD_TESTING=OFF -DCMAKE_DEBUG_POSTFIX=d -DCMAKE_INSTALL_PREFIX=../../KDEAPI -DCMAKE_BUILD_TYPE=DEBUG ../
    cmake --build .
    cmake --build . --target install
    cmake -G %CMAKEGENERATOR% -DBUILD_TESTING=OFF -DCMAKE_INSTALL_PREFIX=../../KDEAPI -DCMAKE_BUILD_TYPE=RELEASE ../
    cmake --build .
    cmake --build . --target install
    cd ..\..\
    set PATH=%CD%\KDEAPI;%PATH%
    git clone git://anongit.kde.org/kimageformats.git KImageFormats
    cd KImageFormats
    mkdir .\build && cd .\build
    cmake -G %CMAKEGENERATOR% -DBUILD_TESTING=OFF -DCMAKE_DEBUG_POSTFIX=d -DCMAKE_INSTALL_PREFIX=../../KDEAPI -DCMAKE_BUILD_TYPE=DEBUG ../
    cmake --build .
    cmake --build . --target install
    cmake -G %CMAKEGENERATOR% -DBUILD_TESTING=OFF -DCMAKE_INSTALL_PREFIX=../../KDEAPI -DCMAKE_BUILD_TYPE=RELEASE ../
    cmake --build .
    cmake --build . --target install
    cd ..\..\
    7z a -tzip KDElib.zip .\KDEAPI\*
    

    You'll need to have installed 7-zip, curl, CMake and git.
    You'll need to change the initial lines to match your system:

    • set cmake_path=C:\Program Files\CMake\bin: path to the CMake executable
    • set 7zip_path=C:\Program Files\7-Zip: path to the 7-zip executable
    • set git_path=C:\Program Files\Git\bin: path to the git executable
    • set qt_path=C:\Qt\5.12\msvc2015_64: path to your qt directory
    • set curl_path=C:\libcurl\bin: path to the curl executable
    • set compiler_path=C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC: path to the compiler binary folder
    • set comp_platform=amd64 can be either amd64 or x86 determines if the build is 64 or 32 bit
    • set use_mingw=false set to true if you use MinGW or false if you use MSVC

    One final thing, if you use MinGW you might need to adjust the line if %use_mingw%==true (ren bin_i686 lib) else (mkdir lib && mkdir bin) changing bin_i686 to the name of the folder containing the libraries that match your compiler (there are 3 available)

    "La mort n'est rien, mais vivre vaincu et sans gloire, c'est mourir tous les jours"
    ~Napoleon Bonaparte

    On a crusade to banish setIndexWidget() from the holy land of Qt

    1 Reply Last reply
    5
    • SGaistS SGaist

      You can't mix and match C++ libraries built with VS and MinGW, you have to always use the same compiler.

      N Offline
      N Offline
      Nathan Miguel
      wrote on last edited by
      #35

      @SGaist @VRonin you save my lifeeeeeee. but Well I chose to use VS because mingw gave object error, but how can I include it in qt now, you can give a clearer explanation because documentation is confusing

      VRoninV 1 Reply Last reply
      0
      • N Nathan Miguel

        @SGaist @VRonin you save my lifeeeeeee. but Well I chose to use VS because mingw gave object error, but how can I include it in qt now, you can give a clearer explanation because documentation is confusing

        VRoninV Offline
        VRoninV Offline
        VRonin
        wrote on last edited by
        #36

        @Nathan-Miguel said in How can I open openexr image on qt widget:

        but how can I include it in qt

        I imagine you mean Qt Creator. Right click on your project -> add library -> external library -> select the .lib file and the include directory (the d suffix should be detected automatically).

        "La mort n'est rien, mais vivre vaincu et sans gloire, c'est mourir tous les jours"
        ~Napoleon Bonaparte

        On a crusade to banish setIndexWidget() from the holy land of Qt

        N 1 Reply Last reply
        0
        • VRoninV VRonin

          @Nathan-Miguel said in How can I open openexr image on qt widget:

          but how can I include it in qt

          I imagine you mean Qt Creator. Right click on your project -> add library -> external library -> select the .lib file and the include directory (the d suffix should be detected automatically).

          N Offline
          N Offline
          Nathan Miguel
          wrote on last edited by Nathan Miguel
          #37

          @VRonin even the libs was fine, but in question my qt still does not open and I still have some doubts,

          1. Do I need to add the openexr and libs includes?
          2. Can I continue using the QPixelmap label?
          3. In kimageformat did not come any include in .h, do I have to use .desktop or use the openexr includes to open the image?

          This is the function I'm using to open an image

          void MainWindow::on_actionOpen_Image_triggered()
          {
              QString filter = "Imagens (*.bmp *.cur *.gif *icns *.ico *.jpg *.jpeg *.pdm *.pgm *.png *.ppm *.svg *.tga *.tif *.tiff *.wbmp *.webp *.xmb *.xpm) ;; All Files (*.*)";
              QString filename = QFileDialog::getOpenFileName(this, "Open", QDir::homePath(), filter);
              QFile file(filename);
              QImage image(filename);
              if (!image.isNull())
                  {
                       QImage image(filename);
                       image = image.scaledToWidth(ui->labelimg->width(), Qt::SmoothTransformation);
                       image = image.scaledToWidth(ui->labelimg->height(), Qt::SmoothTransformation);
                       ui->labelimg->setPixmap(QPixmap::fromImage(image));
                  }
              else
                  {
                      QMessageBox::warning(this, "Error", "Image can not open");
                      filename = "";
                  }
          
          }
          
          1 Reply Last reply
          0
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #38

            Where did you install the plugins ?
            You can also set the QT_DEBUG_PLUGINS environment variable to 1 in the Run part of the Project panel to see what is happening.

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            N 1 Reply Last reply
            0
            • SGaistS SGaist

              Where did you install the plugins ?
              You can also set the QT_DEBUG_PLUGINS environment variable to 1 in the Run part of the Project panel to see what is happening.

              N Offline
              N Offline
              Nathan Miguel
              wrote on last edited by Nathan Miguel
              #39

              @SGaist The .desktop files are in the files and programs folder, the libs continued in the folder on I compiled, which was in C: / Git / kimageformat / build, and the dll were for the qt compiler itself, msvc2017-64 in the plugin / image folder

              One more thing, in this directory "C: \ Qt \ 5.12.0 \ msvc2017_64 \ plugins \ imageformats", I realized that the "tga" format, had tbm support here, and gives the same error when I try to open open exr in the app debug "QImage :: scaleWidth: Image is a null image".

              First I used the .dll, .pdb files with this name "kimg_exr", then renamed "qexr", both the dll and the pdb, but it still did not work, nor with the native tga that worked right.

              And if it is useful these are my includes

              #include "mainwindow.h"
              #include "ui_mainwindow.h"
              #include <QDesktopServices>
              #include <QMessageBox>
              #include <QUrl>
              #include <QFile>
              #include <QFileDialog>
              #include <QImage>
              #include <QPixmap>
              #include <QImageIOPlugin>
              #include <QImageIOHandler>
              

              source code: https://github.com/nathanmiguel123/Denoiser-Script

              1 Reply Last reply
              0
              • SGaistS Offline
                SGaistS Offline
                SGaist
                Lifetime Qt Champion
                wrote on last edited by
                #40

                Did you call nmake install at some point ?

                Interested in AI ? www.idiap.ch
                Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                N 1 Reply Last reply
                0
                • SGaistS SGaist

                  Did you call nmake install at some point ?

                  N Offline
                  N Offline
                  Nathan Miguel
                  wrote on last edited by
                  #41

                  @SGaist noup

                  1 Reply Last reply
                  0
                  • SGaistS Offline
                    SGaistS Offline
                    SGaist
                    Lifetime Qt Champion
                    wrote on last edited by
                    #42

                    Then this might explain the missing plugins.

                    Interested in AI ? www.idiap.ch
                    Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                    N 1 Reply Last reply
                    0
                    • SGaistS SGaist

                      Then this might explain the missing plugins.

                      N Offline
                      N Offline
                      Nathan Miguel
                      wrote on last edited by
                      #43

                      @SGaist So I'm practically going to have to build manually?

                      1 Reply Last reply
                      0
                      • SGaistS Offline
                        SGaistS Offline
                        SGaist
                        Lifetime Qt Champion
                        wrote on last edited by
                        #44

                        Build what manually ?

                        The fact that you didn't call nmake install after building the module just means that you didn't install the libraries/plugins you built so that might be a reason why Qt can't find them. You should first try that.

                        Interested in AI ? www.idiap.ch
                        Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                        N 1 Reply Last reply
                        0
                        • SGaistS SGaist

                          Build what manually ?

                          The fact that you didn't call nmake install after building the module just means that you didn't install the libraries/plugins you built so that might be a reason why Qt can't find them. You should first try that.

                          N Offline
                          N Offline
                          Nathan Miguel
                          wrote on last edited by
                          #45

                          @SGaist well I did it, but still I keep giving it not opening

                          16:59:10: Running steps for project src...
                          16:59:10: Starting: "C:\Qt\Tools\QtCreator\bin\jom.exe" clean
                          	C:\Qt\Tools\QtCreator\bin\jom.exe -f Makefile.Debug clean
                          	del debug\moc_predefs.h
                          	del debug\moc_mainwindow.cpp
                          	del ui_mainwindow.h
                          	del debug\main.obj debug\mainwindow.obj debug\moc_mainwindow.obj
                          	del debug\src.exp debug\src.vc.pdb debug\src.ilk debug\src.idb
                          	C:\Qt\Tools\QtCreator\bin\jom.exe -f Makefile.Release clean
                          	del release\moc_predefs.h
                          	del release\moc_mainwindow.cpp
                          	del ui_mainwindow.h
                          	del release\main.obj release\mainwindow.obj release\moc_mainwindow.obj
                          	del release\src.exp
                          NÆo foi poss¡vel encontrar C:\Git\Denoiser-Script\build-src-Desktop_Qt_5_12_0_MSVC2017_64bit-Debug\release\moc_predefs.h
                          NÆo foi poss¡vel encontrar C:\Git\Denoiser-Script\build-src-Desktop_Qt_5_12_0_MSVC2017_64bit-Debug\release\moc_mainwindow.cpp
                          NÆo foi poss¡vel encontrar C:\Git\Denoiser-Script\build-src-Desktop_Qt_5_12_0_MSVC2017_64bit-Debug\ui_mainwindow.h
                          NÆo foi poss¡vel encontrar C:\Git\Denoiser-Script\build-src-Desktop_Qt_5_12_0_MSVC2017_64bit-Debug\release\main.obj
                          NÆo foi poss¡vel encontrar C:\Git\Denoiser-Script\build-src-Desktop_Qt_5_12_0_MSVC2017_64bit-Debug\release\src.exp
                          	del src.exp
                          NÆo foi poss¡vel encontrar C:\Git\Denoiser-Script\build-src-Desktop_Qt_5_12_0_MSVC2017_64bit-Debug\src.exp
                          	del src.vc.pdb
                          NÆo foi poss¡vel encontrar C:\Git\Denoiser-Script\build-src-Desktop_Qt_5_12_0_MSVC2017_64bit-Debug\src.vc.pdb
                          	del src.ilk
                          NÆo foi poss¡vel encontrar C:\Git\Denoiser-Script\build-src-Desktop_Qt_5_12_0_MSVC2017_64bit-Debug\src.ilk
                          	del src.idb
                          NÆo foi poss¡vel encontrar C:\Git\Denoiser-Script\build-src-Desktop_Qt_5_12_0_MSVC2017_64bit-Debug\src.idb
                          16:59:11: The process "C:\Qt\Tools\QtCreator\bin\jom.exe" exited normally.
                          16:59:11: Starting: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\nmake.exe" 
                          
                          Microsoft (R) Program Maintenance Utility Versão 14.16.27025.1
                          Direitos autorais da Microsoft Corporation. Todos os direitos reservados.
                          	"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\nmake.exe" -f Makefile.Debug
                          
                          Microsoft (R) Program Maintenance Utility Versão 14.16.27025.1
                          Direitos autorais da Microsoft Corporation. Todos os direitos reservados.
                          	C:\Qt\5.12.0\msvc2017_64\bin\uic.exe ..\src\mainwindow.ui -o ui_mainwindow.h
                          	cl -BxC:\Qt\5.12.0\msvc2017_64\bin\qmake.exe -nologo -Zc:wchar_t -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -Zc:referenceBinding -Zc:__cplusplus -Zi -MDd -std:c++17 -W3 -w34100 -w34189 -w44996 -w44456 -w44457 -w44458 -wd4577 -wd4467 -E ..\..\..\Qt\5.12.0\msvc2017_64\mkspecs\features\data\dummy.cpp 2>NUL >debug\moc_predefs.h
                          	C:\Qt\5.12.0\msvc2017_64\bin\moc.exe -DUNICODE -D_UNICODE -DWIN32 -D_ENABLE_EXTENDED_ALIGNED_STORAGE -DWIN64 -DQT_DEPRECATED_WARNINGS -DQT_QML_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB --compiler-flavor=msvc --include C:/Git/Denoiser-Script/build-src-Desktop_Qt_5_12_0_MSVC2017_64bit-Debug/debug/moc_predefs.h -IC:/Qt/5.12.0/msvc2017_64/mkspecs/win32-msvc -IC:/Git/Denoiser-Script/src -IC:/Qt/5.12.0/msvc2017_64/include -IC:/Qt/5.12.0/msvc2017_64/include/QtWidgets -IC:/Qt/5.12.0/msvc2017_64/include/QtGui -IC:/Qt/5.12.0/msvc2017_64/include/QtANGLE -IC:/Qt/5.12.0/msvc2017_64/include/QtCore -I. -I"C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\include" -I"C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\include\um" -I"C:\Program Files (x86)\Windows Kits\10\include\10.0.17763.0\ucrt" -I"C:\Program Files (x86)\Windows Kits\10\include\10.0.17763.0\shared" -I"C:\Program Files (x86)\Windows Kits\10\include\10.0.17763.0\um" -I"C:\Program Files (x86)\Windows Kits\10\include\10.0.17763.0\winrt" -I"C:\Program Files (x86)\Windows Kits\10\include\10.0.17763.0\cppwinrt" ..\src\mainwindow.h -o debug\moc_mainwindow.cpp
                          	cl -c -nologo -Zc:wchar_t -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -Zc:referenceBinding -Zc:__cplusplus -Zi -MDd -std:c++17 -W3 -w34100 -w34189 -w44996 -w44456 -w44457 -w44458 -wd4577 -wd4467 -EHsc /Fddebug\src.vc.pdb -DUNICODE -D_UNICODE -DWIN32 -D_ENABLE_EXTENDED_ALIGNED_STORAGE -DWIN64 -DQT_DEPRECATED_WARNINGS -DQT_QML_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I..\src -I. -I..\..\..\Qt\5.12.0\msvc2017_64\include -I..\..\..\Qt\5.12.0\msvc2017_64\include\QtWidgets -I..\..\..\Qt\5.12.0\msvc2017_64\include\QtGui -I..\..\..\Qt\5.12.0\msvc2017_64\include\QtANGLE -I..\..\..\Qt\5.12.0\msvc2017_64\include\QtCore -Idebug -I. -I\include -I..\..\..\Qt\5.12.0\msvc2017_64\mkspecs\win32-msvc -Fodebug\ @C:\Users\natha\AppData\Local\Temp\nm127F.tmp
                          main.cpp
                          mainwindow.cpp
                          Gerando C¢digo...
                          	cl -c -nologo -Zc:wchar_t -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -Zc:referenceBinding -Zc:__cplusplus -Zi -MDd -std:c++17 -W3 -w34100 -w34189 -w44996 -w44456 -w44457 -w44458 -wd4577 -wd4467 -EHsc /Fddebug\src.vc.pdb -DUNICODE -D_UNICODE -DWIN32 -D_ENABLE_EXTENDED_ALIGNED_STORAGE -DWIN64 -DQT_DEPRECATED_WARNINGS -DQT_QML_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I..\src -I. -I..\..\..\Qt\5.12.0\msvc2017_64\include -I..\..\..\Qt\5.12.0\msvc2017_64\include\QtWidgets -I..\..\..\Qt\5.12.0\msvc2017_64\include\QtGui -I..\..\..\Qt\5.12.0\msvc2017_64\include\QtANGLE -I..\..\..\Qt\5.12.0\msvc2017_64\include\QtCore -Idebug -I. -I\include -I..\..\..\Qt\5.12.0\msvc2017_64\mkspecs\win32-msvc -Fodebug\ @C:\Users\natha\AppData\Local\Temp\nm1EE4.tmp
                          moc_mainwindow.cpp
                          	link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:WINDOWS "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" /MANIFEST:embed /OUT:debug\src.exe @C:\Users\natha\AppData\Local\Temp\nm23F6.tmp
                          16:59:17: The process "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\nmake.exe" exited normally.
                          16:59:17: Configuration unchanged, skipping qmake step.
                          16:59:17: Starting: "C:\Qt\Tools\QtCreator\bin\jom.exe" 
                          	C:\Qt\Tools\QtCreator\bin\jom.exe -f Makefile.Debug
                          16:59:17: The process "C:\Qt\Tools\QtCreator\bin\jom.exe" exited normally.
                          16:59:17: Elapsed time: 00:07.
                          
                          1 Reply Last reply
                          0
                          • SGaistS Offline
                            SGaistS Offline
                            SGaist
                            Lifetime Qt Champion
                            wrote on last edited by
                            #46

                            Did you run your application with the QT_DEBUG_PLUGINS environment variable set to 1 to see what exactly is happening with the plugins ?

                            Interested in AI ? www.idiap.ch
                            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                            N 1 Reply Last reply
                            0
                            • SGaistS SGaist

                              Did you run your application with the QT_DEBUG_PLUGINS environment variable set to 1 to see what exactly is happening with the plugins ?

                              N Offline
                              N Offline
                              Nathan Miguel
                              wrote on last edited by
                              #47

                              @SGaist I already tried td and q_debug_plugin does not appear, I do not know how to implement it

                              1 Reply Last reply
                              0
                              • SGaistS Offline
                                SGaistS Offline
                                SGaist
                                Lifetime Qt Champion
                                wrote on last edited by
                                #48

                                Might be a silly remark but the casing is important as well as the name. It's QT_DEBUG_PLUGINS not q_debug_plugin.

                                Interested in AI ? www.idiap.ch
                                Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                                N 1 Reply Last reply
                                0
                                • SGaistS SGaist

                                  Might be a silly remark but the casing is important as well as the name. It's QT_DEBUG_PLUGINS not q_debug_plugin.

                                  N Offline
                                  N Offline
                                  Nathan Miguel
                                  wrote on last edited by
                                  #49

                                  @SGaist In fact I researched this way, but even so I did not this option, nor to implement in code

                                  1 Reply Last reply
                                  0

                                  • Login

                                  • Login or register to search.
                                  • First post
                                    Last post
                                  0
                                  • Categories
                                  • Recent
                                  • Tags
                                  • Popular
                                  • Users
                                  • Groups
                                  • Search
                                  • Get Qt Extensions
                                  • Unsolved