hashirama/goldendict-ng
hashirama/goldendict-ng
0
0
Fork 0
mirror of https://github.com/xiaoyifang/goldendict-ng.git synced 2024-11-24 16:54:08 +00:00
Code Issues Actions 1 Projects Releases Wiki Activity
goldendict-ng/goldendict.vcxproj

1329 lines
81 KiB
XML
Raw Normal View History

Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<?xml version="1.0" encoding="utf-8"?>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ItemGroup Label="ProjectConfigurations">
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ProjectConfiguration Include="Release|x64">
<Configuration>Release</Configuration>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<Platform>x64</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="Debug|x64">
<Configuration>Debug</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
</ItemGroup>
<PropertyGroup Label="Globals">
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ProjectGuid>{099B3DB8-81EE-3E0D-9C12-CB2AE08A1574}</ProjectGuid>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<RootNamespace>GoldenDict</RootNamespace>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<Keyword>QtVS_v304</Keyword>
<WindowsTargetPlatformVersion>10.0.19041.0</WindowsTargetPlatformVersion>
<WindowsTargetPlatformMinVersion>10.0.19041.0</WindowsTargetPlatformMinVersion>
rename qt4x5.hh to utils.hh the filename qt4x5 is not proper now,for the qt4 version can never meet.and the qt5 is actually mean qt>5 .
2021-11-27 07:17:33 +00:00
<QtMsBuild Condition="'$(QtMsBuild)'=='' or !Exists('$(QtMsBuild)\qt.targets')">$(MSBuildProjectDirectory)\QtMsBuild</QtMsBuild>
</PropertyGroup>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'" Label="Configuration">
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<PlatformToolset>v140</PlatformToolset>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<OutputDirectory>release\</OutputDirectory>
<ATLMinimizesCRunTimeLibraryUsage>false</ATLMinimizesCRunTimeLibraryUsage>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<CharacterSet>NotSet</CharacterSet>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ConfigurationType>Application</ConfigurationType>
<IntermediateDirectory>build\</IntermediateDirectory>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<PrimaryOutput>GoldenDict</PrimaryOutput>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'" Label="Configuration">
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<PlatformToolset>v140</PlatformToolset>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<OutputDirectory>debug\</OutputDirectory>
<ATLMinimizesCRunTimeLibraryUsage>false</ATLMinimizesCRunTimeLibraryUsage>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<CharacterSet>NotSet</CharacterSet>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ConfigurationType>Application</ConfigurationType>
<IntermediateDirectory>build\</IntermediateDirectory>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<PrimaryOutput>GoldenDict</PrimaryOutput>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
</PropertyGroup>
rename qt4x5.hh to utils.hh the filename qt4x5 is not proper now,for the qt4 version can never meet.and the qt5 is actually mean qt>5 .
2021-11-27 07:17:33 +00:00
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
<Target Name="QtMsBuildNotFound" BeforeTargets="CustomBuild;ClCompile" Condition="!Exists('$(QtMsBuild)\qt.targets') or !Exists('$(QtMsBuild)\qt.props')">
<Message Importance="High" Text="QtMsBuild: could not locate qt.targets, qt.props; project may not build correctly." />
</Target>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ImportGroup Label="ExtensionSettings" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" />
</ImportGroup>
<ImportGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'" Label="PropertySheets">
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" />
</ImportGroup>
rename qt4x5.hh to utils.hh the filename qt4x5 is not proper now,for the qt4 version can never meet.and the qt5 is actually mean qt>5 .
2021-11-27 07:17:33 +00:00
<PropertyGroup Label="UserMacros" />
<ImportGroup Condition="Exists('$(QtMsBuild)\qt_defaults.props')">
<Import Project="$(QtMsBuild)\qt_defaults.props" />
</ImportGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
<OutDir>debug\</OutDir>
<IntDir>build\</IntDir>
<TargetName>GoldenDict</TargetName>
<IgnoreImportLibrary>true</IgnoreImportLibrary>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
<OutDir>release\</OutDir>
<IntDir>build\</IntDir>
<TargetName>GoldenDict</TargetName>
<IgnoreImportLibrary>true</IgnoreImportLibrary>
<LinkIncremental>false</LinkIncremental>
</PropertyGroup>
<PropertyGroup Label="QtSettings" Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
<QtInstall>5.15.2_msvc2019_64</QtInstall>
<QtModules>core;xml;sql;network;gui;svg;help;multimedia;widgets;qml;positioning;printsupport;webchannel;quick;webengine;webenginewidgets</QtModules>
</PropertyGroup>
<PropertyGroup Label="QtSettings" Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
<QtInstall>5.15.2_msvc2019_64</QtInstall>
<QtModules>core;xml;sql;network;gui;svg;help;multimedia;widgets;qml;positioning;printsupport;webchannel;quick;webengine;webenginewidgets</QtModules>
</PropertyGroup>
<ImportGroup Condition="Exists('$(QtMsBuild)\qt.props')">
<Import Project="$(QtMsBuild)\qt.props" />
</ImportGroup>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
<ClCompile>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<AdditionalIncludeDirectories>.;winlibs\include;qtsingleapplication\src;build;/include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
<AdditionalOptions>-Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -w34100 -w34189 -w44996 -w44456 -w44457 -w44458 %(AdditionalOptions)</AdditionalOptions>
<AssemblerListingLocation>build\</AssemblerListingLocation>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<BrowseInformation>false</BrowseInformation>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<DebugInformationFormat>None</DebugInformationFormat>
<DisableSpecificWarnings>4290;4577;4467;%(DisableSpecificWarnings)</DisableSpecificWarnings>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ExceptionHandling>Sync</ExceptionHandling>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ObjectFileName>build\</ObjectFileName>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<Optimization>MaxSpeed</Optimization>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<PreprocessorDefinitions>_WINDOWS;UNICODE;_UNICODE;WIN32;_ENABLE_EXTENDED_ALIGNED_STORAGE;WIN64;MAKE_QTMULTIMEDIA_PLAYER;MAKE_FFMPEG_PLAYER;__WIN32;_CRT_SECURE_NO_WARNINGS;NOMINMAX;__WIN64;GD_NO_MANIFEST;NO_CONSOLE;PROGRAM_VERSION="1.5.0";MAKE_ZIM_SUPPORT;MAKE_EXTRA_TIFF_HANDLER;MAKE_CHINESE_CONVERSION_SUPPORT;QT_QTSINGLEAPPLICATION_IMPORT;NDEBUG;QT_NO_DEBUG;QT_QMLMODELS_LIB;%(PreprocessorDefinitions)</PreprocessorDefinitions>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<PreprocessToFile>false</PreprocessToFile>
rename qt4x5.hh to utils.hh the filename qt4x5 is not proper now,for the qt4 version can never meet.and the qt5 is actually mean qt>5 .
2021-11-27 07:17:33 +00:00
<ProgramDataBaseFileName>
</ProgramDataBaseFileName>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
<RuntimeTypeInfo>true</RuntimeTypeInfo>
<SuppressStartupBanner>true</SuppressStartupBanner>
<TreatWChar_tAsBuiltInType>true</TreatWChar_tAsBuiltInType>
<WarningLevel>Level3</WarningLevel>
rename qt4x5.hh to utils.hh the filename qt4x5 is not proper now,for the qt4 version can never meet.and the qt5 is actually mean qt>5 .
2021-11-27 07:17:33 +00:00
<MultiProcessorCompilation>true</MultiProcessorCompilation>
</ClCompile>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<Link>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<AdditionalDependencies>z.lib;bz2.lib;lzo2.lib;shell32.lib;user32.lib;sapi.lib;.\winlibs\lib\msvc\hunspell.lib;.\winlibs\lib\msvc\iconv.lib;wsock32.lib;psapi.lib;ole32.lib;oleaut32.lib;advapi32.lib;comdlg32.lib;.\winlibs\lib\msvc\vorbisfile.lib;.\winlibs\lib\msvc\vorbis.lib;.\winlibs\lib\msvc\ogg.lib;.\winlibs\lib\msvc\ao.lib;.\winlibs\lib\msvc\swresample-gd.lib;.\winlibs\lib\msvc\avutil-gd.lib;.\winlibs\lib\msvc\avformat-gd.lib;.\winlibs\lib\msvc\avcodec-gd.lib;uxtheme.lib;.\winlibs\lib\msvc\lzma.lib;zstd.lib;.\winlibs\lib\msvc\tiff.lib;.\winlibs\lib\msvc\eb.lib;.\winlibs\lib\msvc\opencc.lib;.\qtsingleapplication\lib\QtSolutions_SingleApplication-head.lib;$(QTDIR)\lib\Qt5QmlModels.lib;shell32.lib;%(AdditionalDependencies)</AdditionalDependencies>
<AdditionalLibraryDirectories>.\winlibs\lib\msvc;.\qtsingleapplication\lib;C:\openssl\lib;C:\Utils\my_sql\mysql-5.7.25-winx64\lib;C:\Utils\postgresql\pgsql\lib;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<AdditionalOptions>"/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" %(AdditionalOptions)</AdditionalOptions>
<DataExecutionPrevention>true</DataExecutionPrevention>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<EnableCOMDATFolding>true</EnableCOMDATFolding>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<GenerateDebugInformation>false</GenerateDebugInformation>
<IgnoreImportLibrary>true</IgnoreImportLibrary>
<LinkIncremental>false</LinkIncremental>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<OptimizeReferences>true</OptimizeReferences>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<OutputFile>$(OutDir)\GoldenDict.exe</OutputFile>
<RandomizedBaseAddress>true</RandomizedBaseAddress>
<SubSystem>Windows</SubSystem>
<SuppressStartupBanner>true</SuppressStartupBanner>
<Version>1.5</Version>
</Link>
<Midl>
<DefaultCharType>Unsigned</DefaultCharType>
<EnableErrorChecks>None</EnableErrorChecks>
<WarningLevel>0</WarningLevel>
</Midl>
<ResourceCompile>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<PreprocessorDefinitions>_WINDOWS;UNICODE;_UNICODE;WIN32;_ENABLE_EXTENDED_ALIGNED_STORAGE;WIN64;MAKE_QTMULTIMEDIA_PLAYER;MAKE_FFMPEG_PLAYER;__WIN32;_CRT_SECURE_NO_WARNINGS;NOMINMAX;__WIN64;GD_NO_MANIFEST;NO_CONSOLE;PROGRAM_VERSION=\"1.5.0\";MAKE_ZIM_SUPPORT;MAKE_EXTRA_TIFF_HANDLER;MAKE_CHINESE_CONVERSION_SUPPORT;QT_QTSINGLEAPPLICATION_IMPORT;NDEBUG;QT_NO_DEBUG;QT_SVG_LIB;QT_WEBENGINEWIDGETS_LIB;QT_PRINTSUPPORT_LIB;QT_HELP_LIB;QT_WIDGETS_LIB;QT_WEBENGINECORE_LIB;QT_QUICK_LIB;QT_MULTIMEDIA_LIB;QT_GUI_LIB;QT_XML_LIB;QT_QMLMODELS_LIB;QT_WEBCHANNEL_LIB;QT_QML_LIB;QT_NETWORK_LIB;QT_POSITIONING_LIB;QT_SQL_LIB;QT_CORE_LIB;%(PreprocessorDefinitions)</PreprocessorDefinitions>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
</ResourceCompile>
rename qt4x5.hh to utils.hh the filename qt4x5 is not proper now,for the qt4 version can never meet.and the qt5 is actually mean qt>5 .
2021-11-27 07:17:33 +00:00
<QtRcc>
<Compression>default</Compression>
<ExecutionDescription>Rcc'ing %(Identity)...</ExecutionDescription>
<QtRccDir>build</QtRccDir>
<QtRccFileName>qrc_%(Filename).cpp</QtRccFileName>
</QtRcc>
<QtMoc>
<CompilerFlavor>msvc</CompilerFlavor>
<Include>./build/moc_predefs.h</Include>
<ExecutionDescription>Moc'ing %(Identity)...</ExecutionDescription>
<DynamicSource>output</DynamicSource>
<QtMocDir>build</QtMocDir>
<QtMocFileName>moc_%(Filename).cpp</QtMocFileName>
</QtMoc>
<QtUic>
<ExecutionDescription>Uic'ing %(Identity)...</ExecutionDescription>
<QtUicDir>build</QtUicDir>
<QtUicFileName>ui_%(Filename).h</QtUicFileName>
</QtUic>
</ItemDefinitionGroup>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
<ClCompile>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<AdditionalIncludeDirectories>.;winlibs\include;qtsingleapplication\src;build;/include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
<AdditionalOptions>-Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -w34100 -w34189 -w44996 -w44456 -w44457 -w44458 %(AdditionalOptions)</AdditionalOptions>
<AssemblerListingLocation>build\</AssemblerListingLocation>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<BrowseInformation>false</BrowseInformation>
<DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<DisableSpecificWarnings>4290;4577;4467;%(DisableSpecificWarnings)</DisableSpecificWarnings>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ExceptionHandling>Sync</ExceptionHandling>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ObjectFileName>build\</ObjectFileName>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<Optimization>Disabled</Optimization>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<PreprocessorDefinitions>_CONSOLE;UNICODE;_UNICODE;WIN32;_ENABLE_EXTENDED_ALIGNED_STORAGE;WIN64;MAKE_QTMULTIMEDIA_PLAYER;MAKE_FFMPEG_PLAYER;__WIN32;_CRT_SECURE_NO_WARNINGS;NOMINMAX;__WIN64;GD_NO_MANIFEST;PROGRAM_VERSION="1.5.0";MAKE_ZIM_SUPPORT;MAKE_EXTRA_TIFF_HANDLER;MAKE_CHINESE_CONVERSION_SUPPORT;QT_QTSINGLEAPPLICATION_IMPORT;QT_QMLMODELS_LIB;%(PreprocessorDefinitions)</PreprocessorDefinitions>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<PreprocessToFile>false</PreprocessToFile>
<RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
<RuntimeTypeInfo>true</RuntimeTypeInfo>
<SuppressStartupBanner>true</SuppressStartupBanner>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<TreatWChar_tAsBuiltInType>true</TreatWChar_tAsBuiltInType>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<WarningLevel>Level3</WarningLevel>
rename qt4x5.hh to utils.hh the filename qt4x5 is not proper now,for the qt4 version can never meet.and the qt5 is actually mean qt>5 .
2021-11-27 07:17:33 +00:00
<MultiProcessorCompilation>true</MultiProcessorCompilation>
</ClCompile>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<Link>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<AdditionalDependencies>z.lib;bz2.lib;lzo2.lib;shell32.lib;user32.lib;sapi.lib;.\winlibs\lib\msvc\hunspelld.lib;.\winlibs\lib\msvc\iconv.lib;wsock32.lib;psapi.lib;ole32.lib;oleaut32.lib;advapi32.lib;comdlg32.lib;.\winlibs\lib\msvc\vorbisfile.lib;.\winlibs\lib\msvc\vorbis.lib;.\winlibs\lib\msvc\ogg.lib;.\winlibs\lib\msvc\ao.lib;.\winlibs\lib\msvc\swresample-gd.lib;.\winlibs\lib\msvc\avutil-gd.lib;.\winlibs\lib\msvc\avformat-gd.lib;.\winlibs\lib\msvc\avcodec-gd.lib;uxtheme.lib;.\winlibs\lib\msvc\lzma.lib;zstd.lib;.\winlibs\lib\msvc\tiff.lib;.\winlibs\lib\msvc\eb.lib;.\winlibs\lib\msvc\openccd.lib;.\qtsingleapplication\lib\QtSolutions_SingleApplication-headd.lib;$(QTDIR)\lib\Qt5QmlModelsd.lib;%(AdditionalDependencies)</AdditionalDependencies>
<AdditionalLibraryDirectories>.\winlibs\lib\msvc;.\qtsingleapplication\lib;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<AdditionalOptions>"/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" %(AdditionalOptions)</AdditionalOptions>
<DataExecutionPrevention>true</DataExecutionPrevention>
<GenerateDebugInformation>true</GenerateDebugInformation>
<IgnoreImportLibrary>true</IgnoreImportLibrary>
<OutputFile>$(OutDir)\GoldenDict.exe</OutputFile>
<RandomizedBaseAddress>true</RandomizedBaseAddress>
<SubSystem>Console</SubSystem>
<SuppressStartupBanner>true</SuppressStartupBanner>
<Version>1.5</Version>
</Link>
<Midl>
<DefaultCharType>Unsigned</DefaultCharType>
<EnableErrorChecks>None</EnableErrorChecks>
<WarningLevel>0</WarningLevel>
</Midl>
<ResourceCompile>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<PreprocessorDefinitions>_CONSOLE;UNICODE;_UNICODE;WIN32;_ENABLE_EXTENDED_ALIGNED_STORAGE;WIN64;MAKE_QTMULTIMEDIA_PLAYER;MAKE_FFMPEG_PLAYER;__WIN32;_CRT_SECURE_NO_WARNINGS;NOMINMAX;__WIN64;GD_NO_MANIFEST;PROGRAM_VERSION=\"1.5.0\";MAKE_ZIM_SUPPORT;MAKE_EXTRA_TIFF_HANDLER;MAKE_CHINESE_CONVERSION_SUPPORT;QT_QTSINGLEAPPLICATION_IMPORT;QT_SVG_LIB;QT_WEBENGINEWIDGETS_LIB;QT_PRINTSUPPORT_LIB;QT_HELP_LIB;QT_WIDGETS_LIB;QT_WEBENGINECORE_LIB;QT_QUICK_LIB;QT_MULTIMEDIA_LIB;QT_GUI_LIB;QT_XML_LIB;QT_QMLMODELS_LIB;QT_WEBCHANNEL_LIB;QT_QML_LIB;QT_NETWORK_LIB;QT_POSITIONING_LIB;QT_SQL_LIB;QT_CORE_LIB;_DEBUG;%(PreprocessorDefinitions)</PreprocessorDefinitions>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
</ResourceCompile>
rename qt4x5.hh to utils.hh the filename qt4x5 is not proper now,for the qt4 version can never meet.and the qt5 is actually mean qt>5 .
2021-11-27 07:17:33 +00:00
<QtMoc>
<CompilerFlavor>msvc</CompilerFlavor>
<Include>./build/moc_predefs.h</Include>
<ExecutionDescription>Moc'ing %(Identity)...</ExecutionDescription>
<DynamicSource>output</DynamicSource>
<QtMocDir>build</QtMocDir>
<QtMocFileName>moc_%(Filename).cpp</QtMocFileName>
</QtMoc>
<QtRcc>
<Compression>default</Compression>
<ExecutionDescription>Rcc'ing %(Identity)...</ExecutionDescription>
<QtRccDir>build</QtRccDir>
<QtRccFileName>qrc_%(Filename).cpp</QtRccFileName>
</QtRcc>
<QtUic>
<ExecutionDescription>Uic'ing %(Identity)...</ExecutionDescription>
<QtUicDir>build</QtUicDir>
<QtUicFileName>ui_%(Filename).h</QtUicFileName>
</QtUic>
</ItemDefinitionGroup>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ItemGroup>
<ClCompile Include="mouseover_win32\ThTypes.c" />
<ClCompile Include="aard.cc" />
<ClCompile Include="about.cc" />
<ClCompile Include="article_maker.cc" />
<ClCompile Include="article_netmgr.cc" />
<ClCompile Include="articleview.cc" />
<ClCompile Include="articlewebview.cc" />
<ClCompile Include="atomic_rename.cc" />
<ClCompile Include="audiolink.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="audioplayerfactory.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="belarusiantranslit.cc" />
<ClCompile Include="bgl.cc" />
<ClCompile Include="bgl_babylon.cc" />
<ClCompile Include="broken_xrecord.cc" />
<ClCompile Include="btreeidx.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="chinese.cc" />
<ClCompile Include="chineseconversion.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="chunkedstorage.cc" />
<ClCompile Include="config.cc" />
<ClCompile Include="country.cc" />
<ClCompile Include="decompress.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="delegate.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="dictdfiles.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="dictheadwords.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="dictinfo.cc" />
<ClCompile Include="dictionary.cc" />
<ClCompile Include="dictionarybar.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="dictserver.cc" />
<ClCompile Include="dictzip.c" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="dsl.cc" />
<ClCompile Include="dsl_details.cc" />
<ClCompile Include="editdictionaries.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="epwing.cc" />
<ClCompile Include="epwing_book.cc" />
<ClCompile Include="epwing_charmap.cc" />
<ClCompile Include="externalaudioplayer.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="externalviewer.cc" />
<ClCompile Include="extlineedit.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="favoritespanewidget.cc" />
<ClCompile Include="ffmpegaudio.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="file.cc" />
<ClCompile Include="filetype.cc" />
<ClCompile Include="folding.cc" />
<ClCompile Include="forvo.cc" />
<ClCompile Include="fsencoding.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="ftshelpers.cc" />
<ClCompile Include="fulltextsearch.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="gdappstyle.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="gddebug.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="german.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="gestures.cc" />
<ClCompile Include="gico_schemahandler.cpp" />
<ClCompile Include="gls.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="greektranslit.cc" />
<ClCompile Include="groupcombobox.cc" />
<ClCompile Include="groups.cc" />
<ClCompile Include="groups_widgets.cc" />
<ClCompile Include="guids.c" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="helpwindow.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="history.cc" />
<ClCompile Include="historypanewidget.cc" />
<ClCompile Include="hotkeyedit.cc" />
<ClCompile Include="hotkeywrapper.cc" />
<ClCompile Include="htmlescape.cc" />
<ClCompile Include="hunspell.cc" />
<ClCompile Include="iconv.cc" />
<ClCompile Include="indexedzip.cc" />
<ClCompile Include="initializing.cc" />
<ClCompile Include="instances.cc" />
<ClCompile Include="keyboardstate.cc" />
<ClCompile Include="langcoder.cc" />
<ClCompile Include="language.cc" />
<ClCompile Include="loaddictionaries.cc" />
<ClCompile Include="lsa.cc" />
<ClCompile Include="main.cc" />
<ClCompile Include="mainstatusbar.cc" />
<ClCompile Include="maintabwidget.cc" />
<ClCompile Include="mainwindow.cc" />
<ClCompile Include="mdictparser.cc" />
<ClCompile Include="mdx.cc" />
<ClCompile Include="mediawiki.cc" />
<ClCompile Include="mouseover.cc" />
<ClCompile Include="mruqmenu.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="multimediaaudioplayer.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="mutex.cc" />
<ClCompile Include="orderandprops.cc" />
<ClCompile Include="parsecmdline.cc" />
<ClCompile Include="preferences.cc" />
<ClCompile Include="processwrapper.cc" />
<ClCompile Include="programs.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="ripemd.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="romaji.cc" />
<ClCompile Include="russiantranslit.cc" />
<ClCompile Include="scanpopup.cc" />
<ClCompile Include="sdict.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="slob.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="sounddir.cc" />
<ClCompile Include="sources.cc" />
<ClCompile Include="speechclient_win.cc" />
<ClCompile Include="speechhlp.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="splitfile.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="stardict.cc" />
<ClCompile Include="stylescombobox.cc" />
<ClCompile Include="termination.cc" />
<ClCompile Include="texttospeechsource.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="tiff.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="translatebox.cc" />
<ClCompile Include="transliteration.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="treeview.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="ufile.cc" />
<ClCompile Include="utf8.cc" />
<ClCompile Include="voiceengines.cc" />
<ClCompile Include="webmultimediadownload.cc" />
<ClCompile Include="website.cc" />
update visual studio project files.
2021-12-14 15:16:56 +00:00
<ClCompile Include="weburlrequestinterceptor.cpp" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="wildcard.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="wordbyauto.cc" />
<ClCompile Include="wordfinder.cc" />
<ClCompile Include="wordlist.cc" />
<ClCompile Include="wstring.cc" />
<ClCompile Include="wstring_qt.cc" />
<ClCompile Include="x64.cc" />
<ClCompile Include="xdxf.cc" />
<ClCompile Include="xdxf2html.cc" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClCompile Include="zim.cc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClCompile Include="zipfile.cc" />
<ClCompile Include="zipsounds.cc" />
</ItemGroup>
<ItemGroup>
<ClInclude Include="mouseover_win32\ThTypes.h" />
<ClInclude Include="aard.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="about.hh">
</QtMoc>
<QtMoc Include="article_maker.hh">
</QtMoc>
<QtMoc Include="article_netmgr.hh">
</QtMoc>
<QtMoc Include="articleview.hh">
</QtMoc>
<QtMoc Include="articlewebview.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="atomic_rename.hh" />
<ClInclude Include="audiolink.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClInclude Include="audioplayerfactory.hh" />
<QtMoc Include="audioplayerinterface.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="belarusiantranslit.hh" />
<ClInclude Include="bgl.hh" />
<ClInclude Include="bgl_babylon.hh" />
<ClInclude Include="broken_xrecord.hh" />
<ClInclude Include="btreeidx.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClInclude Include="chinese.hh" />
<QtMoc Include="chineseconversion.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="chunkedstorage.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="config.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="country.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClInclude Include="cpp_features.hh" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="decompress.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClInclude Include="delegate.hh" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="dictdfiles.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="dictheadwords.hh">
</QtMoc>
<QtMoc Include="dictinfo.hh">
</QtMoc>
<QtMoc Include="dictionary.hh">
</QtMoc>
<QtMoc Include="dictionarybar.hh">
</QtMoc>
<ClInclude Include="dictserver.hh" />
<QtMoc Include="dictspanewidget.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="dictzip.h" />
<ClInclude Include="dsl.hh" />
<ClInclude Include="dsl_details.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="editdictionaries.hh">
</QtMoc>
<ClInclude Include="epwing.hh" />
<ClInclude Include="epwing_book.hh" />
<ClInclude Include="epwing_charmap.hh" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="ex.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="externalaudioplayer.hh">
</QtMoc>
<QtMoc Include="externalviewer.hh">
</QtMoc>
<QtMoc Include="extlineedit.hh">
</QtMoc>
<QtMoc Include="favoritespanewidget.hh">
</QtMoc>
<QtMoc Include="ffmpegaudio.hh">
</QtMoc>
<QtMoc Include="ffmpegaudioplayer.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="file.hh" />
<ClInclude Include="filetype.hh" />
<ClInclude Include="folding.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="forvo.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="fsencoding.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClInclude Include="ftshelpers.hh" />
<QtMoc Include="fulltextsearch.hh">
</QtMoc>
<QtMoc Include="gdappstyle.hh">
</QtMoc>
<ClInclude Include="gddebug.hh" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="german.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClInclude Include="gestures.hh" />
<QtMoc Include="gico_schemahandler.h">
</QtMoc>
<ClInclude Include="gls.hh" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="greektranslit.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="groupcombobox.hh">
</QtMoc>
<QtMoc Include="groups.hh">
</QtMoc>
<QtMoc Include="groups_widgets.hh">
</QtMoc>
<QtMoc Include="helpwindow.hh">
</QtMoc>
<QtMoc Include="history.hh">
</QtMoc>
<QtMoc Include="historypanewidget.hh">
</QtMoc>
<QtMoc Include="hotkeyedit.hh">
</QtMoc>
<ClInclude Include="hotkeys.h" />
<QtMoc Include="hotkeywrapper.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="htmlescape.hh" />
<ClInclude Include="hunspell.hh" />
<ClInclude Include="iconv.hh" />
<ClInclude Include="inc_case_folding.hh" />
<ClInclude Include="inc_diacritic_folding.hh" />
<ClInclude Include="indexedzip.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="initializing.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="instances.hh" />
<ClInclude Include="keyboardstate.hh" />
<ClInclude Include="langcoder.hh" />
<ClInclude Include="language.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="loaddictionaries.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="lsa.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="mainstatusbar.hh">
</QtMoc>
<QtMoc Include="maintabwidget.hh">
</QtMoc>
<QtMoc Include="mainwindow.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="mdictparser.hh" />
<ClInclude Include="mdx.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="mediawiki.hh">
</QtMoc>
<QtMoc Include="mouseover.hh">
</QtMoc>
<QtMoc Include="mruqmenu.hh">
</QtMoc>
<QtMoc Include="multimediaaudioplayer.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="mutex.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="orderandprops.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="parsecmdline.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="preferences.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="processwrapper.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="programs.hh">
</QtMoc>
rename qt4x5.hh to utils.hh the filename qt4x5 is not proper now,for the qt4 version can never meet.and the qt5 is actually mean qt>5 .
2021-11-27 07:17:33 +00:00
<ClInclude Include="utils.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClInclude Include="ripemd.hh" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="romaji.hh" />
<ClInclude Include="russiantranslit.hh" />
<ClInclude Include="sapi.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="scanpopup.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="sdict.hh" />
<ClInclude Include="searchpanewidget.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClInclude Include="slob.hh" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="sounddir.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="sources.hh">
</QtMoc>
<QtMoc Include="speechclient.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="speechhlp.hh" />
<ClInclude Include="sphelper.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClInclude Include="splitfile.hh" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="sptr.hh" />
<ClInclude Include="stardict.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="stylescombobox.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="termination.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="texttospeechsource.hh">
</QtMoc>
<ClInclude Include="tiff.hh" />
<QtMoc Include="translatebox.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="transliteration.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClInclude Include="treeview.hh" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="ufile.hh" />
<ClInclude Include="uiauto.hh" />
<ClInclude Include="utf8.hh" />
<ClInclude Include="voiceengines.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="webmultimediadownload.hh">
</QtMoc>
<QtMoc Include="website.hh">
</QtMoc>
update visual studio project files.
2021-12-14 15:16:56 +00:00
<QtMoc Include="weburlrequestinterceptor.h" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClInclude Include="wildcard.hh" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="wordbyauto.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtMoc Include="wordfinder.hh">
</QtMoc>
<QtMoc Include="wordlist.hh">
</QtMoc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="wstring.hh" />
<ClInclude Include="wstring_qt.hh" />
<ClInclude Include="x64.hh" />
<ClInclude Include="xdxf.hh" />
<ClInclude Include="xdxf2html.hh" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ClInclude Include="zim.hh" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<ClInclude Include="zipfile.hh" />
<ClInclude Include="zipsounds.hh" />
</ItemGroup>
<ItemGroup>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<CustomBuild Include="build\moc_predefs.h.cbt">
<FileType>Document</FileType>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)\mkspecs\features\data\dummy.cpp;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">cl -Bx"$(QTDIR)\bin\qmake.exe" -nologo -Zc:wchar_t -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew /wd4290 -O2 -MD -EHsc -GR -W3 -w34100 -w34189 -w44996 -w44456 -w44457 -w44458 -wd4577 -wd4467 -E $(QTDIR)\mkspecs\features\data\dummy.cpp 2&gt;NUL &gt;build\moc_predefs.h</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">Generate moc_predefs.h</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">build\moc_predefs.h;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)\mkspecs\features\data\dummy.cpp;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">cl -Bx"$(QTDIR)\bin\qmake.exe" -nologo -Zc:wchar_t -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew /wd4290 -Zi -MDd -EHsc -GR -W3 -w34100 -w34189 -w44996 -w44456 -w44457 -w44458 -wd4577 -wd4467 -E $(QTDIR)\mkspecs\features\data\dummy.cpp 2&gt;NUL &gt;build\moc_predefs.h</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">Generate moc_predefs.h</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">build\moc_predefs.h;%(Outputs)</Outputs>
</CustomBuild>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
</ItemGroup>
<ItemGroup>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<CustomBuild Include="locale\ar_SA.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\ar_SA.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\ar_SA.ts -qm locale\ar_SA.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\ar_SA.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\ar_SA.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\ar_SA.ts -qm locale\ar_SA.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\ar_SA.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\ay_WI.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\ay_WI.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\ay_WI.ts -qm locale\ay_WI.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\ay_WI.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\ay_WI.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\ay_WI.ts -qm locale\ay_WI.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\ay_WI.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\be_BY.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\be_BY.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\be_BY.ts -qm locale\be_BY.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\be_BY.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\be_BY.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\be_BY.ts -qm locale\be_BY.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\be_BY.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\be_BY@latin.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\be_BY@latin.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\be_BY@latin.ts -qm locale\be_BY@latin.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\be_BY@latin.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\be_BY@latin.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\be_BY@latin.ts -qm locale\be_BY@latin.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\be_BY@latin.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\bg_BG.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\bg_BG.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\bg_BG.ts -qm locale\bg_BG.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\bg_BG.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\bg_BG.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\bg_BG.ts -qm locale\bg_BG.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\bg_BG.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\cs_CZ.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\cs_CZ.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\cs_CZ.ts -qm locale\cs_CZ.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\cs_CZ.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\cs_CZ.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\cs_CZ.ts -qm locale\cs_CZ.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\cs_CZ.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\de_DE.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\de_DE.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\de_DE.ts -qm locale\de_DE.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\de_DE.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\de_DE.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\de_DE.ts -qm locale\de_DE.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\de_DE.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\el_GR.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\el_GR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\el_GR.ts -qm locale\el_GR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\el_GR.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\el_GR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\el_GR.ts -qm locale\el_GR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\el_GR.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\eo_EO.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\eo_EO.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\eo_EO.ts -qm locale\eo_EO.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\eo_EO.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\eo_EO.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\eo_EO.ts -qm locale\eo_EO.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\eo_EO.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\es_AR.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\es_AR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\es_AR.ts -qm locale\es_AR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\es_AR.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\es_AR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\es_AR.ts -qm locale\es_AR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\es_AR.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\es_BO.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\es_BO.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\es_BO.ts -qm locale\es_BO.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\es_BO.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\es_BO.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\es_BO.ts -qm locale\es_BO.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\es_BO.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\es_ES.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\es_ES.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\es_ES.ts -qm locale\es_ES.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\es_ES.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\es_ES.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\es_ES.ts -qm locale\es_ES.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\es_ES.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\fa_IR.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\fa_IR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\fa_IR.ts -qm locale\fa_IR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\fa_IR.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\fa_IR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\fa_IR.ts -qm locale\fa_IR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\fa_IR.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\fi_FI.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\fi_FI.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\fi_FI.ts -qm locale\fi_FI.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\fi_FI.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\fi_FI.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\fi_FI.ts -qm locale\fi_FI.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\fi_FI.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\fr_FR.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\fr_FR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\fr_FR.ts -qm locale\fr_FR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\fr_FR.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\fr_FR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\fr_FR.ts -qm locale\fr_FR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\fr_FR.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\hi_IN.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\hi_IN.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\hi_IN.ts -qm locale\hi_IN.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\hi_IN.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\hi_IN.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\hi_IN.ts -qm locale\hi_IN.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\hi_IN.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\ie_001.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\ie_001.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\ie_001.ts -qm locale\ie_001.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\ie_001.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\ie_001.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\ie_001.ts -qm locale\ie_001.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\ie_001.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\it_IT.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\it_IT.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\it_IT.ts -qm locale\it_IT.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\it_IT.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\it_IT.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\it_IT.ts -qm locale\it_IT.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\it_IT.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\ja_JP.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\ja_JP.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\ja_JP.ts -qm locale\ja_JP.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\ja_JP.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\ja_JP.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\ja_JP.ts -qm locale\ja_JP.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\ja_JP.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\jb_JB.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\jb_JB.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\jb_JB.ts -qm locale\jb_JB.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\jb_JB.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\jb_JB.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\jb_JB.ts -qm locale\jb_JB.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\jb_JB.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\ko_KR.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\ko_KR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\ko_KR.ts -qm locale\ko_KR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\ko_KR.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\ko_KR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\ko_KR.ts -qm locale\ko_KR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\ko_KR.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\lt_LT.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\lt_LT.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\lt_LT.ts -qm locale\lt_LT.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\lt_LT.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\lt_LT.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\lt_LT.ts -qm locale\lt_LT.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\lt_LT.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\mk_MK.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\mk_MK.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\mk_MK.ts -qm locale\mk_MK.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\mk_MK.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\mk_MK.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\mk_MK.ts -qm locale\mk_MK.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\mk_MK.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\nl_NL.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\nl_NL.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\nl_NL.ts -qm locale\nl_NL.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\nl_NL.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\nl_NL.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\nl_NL.ts -qm locale\nl_NL.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\nl_NL.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\pl_PL.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\pl_PL.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\pl_PL.ts -qm locale\pl_PL.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\pl_PL.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\pl_PL.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\pl_PL.ts -qm locale\pl_PL.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\pl_PL.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\pt_BR.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\pt_BR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\pt_BR.ts -qm locale\pt_BR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\pt_BR.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\pt_BR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\pt_BR.ts -qm locale\pt_BR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\pt_BR.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\qu_WI.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\qu_WI.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\qu_WI.ts -qm locale\qu_WI.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\qu_WI.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\qu_WI.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\qu_WI.ts -qm locale\qu_WI.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\qu_WI.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\ru_RU.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\ru_RU.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\ru_RU.ts -qm locale\ru_RU.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\ru_RU.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\ru_RU.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\ru_RU.ts -qm locale\ru_RU.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\ru_RU.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\sk_SK.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\sk_SK.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\sk_SK.ts -qm locale\sk_SK.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\sk_SK.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\sk_SK.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\sk_SK.ts -qm locale\sk_SK.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\sk_SK.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\sq_AL.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\sq_AL.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\sq_AL.ts -qm locale\sq_AL.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\sq_AL.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\sq_AL.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\sq_AL.ts -qm locale\sq_AL.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\sq_AL.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\sr_SR.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\sr_SR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\sr_SR.ts -qm locale\sr_SR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\sr_SR.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\sr_SR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\sr_SR.ts -qm locale\sr_SR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\sr_SR.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\sv_SE.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\sv_SE.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\sv_SE.ts -qm locale\sv_SE.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\sv_SE.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\sv_SE.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\sv_SE.ts -qm locale\sv_SE.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\sv_SE.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\tg_TJ.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\tg_TJ.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\tg_TJ.ts -qm locale\tg_TJ.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\tg_TJ.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\tg_TJ.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\tg_TJ.ts -qm locale\tg_TJ.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\tg_TJ.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\tk_TM.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\tk_TM.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\tk_TM.ts -qm locale\tk_TM.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\tk_TM.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\tk_TM.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\tk_TM.ts -qm locale\tk_TM.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\tk_TM.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\tr_TR.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\tr_TR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\tr_TR.ts -qm locale\tr_TR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\tr_TR.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\tr_TR.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\tr_TR.ts -qm locale\tr_TR.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\tr_TR.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\uk_UA.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\uk_UA.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\uk_UA.ts -qm locale\uk_UA.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\uk_UA.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\uk_UA.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\uk_UA.ts -qm locale\uk_UA.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\uk_UA.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\vi_VN.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\vi_VN.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\vi_VN.ts -qm locale\vi_VN.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\vi_VN.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\vi_VN.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\vi_VN.ts -qm locale\vi_VN.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\vi_VN.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\zh_CN.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\zh_CN.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\zh_CN.ts -qm locale\zh_CN.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\zh_CN.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\zh_CN.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\zh_CN.ts -qm locale\zh_CN.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\zh_CN.qm;%(Outputs)</Outputs>
</CustomBuild>
<CustomBuild Include="locale\zh_TW.ts">
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\zh_TW.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease locale\zh_TW.ts -qm locale\zh_TW.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Release|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Release|x64'">locale\zh_TW.qm;%(Outputs)</Outputs>
<AdditionalInputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\zh_TW.ts;%(AdditionalInputs)</AdditionalInputs>
<Command Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease locale\zh_TW.ts -qm locale\zh_TW.qm</Command>
<Message Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">$(QTDIR)/bin/lrelease</Message>
<Outputs Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">locale\zh_TW.qm;%(Outputs)</Outputs>
</CustomBuild>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
</ItemGroup>
<ItemGroup>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtUic Include="about.ui">
</QtUic>
<QtUic Include="articleview.ui">
</QtUic>
<QtUic Include="authentication.ui">
</QtUic>
<QtUic Include="chineseconversion.ui">
</QtUic>
<QtUic Include="dictgroupwidget.ui">
</QtUic>
<QtUic Include="dictheadwords.ui">
</QtUic>
<QtUic Include="dictinfo.ui">
</QtUic>
<QtUic Include="editdictionaries.ui">
</QtUic>
<QtUic Include="fulltextsearch.ui">
</QtUic>
<QtUic Include="groups.ui">
</QtUic>
<QtUic Include="initializing.ui">
</QtUic>
<QtUic Include="mainwindow.ui">
</QtUic>
<QtUic Include="orderandprops.ui">
</QtUic>
<QtUic Include="preferences.ui">
</QtUic>
<QtUic Include="scanpopup.ui">
</QtUic>
<QtUic Include="sources.ui">
</QtUic>
<QtUic Include="texttospeechsource.ui">
</QtUic>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
</ItemGroup>
<ItemGroup>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\1downarrow.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="CREDITS.txt" />
<None Include="flags\ad.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\addtab.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\ae.png" />
<None Include="flags\af.png" />
<None Include="flags\ag.png" />
<None Include="flags\ai.png" />
<None Include="flags\al.png" />
<None Include="flags\am.png" />
<None Include="flags\an.png" />
<None Include="flags\ao.png" />
<None Include="flags\ar.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\arrow.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="article-style-print.css" />
<None Include="article-style-st-babylon.css" />
<None Include="article-style-st-lingoes-blue.css" />
<None Include="article-style-st-lingoes.css" />
<None Include="article-style-st-lingvo.css" />
<None Include="article-style-st-modern.css" />
<None Include="article-style.css" />
<None Include="flags\as.png" />
<None Include="flags\at.png" />
<None Include="flags\au.png" />
<None Include="flags\aw.png" />
<None Include="flags\ax.png" />
<None Include="flags\az.png" />
<None Include="flags\ba.png" />
<None Include="flags\bb.png" />
<None Include="flags\bd.png" />
<None Include="flags\be.png" />
<None Include="flags\bf.png" />
<None Include="flags\bg.png" />
<None Include="flags\bh.png" />
<None Include="flags\bi.png" />
<None Include="flags\bj.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\blank.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\bm.png" />
<None Include="flags\bn.png" />
<None Include="flags\bo.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\book.png" />
<None Include="icons\bookcase.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\br.png" />
<None Include="flags\bs.png" />
<None Include="flags\bt.png" />
<None Include="flags\bv.png" />
<None Include="flags\bw.png" />
<None Include="flags\by.png" />
<None Include="flags\bz.png" />
<None Include="flags\ca.png" />
<None Include="flags\catalonia.png" />
<None Include="flags\cc.png" />
<None Include="flags\cd.png" />
<None Include="flags\cf.png" />
<None Include="flags\cg.png" />
<None Include="flags\ch.png" />
<None Include="flags\ci.png" />
<None Include="flags\ck.png" />
<None Include="flags\cl.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\clear.png" />
<None Include="icons\closetab.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\cm.png" />
<None Include="flags\cn.png" />
<None Include="flags\co.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\collapse_article.png" />
<None Include="icons\collapse_article_hovered.png" />
<None Include="icons\collapse_opt.png" />
<None Include="icons\configure.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\cr.png" />
<None Include="flags\cs.png" />
<None Include="flags\cu.png" />
<None Include="flags\cv.png" />
<None Include="flags\cx.png" />
<None Include="flags\cy.png" />
<None Include="flags\cz.png" />
<None Include="flags\de.png" />
<None Include="flags\dj.png" />
<None Include="flags\dk.png" />
<None Include="flags\dm.png" />
<None Include="flags\do.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\downarrow.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\dz.png" />
<None Include="flags\ec.png" />
<None Include="flags\ee.png" />
<None Include="flags\eg.png" />
<None Include="flags\eh.png" />
<None Include="flags\en.png" />
<None Include="flags\england.png" />
<None Include="flags\eo.png" />
<None Include="flags\er.png" />
<None Include="icons\error.png" />
<None Include="flags\es.png" />
<None Include="flags\et.png" />
<None Include="flags\europeanunion.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\expand_article.png" />
<None Include="icons\expand_article_hovered.png" />
<None Include="icons\expand_opt.png" />
<None Include="flags\fam.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\fi.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\fileopen.png" />
<None Include="icons\filesave.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\fj.png" />
<None Include="flags\fk.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtRcc Include="flags.qrc">
rename qt4x5.hh to utils.hh the filename qt4x5 is not proper now,for the qt4 version can never meet.and the qt5 is actually mean qt>5 .
2021-11-27 07:17:33 +00:00
<InitFuncName Condition="'$(Configuration)|$(Platform)'=='Release|x64'">flags</InitFuncName>
<InitFuncName Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">flags</InitFuncName>
</QtRcc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\fm.png" />
<None Include="flags\fo.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="flags\folder.png" />
<None Include="icons\folder.png" />
<None Include="icons\forvo.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\fr.png" />
<None Include="flags\ga.png" />
<None Include="flags\gb.png" />
<None Include="flags\gd.png" />
<None Include="flags\ge.png" />
<None Include="flags\gf.png" />
<None Include="flags\gh.png" />
<None Include="flags\gi.png" />
<None Include="flags\gl.png" />
<None Include="flags\gm.png" />
<None Include="flags\gn.png" />
<None Include="flags\gp.png" />
<None Include="flags\gq.png" />
<None Include="flags\gr.png" />
<None Include="flags\gs.png" />
<None Include="flags\gt.png" />
<None Include="flags\gu.png" />
<None Include="flags\gw.png" />
<None Include="flags\gy.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\highlighter.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\hk.png" />
<None Include="flags\hm.png" />
<None Include="flags\hn.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\home.png" />
<None Include="icons\hotkeys.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\hr.png" />
<None Include="flags\ht.png" />
<None Include="flags\hu.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\icon32_aard.png" />
<None Include="icons\icon32_bgl.png" />
<None Include="icons\icon32_dictd.png" />
<None Include="icons\icon32_dsl.png" />
<None Include="icons\icon32_epwing.png" />
<None Include="icons\icon32_gls.png" />
<None Include="icons\icon32_hunspell.png" />
<None Include="icons\icon32_lingoes.png" />
<None Include="icons\icon32_sdict.png" />
<None Include="icons\icon32_slob.png" />
<None Include="icons\icon32_stardict.png" />
<None Include="icons\icon32_wiki.png" />
<None Include="icons\icon32_xdxf.png" />
<None Include="icons\icon32_zim.png" />
<None Include="icons\icon32_zoombase.png" />
<None Include="icons\icon32_zoomin.png" />
<None Include="icons\icon32_zoomout.png" />
<None Include="icons\icon_dsl_native.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\id.png" />
<None Include="flags\ie.png" />
<None Include="flags\il.png" />
<None Include="flags\in.png" />
<None Include="icons\interface.png" />
<None Include="icons\internet.png" />
<None Include="flags\io.png" />
<None Include="flags\iq.png" />
<None Include="flags\ir.png" />
<None Include="flags\is.png" />
<None Include="flags\it.png" />
<None Include="flags\ja.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="flags\jb.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\jm.png" />
<None Include="flags\jo.png" />
<None Include="flags\jp.png" />
<None Include="flags\ke.png" />
<None Include="flags\kg.png" />
<None Include="flags\kh.png" />
<None Include="flags\ki.png" />
<None Include="flags\km.png" />
<None Include="flags\kn.png" />
<None Include="flags\kp.png" />
<None Include="flags\kr.png" />
<None Include="flags\kw.png" />
<None Include="flags\ky.png" />
<None Include="flags\kz.png" />
<None Include="flags\la.png" />
<None Include="flags\lb.png" />
<None Include="flags\lc.png" />
<None Include="flags\li.png" />
<None Include="flags\lk.png" />
<None Include="flags\lr.png" />
<None Include="flags\ls.png" />
<None Include="flags\lt.png" />
<None Include="flags\lu.png" />
<None Include="flags\lv.png" />
<None Include="flags\ly.png" />
<None Include="flags\ma.png" />
<None Include="icons\macicon.png" />
<None Include="flags\mc.png" />
<None Include="flags\md.png" />
<None Include="icons\mdict.png" />
<None Include="flags\me.png" />
<None Include="icons\menu_button.png" />
<None Include="flags\mg.png" />
<None Include="flags\mh.png" />
<None Include="flags\mk.png" />
<None Include="flags\ml.png" />
<None Include="flags\mm.png" />
<None Include="flags\mn.png" />
<None Include="flags\mo.png" />
<None Include="flags\mp.png" />
<None Include="flags\mq.png" />
<None Include="flags\mr.png" />
<None Include="flags\ms.png" />
<None Include="flags\mt.png" />
<None Include="flags\mu.png" />
<None Include="flags\mv.png" />
<None Include="flags\mw.png" />
<None Include="flags\mx.png" />
<None Include="flags\my.png" />
<None Include="flags\mz.png" />
<None Include="flags\na.png" />
<None Include="flags\nc.png" />
<None Include="flags\ne.png" />
<None Include="icons\network.png" />
<None Include="icons\next.png" />
<None Include="flags\nf.png" />
<None Include="flags\ng.png" />
<None Include="flags\ni.png" />
<None Include="flags\nl.png" />
<None Include="flags\no.png" />
<None Include="flags\np.png" />
<None Include="flags\nr.png" />
<None Include="flags\nu.png" />
<None Include="flags\nz.png" />
<None Include="flags\om.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\ontop.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\other.png" />
<None Include="flags\pa.png" />
<None Include="flags\pe.png" />
<None Include="flags\pf.png" />
<None Include="flags\pg.png" />
<None Include="flags\ph.png" />
<None Include="flags\pk.png" />
<None Include="flags\pl.png" />
<None Include="icons\playsound.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\playsound_color.png" />
<None Include="icons\playsound_full.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\pm.png" />
<None Include="flags\pn.png" />
<None Include="flags\pr.png" />
<None Include="icons\prefix.png" />
<None Include="icons\previous.png" />
<None Include="icons\print.png" />
<None Include="icons\programicon.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\programicon_old.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="icons\programicon_scan.png" />
<None Include="icons\programs.png" />
<None Include="flags\ps.png" />
<None Include="flags\pt.png" />
<None Include="icons\pushpin.png" />
<None Include="flags\pw.png" />
<None Include="flags\py.png" />
<None Include="flags\qa.png" />
<None Include="qt-style-macos.css" />
<None Include="qt-style-st-babylon.css" />
<None Include="qt-style-st-lingoes-blue.css" />
<None Include="qt-style-st-lingvo.css" />
<None Include="qt-style-st-modern.css" />
<None Include="qt-style.css" />
<None Include="flags\re.png" />
<None Include="icons\reload.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<QtRcc Include="resources.qrc">
rename qt4x5.hh to utils.hh the filename qt4x5 is not proper now,for the qt4 version can never meet.and the qt5 is actually mean qt>5 .
2021-11-27 07:17:33 +00:00
<InitFuncName Condition="'$(Configuration)|$(Platform)'=='Release|x64'">resources</InitFuncName>
<InitFuncName Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">resources</InitFuncName>
</QtRcc>
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\ro.png" />
<None Include="flags\rs.png" />
<None Include="flags\ru.png" />
<None Include="flags\rw.png" />
<None Include="flags\sa.png" />
<None Include="flags\sb.png" />
<None Include="flags\sc.png" />
<None Include="flags\scotland.png" />
<None Include="flags\sd.png" />
<None Include="flags\se.png" />
<None Include="flags\sg.png" />
<None Include="flags\sh.png" />
<None Include="flags\si.png" />
<None Include="flags\sj.png" />
<None Include="flags\sk.png" />
<None Include="flags\sl.png" />
<None Include="flags\sm.png" />
<None Include="flags\sn.png" />
<None Include="flags\so.png" />
<None Include="flags\sr.png" />
<None Include="flags\st.png" />
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<None Include="icons\star.png" />
<None Include="icons\star_blue.png" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
<None Include="flags\sv.png" />
<None Include="flags\sy.png" />
<None Include="icons\system-search.png" />
<None Include="flags\sz.png" />
<None Include="flags\tc.png" />
<None Include="flags\td.png" />
<None Include="flags\tf.png" />
<None Include="flags\tg.png" />
<None Include="flags\th.png" />
<None Include="flags\tj.png" />
<None Include="flags\tk.png" />
<None Include="flags\tl.png" />
<None Include="flags\tm.png" />
<None Include="flags\tn.png" />
<None Include="flags\to.png" />
<None Include="flags\tr.png" />
<None Include="flags\tt.png" />
<None Include="flags\tv.png" />
<None Include="flags\tw.png" />
<None Include="flags\tz.png" />
<None Include="flags\ua.png" />
<None Include="flags\ug.png" />
<None Include="flags\uk.png" />
<None Include="flags\um.png" />
<None Include="flags\us.png" />
<None Include="flags\uy.png" />
<None Include="flags\uz.png" />
<None Include="flags\va.png" />
<None Include="flags\vc.png" />
<None Include="flags\ve.png" />
<None Include="version.txt" />
<None Include="flags\vg.png" />
<None Include="flags\vi.png" />
<None Include="icons\video.png" />
<None Include="flags\vn.png" />
<None Include="flags\vu.png" />
<None Include="flags\wales.png" />
<None Include="icons\warning.png" />
<None Include="flags\wf.png" />
<None Include="flags\wi.png" />
<None Include="flags\wiki.png" />
<None Include="icons\windows-list.png" />
<None Include="icons\wizard.png" />
<None Include="flags\ws.png" />
<None Include="flags\ye.png" />
<None Include="flags\yt.png" />
<None Include="flags\za.png" />
<None Include="flags\zm.png" />
<None Include="flags\zw.png" />
</ItemGroup>
<ItemGroup>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ResourceCompile Include="goldendict.rc" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
</ItemGroup>
rename qt4x5.hh to utils.hh the filename qt4x5 is not proper now,for the qt4 version can never meet.and the qt5 is actually mean qt>5 .
2021-11-27 07:17:33 +00:00
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
<ImportGroup Condition="Exists('$(QtMsBuild)\qt.targets')">
<Import Project="$(QtMsBuild)\qt.targets" />
</ImportGroup>
update visual studio project file. actually these files should be removed. all these files can be autogenerated by VisualStudio extension <Qt Tools>.
2021-11-26 13:37:19 +00:00
<ImportGroup Label="ExtensionTargets" />
Created a VS2012 project and solution for GoldenDict It uses excellent Visual Studio extensions for Qt, written by Adam Badura (@adambadura). Many thanks! The project file is fully functional in Release-Qt4 configuration, for both x32 and x64 architectures. I decided not to use the official Qt Plugin, since it generates HUGE and broken project files which is painful to maintain. Here we have a pure visual studio solution with proper Visual Studio extensions to support Qt-based development. These extensions cover RCC, Lrelease, MOC and UIC, automagically invoking them when needed, with basically no need for manual steps to maintain. Also, GoldenDict can be built from the command line as well, no Visual Studio is required: For Win32: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=win32 For x64: MSBuild /m goldendict.sln /v:m /nologo /p:Configuration=Release-Qt4 /p:Platform=x64
2013-08-16 13:32:29 +00:00
</Project>
Copy permalink