This software can be built using Visual Studio 2019 and Qt 5.x
- https://www.visualstudio.microsoft.com
- During the installation, make sure to select all the Visual C++ packages.
- https://cmake.org/download/
- This will be used to create the
MSVC 2019project file.
- https://www.qt.io/download-open-source/
- Qt is a cross-platform GUI framework.
- Install Qt 5.15 (64-bit version, tested up to 5.15.2) with the Qt Online Installer for Windows.
- Qt have started to support Windows Ink from 5.12. Unlike WinTab API used until Qt 5.9 , the tablet behaviors are different and are (at least, for OT) problematic.
- The customized Qt5.15.2 are made with cherry-picking the WinTab feature to be officially introduced from 6.0.
- You can build OT with WinTab support by using the prebuilt package of the customized version of Qt for MSVC2019-x64 provided here and checking the
WITH_WINTABcheckbox in CMake to build.
- Boost 1.55.0 or later is required (tested up to 1.73.0).
- http://www.boost.org/users/history/version_1_73_0.html
- Download boost_1_73_0.zip from the above link. Extract all contents to the - '$opentoonz/thirdparty/boost' directory.
- v4.1.0 and later
- https://opencv.org/
- On configuring with CMake or in the environmental variables, specify
OpenCV_DIRto thebuildfolder in the install folder of OpenCV (likeC:/opencv/build).
- Note: You can also perform these next commands with Github for Desktop client.
- Clone the base repository.
- Throughout the explanation
$opentoonzwill represent the root for the base repository.
libanddllfiles are tracked by Git Large File Storage.- Note: git-lfs is also installed with Github Desktop.
- Visual Studio cannot recognize UTF-8 without BOM source code properly. Furthermore, since the endline character is represented with only the LF character, one line comments in Japanese will often cause the following line to be treated as a comment by
MSVSas well. - In order to prevent this, please change the following setting in git so that it will preserve the proper endline characters:
git config core.safecrlf true- Execute
git lfs pullaftergit cloneby using the lfs client.
- Launch CMake
- In
Where is the source code, navigate to$opentoonz/toonz/sources - In
Where to build the binaries, navigate to$opentoonz/toonz/build - Or to wherever you usually build to.
- If the build directory is in the git repository, be sure to add the directory to .gitignore
- If the build directory is different from the one above, be sure to change to the specified directory where appropriate below.
-Click on Configure and select the version of Visual Studio you are using.
-If Qt was installed to a directory other than the default, and the error Specify QT_PATH properly appears, navigate to the
QT_DIRinstall folder and specify the path tomsvc2019_64. Rerun Configure. -If red lines appear in the bottom box, you can safely ignore them. -Click Generate -Should the CMakeLists.txt file change, such as during automatic build cleanup, there is no need to rerun CMake.
Rename the following files:
$opentoonz/thirdparty/LibJPEG/jpeg-9/jconfig.vcto$opentoonz/thirdparty/LibJPEG/jpeg-9/jconfig.h$opentoonz/thirdparty/tiff-4.0.3/libtiff/tif_config.vc.hto$opentoonz/thirdparty/tiff-4.0.3/libtiff/tif_config.h$opentoonz/thirdparty/tiff-4.0.3/libtiff/tiffconf.vc.h to $opentoonz/thirdparty/tiff-4.0.3/libtiff/tiffconf.h$opentoonz/thirdparty/libpng-1.6.21/scripts/pnglibconf.h.prebuilt to $opentoonz/thirdparty/libpng-1.6.21/pnglibconf.h- Note that the destination is a different folder for the last file.
- Open
$opentoonz/toonz/build/OpenToonz.slnand change toDebugorReleasein the top bar. - Compile the build.
- The output will be in the corresponding folder in
$opentoonz/toonz/build/
You will need the Canon SDK. This requires applying for the Canon developer program and downloading the SDK.
- Copy the Header and library folders from the Canon SDK to
$opentoonz/thirdparty/canon- Make sure that the library is the one from the EDSDK_64 folder.
Check the WITH_CANON checkbox in CMake to build with Canon DSLR camera support.
To run the program with Canon DSLR camera support, you will need to copy the .dll files from the Canon SDK into the folder where your project is built.
-
Copy the entire contents of $opentoonz/toonz/build/Release to an appropriate folder.
-
Open a Command Prompt and navigate to
QT_DIR/msvc2015_64/bin. Run the Qt programwindeployqt.exewith the path forOpenToonz.exeas an argument. (Another way to do this is navigate to the exe that was created in your Release folder and drag and drop the Opentoonz.exe on top of the windeployqt.exe This will automatically generate the QT files and folders you will need.)
- The necessary Qt library files should be in the same folder as
OpenToonz.exe - These include:
D3Dcompiler_**.dllQt5Core.dllQt5Gui.dllQt5Multimedia.dllQt5Network.dllQt5OpenGL.dllQt5PrintSupport.dllQt5Script.dllQt5SerialPort.dllQt5Svg.dllQt5Widgets.dllQt5Xml.dll
- These files should be in the corresponding folders in the same folder
OpenToonz.exe. ├── audio │ ├── qtaudio_wasapid.dll │ └── qtaudio_windowsd.dll ├── bearer │ └── qgenericbearerd.dll ├── iconengines │ └── qsvgicond.dll ├── imageformats │ ├── qgifd.dll │ ├── qicnsd.dll │ ├── qicod.dll │ ├── qjpegd.dll │ ├── qsvgd.dll │ ├── qtgad.dll │ ├── qtiffd.dll │ ├── qwbmpd.dll │ └── qwebpd.dll ├── mediaservice │ ├── dsengined.dll │ ├── qtmedia_audioengined.dll │ └── wmfengined.dll ├── platforms │ └── qwindowsd.dll ├── playlistformats │ └── qtmultimedia_m3ud.dll ├── printsupport │ └── windowsprintersupportd.dll ├── styles │ └── qwindowsvistastyled.dll
- Copy the following files to the same folder as
OpenToonz.exe
$opentoonz/thirdparty/glut/3.7.6/lib/glut64.dll$opentoonz/thirdparty/glew/glew-1.9.0/bin/64bit/glew32.dll$opentoonzthirdparty/libmypaint/dist/64/*.dllturbojpeg.dllfrom libjpeg-turbo packageopencv_world***.dllfrom OpenCV package
- Copy the
srvfolder from the previous OpenToonz installation to the same folder asOpenToonz.exe
- If there is no
srvfolder, OpenToonz can still be used. However, various file formats such asmovcannot be used. - Creating the files for
srvis discussed later.
If a previous binary of OpenToonz was already installed, this step and the following about creating a registry key has already been dealt with. So feel free to skip these parts.
- Copy the files from
$opentoonz/stuffto an appropriate folder.
- Using the registry editor, create the following key and copy the path of the
$opentoonz/stufffolder from above to it.
- HKEY_LOCAL_MACHINE\SOFTWARE\OpenToonz\OpenToonz\TOONZROOT
OpenToonz.exe can now be run. Congratulations!
- In the Solution Explorer, select the OpenToonz project within the OpenToonz solution.
- In the Project menu, choose Set as StartUp Project.
OpenToonz utilizes the QuickTime SDK's mov and associated file formats. Since the QuickTime SDK only comes in 32-bit versions, the 32-bit file t32bitsrv.exe from the QuickTime SDK is used in both the 64-bit and 32-bit versions of OpenToonz. As a result, the following instructions apply to both the 32 and 64-bit versions of OpenToonz.
- https://www.qt.io/download-open-source/
- Install Qt 5.x (32-bit version) by the by Qt Online Installer for Windows.
- Sign in using your Apple developer ID and download
QuickTime 7.3 SDK for Windows.zipfrom the following url.
- After installing the QuickTime SDK, copy the contents of
C:\Program Files (x86)\QuickTime SDKto$opentoonz/thirdparty/quicktime/QT73SDK
- Follow the same instructions as for the 64-bit version, but change the following:
$opentoonz/toonz/buildto$opentoonz/toonz/build32Visual Studio 16 2019 x64toVisual Studio 16 2019 Win32
- Change
QT_PATHto the path of your 32-bit version of Qt
- Open
$opentoonz/toonz/build32/OpenToonz.sln
- For the 64-bit version, copy the following files to the
srvfolder:- From
$opentoonz/toonz/build32/Release- t32bitsrv.exe
- image.dll
- tnzbase.dll
- tnzcore.dll
- tnzext.dll
- toonzlib.dll
- From the 32-bit version of Qt
- run
windeployqtto obtain required libraries - additionally, Qt5Gui.dll
- run
$opentoonz/thirdparty/glut/3.7.6/lib/glut32.dll
- From
Qt translation files are generated first from the source code to .ts files, then from .ts files to a .qm file. These files can be created in Visual Studio if the translation_ project and Build translation_??? only (translation_???のみをビルド」) is used. These files are not created in the default Build Project Solution.