회사 물류프로그램에 프린터 라이브러리로 사용하던 프로젝트가 클로즈 되어 버렸다.
오픈소스 프린터 라이브러리는 pulas 라는 ...
일단은 프로젝트가 빌드된 환경은 Qt 5.5.1버전으로 공식다운로드 사이트에서는 찾기 어려웠다.
이전 포스팅을 할 당시에는 5.5.1을 꼭 해야한다는 의무감이 없어서 이런 저런 삽질을 많이 했었던 것 같다. 하지만 5.8.0에서 Makefile project.o file not found 오류와
5.7.1에서 빌드시 QMAKE_PRL_TARGET 문제등을 겪은 후 5.5.1을 찾아야겠다는 생각을 하게 되었고 구글을 통해서 찾을 수 있었다.
(QMAKE_PRL_TARGET 문제 참고사이트 >> https://bugreports.qt.io/browse/QTBUG-51977 )
Qt 5.5.1버전은 아래주소에서 다운받을 수 있었다.
https://download.qt.io/archive/qt/5.5/5.5.1/
빌드는 Static한 빌드를 해야한다. 따라서 Static으로 설치하는 법에 대해서 공유한다.
qt-opensource-windows-x86-mingw492-5.5.1.exe prebuild된 설치파일을 받아서 설치를 진행한다.
대략 30분쯤 후 설치된다.
아래주소로 다시 이동한다.
https://download.qt.io/archive/qt/5.5/5.5.1/single/
qt-everywhere-opensource-src-5.5.1.7z 이 파일은 받지 않아도 되나 혹시나
필요할 경우를 위해서 경로를 남긴다.
webkit을 프로젝트에 포함해야 했기에 webkit을 빌드해야한다.
압축을 해제한 소스폴더에 보면 qtwebkit이존재하고 거시서 빌드스크립트를 실행시켜줘야한다.
빌드를 위해서는 루비와 펄이 필요하다.
그리고 GnuWin32중에서 flex와 bison이 필요한데...
flex는 win_flex의 이름을 flex로 변경해서 실행하는데 win_flex도 있어야한다.ㅡㅡ;
관련오류는 스택오버플로우에 ....
http://stackoverflow.com/questions/33916633/qt5-5-1-nmake-unknown-flag-for-usage-error
In my case I've installed the GnuWin32 files (C:\Program Files
(x86)\GnuWin32\bin): "flex.exe" and "bison.exe" (and other files there)
and the "winflex" files (C:\winflex): "win_flex.exe" and
"win_bison.exe". All of this files are in the PATH variable (set
PATH=%PATH%;C:\winflex;...).
And for correct work I did following:
1) rename C:\Program Files (x86)\GnuWin32\bin\flex.exe to some unused name.
2) rename C:\Program Files (x86)\GnuWin32\bin\bison.exe to some unused name.
3) rename C:\winflex\win_bison.exe to bison.exe.
And the flex error fixed.
이제 펄 스크립트를 실행해보자..
qtwebkit 폴더안에서...
perl Tools\Scripts\build-webkit --qt --release
잘 안된다면 환경탓.
이젠 아래 주소로 이동한다.
https://wiki.qt.io/Building_a_static_Qt_for_Windows_using_MinGW#Command_line
이 페이지를 중심으로 설치를 진행하면 잘 된다.
내용은 아래와 같다.
따라서 설치를 진행해주면 되는데
영어가 귀찮다면 일단은 스크롤로 하단까지 이동...
--------------------------------------------------------------------------------
Why a static Qt?
On Windows, the pre-built environments from
qt.io
are dynamically linked. This means that your Qt application dynamically
references the Qt DLL's which are installed with the pre-built
environment.
This is probably the preferred environment for developing and
debugging since everything is there and ready to use. However, when it
comes to deploying an application on systems without pre-installed Qt
environments, it becomes complicated. There are several DLL’s to deploy
with the application. Even using the classical
DLL Dependency Walker
tool, you cannot find all required DLL’s since some of them are
dynamically loaded at execution. So, when the application is ready to
deploy, it is easier to build a static version of it. But building a
static version of the application requires a static version of the Qt
environment in addition to the pre-built dynamic Qt environment.
This article describes an automated way of downloading, building
and installing a static Qt development environment using a Windows
PowerShell script.
Note that building and installing a static version of Qt on
Windows was somewhat problematic up to Qt 4. But Qt 5 has now a much
better support for static builds on Windows and this article takes
advantage of that.
MinGW vs. MSVC
On Windows, two pre-built environments can be downloaded: one using
MinGW and one using Microsoft Visual Studio. The two environments are
incompatible and cannot be mixed. You have to choose one.
This article describes how to build a static version of Qt in a
MinGW environment. If you need a static Qt for MSVC, you may probably
find some ideas here but there is definitely some extra work.
Target environment
When you develop Qt applications on Windows and need to deploy them
later on "general purpose" Windows machines, the recommended Qt
environment contains two distinct builds of the same version of Qt:
- A dynamic version, installed in C:\Qt from a pre-built package.
- A static version, installed in C:\Qt\Static using the procedure which is described in this article.
The pre-built dynamic environment shall be used for development and
debugging. In addition to the Qt command line tools (qmake, moc, uic,
lupdate, lrelease, etc.), it contains the high-level GUI tools such as
Qt Creator, Assistant, Linguist, etc. The installation is
straightforward, everything is here, well integrated, working like a
charm.
The static environment shall be used to release the deployment
version of the application, after it has been fully developed and
debugged using the dynamic environment. The static environment contains
only the Qt command line tools. There are at least two reasons for not
building static versions of the GUI tools. First, releasing a new
version of an application is typically a task that you automate using a
script and there is no need for GUI tools at this stage. Second, it is
probably impossible to build a static version of Qt Creator because of
the lack of support for plugins in a static environment.
Restrictions in a static environment
Although building a static version of your application makes it
easier to deploy, there are some restrictions in a static environment.
Be sure to check that your application complies with these constraints
before going further.
- There are licensing issues in distributing applications embedding Qt code in a static link. See here and here
for more details. While you are probably safe if your application is
distributed according to the terms of a recognized free and open-source
license, you should definitely check the licensing issue for proprietary
or closed-source applications.
- The application cannot use a dynamic modular approach using
plugins. But you cannot both ask for a static environment and for a
dynamic loading of your own DLL's.
Also note the following points:
- The static executable file of the application is bigger than the
dynamic one since all used Qt code is copied into the executable.
However, if your application has only one executable, the total deployed
size is smaller since only the Qt code which is actually used is
linked. When deploying a dynamic version of the application, you have to
install all required Qt DLL's with the application and the overall size
of all these DLL's is larger than the static application.
- A Qt static build means that no Qt or MinGW DLL's are used.
However, the static executable file of the application still references
the Windows DLL's such as kernel32.dll or user32.dll. These DLL's,
however, are installed with Windows and do not need to be deployed with
the application.
Prerequisites
Dynamic pre-built Qt environment
Install the dynamic pre-built package from
qt.io.
Select the package named "Qt 5.5.0 for Windows 32-bit (MinGW 4.9.2, 959
MB)". The exact name and version may vary. You can also
browse the tree of installation packages.
Preferably plan the installation of the same version of Qt for
the dynamic and static builds. This is not a strict requirement but it
is a safe configuration. At the time of writing of this article, the
latest Qt version is
5.5.0.
During installation, select the default installation location (
C:). Be sure to add the MinGW environment in the installation (selectable in the "Tools" branch of the installation options).
If you have a separated MinGW environment that you prefer to use
and do not install the one from the Qt package installer, be sure to
specify the option
-MingwDir in the static build script (see below).
Windows PowerShell
The script which builds the static Qt environment is a PowerShell script.
The PowerShell version 3.0 or higher is required. PowerShell 3.0
comes with Windows 8 but it can be installed on Windows 7 as well from
Microsoft download.
It is probably impossible to install PowerShell 3.0 on Windows XP or
Vista. This article consequently applies to Windows 7 and higher only.
7-Zip
The build script also requires
7-Zip to uncompress the downloaded Qt source code. Be sure to install it first.
Building the Qt static environment
Download and run, all done
Download the script named
windows-build-qt-static.ps1 and execute it.
The above link fetches the script directly from the git repository of a small open-source project named
QtlMovie. You may want to have a look at the various build scripts in this project for sample application builds and installations.
The
windows-build-qt-static.ps1 script can be directly
invoked from the Windows Explorer if you are ok with the default
parameter values (see below). If you are not familiar with PowerShell,
simply right-click on the file and select "Run with PowerShell".
The script performs the following steps:
- Download Qt source code.
- Build a static version of Qt using the MinGW compiler in the
pre-built dynamic environment. It builds the libraries and the command
line tools (qmake, moc, uic, lupdate, lrelease, etc.)
- Install the static version of Qt in C:\Qt\Static by default.
The execution of this script may take a couple of hours to complete,
depending on your processing power. So you have to be patient. Qt is a
complex framework with a very large amount of code.
Command line syntax
Alternatively, you can invoke the script from the PowerShell prompt using the following syntax:
windows-build-qt-static.ps1 [-QtSrcUrl url] [-QtStaticDir directory] [-QtVersion string] [-MingwDir directory] [-NoPause]
Command line parameters
-QtSrcUrl url
Specify the URL of the Qt source file archive. By default, the latest identified version is hardcoded (
[1] at the time of this article was edited).
Instead of using the parameter on the command line, you may want
to modify the default value in the script using another URL / version.
Update the following line:
$QtSrcUrl = "http://download.qt-project.org/official_releases/qt/5.5/5.5.0/single/qt-everywhere-opensource-src-5.5.0.7z",
-QtStaticDir directory
Specify the root directory where the static versions of Qt are installed. By default:
C:.
-QtVersion string
Specify the Qt version. By default, the script tries to extract
the version number from the Qt source file name. Usually, this is
sufficient, the script will find "5.5.0" or "5.0.0-rc1" for instance. If
the naming scheme of the Qt source file changes one day, you may need
to specify an explicit value to this parameter.
-MingwDir directory
Specify the root directory of the MinGW environment. By default,
use the version which was installed by the prebuilt Qt environment.
When the prebuilt environment for Qt 5.5.0 is installed for instance, the script locates MinGW in
C:\5.5.0\Tools\mingw492_32.
If you chose not to install MinGW as part of the prebuilt environment
for Qt, you have to specify the root directory of your MinGW
installation.
-NoPause
Do not wait for the user to press
enter at the end of execution. By default, the scripts executes a
pause instruction at the end of execution, which is useful when the script was run from the Windows Explorer.
Using the Qt static environment
Command line
This section describes how to use the static Qt environment from the
command line, either the traditional Windows command shell (cmd.exe) or
the Windows PowerShell.
Simply add the
bin subdirectory of the static Qt environment in front of the
Path environment variable. For Qt 5.5.0, this is
C:\Qt\Static\5.5.0\bin.
Do not forget to also include the MinGW environment in the path.
With the dynamic pre-built Qt environment, you may want to add Qt
Creator also.
The following commands summarize the command line setups for the various environments.
Dynamic pre-built Qt with the traditional Windows command shell:
set Path=C:\Qt\Qt5.5.0\5.5.0\mingw492_32\bin;C:\Qt\Qt5.5.0\Tools\mingw492_32\bin;C:\Qt\Qt5.5.0\Tools\QtCreator\bin;C:32;C:
Dynamic pre-built Qt with the Windows PowerShell:
$env:Path=C:\Qt\5.5.0\5.5.0\mingw492_32\bin;C:\Qt\Qt5.5.0\Tools\mingw492_32\bin;C:\Qt\5.5.0\Tools\QtCreator\bin;C:\32;C:
Static Qt build with the traditional Windows command shell:
set Path=C:\2.0\bin;C:\Qt\Qt5.5.0\Tools\mingw492_32\bin;C:\32;C:
Static Qt build with the Windows PowerShell:
$env:Path=C:\Qt\.5.0\bin;C:\Qt\Qt5.5.0\Tools\mingw492_32\bin;C:\32;C:
Using the Qt static environment with Qt Creator
This section describes how to use the static Qt environment from Qt
Creator. Note that Qt Creator itself is part of the dynamic pre-built
environment. By default, it builds the applications for this dynamic
environment. But it is possible to configure it to additionally use the
static Qt environment.
The following description is based on a Qt 5.5.0 / Qt Creator
3.4.2 installation, without additional customization of Qt Creator.
Change the version numbers to adapt to your configuration.
Qt Creator setup
Open the Qt Creator options edit box (menu "Tools" then "Options…"). Select "Build & Run".
Go to tab "Qt Versions". In the "qmake location" table, there
must be an "Auto-detected" part and a "Manual" part. In the
"Auto-detected" part, there should be one line named "Qt 5.5.0 MinGW
32bit C:\Qt\Qt5.5.0\5.5\mingw492_32\bin\qmake.exe". The "Manual" part is
initially empty.
Click "Add", browse to C:\Qt\Qt5.5.0\bin and select "qmake.exe".
The version name is automatically set to "Qt 5.5.0 (5.5.0)". You should
set a more meaningful name such as "Qt 5.5.0 MinGW Static 32bit"
Then go to tab "Kits". Again, there must be an "Auto-detected"
part and an initially empty "Manual" part. Click "Add". Set a meaningful
name such as "Desktop Qt 5.5.0 MinGW Static 32bit". In the "Qt version"
field, select your static environment, named "Qt 5.5.0 MinGW Static
32bit" if you followed the above advice.
Then click "OK" to terminate the options setup.
Project setup
In each project you want to deploy with a static build, edit the project setup (select "Projects" in the left vertical pane).
Click "Add Kit" in the upper left corner and select your static
kit, named "Desktop Qt 5.5.0 MinGW Static 32bit" if you followed the
above advice.
The new kit for your project is configured. Note that, by
default, there are distinct build directories for the dynamic and static
versions of your project.
Now you can build your application in any combination of static
vs. dynamic and release vs. debug. In the bottom part of the left pane,
the project selector (the computer icon with the name of your project
and either "Release" or "Debug") lets you select the combination you
want.
Note that it is recommended to build only release versions of the
application with the static environment. Avoid building a debug version
of the application with the static environment. There are several
reasons for that:
- The recommended environment for the development, debug and test phase is the pre-built dynamic environment, not the static one.
- The size of a static application in debug mode is insanely huge.
For a given application, the following sizes have been observed for the
application executable file:
- Dynamic + Release: 1 MB
- Dynamic + Debug: 33 MB
- Static + Release: 16 MB
- Static + Debug: 297 MB
--------------------------------------------------------------------------------
윈도우즈의 파워쉘과 7zip이 먼저 설치되어 있어야 한다.
파워쉘은 윈도우 기본이지만 혹시나 확인해보길 바란다.
7zip은 잘 설치하면 된다.
해당페이지의 중간쯤 위치한
windows-build-qt-static.ps1 and execute it ...
파일 다운로드 링크를 남긴다.
https://sourceforge.net/p/qtlmovie/code/ci/v1.2.16/tree/build/windows-build-qt-static.ps1?format=raw
이 파일을 다운로드 받는다.
파일을 열어보면
78라인쯤에
$QtSrcUrl = "http://download.qt-project.org/official_releases/qt/5.3/5.3.0/single/qt-everywhere-opensource-src-5.3.0.7z",
$QtStaticDir = "C:\Qt\Static",
$QtVersion = "",
$MingwDir = "",
[switch]$NoPause = $false
여기서 다운로드 주소가 변경된다.
param(
$QtSrcUrl = "https://download.qt.io/archive/qt/5.5/5.5.1/single/qt-everywhere-opensource-src-5.5.1.7z",
$QtStaticDir = "D:\Qt\Static",
$QtVersion = "5.5.1",
$MingwDir = "D:\Qt\Qt5.5.1\Tools\mingw492_32",
[switch]$NoPause = $false
154라인에 파워쉘 path설정이 있는데 약간 수정이 필요하다.
$env:path = $env:path +";$MingwDir\bin;$MingwDir\opt\bin;$env:SystemRoot\system32;$env:SystemRoot"
Path가 path로 변경되어야한다.
이렇게 수정한 후 파워쉘에서 실행을 해주면 된다.
여기서 보듯이 이미 prebuild된 Qt를 설치하는 것이 좋다.
나중에 Creator도 당연히 필요하니까.
빌드는 대략 3시간 정도 걸렸던 것 같다.
이제 크리에이터를 실행하고 옵션을 수정하여 마무리한다.
추후 사진을 첨부하도록 하겠다.
