Navigation

    Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    1. Home
    2. Tags
    3. win32
    Log in to post

    • UNSOLVED Building Qt for Win32 fails due to lack of libEGL.lib
      General and Desktop • win32 qt build failed • • pderocco  

      1
      0
      Votes
      1
      Posts
      66
      Views

      No one has replied

    • UNSOLVED Win32 static linking?
      QML and Qt Quick • qml static library msvc2017 win32 32bit • • pderocco  

      12
      0
      Votes
      12
      Posts
      1730
      Views

      @SGaist said in Win32 static linking?: Qt Creator architecture has nothing to do with the architecture of your application. To build a 32bit version of your application, use the 32bit package for MSVC2017. The same goes for the 64bit version. Yeah, that worked. When I tried it in 5.12.0 and failed, there must have been something misconfigured. I currently don't know for the static version, however when building the dynamic version you can say to configure that it should build dynamic backend selection. Following some info from another post, I tried the following configure.bat options: -prefix "C:\Qt\Qt5.12.2\5.12.2\msvc2017sr" -release -platform win32-msvc -confirm-license -opensource -nomake examples -nomake tests -static -static-runtime -opengl dynamic -angle -combined-angle-lib -no-feature-d3d12 Now it works on the 32-bit Windows machine I used to build Qt and the application (and still works fine on the 64-bit machine I can also build it on), but when I run it on another Win7 64-bit machine that has never had Qt installed on it, I just get the window frame again. Is it looking for a DLL? I only have a nebulous idea of what some of those configure options actually mean, so I don't know what to try next.
    • UNSOLVED How can I set the string QLineEdit in application with help of other application or shell script?
      General and Desktop • windows win32 shell qt 5.11.1 • • Yash001  

      15
      0
      Votes
      15
      Posts
      896
      Views

      @SGaist Thank you inform about me QtSingleApplication class. I will modify code and use QtSingleApplication.
    • UNSOLVED Use a QDialog box in Win32 Application
      General and Desktop • win32 qinputdialog console app • • falcon010216  

      4
      0
      Votes
      4
      Posts
      555
      Views

      @newbieQTDev said in Use a QDialog box in Win32 Application: This is the version of my QT. No this is the Qt version which was used to build QtCreator (which is a Qt app). You're using Qt 5.6.0
    • UNSOLVED Black flicker areas resizing Direct3D11 widget in Qt 5.6
      General and Desktop • opengl qt 5.6.0 win32 directx painting • • Goombert  

      1
      0
      Votes
      1
      Posts
      919
      Views

      No one has replied

    • QtCreator - building a Win32 application with cmake [SOLVED]
      Tools • qtcreator cmake win32 • • Gustavo Ribeiro Croscato  

      2
      0
      Votes
      2
      Posts
      3594
      Views

      I found a solution. In case anyone has the same problem just add the following to you CMakeLists.txt: if(WIN32) set(GUI_TYPE WIN32) elseif(APPLE) set(GUI_TYPE MACOSX_BUNDLE) endif() then add ${GUI_TYPE} to your target. My CMakeLists.txt is now project(Win32App) cmake_minimum_required(VERSION 3.0.2 FATAL_ERROR) if(WIN32) set(GUI_TYPE WIN32) elseif(APPLE) set(GUI_TYPE MACOSX_BUNDLE) endif() set(SRC main.cpp ) set(HDR) set(RES) add_definitions(-DWIN32 -D_WINDOWS -D_UNICODE -DUNICODE) set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} /SUBSYSTEM:WINDOWS,5.01") add_custom_target(${PROJECT_NAME}_HEADERS SOURCES ${HDR}) add_executable(${CMAKE_PROJECT_NAME} ${GUI_TYPE} ${SRC} ${RES})
    • UNSOLVED qFormatLogMessage and backtrace on win32 / msvc2013
      General and Desktop • qt5.5.1 msvc2013 win32 logging backtrace • • BenV666  

      2
      0
      Votes
      2
      Posts
      1273
      Views

      Hi and welcome to devnet, Do you have by any change QT_FATAL_WARNINGS defined ? If not, can you try the same thing with the 5.6 beta ?
    • in scopes, how do I specify 64-bit Windows? [SOLVED]
      General and Desktop • qmake win32 64 bits 32 bits • • Karen Morrissey  

      12
      0
      Votes
      12
      Posts
      5978
      Views

      @SGaist Oh, I see where to do that. Thanks. I think that last part makes for a solution.
    • qmake LIBS variable: is it necessary to have separate win32 and unix scopes?
      General and Desktop • qmake win32 libs unix • • Bart_Vandewoestyne  

      4
      0
      Votes
      4
      Posts
      1193
      Views

      As soon as paths or library names differ, you will have to use scoped declarations. Otherwise it really does not matter. Win32 also links correctly using -lSomeCoolLib, therefor you could just use one LIBS directive.
    • Focus problems when embedding a native window
      General and Desktop • desktop win32 • • Zylann  

      5
      0
      Votes
      5
      Posts
      3255
      Views

      This thread is 4 years old, but I want to give a solution anyway. I spent the past 2 months trying to figure out how to do this, and all the threads I found are talking about issues but nobody gave me a solution. Actually, the QWidget you create has its own focus but is not "parent" of the HWND you are embedding on it, so you have to make the keyboard focus by yourself. The best way to do that is by using the SetFocus function of the winuser library (WinUser.h): https://docs.microsoft.com/en-us/windows/desktop/api/winuser/nf-winuser-setfocus Like, in example: m_qwindow = QWindow::fromWinId(m_handle); m_widget = QWidget::createWindowContainer(m_qwindow, this); // tell the os to focus the viewport window SetFocus(m_handle); with m_handle being the HWND (or WId) used to create the QWindow. Unfortunately, this solution works only on windows (but maybe there are equivalents on another os). It also doesn't work when clicking on the embedded window, because it isn't owned by Qt. maybe you can try to mess with QFocusFrame (I haven't tried this at all, but it should be a way to use it as a fix by putting it over the embedded window) or, if the window you are embedding is one of your creations, put the SetFocus() function in its code, as a callback when clicked. I hope that even with 4 years late, this solution is still helping the desperate developers like who I was the past two months.
    • The overlap section turns into black with a widget upon a window which Created by Win32 plugin DLL
      3rd Party Software • qwidget win32 overlap section • • vimelo  

      1
      0
      Votes
      1
      Posts
      399
      Views

      No one has replied

    • [solved] How to create a service with Qt and sc.exe under windows 7
      General and Desktop • qprocess win32 windows service shellexecute • • stephane78  

      11
      0
      Votes
      11
      Posts
      3943
      Views

      @koahnig it is out of subject on this forum, but I tested with the win32 function Shellexecute and "runas" as second parameter instead of qprocess and it created my service.so I mark this subject solved.thanks.
    • Linking Error using WINAPI-Function "DisableProcessWindowsGhosting()" from User32.dll
      General and Desktop • qtcreator mingw libraries win32 • • JanGeorgi  

      2
      0
      Votes
      2
      Posts
      1727
      Views

      This function is only for desktop applications. It may not exist for embedded systems. I would check if the function exist before doing anything else. If you list the exported functions from USER32 and don't see it then this explains the linker error.
    • Qt main event loop in Win32 Dll
      General and Desktop • event loop win32 winmigrate qmfcapp • • MaxW  

      1
      0
      Votes
      1
      Posts
      870
      Views

      No one has replied