I ran ./configure with -static -static-runtime -target xp. Unfortuantely my application does not run when I use QMediaPlayer on Windows XP. There is a missing reference to MF.dll which aborts the program start with a critical error message.
Pretty much this bug: https://bugreports.qt.io/browse/QTBUG-42460
Does anyone has figured out how to clean the reference to MF.dll? My guess was -no-wmf-backend, but the person who reported the bug said it's not enough. Before I recompile another 8 hours, I would like to have some clarification, thank you.
In config.tests before building Qt and running configure, there is a file called evr. Let it fail to avoid MF.dll dependency on Windows XP. QMediaPlayer will just work fine then.
Related
I want to build Qt 5.4.1 form source with MSVC2013 under windows 10 condition.
However, when I do the configuration, it just stopped without any errors.
I downloaded qt-everywhere-enterprise-src-5.4.1.zip and unzip it.
I installed active perl ver5.2.6, python 3.7.6, ruby devkit 2.7.6 and added there path to environment variables.
And then, in the Developer Command Prompt for VS2013, typed
path_of_src\qtbase\configure -platform win32-msvc2013
then it shows me the following messages and just stopped configuration.
+ cd qtbase
+ ...\qt-everywhere-enterprise-src-5.4.1\qtbase\configure.bat -top-level -platform win32-msvc2013
Qt: Untested Windows version 10.0 detected!
This is the Qt
(and I even did not put -top-level option)
I think some words and process should be followed after 'This is the Qt' sentence, but there wasn't.
Also it doesn't show me any error messages so I'm stuck in a labyrinth now...
Please let me know if you have any idea or need further information.
Thank you in advance.
Best wishes,
JESuh
Last time I used Qt Creator, it was still using gdb (not lldb) and it's working just fine before upgrading to El Capitan.
Has anybody managed to debug using Qt Creator 3.4.2 and Qt 5.5.0 on El Capitan?
Can someone please give me any pointers of how to set it up correctly since mine does not even stop at breakpoint?
I had the same issue and clicking on Enable QML in the Debugger Settings (from Projects > Execution parameters) seems to make the breaking points work again.
I ignore why and it complains about not being able to connect to the QML debug process after the end of the debugging session, but at least the breaking points work now.
I also have lldb and not gdb.
QT5.6.2 with macOS 10.11.6, after a totally reinstall I finally solved it, my solution:
in terminal,brew uninstal qt(maybe this is the problem)
run MaintenanceTool.app,see Uninstall and Reinstall QtSDK on Mac system
reboot
reinstall Qt
This is just a blind guess, i had the same problem. I solved it with the following configuration the .pro:
CONFIG -= app_bundle
Looks like debugging doesn't work inside a bundle.
I am not able to run programs from Qt Creator, I am always getting error:
Starting C:\path\to\executable\program.exe...
Failed to start program. Path or permissions wrong?
C:\path\to\executable\program.exe exited with code -1
It happened after I built Qt statically. What I did:
Installed Qt 5.2.0 with MinGW from official site (including source component), then installed Python 2.7.6 and Perl. Then built Qt statically from path\to\qt\5.2.0\Src and it showed no errors. After this everything was fine. But when I added new path to qmake.exe (in Qt Versions tab, Build & Run Options section) and added new Kit (Kits tab) with this version I started getting this error. Moreover, now all .exe files have yellow shield near the icon in the Explorer (no matter they were built statically or not). It means that they use administrative privileges, but before I added new Kit executables had no yellow shield! For statically built programs it is fine that Creator can't run them because of administrative privileges that the use, but what happened to dynamically linked programs? I didn't touch any other settings except for adding new Kit.
Edit:
I am using MinGW on Windows 8.1,
qt was configured with this line:
configure.exe -release -opensource -c++11 -static -no-opengl -no-angle -no-vcproj -platform win32-g++ -nomake examples -nomake tests
I seem to have exactly the same problem as iamnp.
In my case, this is an application that compiles and runs smoothly on Windows 7 with Qt 4.8. Adding to the issue is that I'm switching both operating system (Windows 8.1) and Qt version (Qt 5.2) at the same time. But, I wouldn't be surprised that I and iamnp are actually not the only people having this issue.
I have tried the solution of Guilherme (i.e. run QT Creator as administrator), but this didn't resolve the problem.
If somebody has some other idea on what I should try, let me know. In the meantime, I'll try to test this in a minimal application to see what happens.
I just updated my Qt to 4.8.3, because the program built from older version is not compatible to the new framework.
So I have to upgrade.
This process was frustrating and time consuming. So many problems came out.
I download Qt from this url:
http://qt-project.org/downloads
At beginning, I installed the MinGW one (I'm not a fan of MSVC).
I tried the newest ( I think it's 4.6) version of MinGW and order version (4.4).
However, after I installed MinGW and tried to install Qt 4.8.3, during the process, the following message shows up:
There is a problem with your MinGW installation:
The installer could not find a valid C:\MinGW\include\w32api.h (Only versions with W32API 3.13 are supported)
Do you still want to continue? (Your installation may not work)
The 4.6 version does have this w32api.h file, I don't know what's going on. And I have trouble finding MinGW 4.4 with this head file.
I decide to ignore this warning and continue to install Qt and Qt creator. After that,
I opened my current project, configure it (why the configuration become so complex...), I tried to build it.
Then the following message shows up because some external lib I used requires Exception Handling:
exception handling disabled, use -fexceptions to enable
And I don't know how to enable the it.
I tried to add -fexceptions flag in QMAKE_CXXFLAGS but it doesn't work.
By the way, I tried the VC version of Qt too, but I used the MinGW before and the VC compiler is quite different, if I use VC version, it will take a lot of time to make it compilable by VC compiler.
Does anyone know how to install Qt 4.8.3 on Windows? my project works fine before, now I just want to compile it successfully.......
These are not the only problem.
I updated the Qt on Mac machine too, it is easier to have the compiler work since it's unix base.
However, I used QtWebkit lib in my project and obviously, they changed this lib and it's not compatible to order version.
I can compile my project on Mac, however, every time I run it, following massage shows up and the program stopped.
dyld: Symbol not found: _OBJC_CLASS_$_CALayerHost Referenced from:
/Library/Frameworks/QtWebKit.framework/Versions/4/QtWebKit Expected
in:
/System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
The program has unexpectedly finished.
Does any one know how to solve this QtWebKit problem? I'll really appreciate.
I remembered that when Qt is under nokia, it's so easy to install and use, the Qt SDK is perfect.
I really hate the change made after it was bought by digia.........
I found solutions of my first two problems:
for the first problem, as I described, download the MinGW provided by Nokia Qt
ftp.qt.nokia.com/misc/MinGW-gcc440_1.zip [ftp.qt.nokia.com]
Tried several versions of MinGW 4.4, I think this is the only one works.
About the second problem, add following configure in the project file:
CONFIG += exceptions
Now the QWebKit problem is only one unsolved.
Is it all relevant that your include directory for MinGW has two "i's" in it or was that a typographic error when posted on SO? See:
The installer could not find a valid C:\MinGW\iinclude\w32api.h
I am trying to install MacVim in my Macbook Pro from Homebrew. However it "got stuck" at
xcodebuild -project MacVim/Macvim.xcodeproj ARCHS="x86_64" ONLY_ACTIVE_ARCHS="NO"
for nearly 6 hours. Last time I remember building from source that took me so long was the Open Office.
By the way. I am running Lion. I know there is no stable version of MacVim for Lion yet but I guess this shouldn't be a problem building it. I have Xcode 4 installed with Command Line Tools.
Am I missing something?
Thanks in Advance.
Problem solved. What happened is that I installed the command line tools for xcode but its path was not properly configured. For example, to compile MacVim it required xcodebuild to run. The only reference for xcodebuild I found in my system was in /usr/bin so I set the path to that location. Even though xcodebuild was being found by make, it would get stuck forever and not returning any erros (weird). I tried to build other application purely based on gcc and it got stuck with no errors too. Finaly I found the correct path for command-line tools for Xcode 4.3. The code to set it up is:
sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
source: http://jeffreyearly.com/2012/02/28/broken-command-line-tools-clt-in-xcode-4-3/