Qt Build For Mac
2020年11月2日Download: http://gg.gg/mu6zg
*Qt Mac Address
*Build Standalone Qt Application For Mac
Is there a step-by-step guide on how to build QT5.x static anywhere? Im trying to deploy an Application on OSX and want everything build into a single executable I am using external Libraries which are already build statically and work fine. Get the full Qt experience with a licensing plan designed to support your business goals plus access to the official Qt Support Helpdesk and a close strategic relationship with The Qt Company. Buy Qt Now Contact us. New to Qt and want to try before you buy? Download a free trial of the Qt framework, tools for desktop and embedded. Qt is the faster, smarter way to create innovative devices, modern UIs & applications for multiple screens. Cross-platform software development at its best. Qt documentation: Deploying on Mac. Qt offers a deployment tool for Mac: 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. Latest Mac build: SoulseekQt-2018-11-16.dmg (requires OSX 10.9 or higher) Latest Linux 64-bit AppImage: SoulseekQt-2018-1-30-64bit-appimge.tgz If you’re looking for the original Soulseek client for Windows (Soulseek NS), please go here.
EnArBgDeElEsFaFiFrHiHuItJaKnKoMsNlPlPtRuSqThTrUkZhIMPORTANT: The content of this page is outdated. Reason: This refers to an old version of Qt and the links are no longer valid. Use the Qt documentation on building instead.If you have checked or updated this page and found the content to be suitable, please remove this notice.Required SDKs and tools
Here are the tools required to build a Qt Shared or a Qt Static library. First, please, download and install :1. Qt source code (I think you know where to find it :))2. On machines not having a previous Qt version already installed you need to install also Perl (e.g. ActivePerl ) prior to configure. Otherwise you may receive following error message at the end of configure: > Perl not found in environment - cannot run syncqt.3. Microsoft Platform SDK (most recent at time of last wiki edit is Microsoft Windows 7.1 SDK.). The SDK includes the Microsoft Visual C++ compilers and debugging tools. You can in addition install Visual Studio Express if you like the IDE (not required!).4. KB2485545 or Service Pack 1 are required for MSVC 2010 when building a 64bit library on intel x86 based CPUs. They fix a bug in the MSVC2010 compiler, and without it you will experience crashes when running 64bit binaries.5. OpenSSL libraries or source code (if you want to build it yourself)
For Shared (if you want Phonon support) also requiredQt Mac Address
Ok, all done but… If you decided to build OpenSSL yourself (really, I recommend you) it is also required
*ActivePerl (community edition is free)Installation
At first I recommend you to install all packages into one directory (for example _C:):
*C: (for Visual C+)
*C:7.1 SDK (for platform SDK)
*C: (for OpenSSL library or unpack source code anywhere for build)
* …
It is not required to install examples, demos, docs, libraries not for target architecture e.g. ;)Environment setup
It looks good to have a script to set up the environment instead of setting it all using system PATH variable:
This file is .bat (or.cmd) script. Just modify and save it for your environment. I set it up from tool’s (MSVC, SDKs) prompts.
You can add it to start menu or make a label (change script address at label preferences to ’cmd /k path/to/setqtenv.cmd’).What we have
At my computer I have installed MSVC+ 2010 Express Edition to C:, Windows 7.1 SDK C:7.1 SDK, DirectX SDK C:SDK, Perl C: (impossible to change), NASM unpacked to C:, Qt Desktop (4.7.1) source code (from qt-everywhere-opensource-src-4.7.1.tar.gz) unpacked to C: and OpenSSL source code unpacked to C:–1.0.0c’Static’ tips
Before you start to build a static Qt Desktop library, you must know that for now you will have a dependence with MSVC Redistributable. To escape this you must replace -MD (d) build flag with -MT (d) (I will not recommend you use it, because it can cause runtime errors, etc.For example with this configuration I cannot start QtDesigner app.The reason is unknown.)
It’s available as both Static and Shared builds.Building OpenSSL
At first, open your new Qt prompt, cd to your OpenSSL source directory and setup (if not set) Perl bin directory path (and check it?):
Something like this:
If all is ok, we can continue…
Configuring and preparing OpenSSL (copy-paste it, here is underscore symbols):
If you have NASM:
And if not:
Here we set up compiler and destination directory.
Now open msntdll.mak (for Static — msnt.mak) file and replace at LFLAGS/debug with /release.
For Static build flag -MT is applied by default (look at ’Static’ tips). For shared -MD is used (change CFLAG’s at msntdll.mak from /MD to /MT if required for you).
Ok, building, testing and ’installing’:
For Shared:
And for Static:
Ready. Now you can remove your OpenSSL source code (C:–1.0.0c here, on screenshot) directory and Perl installation. They are no longer required.Configuring Qt Desktop
There are 2 steps:
* Check/Change build flags
* ConfigureNote: MSVC supports build with multiple processes. Really. You can add -MP[processMax] flag. Details here.
For first step (are you really sure with ’Static’ tips?) we are going to %QTDIR%32-msvc2010 (I know that you know that real path is C:32-msvc2010 and if you have different version of MSVC it will be different spec directory ;)). Here we are interested in the qmake.conf configuration file.Build Standalone Qt Application For Mac
Edit QMAKE_CFLAGS_RELEASE, QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO & QMAKE_CFLAGS_DEBUG variables. For example:
Next — configuring. My configuration (shared) is:
As you see, I do not want to build Qt3 support module, some styles, using image libs from Qt source, some additional instructions sets are enabled and some another stuff.
Ok, let’s configure… Accepting license… Please, wait… (building qmake now) :)
All the project’s files are read and now we able to build libs, tools, examples, etc. Just nmake it to build all. Also we are able to make only libs (nmake sub-src), tools (nmake sub-tools, but after libs)…Recommendations
Copy (or move) OpenSSL libraries (*.dll) from %QTDIR% directory to Qt bin directory and add %QTDIR% to system %PATH% variable.Reduce used HDD space
Attention! This operations removes debugging information! (if you set release-and-debug)
Just at %QTDIR% run nmake clean to delete all tmp objects, etc. Then rebuild translations (go to %QTDIR% and run nmake). And remove libraries (.dll) from %QTDIR%. Retrieved from ’https://wiki.qt.io/index.php?title=Building_Qt_Desktop_for_Windows_with_MSVC&oldid=36647’
Download: http://gg.gg/mu6zg
*Qt Mac Address
*Build Standalone Qt Application For Mac
Is there a step-by-step guide on how to build QT5.x static anywhere? Im trying to deploy an Application on OSX and want everything build into a single executable I am using external Libraries which are already build statically and work fine. Get the full Qt experience with a licensing plan designed to support your business goals plus access to the official Qt Support Helpdesk and a close strategic relationship with The Qt Company. Buy Qt Now Contact us. New to Qt and want to try before you buy? Download a free trial of the Qt framework, tools for desktop and embedded. Qt is the faster, smarter way to create innovative devices, modern UIs & applications for multiple screens. Cross-platform software development at its best. Qt documentation: Deploying on Mac. Qt offers a deployment tool for Mac: 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. Latest Mac build: SoulseekQt-2018-11-16.dmg (requires OSX 10.9 or higher) Latest Linux 64-bit AppImage: SoulseekQt-2018-1-30-64bit-appimge.tgz If you’re looking for the original Soulseek client for Windows (Soulseek NS), please go here.
EnArBgDeElEsFaFiFrHiHuItJaKnKoMsNlPlPtRuSqThTrUkZhIMPORTANT: The content of this page is outdated. Reason: This refers to an old version of Qt and the links are no longer valid. Use the Qt documentation on building instead.If you have checked or updated this page and found the content to be suitable, please remove this notice.Required SDKs and tools
Here are the tools required to build a Qt Shared or a Qt Static library. First, please, download and install :1. Qt source code (I think you know where to find it :))2. On machines not having a previous Qt version already installed you need to install also Perl (e.g. ActivePerl ) prior to configure. Otherwise you may receive following error message at the end of configure: > Perl not found in environment - cannot run syncqt.3. Microsoft Platform SDK (most recent at time of last wiki edit is Microsoft Windows 7.1 SDK.). The SDK includes the Microsoft Visual C++ compilers and debugging tools. You can in addition install Visual Studio Express if you like the IDE (not required!).4. KB2485545 or Service Pack 1 are required for MSVC 2010 when building a 64bit library on intel x86 based CPUs. They fix a bug in the MSVC2010 compiler, and without it you will experience crashes when running 64bit binaries.5. OpenSSL libraries or source code (if you want to build it yourself)
For Shared (if you want Phonon support) also requiredQt Mac Address
Ok, all done but… If you decided to build OpenSSL yourself (really, I recommend you) it is also required
*ActivePerl (community edition is free)Installation
At first I recommend you to install all packages into one directory (for example _C:):
*C: (for Visual C+)
*C:7.1 SDK (for platform SDK)
*C: (for OpenSSL library or unpack source code anywhere for build)
* …
It is not required to install examples, demos, docs, libraries not for target architecture e.g. ;)Environment setup
It looks good to have a script to set up the environment instead of setting it all using system PATH variable:
This file is .bat (or.cmd) script. Just modify and save it for your environment. I set it up from tool’s (MSVC, SDKs) prompts.
You can add it to start menu or make a label (change script address at label preferences to ’cmd /k path/to/setqtenv.cmd’).What we have
At my computer I have installed MSVC+ 2010 Express Edition to C:, Windows 7.1 SDK C:7.1 SDK, DirectX SDK C:SDK, Perl C: (impossible to change), NASM unpacked to C:, Qt Desktop (4.7.1) source code (from qt-everywhere-opensource-src-4.7.1.tar.gz) unpacked to C: and OpenSSL source code unpacked to C:–1.0.0c’Static’ tips
Before you start to build a static Qt Desktop library, you must know that for now you will have a dependence with MSVC Redistributable. To escape this you must replace -MD (d) build flag with -MT (d) (I will not recommend you use it, because it can cause runtime errors, etc.For example with this configuration I cannot start QtDesigner app.The reason is unknown.)
It’s available as both Static and Shared builds.Building OpenSSL
At first, open your new Qt prompt, cd to your OpenSSL source directory and setup (if not set) Perl bin directory path (and check it?):
Something like this:
If all is ok, we can continue…
Configuring and preparing OpenSSL (copy-paste it, here is underscore symbols):
If you have NASM:
And if not:
Here we set up compiler and destination directory.
Now open msntdll.mak (for Static — msnt.mak) file and replace at LFLAGS/debug with /release.
For Static build flag -MT is applied by default (look at ’Static’ tips). For shared -MD is used (change CFLAG’s at msntdll.mak from /MD to /MT if required for you).
Ok, building, testing and ’installing’:
For Shared:
And for Static:
Ready. Now you can remove your OpenSSL source code (C:–1.0.0c here, on screenshot) directory and Perl installation. They are no longer required.Configuring Qt Desktop
There are 2 steps:
* Check/Change build flags
* ConfigureNote: MSVC supports build with multiple processes. Really. You can add -MP[processMax] flag. Details here.
For first step (are you really sure with ’Static’ tips?) we are going to %QTDIR%32-msvc2010 (I know that you know that real path is C:32-msvc2010 and if you have different version of MSVC it will be different spec directory ;)). Here we are interested in the qmake.conf configuration file.Build Standalone Qt Application For Mac
Edit QMAKE_CFLAGS_RELEASE, QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO & QMAKE_CFLAGS_DEBUG variables. For example:
Next — configuring. My configuration (shared) is:
As you see, I do not want to build Qt3 support module, some styles, using image libs from Qt source, some additional instructions sets are enabled and some another stuff.
Ok, let’s configure… Accepting license… Please, wait… (building qmake now) :)
All the project’s files are read and now we able to build libs, tools, examples, etc. Just nmake it to build all. Also we are able to make only libs (nmake sub-src), tools (nmake sub-tools, but after libs)…Recommendations
Copy (or move) OpenSSL libraries (*.dll) from %QTDIR% directory to Qt bin directory and add %QTDIR% to system %PATH% variable.Reduce used HDD space
Attention! This operations removes debugging information! (if you set release-and-debug)
Just at %QTDIR% run nmake clean to delete all tmp objects, etc. Then rebuild translations (go to %QTDIR% and run nmake). And remove libraries (.dll) from %QTDIR%. Retrieved from ’https://wiki.qt.io/index.php?title=Building_Qt_Desktop_for_Windows_with_MSVC&oldid=36647’
Download: http://gg.gg/mu6zg
コメント