- Qt 4.6 Download Mac Iso
- Qt 4.6 Download Mac Os
- Qt 4.6
- Qt 4.6 Download
- Qt 4.6 Download Mac Installer
- Qt 4.6 Download Mac Download
Our website provides a free download of Qt Linguist 4.6.0 for Mac. The Qt Linguist installer is commonly called QtLinguist-4.6.0-OSX.dmg. The following version: 4.6 is the most frequently downloaded one by the program users. The actual developer of this free software for Mac is Alessandro Portale. The program belongs to System Tools. The latest version of Qt Linguist is 4.6 on Mac Informer. It is a perfect match for the System Tools category. The app is developed by Alessandro Portale. Nov 29, 2017. The installation procedure is different on each Qt platform. Please follow the instructions for your platform from the following list. Download a free trial of the Qt framework, tools for desktop and embedded development, plus other enterprise add-ons. What's in Qt? Existing customers. Find them in the Qt account licensing portal or through the Maintenance tool in your Qt installation directory.
Home · All Classes · All Functions · Overviews |
[Deploying Qt Applications]
Beginning with Qt 4.5, a deployment tool is included that automates the prodecures described here.
This document describes how to create a bundle and how to make sure that the application will find the resources it needs at run-time. The sims 3 update 1.67 download mac. We demonstrate the procedures in terms of deploying the Plug & Paint application that is provided in Qt's examples directory.
The Bundle
On the Mac, a GUI application must be built and run from a bundle. A bundle is a directory structure that appears as a single entity when viewed in the Finder. A bundle for an application typcially contains the executable and all the resources it needs. See the image below:
The bundle provides many advantages to the user. One primary advantage is that, since it is a single entity, it allows for drag-and-drop installation. As a programmer you can access bundle information in your own code. This is specific to Mac OS X and beyond the scope of this document. More information about bundles is available on Apple's Developer Website.
A Qt command line application on Mac OS X works similar to a command line application on Unix and Windows. You probably don't want to run it in a bundle: Add this to your application's .pro:
This will tell qmake not to put the executable inside a bundle. Please refer to the X11 deployment documentation for information about how to deploy these 'bundle-less' applications.
Xcode
We will only concern ourselves with command-line tools here. While it is possible to use Xcode for this, Xcode has changed enough between each version that it makes it difficult to document it perfectly for each version. A future version of this document may include more information for using Xcode in the deployment process.
Static Linking
If you want to keep things simple by only having a few files to deploy, then you must build everything statically.
Building Qt Statically
Start by installing a static version of the Qt library. Remember that you will not be able to use plugins and you must build in all the image formats, SQL drivers, etc.
You can check the various options that are available by running configure -help.
Linking the Application to the Static Version of Qt
Once Qt is built statically, the next step is to regenerate the makefile and rebuild the application. First, we must go into the directory that contains the application:
Now run qmake to create a new makefile for the application, and do a clean build to create the statically linked executable:
You probably want to link against the release libraries, and you can specify this when invoking qmake. If you have Xcode Tools 1.5 or higher installed, you may want to take advantage of 'dead code stripping' to reduce the size of your binary even more. You can do this by passing LIBS+= -dead_strip to qmake in addition to the -config release parameter. This doesn't have as large an effect if you are using GCC 4, since Qt will then have function visibility hints built-in, but if you use GCC 3.3, it could make a difference.
Now, provided that everything compiled and linked without any errors, we should have a plugandpaint.app bundle that is ready for deployment. One easy way to check that the application really can be run stand-alone is to copy the bundle to a machine that doesn't have Qt or any Qt applications installed, and run the application on that machine.
El capitan mac download free. You can check what other libraries your application links to using the otool:
Here is what the output looks like for the static Plug & Paint:
For more information, see the Application Dependencies section.
If you see Qt libraries in the output, it probably means that you have both dynamic and static Qt libraries installed on your machine. The linker will always choose dynamic over static. There are two solutions: Either move your Qt dynamic libraries (.dylibs) away to another directory while you link the application and then move them back, or edit the Makefile and replace link lines for the Qt libraries with the absolute path to the static libraries. For example, replace
with
The Plug & Paint example consists of several components: The core application (Plug & Paint), and the Basic Tools and Extra Filters plugins. Since we cannot deploy plugins using the static linking approach, the bundle we have prepared so far is incomplete. The application will run, but the functionality will be disabled due to the missing plugins. To deploy plugin-based applications we should use the framework approach.
Frameworks
We have two challenges when deploying the Plug & Paint application using frameworks: The Qt runtime has to be correctly redistributed along with the application bundle, and the plugins have to be installed in the correct location so that the application can find them.
When distributing Qt with your application using frameworks, you have two options: You can either distribute Qt as a private framework within your application bundle, or you can distribute Qt as a standard framework (alternatively use the Qt frameworks in the installed binary). These two approaches are essentially the same. The latter option is good if you have many Qt applications and you would prefer to save memory. The former is good if you have Qt built in a special way, or want to make sure the framework is there. It just comes down to where you place the Qt frameworks.
Building Qt as Frameworks
We assume that you already have installed Qt as frameworks, which is the default when installing Qt, in the /path/to/Qt directory. For more information on how to build Qt, see the Installation documentation.
When installing, the identification name of the frameworks will also be set. The identification name is what the dynamic linker (dyld) uses to find the libraries for your application.
Linking the Application to Qt as Frameworks
After ensuring that Qt is built as frameworks, we can build the Plug & Paint application. First, we must go into the directory that contains the application:
Now run qmake to create a new makefile for the application, and do a clean build to create the dynamically linked executable:
This builds the core application, the following will build the plugins:
Now run the otool for the Qt frameworks, for example Qt Gui:
You will get the following output:
For the Qt frameworks, the first line (i.e. path/to/Qt/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.0.0, current version 4.0.1)) becomes the framework's identification name which is used by the dynamic linker (dyld).
But when you are deploying the application, your users may not have the Qt frameworks installed in the specified location. For that reason, you must either provide the frameworks in an agreed upon location, or store the frameworks in the bundle itself. Regardless of which solution you choose, you must make sure that the frameworks return the proper identification name for themselves, and that the application will look for these names. Luckily we can control this with the install_name_tool command-line tool.
The install_name_tool works in two modes, -id and -change. The -id mode is for libraries and frameworks, and allows us to specify a new identification name. We use the -change mode to change the paths in the application.
Let's test this out by copying the Qt frameworks into the Plug & Paint bundle. Looking at otool's output for the bundle, we can see that we must copy both the QtCore and QtGui frameworks into the bundle. We will assume that we are in the directory where we built the bundle.
First we create a Frameworks directory inside the bundle. This follows the Mac OS X application convention. We then copy the frameworks into the new directory. Since frameworks contain symbolic links, and we want to preserve them, we use the -R option.
Then we run install_name_tool to set the identification names for the frameworks. The first argument after -id is the new name, and the second argument is the framework which identification we wish to change. The text @executable_path is a special dyld variable telling dyld to start looking where the executable is located. The new names specifies that these frameworks will be located 'one directory up and over' in the Frameworks directory.
Now, the dynamic linker knows where to look for QtCore and QtGui. Then we must make the application aware of the library locations as well using install_name_tool's -change mode. This basically comes down to string replacement, to match the identification names that we set for the frameworks.
Finally, since the QtGui framework depends on QtCore, we must remember to change the reference for QtGui:
After all this we can run otool again and see that the application will look in the right locations.
Of course, the thing that makes the Plug & Paint example interesting are its plugins. The basic steps we need to follow with plugins are:
- Put the plugins inside the bundle
- Make sure that the plugins use the correct library using the install_name_tool
- Make sure that the application knows where to get the plugins
While we can put the plugins anywhere we want in the bundle, the best location to put them is under Contents/Plugins. When we built the Plug & Paint plugins, the DESTDIR variable in their .pro file put the plugins' .dylib files in a plugins subdirectory in the plugandpaint directory. So, in this example, all we need to do is move this directory:
Brother hl l2300d software mac. If we run otool on for example the Basic Tools plugin's .dylib file we get the following information.
Then we can see that the plugin links to the Qt frameworks it was built against. Since we want the plugins to use the framework in the application bundle we change them the same way as we did for the application. For example for the Basic Tools plugin:
We must also modify the code in tools/plugandpaint/mainwindow.cpp to cdUp() one directory since the plugins live in the bundle. Add the following code to the mainwindow.cpp file:
The additional code in tools/plugandpaint/mainwindow.cpp also enables us to view the plugins in the Finder, as shown to the left. We can also add plugins extending Qt, for example adding SQL drivers or image formats. We just need to follow the directory structure outlined in plugin documentation, and make sure they are included in the QCoreApplication::libraryPaths(). Let's quickly do this with the image formats, following the approach from above. Copy Qt's image format plugins into the bundle: https://productyellow850.weebly.com/watermark-for-mac-free-download.html. Use install_name_tool to link the plugins to the frameworks in the bundle: Then we update the source code in tools/plugandpaint/main.cpp to look for the new plugins. After constructing the QApplication, we add the following code: First, we tell the application to only look for plugins in this directory. In our case, this is what we want since we only want to look for the plugins that we distribute with the bundle. If we were part of a bigger Qt installation we could have used QCoreApplication::addLibraryPath() instead. |
Warning: When deploying plugins, and thus make changes to the source code, the default identification names are reset when rebuilding the application, and you must repeat the process of making your application link to the Qt frameworks in the bundle using install_name_tool.
Now you should be able to move the application to another Mac OS X machine and run it without Qt installed. Alternatively, you can move your frameworks that live outside of the bundle to another directory and see if the application still runs.
If you store the frameworks in another location than in the bundle, the technique of linking your application is similar; you must make sure that the application and the frameworks agree where to be looking for the Qt libraries as well as the plugins.
Creating the Application Package
When you are done linking your application to Qt, either statically or as frameworks, the application is ready to be distributed. Apple provides a fair bit of information about how to do this and instead of repeating it here, we recommend that you consult their software delivery documentation.
Although the process of deploying an application do have some pitfalls, once you know the various issues you can easily create packages that all your Mac OS X users will enjoy.
Application Dependencies
Qt Plugins
Your application may also depend on one or more Qt plugins, such as the JPEG image format plugin or a SQL driver plugin. Be sure to distribute any Qt plugins that you need with your application, and note that each type of plugin should be located within a specific subdirectory (such as imageformats or sqldrivers) within your distribution directory, as described below.
Note: If you are deploying an application that uses QtWebKit to display HTML pages from the World Wide Web, you should include all text codec plugins to support as many HTML encodings possible.
The search path for Qt plugins (as well as a few other paths) is hard-coded into the QtCore library. By default, the first plugin search path will be hard-coded as /path/to/Qt/plugins. But using pre-determined paths has certain disadvantages. For example, they may not exist on the target machine. For that reason you need to examine various alternatives to make sure that the Qt plugins are found:
- Using qt.conf. This is the recommended approach since it provides the most flexibility.
- Using QApplication::addLibraryPath() or QApplication::setLibraryPaths().
- Using a third party installation utility to change the hard-coded paths in the QtCore library.
The How to Create Qt Plugins document outlines the issues you need to pay attention to when building and deploying plugins for Qt applications.
Additional Libraries
You can check which libraries your application is linking against by using the otool tool. To use otool, all you need to do is to run it like this:
Unlike the deployment processes on X11 and Windows, compiler specific libraries rarely have to be redistributed along with your application. But since Qt can be configured, built, and installed in several ways on Mac OS X, there are also several ways to deploy applications. Seagate freeagent goflex mac driver download. Typically your goals help determine how you are going to deploy the application. The last sections describe a couple of things to keep in mind when you are deploying your application.
Mac OS X Version Dependencies
From Qt 4.6, Mac OS X 10.3 (Panther) is no longer supported. Qt 4.6 applications can be built and deployed on Mac OS X 10.4 (Tiger) and higher. This is achieved using weak linking. In weak linking, Qt tests whether a function added in a newer version of Mac OS X is available on the computer it is running on. This allows Qt to use newer features, when it runs on a newer version of OS X, while remaining compatible on the older versions.
For more information about cross development issues on Mac OS X, see Apple's Developer Website.
Since the linker is set to be compatible with all OS X versions, you must change the MACOSX_DEPLOYMENT_TARGET environment variable to get weak linking to work for your application. You can add:
to your .pro file, and qmake will take care of this for you.
For more information about C++ runtime environment, see Apple's Developer Website
Deploying Phonon Applications on Mac OS X
- If you build your Qt 4.6 Phonon application on OS X 10.4 (Tiger), it will run on OS X 10.4 and higher.
- If you are using Leopard but would like to build your application against Tiger, you can use:
Architecture Dependencies
The Qt for Mac OS X libraries, tools, and examples can be built 'universal' (i.e. they run natively on both Intel and PowerPC machines). This is accomplished by passing -universal on the configure line of the source package, and requires that you use GCC 4.0.x. On PowerPC hardware you will need to pass the universal SDK as a command line argument to the Qt configure command. For example:
From 4.1.1 the Qt binary package is already universal.
If you want to create a binary that runs on older versions of PowerPC and x86, it is possible to build Qt for the PowerPC using GCC 3.3, and for x86 one using GCC 4.0, and use Apple's lipo(1) tool to stitch them together. This is beyond the scope of this document and is not something we have tried, but Apple documents it on their developer website.
Once you have a universal Qt, qmake will generate makefiles that will build for its host architecture by default. If you want to build for a specific architecture, you can control this with the CONFIG line in your .pro file. Use CONFIG+=ppc for PowerPC, and CONFIG+=x86 for x86. If you desire both, simply add both to the CONFIG line. PowerPC users also need an SDK. For example:
Besides lipo, you can also check your binaries with the file(1) command line tool or the Finder.
The Mac Deployment Tool
The Mac deployment tool can be found in QTDIR/bin/macdeployqt. It is designed to automate the process of creating a deployable application bundle that contains the Qt libraries as private frameworks.
Argouml download mac os x. The mac deployment tool also deploys the Qt plugins, according to the following rules:
- Debug versions of the plugins are not deployed.
- The designer plugins are not deployed.
- The Image format plugins are always deployed.
- SQL driver plugins are deployed if the application uses the QtSql module.
- Script plugins are deployed if the application uses the QtScript module.
- The Phonon backend plugin is deployed if the application uses the Phonon module.
- The svg icon plugin is deployed if the application uses the QtSvg module.
- The accessibility plugin is always deployed.
- Accessibility for Qt3Support is deployed if the application uses the Qt3Support module.
Note: If you want a 3rd party library to be included in your application bundle, then you must add an excplicit lib entry for that library to your application's .pro file. Download pictures from iphone 5 to mac. Otherwise, the macdeployqt tool will not copy the 3rd party .dylib into the bundle.
macdeployqt supports the following options:
- -no-plugins: Skip plugin deployment
- -dmg : Create a .dmg disk image
- -no-strip : Don't run 'strip' on the binaries
[Deploying Qt Applications]
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies) | Trademarks |
So, you’ve decided to download an older version of Mac OS X. There are many reasons that could point you to this radical decision. Encryption software for mac download. To begin with, some of your apps may not be working properly (or simply crash) on newer operating systems. Also, you may have noticed your Mac’s performance went down right after the last update. Finally, if you want to run a parallel copy of Mac OS X on a virtual machine, you too will need a working installation file of an older Mac OS X. Further down we’ll explain where to get one and what problems you may face down the road.
A list of all Mac OS X versions
We’ll be repeatedly referring to these Apple OS versions below, so it’s good to know the basic macOS timeline.
Cheetah 10.0 | Puma 10.1 | Jaguar 10.2 |
Panther 10.3 | Tiger 10.4 | Leopard 10.5 |
Snow Leopard 10.6 | Lion 10.7 | Mountain Lion 10.8 |
Mavericks 10.9 | Yosemite 10.10 | El Capitan 10.11 |
Sierra 10.12 | High Sierra 10.13 | Mojave 10.14 |
Catalina 10.15 |
STEP 1. Prepare your Mac for installation
Given your Mac isn’t new and is filled with data, you will probably need enough free space on your Mac. This includes not just space for the OS itself but also space for other applications and your user data. One more argument is that the free space on your disk translates into virtual memory so your apps have “fuel” to operate on. The chart below tells you how much free space is needed.
Note, that it is recommended that you install OS on a clean drive. Next, you will need enough disk space available, for example, to create Recovery Partition. Here are some ideas to free up space on your drive:
- Uninstall large unused apps
- Empty Trash Bin and Downloads
- Locate the biggest files on your computer:
Go to Finder > All My Files > Arrange by size
Then you can move your space hoggers onto an external drive or a cloud storage.
If you aren’t comfortable with cleaning the Mac manually, there are some nice automatic “room cleaners”. Our favorite is CleanMyMac as it’s most simple to use of all. It deletes system junk, old broken apps, and the rest of hidden junk on your drive.
Then you can move your space hoggers onto an external drive or a cloud storage.
If you aren’t comfortable with cleaning the Mac manually, there are some nice automatic “room cleaners”. Our favorite is CleanMyMac as it’s most simple to use of all. It deletes system junk, old broken apps, and the rest of hidden junk on your drive.
Download CleanMyMac for OS 10.4 - 10.8 (free version)
Download CleanMyMac for OS 10.9 (free version)
Download CleanMyMac for OS 10.10 - 10.14 (free version)
STEP 2. Get a copy of Mac OS X download
Normally, it is assumed that updating OS is a one-way road. That’s why going back to a past Apple OS version is problematic. The main challenge is to download the OS installation file itself, because your Mac may already be running a newer version. If you succeed in downloading the OS installation, your next step is to create a bootable USB or DVD and then reinstall the OS on your computer.
How to download older Mac OS X versions via the App Store
If you once had purchased an old version of Mac OS X from the App Store, open it and go to the Purchased tab. There you’ll find all the installers you can download. However, it doesn’t always work that way. The purchased section lists only those operating systems that you had downloaded in the past. But here is the path to check it:
- Click the App Store icon.
- Click Purchases in the top menu.
- Scroll down to find the preferred OS X version.
- Click Download.
This method allows you to download Mavericks and Yosemite by logging with your Apple ID — only if you previously downloaded them from the Mac App Store.
Without App Store: Download Mac OS version as Apple Developer
If you are signed with an Apple Developer account, you can get access to products that are no longer listed on the App Store. If you desperately need a lower OS X version build, consider creating a new Developer account among other options. The membership cost is $99/year and provides a bunch of perks unavailable to ordinary users.
Nevertheless, keep in mind that if you visit developer.apple.com/downloads, you can only find 10.3-10.6 OS X operating systems there. Newer versions are not available because starting Mac OS X Snow Leopard 10.7, the App Store has become the only source of updating Apple OS versions.
Purchase an older version of Mac operating system
You can purchase a boxed or email version of past Mac OS X directly from Apple. Both will cost you around $20. For the reason of being rather antiquated, Snow Leopard and earlier Apple versions can only be installed from DVD.
Buy a boxed edition of Snow Leopard 10.6
Get an email copy of Lion 10.7
Get an email copy of Mountain Lion 10.8
Get an email copy of Lion 10.7
Get an email copy of Mountain Lion 10.8
The email edition comes with a special download code you can use for the Mac App Store. Note, that to install the Lion or Mountain Lion, your Mac needs to be running Snow Leopard so you can install the newer OS on top of it.
How to get macOS El Capitan download
Qt 4.6 Download Mac Iso
If you are wondering if you can run El Capitan on an older Mac, rejoice as it’s possible too. But before your Mac can run El Capitan it has to be updated to OS X 10.6.8. So, here are main steps you should take:
1. Install Snow Leopard from install DVD.
2. Update to 10.6.8 using Software Update.
3. Download El Capitan here.
2. Update to 10.6.8 using Software Update.
3. Download El Capitan here.
“I can’t download an old version of Mac OS X”
If you have a newer Mac, there is no physical option to install Mac OS versions older than your current Mac model. For instance, if your MacBook was released in 2014, don’t expect it to run any OS released prior of that time, because older Apple OS versions simply do not include hardware drivers for your Mac.
But as it often happens, workarounds are possible. There is still a chance to download the installation file if you have an access to a Mac (or virtual machine) running that operating system. For example, to get an installer for Lion, you may ask a friend who has Lion-operated Mac or, once again, set up a virtual machine running Lion. Then you will need to prepare an external drive to download the installation file using OS X Utilities.
After you’ve completed the download, the installer should launch automatically, but you can click Cancel and copy the file you need. Below is the detailed instruction how to do it.
STEP 3. Install older OS X onto an external drive
The following method allows you to download Mac OS X Lion, Mountain Lion, and Mavericks.
Qt 4.6 Download Mac Os
- Start your Mac holding down Command + R.
- Prepare a clean external drive (at least 10 GB of storage).
- Within OS X Utilities, choose Reinstall OS X.
- Select external drive as a source.
- Enter your Apple ID.
Now the OS should start downloading automatically onto the external drive. After the download is complete, your Mac will prompt you to do a restart, but at this point, you should completely shut it down. Now that the installation file is “captured” onto your external drive, you can reinstall the OS, this time running the file on your Mac.
- Boot your Mac from your standard drive.
- Connect the external drive.
- Go to external drive > OS X Install Data.
Locate InstallESD.dmg disk image file — this is the file you need to reinstall Lion OS X. The same steps are valid for Mountain Lion and Mavericks.
How to downgrade a Mac running later macOS versions
If your Mac runs macOS Sierra 10.12 or macOS High Sierra 10.13, it is possible to revert it to the previous system if you are not satisfied with the experience. You can do it either with Time Machine or by creating a bootable USB or external drive.
Instruction to downgrade from macOS Sierra
Instruction to downgrade from macOS Sierra
Qt 4.6
Instruction to downgrade from macOS High Sierra
Instruction to downgrade from macOS Mojave
Qt 4.6 Download
Instruction to downgrade from macOS Catalina
Before you do it, the best advice is to back your Mac up so your most important files stay intact. In addition to that, it makes sense to clean up your Mac from old system junk files and application leftovers. The easiest way to do it is to run CleanMyMac X on your machine (download it for free here).
Qt 4.6 Download Mac Installer
Visit your local Apple Store to download older OS X version
Qt 4.6 Download Mac Download
If none of the options to get older OS X worked, pay a visit to nearest local Apple Store. They should have image installations going back to OS Leopard and earlier. You can also ask their assistance to create a bootable USB drive with the installation file. So here you are. We hope this article has helped you to download an old version of Mac OS X. Below are a few more links you may find interesting.