The identification name is what the dynamic linker ( dyld ) uses to find the libraries for your application.We demonstrate the procedures in terms of deploying the Plug Paint application that is provided in Qts examples directory.
![]()
As a programmer you can access bundle information in your own code. Libstdc . Boost Libraries On Xcode Mac OS X And BeyondThis is specific to Mac OS X and beyond the scope of this document. More information about bundles is available on Apples Developer Website. You probably dont want to run it in a bundle: Add this to your applications.pro. Libstdc . Boost Libraries On Xcode How To Deploy ThesePlease refer to the X11 deployment documentation for information about how to deploy these bundle-less applications. 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. Remember that you will not be able to use plugins and you must build in all the image formats, SQL drivers, etc. First, we must go into the directory that contains the application. 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 -deadstrip to qmake in addition to the -config release parameter. This doesnt 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. One easy way to check that the application really can be run stand-alone is to copy the bundle to a machine that doesnt have Qt or any Qt applications installed, and run the application on that machine. 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. 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. 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. For more information on how to build Qt, see the Installation documentation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |