SET QSG_VISUALIZE=batches<br />
or<br />
SET QSG_VISUALIZE=clip<br />
or<br />
SET QSG_VISUALIZE=changes<br />
or<br />
SET QSG_VISUALIZE=overdraw</p>
<p>qmlviewer test.qml<br />
When changing configure settings, it's sometimes necessary to perform complete clean rebuild. The best way how to do that is download completely new source package.
nmake clean or nmake distclean unfortunately didn't work for 100%
It's necessary to have installed Ruby, Python and Perl
So, one more attempt. Previous articles (part1, part2) mentioned possible solutions to fix crash insinde the QTreeWidget and QAccessibleTableCell.
Unfortunately, deselecting current item still doesn't fix all issues. The problem with deselection is that it's not handled correctly via QAccessibleTableCell:
If current index isn't valid, QAccessible doesn't correctly update currect QAccessibleTableCell object which caused all this evil crashes.
So there are two ways how to fix it. One is to manually set QAccessibleTableCell but I didn't find a way how to do that. The second way is to disable QAccessible for Property editor. Unfortunately it's not an easy task. In QAccessible exists method setActive:
QAccessible::setActive(false)
But this method works only with AccessibleObserver class but not with QPlatformAcessibility which handles real QAcessible::isActive result. Because of this it's necessary to update setActive method in file qacessible.cpp inside the Qt.
Original method:
</p>
<p>void QAccessible::setActive(bool active)<br />
{<br />
for(int i = 0; i < qAccessibleActivationObservers()->count() ;++i)<br />
qAccessibleActivationObservers()->at(i)->accessibilityActiveChanged(active);<br />
}</p>
<p>
In case you will find better way how to turn off accessibility, please let me know.
But there is still one more problem. Occasionally OS X decides to switch accessible back on:
And this is probably the reason why everything works ok on older OS X but not on 10.10. Because OS X 10.10 randomly turns accessible on which causes this crash. Accessible is usually turned on when opening some modal dialog.
This explains why opening an empty dialog increased the probability to crash the application. The only solution I have found is to disable QAccessible every time the PropertyEditor is cleared up.
As mentioned in the first part of this article, the workaround with focus unfortunately didn't work. In some cases application is still crashing. So after next hours of debugging and unsuccessful consulting the problem on stack overflow I probably found a the core reason of this bug and the solution too.
The core of this problem doesn't lie in the QTreeModel, but in Qt implementation of Cocoa Accessible. The problem is that although the PropertyTree is correctly cleared, there is object QAccessibleTableCell which isn't correctly updated after
clear()
.
This means that although the PropertyTree and TreeWidget is empty, the QAccessibleTableCell object still holds m_index variable to invalid element. And when
NSAcessibleEntryPointrAttributeNames
is executed, m_index is translated to QTreeWidget element pointer and accessed. And this means that application completely crashes.
The solution is pretty simple. Together with property editor clear set also current index and selected index to NULL.
To be more specific, problem occurs only in very specific circumstances. It's in situation, when application is compiled as console-app and it's compiled on Mac OS X version older than 10.9:
CONFIG -= gui<br />
CONFIG -= console<br />
and when you're using QEventLoop::exec in mode processing all events except user events (QEventLoop::ExcludeUserInputEvents):
</p>
<p>//it's only demonstration, not full code...<br />
QNetworkAccessManager manager; ...<br />
QNetworkRequest request; ...<br />
QNetworkReply *reply = manager->post(request,arData);<br />
...</p>
<p>eventLoop.exec(QEventLoop::ExcludeUserInputEvents);<br />
In this situation, application hangs-up. When the application is compiled with GUI mode or when application is compiled on Linux/Windows (no matter if gui or console), everything works find. To fix this problem, it's necessary to implement hack similar to this (simplified version):
This is very interesting crash and I think it should be considered as Qt bug. This problem arise only under very special circumstances. But one after another.
You will identify this problem when your application stopped/exited immediately after the start without any visible error message. It looks like the application isn't executed at all. When you check application log (Computer -> manage -> Event viewer -> Windows logs -> Application), you will see Error logs:
The most interesting part of this log is crash location: ntdll.dll
At first sight it seems like some problem inside the windows. But the opposite is true, the problem (as almost always) is inside your app ;-).
As the next step, you can try to debug this executable via Visual Studio to see what happens inside. Simply open executable as project together with .pdb files and execute it. Now you can see that application is correctly executed but crashes as soon as it touches Qt library. The location of crash is inside ntdll.dll in RtlHeapFree() function.
So the problem is inside the Qt, right? Almost true, but not for the 100%. When I tried to run this application on computers of my colleagues, everything works ok. So why the application doesn't work on my computer too?
Resolution
The problem is in new Qt5 plugin system. Besides the common Qt5*.dll files which are loaded immediately after the application start, Qt5 is also loading plugins/platform-plugins dynamically when the application is executed. To locate this plugins, Qt5 uses following method to identify directories where to search for plugins:
For some strange reason this library returns as first directory path where Qt5 libraries were compiled and after that location based on the executable. So if your Qt5 path is C:\Qt5, this will be the first path where all plugins are searched for, no matter if the correct version of plugin is located in APP\plugins or APP\platforms. **I think this is serious bug in Qt5**.
Where is the problem?
And here we're getting to the core of the whole problem.
**If application is compiled on computer with one compiler and used on second computer which contains the same path to which original computer has installed Qt, the application will load all plugins from your folder instead of itself folder.**
In case your computer will contain different version of Qt, different compiler or different platform, application loads incorrect libraries and crashes. Completely, silently and without easy way to determine what's wrong.
Solution?
The solution is simple, but it isn't achievable from outside of the Qt library. It would be necessary to Qt as first tried to load libraries from application directory. And only if no plugins were found in application directory, the application would try to search for plugins in Qt directory.
Qt change solution
The simplest way how to fix this issue inside the Qt library would be to rename/update appendApplicationPathToLibraryPaths function to prependApplicationPathToLibraryPaths and change
Unfortunately it isn't possible to simply change this behavior from your app. All of these operations happen directly in QCoreApplication constructor so if you try to change it after, it's too late.
The temporary solution before this problem will be resolved is to reinitialize library paths before QCoreApplication is initialized. It's necessary to clean libray paths, compute new paths and re-initialize QCoreApplication::libraryPaths before QCoreApplication object is initialized. This can be done in main.cpp of your application before you will create QApplication/QCoreApplication object.
For debugging purposes it's a good idea to keep .pdb files also for release version of your libraries. Unfortunately in default configuration Qt library doesn't generate .pdb files. It's a not big deal, create .pdb files for release version it's pretty simple.
1) Add compilation flags to .pro file
The easiest way how to create pdb files is pass /Zi switch to compiler and /Debug to linker.
As pointed out in this QtProject article, another way is to edit mkspec so any future compilations will have this option turned on. It's necessary to modify correct mkspec file, for example
After some google-searching I found out that the problem is in core of our application. When subclassing Qt QApplication, it's necessary to pass argc with reference, not by value. So after adding one little &, everything works like charm!
My VS2010 on every build always recreate all .moc files and associated .cpp files. Problem was in incredibuild clausule during compilation of my Qt libraries.
Although qmake added all these incredibuild defines to my VS project, Incredibuild still doesn't compile it in parallel so it was totally useless. The most simply way is edit incredibuild_xge.prf and turn-off it.
[caption id="" align="aligncenter" width="637"] The procedure entry point GetTickCount64 could not be located in the dynamic link library KERNEL32.dll[/caption]
Today we received report from one of our customers about problem with our ORM Designer on WindowsXP - 32bit. Our latest version returns following error:
The procedure entry point GetTickCount64 could not be located in the dynamic link library KERNEL32.dll
**The problem is that GetTickCount64 doesn't exists in XP system**.
**Solution:**
It's necessary to compile your application (and any library which uses GetTickCount64) with correct **WINVER** and **_WIN32_WINNT **defines value. List of WINVER values for all Windows version can be found here.
You can define these values in your resource.h file:
#define WINVER 0x0501
#define _WIN32_WINNT 0x0501
or add it to a project property -> C/C++ -> Preprocessor -> Preprocessor Definitions:
**Qt Solution:**
If you want to define these values automatically in Qt project, add following lines to your .pro file:
#Windows XP compatability
DEFINES += "WINVER=0x0501"
DEFINES += "_WIN32_WINNT=0x0501"
"OrmDesigner2" can't be opened because it is from an unidentified developer.<br />
[caption id="" align="aligncenter" width="435"] MacOS unidentified developer in ORM Designer[/caption]
Solution
To solve this error message it's necessary to do following steps:
Register in Apple developer program and pay $99 per year
Download and install developer certificate
Sign whole application
Test it!
1) Register on Developer.apple.com
You need to create registration here: https://developer.apple.com/. It's necessary to fill info about contact person and company. After that, your registration will be reviewed by apple team and if everything will be OK, your registration will be approved.
**2) Use Apple site to generate certificates**
Open https://developer.apple.com/account/overview.action ,choose **Certificates, ** Click Add. Than select certificate parameters suitable for your need. In my case it was **Mac Development** and ** Developer ID.**
Now you need to install this certificate to your developer machine. Simply double-click on certificate and let system to import it. You can check that certificate is imported in **Go->Utilities->Keychain Access->login. **Now search for "Developer ID Application: XXXX"
**Note: **In my case when I transfer certificate to several developer machines I need to migrate also other Apple certificates. Without that my certificate wasn't a valid.
**3) Sign your application**
Now you need to sign your application including all plugins and frameworks inside app bundle. **After you sing your app, you can't do any changes in the bundle.** So as first run your deploy as usual and as **last step **do app singing.
For ORM Designer sign script looks like this:
#go to deploy directory<br />cd$StarkDeploy.directory$/deploy</p>
<p>#sign app<br />
codesign --force --verify --verbose --sign "Developer ID Application: Inventic s.r.o." ./OrmDesigner2.app</p>
<p>#sign all *.dylib files<br />
find OrmDesigner2.app -name *.dylib | xargs -I $ codesign --force --verify --verbose --sign "Developer ID Application: Inventic s.r.o." $</p>
<p>#sign all Qt* frameworks<br />
find OrmDesigner2.app -name Qt* -type f | xargs -I $ codesign --force --verify --verbose --sign "Developer ID Application: Inventic s.r.o." $<br />
4) Test it!
As last step it's necessary to test that sign process was successful. As first you can try following command line to validate it:
Now when you checked that App is correctly signed, it's time to try it on clean computer where no security policy changes was made. Upload your app and execute it.
If you don't see annoying screen "Can't execute application from unidentified developer", **you win** ;-).
Standard Qt application on retina display looks ugly. Fuzzy fonts and images. This is how ORM Designer originaly looks on Retina:
[caption id="" align="aligncenter" width="2880"] ORM Designer on Retina before optimizations[/caption]
Improve font autoscaling
First step how to improve Qt application on retina is by adding following definise to Info.plist
NSPrincipalClass<br />
NSApplication<br />
[caption id="" align="alignnone" width="405"] How to update Info.plist[/caption]
If you're updating existing application, it's necessary to copy application to different location after Info.plist update. MacOS cache all .plist files and without that update will not be apply.
After applying this fix, this is how application looks:
[caption id="" align="aligncenter" width="2880"] How ORM Designer looks after fix[/caption]
To add DBUS to Qt compilation, add following switch
./configure -opensource -dbus ....<br />
If you get following error:
The QtDBus module cannot be enabled because libdbus-1 version 0.93 was not found.<br />
Turn on verbose messaging (-v) to ./configure to see the final report.<br />
If you believe this message is in error you may use the continue<br />
switch (-continue) to ./configure to continue.<br />
It's necessary to install libsbus:
sudo apt-get install libdbus-1-3<br />
Reading package lists... Done<br />
Building dependency tree<br />
Reading state information... Done<br />
libdbus-1-3 is already the newest version.<br />
Integration of Google breakpad on any platform is really challenge. I didn't figure out how to do it by using recommended ways. So I did it my way ;-)
Create your own Qt project
As first thing I did when integrating Qt and Breakpad is creation of my own .pri file. I manually add all required files from Breakpad one-by-one, starting with src/platform/exception_handler continuing with all files included in previous ones. The complete .pri file you will find at end of this post.
After that I created simple CCrashHandler (inspired by qt-breakpad project) class which register exception handler. It's necessary to implement this handler for each platform separately because each platform have different parameters in google_breakpad::ExceptionHandler() constructor. CrashHandler source code you can find also at end of this post.
#get breakpad latest version<br />
svn checkout http://google-breakpad.googlecode.com/svn/trunk/ google-breakpad-read-only</p>
<p>#compile all breakpad tools for extracting symbol files<br />
./configure<br />
make<br />
sudo make install</p>
<p>#when compilation is ready, you should have installed file dump_syms from original directory /src/tools/linux/dump_syms in your /usr/bin<br />
dump_syms<br />
Generate symbol file and test debug info
Now how to generate and use symbol file:
#generate .sym file<br />
dump_syms ./Application > Application.sym</p>
<p>#store sym file in the correct location<br />
#this step is necessary. Without that minidump_stackwalk tool doesn't work</p>
<p>head -n1 Application.sym<br />
#Result: MODULE Linux x86_64 6EDC6ACDB282125843FD59DA9C81BD830 Application</p>
<p>mkdir -p ./symbols/Application/6EDC6ACDB282125843FD59DA9C81BD830<br />
mv Application.sym ./symbols/Application/6EDC6ACDB282125843FD59DA9C81BD830</p>
<p>#show stack with using minidump_stackwalk tool<br />
minidump_stackwalk ./crash.dmp ./symbols<br />
Result of minidump_stackwalk tool can look like this:
This command correctly creates folder Application/uuid in path symbol-storage and copy generated .sym file inside.
Using Breakpad on MacOS:
To integrate Breakpad and Qt on MacOS I used the same article as for Linux because I'm using gcc and linux-like development toolchain. For native XCode integration you have to probably use this article.
Notes MacOS
GCC 4.6.3
Qt creator toolchain
Mac OS 10.7.3 64bit
Don't using any of XCode tool chaing
Do almost all steps like on Linux integration. There is one exception, because you can't compile Breakpad tools using linux-like configure&make. You have to build these tools with XCode.
Compile google_breakpad/src/tools/mac/dump_syms/dump_syms.xcodeproj with XCode
Before I managed to successfully compile dump_syms in XCode, I have to update Architectures Debug/Release to 64-bit Intel and BaseSDK to "Latest Mac OS X". I also fix all issues displayed in the left part of XCode window.
Next step is change compilation type from Debug to Release. After a short searching I found a way in "Schema->Edit schema->Build configuration".
To be honest, I was not sure what I did, but it worked ;-). Maybe there is some easier way how to compile dump_syms in xcode, but I don't know how. This was my first contact with XCode ;-).
The application is compiled to path "/Users/User/Library/Developer/Xcode/DerivedData/dump_syms-bjvr/Build/Products/Release/dump_syms". Now copy dump_syms to safe location from where you will use it.
Google breakpad under windows generates common .dmp files which can by simply load directly to VS
Generate symbol files and test debug info
You have to choices for Windows. First option is use standard .PDB and .DMP files mechanism in VS. Second is use the same way how you can did it for Linux and Mac.
**First way**: Let compiler generate .PDB file. Store this files and use them later in VS together with your crash dump.
**Second way**: Use dump_sys.exe. This file is located in the google breakpad directory tree: google-breakpad\src\tools\windows\binaries\dump_syms.exe .
The most amazing thing I found about dump_syms is their platform independence. If you correctly extract symbol file on each platform and store it in one location, you can analyze any crashdump on one location. No matter what is source platform, you will analyze .dmp file by using **minidump_stackwalk ./crash.dmp ./symbols**.
How to include CrashHandler directly to your project
This is what I get when I follow all includes from **.h** and **.cpp** files starting with exception_handler.h for all platforms. With small modification you can include it to your project and your application will be fully breakpad-able ;-).
And this is the minimal implementation of your new CrashHandler. My ownd crash handler is much more sophisticate to perform reporting, sending crash dump etc. But for purposes of this article this is what you need (And also I don't want to share my whole know-how here ;-)))
Today I encounter this error after applying **macdeployqt** to my application. There is a lot of questions about this topic on google but not very answers.
The most important thing is setup following variable.
export DYLD_PRINT_LIBRARIES=1<br />
Using this you will se which libraries are loaded during execution of your application. The interesting thing is, that I see loading a libraries from their original directories instead of Application.app. But when I temporary moved these libraries from their location, libraries begin to load from then bundle location.
The reason for my "QWidget: Must construct a QApplication before a QPaintDevice" was executing an older version of QTitanRibbon from shared libraries path instead of the newest one compiled directly to /usr/lib.
The second reason for this issue was caused by another path in "export DYLD_LIBRARY_PATH". It seems that application search for libraries first in DYLD_LIBRARY_PATH and after in paths from their inner records.
In this article I will show how to create DMG installer in reusable way. The most of things and ideas presented here are ideas from several articles mentioned on the end of this article.
1) As first step we need to create our DMG template with link to Applications.
2) Next we have to modify the visual representation of DMG file.
3) Next we store created DMG as template
4) Now mount copied template as directory, fill DMG with real files
5) Detach mounted DMG, pack DMG
6) Distribute app ;-)
More detailed info about all these steps you will find in articles mentioned below. Here is a short script I wrote for three-phase deploying (1) create template, 2) pack template, 3)fill template with real data and compress it)
In first part of this article I introduced a manual way how to deploy MacOS application. Because doing all these stuff manually was a lot of hand work, Qt introduced small tool called **macdeployqt**.
This utility looks very good, but also have some drawbacks. As first I will show you how utility works:
macdeployqt Application.app<br />
That's all ;-). This command should do all the hard work for you. But in some cases it didn't.
ERROR: no file at "/usr/lib/libboost_iostreams.dylib"<br />
ERROR: no file at "/usr/lib/libboost_filesystem.dylib"<br />
ERROR: no file at "/usr/lib/libboost_system.dylib"<br />
ERROR: no file at "/usr/lib/libboost_thread.dylib"<br />
ERROR: no file at "/usr/lib/libboost_date_time.dylib"<br />
ERROR: no file at "/usr/lib/libboost_regex.dylib"<br />
ERROR: no file at "/usr/lib/libboost_chrono.dylib"<br />
ERROR: no file at "/usr/lib/libyaml-cpp.0.2.dylib"<br />
The problem is that libraries mentioned in the previous list doesn't has included absolute path. If you inspecit this library, you will se this:
otool -L libboost_regex.dylib<br />
libboost_regex.dylib:<br />
libboost_regex.dylib (compatibility version 0.0.0, current version 0.0.0)<br />
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 52.0.0)<br />
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)<br />
And this is the problem. Inner path in library is only filename without full path, so when we link library with our executable, our executable also has only relative path. And when macdeployqt try to find this library, automatically try to search in /usr/lib.
One possible solution is copy libraries to /usr/lib. Second solution is update paths in libraries to absolute paths. The third way is fix library linker to include full paths in libraries.
I found out that the simplies way how to fix it is call install_name_tool after library compilation and fix the path (don't forget to update library paths inside other library paths!)
So, now when we have updated all libraries, we can try to create application bundle again
macdeployqt AtomixDevelopment.app/<br />
And if we did everything correctly, now we should have a working app ;-).
Troubleshooting
In some cases you can get error "Permission defined", "Bad file descriptor" or other similar errors when using macdeployqt.
ERROR: "install_name_tool: can't open input file: OrmDesigner2.app/Contents/Frameworks//libssl.1.0.0.dylib for writing (Permission denied)<br />
install_name_tool: can't lseek to offset: 0 in file: OrmDesigner2.app/Contents/Frameworks//libssl.1.0.0.dylib for writing (Bad file descriptor)<br />
install_name_tool: can't write new headers in file: OrmDesigner2.app/Contents/Frameworks//libssl.1.0.0.dylib (Bad file descriptor)<br />
install_name_tool: can't close written on input file: OrmDesigner2.app/Contents/Frameworks//libssl.1.0.0.dylib (Bad file descriptor)<br />
The reason is insufficient permissions for modifying copied libraries. Simple execute
sudo macdeployqt<br />
and everything should work ok. Another workaround for this issue is using newer version of Qt. I figured out that on MacOS I wrongly use Qt 4.7.4. When I correct this to version Qt 4.8.2 this issue was solved.
DMG file
If you want to create simply DMG file, simply call macdeployqt with param --dmg. But this dmg doesn't look so good:
This will need more investigation how to make DMG files nicer ;-).
Notes
Everytime you run macdeployqt run it on clean folder. The best way is to call rm -rf Application, compile app and than run macdeployqt
Notes to bug in macdeployqt
The problem is caused by invalid permissions. Copied libraries have the same permissions like in the source location. There are three different solutions:
Use sudo and execute macdeployqt with root permissions
Update external libraries permissions to rw, so also copies will have a correct permissions
Update macdeployqt script. In file shared.cpp on line 91 is method copyFilePrintStatus. Here is a necessary to update copied files permissions to correct rw
In my case the problem was in file liblzma.5.dylib
Frameworks/liblzma.5.dylib is not writable (Permission denied)<br />
The first usefull command for tracking dependencies between your application and other shared libraries is otool:
#path to executable, not .App directory!<br />
otool -L Application.app/Contents/MacOS/AppExecutable<br />
Now we can see paths to our libraries. The bad news is that MacOS doesn't have any -RPATH and $ORIGIN. The good news is utility install_name_tool and variable @executable_path which works similar like $ORIGIN. Note: For newer versions of MacOS there are more variables like @executable_path. On version 10.4 was introduced @loader_path and on version 10.5 apple introduce @rpath variable.
The step-by-step solution
As first step it's necessary to upload all dependent libraries directly to the Application.app/Contents/MacOS/. For list all required files use otool:
cd Application.app/Contents/MacOS<br />
otool -L AppExecutable<br />
When we have copied all libraries, we need to change paths **for** and **in** all libraries.
Here is example how to set libxml2 library. As first step we will check how is library referred.
$user otool -L AtomixDevelopment</p>
<p>AtomixDevelopment:<br />
libboost_iostreams.dylib (compatibility version 0.0.0, current version 0.0.0)<br />
libboost_filesystem.dylib (compatibility version 0.0.0, current version 0.0.0)<br />
/Users/User/dev/SharedLibraries/libxml/lib/libxml2.2.dylib (compatibility version 10.0.0, current version 10.8.0)<br />
/Users/User/dev/SharedLibraries/libxslt/lib/libxslt.1.dylib (compatibility version 3.0.0, current version 3.26.0)<br />
/Users/User/dev/SharedLibraries/libxslt/lib/libexslt.0.dylib (compatibility version 9.0.0, current version 9.15.0)<br />
And Library:
User$ otool -L libxml2.2.dylib<br />
libxml2.2.dylib:<br />
/Users/User/dev/SharedLibraries/libxml/lib/libxml2.2.dylib (compatibility version 10.0.0, current version 10.8.0)<br />
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)<br />
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)<br />
/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)<br />
When we checked libxml2.2.dylib library with otool, we can see that library has hardocoded our development path. This isn't good ;-). So we now change this value to path relative to the executable and again verify this inner path.
install_name_tool -id "@loader_path/libxml2.2.dylib" libxml2.2.dylib<br />
otool -L libxml2.2.dylib<br />
libxml2.2.dylib:<br />
@loader_path/libxml2.2.dylib (compatibility version 10.0.0, current version 10.8.0)<br />
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)<br />
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)<br />
/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)<br />
As you can see, now is path (first line) set up to reffer @loader_path/libxml2.2.dylib. It's correct now. As second step we have to update path in our executable, because also there is path hardcoded to our library repository.
install_name_tool -change "/Users/User/dev/ExternalLibraries/../SharedLibraries/libxml/lib/libxml2.2.dylib" "@loader_path/libxml2.2.dylib" AtomixDevelopment</p>
<p>otool -L AtomixDevelopment<br />
AtomixDevelopment:<br />
libboost_iostreams.dylib (compatibility version 0.0.0, current version 0.0.0)<br />
libboost_filesystem.dylib (compatibility version 0.0.0, current version 0.0.0)<br />
@loader_path/libxml2.2.dylib (compatibility version 10.0.0, current version 10.8.0)<br />
...<br />
So, now we have changed also path in our executable. And now we need to do all these steps for all libraries..... ;-).
Notes
To follow the MacOS application convention it's better to place libraries to folder Application.app/Contents/Frameworks. Here is a directory schema for Qt example application plugAndPaint.
Today I encountered another issue when compiling my Qt application http://www.orm-designer.com/ under Linux. The size of final executable was about 400MB.
The first thought was that there is some static libraries compiled to application. But the problem was elsewhere.
Unlike to Windows compilation where linker creates .exe and .pdb file, linux linker creates only one final file. So this file includes also lot of additional symbols useful for debugging and post-mortem bugs finding. But it is not so usefull for distribution your application. To strip all these symbols, use following command
strip --strip-unneeded /path/to/application<br />
Strip command have a lot of switches, but after a short testing it seems that the results are the same. Maybe I'm doing something wrong or simply my executable doesn't contain any additional infos for stripping.
**I found solution also for the problem with executing application form in-app directory!!, Look to text bellow.** Warning: This solution has one big disadvantage ;-(. It's necessary to execute application only from app-dir. In other cases system doesn't find required libraries. The solution could be run patchelf on the client computer with final installation path
I read a lot of articles about deploying applications but all of the suggested methods was impractical, too complex or unusable. Here is a list of them:
Using qt.conf in Qt resource or application dir. Usefull for Qt libraries, but not third party libraries
Installing Qt and third-party libraries in one of the system library path. This method need root permission for app users
Using -rpath to specify predetermined path. This method requires the users have this directory and have the full access to this directory
Another solution, the simplest one
I'm not sure why this solution isn't mentioned in Qt forums or anywhere else. Maybe this solution isn't so clean and perfect for Linux gurus, but it's perfect for me.
The solution is in simply changing the search path in already compiled application to "." (current directory) **current application location by using $ORIGIN variable**, so application will search all libraries in application directory first. It's simple, it's clean. All libraries distributed with application will be isolated in application directory and app-loader will not load any other library by mistake.
**Updated**: The keyword $ORIGIN do the trick, that you can run application from anywhere on your computer. $ORIGIN is absolute path to your executable.
And how to do this change? As first, you need to download small utility called PatchELF. With this application you can change -rpath in app to anything you need.
In file included from /usr/include/glib-2.0/glib/gasyncqueue.h:34:0,<br />
from /usr/include/glib-2.0/glib.h:34,<br />
from /usr/include/glib-2.0/gobject/gbinding.h:30,<br />
from /usr/include/glib-2.0/glib-object.h:25,<br />
from /usr/include/glib-2.0/gio/gioenums.h:30,<br />
from /usr/include/glib-2.0/gio/giotypes.h:30,<br />
from /usr/include/glib-2.0/gio/gio.h:28,<br />
from wtf/gobject/GOwnPtr.cpp:24:<br />
/usr/include/glib-2.0/glib/gthread.h:51:16: error: ‘union’ tag used in naming ‘struct _GMutex’ [-fpermissive]<br />
/usr/include/glib-2.0/glib/gthread.h:58:7: error: ‘union’ tag used in naming ‘struct _GMutex’ [-fpermissive]<br />
make[2]: ***[.obj/release-static/GOwnPtr.o] Error 1<br />
make[2]: Leaving directory `/home/honza/qt-everywhere-opensource-src-4.8.2/src/3rdparty/webkit/Source/JavaScriptCore'<br />
make[1]: *** [sub-JavaScriptCore-JavaScriptCore-pro-make_default-ordered] Error 2<br />
make[1]: Leaving directory `/home/honza/qt-everywhere-opensource-src-4.8.2/src/3rdparty/webkit/Source'<br />
make: ***[sub-webkit-make_default-ordered] Error 2<br />
the reason is because of incompatibility between Qt 4.8.2 and glib-2.0.
The solution is described in this (not commited) bug fix:
This error is caused by bug in **QMAKE_HOST** variable used in WebCore.pro file. This variable is tested to determine destination platform (x86 or x64).
This variable contains x86 value also on 64-bit builds instead of x86_64 value. This value is tested on the following line in a WebCore.pro file:
When you compile your project for MSVC 2010, .asm file isn't included. It's necessary to add win32-msvc2010 to this definition. So updated WebCore.pro for Qt 4.8 will look like this:
Next problem which I found during compilation is wrongly set QMAKE_TARGET.arg. For unspecified reason, when I compile 64bit library in 64bit system in 64bit VS command line, this variable has value x86 instead of x86_64.
The problem is in the qmake project.cpp file. QMAKE trying to determine 64/32 bit version based on the %PATH% configuration. Qmake search for VS-PATH\bin\amd64 of \bin\x86_amd64 string. Unfortunately there is a bug in concating searched string. This is how looks original project.cpp file at line 3177:
Because building Qt demos and examples is time consuming and sometime can't be correctly done because of missing sub-parts of Qt, it's good to remove it from main Qt build. To do this, pass following parameters to the ./configure script:
If your application using some externals dynamic libraries (called .dylib in MacOs system), you have to provide all these libraries. The simplest way is to provide these libraries into the Application.app directory.
Find out which libraries are used
Qt provide really useful tool called **"otool"** which serves to lots of purpose. One of them is to detect which shared libraries are required by our application. For this purpose otool has parameter -L. The usage is following:
otool -L ./Test1.app/Contents/MacOS/Test1<br />
Output could looks like this:
./Test1:<br />
libboost_iostreams.dylib (compatibility version 0.0.0, current version 0.0.0)<br />
libboost_filesystem.dylib (compatibility version 0.0.0, current version 0.0.0)<br />
libboost_system.dylib (compatibility version 0.0.0, current version 0.0.0)<br />
libboost_thread.dylib (compatibility version 0.0.0, current version 0.0.0)<br />
libboost_date_time.dylib (compatibility version 0.0.0, current version 0.0.0)<br />
libboost_regex.dylib (compatibility version 0.0.0, current version 0.0.0)<br />
/Users/dev/dev/SharedLibraries/libiconv/lib/libiconv.2.dylib (compatibility version 8.0.0, current version 8.0.0)<br />
/Users/dev/dev/ExternalLibraries/../SharedLibraries/libxml/lib/libxml2.2.dylib (compatibility version 10.0.0, current version 10.8.0)<br />
/Users/dev/dev/ExternalLibraries/../SharedLibraries/libxslt/lib/libxslt.1.dylib (compatibility version 3.0.0, current version 3.26.0)<br />
/Users/dev/dev/ExternalLibraries/../SharedLibraries/libxslt/lib/libexslt.0.dylib (compatibility version 9.0.0, current version 9.15.0)<br />
/Users/dev/dev/ExternalLibraries/yaml-cpp-0.2.5/build/libyaml-cpp.0.2.dylib (compatibility version 0.2.0, current version 0.2.5)<br />
QtGui.framework/Versions/4/QtGui (compatibility version 4.7.0, current version 4.7.0)<br />
QtCore.framework/Versions/4/QtCore (compatibility version 4.7.0, current version 4.7.0)<br />
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)<br />
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 625.0.0)<br />
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0)<br />
Output from "otool" is simmilar to linux tool "ldd".
The Mac Deployment Tool
Because manual copying and configuring all shared libraries to our application could be difficult, Qt have deployment tool which do all work for us. Tool is called "macdeployqt" and can be found in /Developer/Tools/Qt/macdeployqt.
**Note:** Every time when you call macdeployqt tool, project have to be build from scratch. But is sufficient when whole result directory is removed and linked again:
How to configure script for automatic run after login
Create .bash_profile file in your home directory.
nano ~/.bash_profile
And enter following content to the new created file:
# ~/.bash_profile# include .bashrc if it existsif[ -f ~/.bashrc ]; then
. ~/.bashrc
fi
How to configure new search path
If you want to have bin folder in your home directory, enter following code snippet to your .bash_profile file:
PATH=$PATH;/Users/thomas/bin
Conclusion & Note
It's possible that all of these task can be done in simpler way, or can't be done at all. All comments and tips are based on my current experience with my first Linux configuration in my life ;-)
As first, create some directory where you want to mount your shared drive
mkdir mnt
cd mnt
mkdir computer_d
mount -t smbfs //user_name:[email protected]/d computer_d
</div>
Conclusion & Note
It's possible that all of these task can be done in simpler way, or can't be done at all. All comments and tips are based on my current experience with my first MacOS configuration in my life ;-)
When you want to use different configurations for different platforms in your .pro file, it's necessary to correctly setup three variables: QMAKESPEC, QTDIR and PATH.
Here is how to configure for different platforms:
Microsoft Windows:
In SystemPropertes -> Enviroment variables add/update following values:
You can optionally use LANG variable to setup QtCreator language.
Old qt 3.0 guide: http://doc.trolltech.com/3.0/qmake-guide.html
How to configure enviroment: http://doc.qt.nokia.com/4.0/qmake-environment-reference.html
One of big disadvantage when creating Visual studio project from .pro files using qmake is missing support for hierachical folders. All files are stored in in four folders (filters) named "Source Files", "Header Files", "Generated Files" and "Form Files". When you have large project, this arrangement is really hard to use.
Simple Solution
qmake has undocumented setting parameter "flat". Using this switch, you can tell qmake to create filters in Visual studio dependent to directory structures of files. Only drawback of this solution is continuing sorting to "Source files","Header files",...
So result of this solution will look like this:
To achieve this behaviour, only thing what have to be done is add following line to your .pro file:
CONFIG -= flat
Final solution
But what to do when you want to have all files stored together in structure dependent on directory structure? Only solution which I found is update qmake project for myself. This update is simply and here is what is need to be done:
Add new method initHeaderAndSourceFiles to file msvc_vcproj.cpp and .h with following content
Command line for generating Visual studio project file from Qt .pro file.
qmake -tp vc test.pro
Missing moc_*.cpp file
When some of moc file isn't properly generated and getting following error:
c1xx : fatal error C1083: Cannot open source file: '.\debug\moc_xxx.cpp': No such file or directory
try following:
Select corresponding .h file (for moc_xxx.cpp select xxx.h) in a project tree and select **Compile** from context menu. If the file is marked as "up-to-date", try to change something in this file and repeat a compilation. If in the output window will be "up-to-date" again, you found a problem.
Use context menu on the corresponding .h file, select properties and edit "Configuration properties |Custom build steps|General|Outputs" to any value (add some char to the end of value), confirm change by Ok button and then return value back to original (remove added char). After that, compilation on correspond file will be successfully performed.
it’s because this file isn’t in /usr/include/glib-2.0, but in /usr/lib/glib-2.0. So you have to include also this /usr/lib path or copy file to include/glib-2.0
Hints and tips
How to create symbolic link to directory
create symbolic link using **ln -nsf /usr/include/gtk-2.0/gtk /usr/include/gtk **
Minimal required libraries
List of libraries required by Qt:
libfontconfig1-dev
libfreetype6-dev
libx11-dev
libxcursor-dev
libxext-dev
libxfixes-dev
libxft-dev
libxi-dev
libxrandr-dev
libxrender-dev
And other which are required by some modules of Qt:
To install all required on Linux, use following commands
Download VS 2008 distribution from download site. When 2008 distribution is downloaded, it’s necessary to reconfigure and rebuild it for VS 2005 using next steps.
Linux
Download linux/x11 distro from Qt page. Download 32/64bit distro package. Setup downloaded files as executables:
Second option is open projects.sln located in p:/Qt/4.7.1/ using Visual Studio IDE and compile it.
Linux
As first thing, use configure to setup Qt settings.
As next, run make to build a whole library
After a while when everything is compiled, use make install. This will install library to /usr/local/Trolltech/Qt-4.7.0
MacOS
Currently not tested, using default compilation.
How to compile application
When we have prepared Qt library, it’s time to compile our application.
MacOS
When using qmake without additional params, qmake generate xcode project from .pro instad makefile for g++. To generate makefile, use following params:
MacOS unidentified developer in ORM Designer[/caption]
ORM Designer on Retina before optimizations[/caption]
How to update Info.plist[/caption]
How ORM Designer looks after fix[/caption]
