iqbalrifai
/
Aegisub
mirror of https://github.com/odrling/Aegisub
1
0
Fork 0
Code Issues Releases Wiki Activity
Aegisub/build/libass/libass.vcxproj

121 lines
5.5 KiB
XML
Raw Normal View History

Add libass project
2012-11-17 23:47:33 +01:00
<?xml version="1.0" encoding="utf-8"?>
Upgrade all MSBuild projects to v12 tools Has no real effect, it's what VS 2013 already uses and detailed logging reveals that the build system doesn't even recognize v4 and assumes v12 anyway. Might prevent builds with outdated tools.
2015-01-18 03:03:42 +01:00
<Project DefaultTargets="Build" ToolsVersion="12.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
Add libass project
2012-11-17 23:47:33 +01:00
<PropertyGroup Label="Globals">
<ProjectGuid>{8804F253-DA67-4CC4-926B-0CD2AEE5778D}</ProjectGuid>
<RootNamespace>libass</RootNamespace>
</PropertyGroup>
<!-- Aegisub project configuration -->
<PropertyGroup Label="AegisubConfiguration">
<AegisubProjectType>lib</AegisubProjectType>
</PropertyGroup>
<ImportGroup Label="PropertySheets">
<Import Project="$(MSBuildThisFileDirectory)..\aegisub.props" />
</ImportGroup>
Enable assembly routines for libass on Windows
2015-01-20 01:08:44 +01:00
<ImportGroup Label="Targets">
<Import Project="$(MSBuildThisFileDirectory)..\yasm.targets" />
</ImportGroup>
Add libass project
2012-11-17 23:47:33 +01:00
<!-- Project specific configuration -->
<ItemDefinitionGroup>
<ClCompile>
<AdditionalIncludeDirectories>
$(LibassSrcDir)\libass;
Switch to unpatched libass since it's compilable with VC++ 2013
2013-12-12 19:19:38 +01:00
$(MSBuildThisFileDirectory);
Update VS project to properly locate fribidi headers
2018-10-06 02:56:13 +02:00
$(FribidiSrcDir)\fribidi;
Add libass project
2012-11-17 23:47:33 +01:00
%(AdditionalIncludeDirectories)
</AdditionalIncludeDirectories>
<PreprocessorDefinitions>
inline=__inline;
Fix statically linking fribidi
2012-11-18 01:22:18 +01:00
FRIBIDI_ENTRY=;
Update libass Worth noting that this does NOT currently build, thanks to a few lines in libass that are not compatible with vc++. I'll bump the libass commit when MrSmile's pr gets merged and this is remedied. You can apply this commit to remedy that: https://github.com/libass/libass/pull/321/commits/5317a8dd897a1b6481c1d77e16443f8fdb7621df Also worth noting that while libass switched to nasm, I haven't done so here because it wasn't worth the effort, so I just made a questionable change to the yasm.targets to emulate nasm behavior
2019-01-08 03:23:56 +01:00
_USE_MATH_DEFINES=;
Add libass project
2012-11-17 23:47:33 +01:00
%(PreprocessorDefinitions)
</PreprocessorDefinitions>
</ClCompile>
Rework InstallHeaders target to be more regular
2015-01-18 21:52:27 +01:00
<InstallHeader>
<HeaderRoot>$(LibassSrcDir)\libass</HeaderRoot>
Add libass project
2012-11-17 23:47:33 +01:00
<Destination>ass\</Destination>
Rework InstallHeaders target to be more regular
2015-01-18 21:52:27 +01:00
</InstallHeader>
Enable assembly routines for libass on Windows
2015-01-20 01:08:44 +01:00
<Yasm>
Update libass Worth noting that this does NOT currently build, thanks to a few lines in libass that are not compatible with vc++. I'll bump the libass commit when MrSmile's pr gets merged and this is remedied. You can apply this commit to remedy that: https://github.com/libass/libass/pull/321/commits/5317a8dd897a1b6481c1d77e16443f8fdb7621df Also worth noting that while libass switched to nasm, I haven't done so here because it wasn't worth the effort, so I just made a questionable change to the yasm.targets to emulate nasm behavior
2019-01-08 03:23:56 +01:00
<Config Condition="'$(Platform)'=='Win32'">%(Config) -DARCH_X86_64=0 -DPREFIX -DHAVE_ALIGNED_STACK=0 -DHAVE_CPUNOP=1</Config>
<Config Condition="'$(Platform)'=='x64'">%(Config) -DARCH_X86_64=1 -DHAVE_ALIGNED_STACK=1 -DHAVE_CPUNOP=1</Config>
Enable assembly routines for libass on Windows
2015-01-20 01:08:44 +01:00
</Yasm>
Add libass project
2012-11-17 23:47:33 +01:00
</ItemDefinitionGroup>
<!-- Source files -->
<ItemGroup>
Rework InstallHeaders target to be more regular
2015-01-18 21:52:27 +01:00
<InstallHeader Include="$(LibassSrcDir)\libass\ass.h" />
<InstallHeader Include="$(LibassSrcDir)\libass\ass_types.h" />
Add libass project
2012-11-17 23:47:33 +01:00
</ItemGroup>
Enable assembly routines for libass on Windows
2015-01-20 01:08:44 +01:00
<ItemGroup>
<Yasm Include="$(LibassSrcDir)\libass\x86\be_blur.asm">
<ExcludeFromBuild Condition="'$(Platform)'!='x64'">true</ExcludeFromBuild>
</Yasm>
<Yasm Include="$(LibassSrcDir)\libass\x86\blend_bitmaps.asm" />
Update to libass 0.13.1
2015-10-12 05:56:38 +02:00
<Yasm Include="$(LibassSrcDir)\libass\x86\blur.asm" />
Enable assembly routines for libass on Windows
2015-01-20 01:08:44 +01:00
<Yasm Include="$(LibassSrcDir)\libass\x86\cpuid.asm" />
Update libass Worth noting that this does NOT currently build, thanks to a few lines in libass that are not compatible with vc++. I'll bump the libass commit when MrSmile's pr gets merged and this is remedied. You can apply this commit to remedy that: https://github.com/libass/libass/pull/321/commits/5317a8dd897a1b6481c1d77e16443f8fdb7621df Also worth noting that while libass switched to nasm, I haven't done so here because it wasn't worth the effort, so I just made a questionable change to the yasm.targets to emulate nasm behavior
2019-01-08 03:23:56 +01:00
<Yasm Include="$(LibassSrcDir)\libass\x86\gaussian.asm" />
Enable assembly routines for libass on Windows
2015-01-20 01:08:44 +01:00
<Yasm Include="$(LibassSrcDir)\libass\x86\rasterizer.asm" />
Update libass Worth noting that this does NOT currently build, thanks to a few lines in libass that are not compatible with vc++. I'll bump the libass commit when MrSmile's pr gets merged and this is remedied. You can apply this commit to remedy that: https://github.com/libass/libass/pull/321/commits/5317a8dd897a1b6481c1d77e16443f8fdb7621df Also worth noting that while libass switched to nasm, I haven't done so here because it wasn't worth the effort, so I just made a questionable change to the yasm.targets to emulate nasm behavior
2019-01-08 03:23:56 +01:00
<Yasm Include="$(LibassSrcDir)\libass\x86\utils.asm" />
<Yasm Include="$(LibassSrcDir)\libass\x86\x86inc.asm" />
Enable assembly routines for libass on Windows
2015-01-20 01:08:44 +01:00
</ItemGroup>
Add libass project
2012-11-17 23:47:33 +01:00
<ItemGroup>
<ClInclude Include="$(LibassSrcDir)\libass\ass.h" />
<ClInclude Include="$(LibassSrcDir)\libass\ass_bitmap.h" />
<ClInclude Include="$(LibassSrcDir)\libass\ass_cache.h" />
<ClInclude Include="$(LibassSrcDir)\libass\ass_cache_template.h" />
Update libass Worth noting that this does NOT currently build, thanks to a few lines in libass that are not compatible with vc++. I'll bump the libass commit when MrSmile's pr gets merged and this is remedied. You can apply this commit to remedy that: https://github.com/libass/libass/pull/321/commits/5317a8dd897a1b6481c1d77e16443f8fdb7621df Also worth noting that while libass switched to nasm, I haven't done so here because it wasn't worth the effort, so I just made a questionable change to the yasm.targets to emulate nasm behavior
2019-01-08 03:23:56 +01:00
<ClInclude Include="$(LibassSrcDir)\libass\ass_compat.h" />
<ClInclude Include="$(LibassSrcDir)\libass\ass_directwrite.h" />
Add libass project
2012-11-17 23:47:33 +01:00
<ClInclude Include="$(LibassSrcDir)\libass\ass_drawing.h" />
<ClInclude Include="$(LibassSrcDir)\libass\ass_font.h" />
Update libass Worth noting that this does NOT currently build, thanks to a few lines in libass that are not compatible with vc++. I'll bump the libass commit when MrSmile's pr gets merged and this is remedied. You can apply this commit to remedy that: https://github.com/libass/libass/pull/321/commits/5317a8dd897a1b6481c1d77e16443f8fdb7621df Also worth noting that while libass switched to nasm, I haven't done so here because it wasn't worth the effort, so I just made a questionable change to the yasm.targets to emulate nasm behavior
2019-01-08 03:23:56 +01:00
<ClInclude Include="$(LibassSrcDir)\libass\ass_fontselect.h" />
<ClInclude Include="$(LibassSrcDir)\libass\ass_func_template.h" />
Add libass project
2012-11-17 23:47:33 +01:00
<ClInclude Include="$(LibassSrcDir)\libass\ass_library.h" />
Update libass Worth noting that this does NOT currently build, thanks to a few lines in libass that are not compatible with vc++. I'll bump the libass commit when MrSmile's pr gets merged and this is remedied. You can apply this commit to remedy that: https://github.com/libass/libass/pull/321/commits/5317a8dd897a1b6481c1d77e16443f8fdb7621df Also worth noting that while libass switched to nasm, I haven't done so here because it wasn't worth the effort, so I just made a questionable change to the yasm.targets to emulate nasm behavior
2019-01-08 03:23:56 +01:00
<ClInclude Include="$(LibassSrcDir)\libass\ass_outline.h" />
Add libass project
2012-11-17 23:47:33 +01:00
<ClInclude Include="$(LibassSrcDir)\libass\ass_parse.h" />
Update libass Worth noting that this does NOT currently build, thanks to a few lines in libass that are not compatible with vc++. I'll bump the libass commit when MrSmile's pr gets merged and this is remedied. You can apply this commit to remedy that: https://github.com/libass/libass/pull/321/commits/5317a8dd897a1b6481c1d77e16443f8fdb7621df Also worth noting that while libass switched to nasm, I haven't done so here because it wasn't worth the effort, so I just made a questionable change to the yasm.targets to emulate nasm behavior
2019-01-08 03:23:56 +01:00
<ClInclude Include="$(LibassSrcDir)\libass\ass_rasterizer.h" />
Add libass project
2012-11-17 23:47:33 +01:00
<ClInclude Include="$(LibassSrcDir)\libass\ass_render.h" />
<ClInclude Include="$(LibassSrcDir)\libass\ass_shaper.h" />
Update libass Worth noting that this does NOT currently build, thanks to a few lines in libass that are not compatible with vc++. I'll bump the libass commit when MrSmile's pr gets merged and this is remedied. You can apply this commit to remedy that: https://github.com/libass/libass/pull/321/commits/5317a8dd897a1b6481c1d77e16443f8fdb7621df Also worth noting that while libass switched to nasm, I haven't done so here because it wasn't worth the effort, so I just made a questionable change to the yasm.targets to emulate nasm behavior
2019-01-08 03:23:56 +01:00
<ClInclude Include="$(LibassSrcDir)\libass\ass_string.h" />
Add libass project
2012-11-17 23:47:33 +01:00
<ClInclude Include="$(LibassSrcDir)\libass\ass_types.h" />
<ClInclude Include="$(LibassSrcDir)\libass\ass_utils.h" />
Update libass Worth noting that this does NOT currently build, thanks to a few lines in libass that are not compatible with vc++. I'll bump the libass commit when MrSmile's pr gets merged and this is remedied. You can apply this commit to remedy that: https://github.com/libass/libass/pull/321/commits/5317a8dd897a1b6481c1d77e16443f8fdb7621df Also worth noting that while libass switched to nasm, I haven't done so here because it wasn't worth the effort, so I just made a questionable change to the yasm.targets to emulate nasm behavior
2019-01-08 03:23:56 +01:00
<ClInclude Include="$(LibassSrcDir)\libass\dwrite_c.h" />
Enable assembly routines for libass on Windows
2015-01-20 01:08:44 +01:00
<ClInclude Include="$(LibassSrcDir)\libass\x86\cpuid.h" />
Fix libass project for FastUptodateCheck
2015-01-19 23:54:06 +01:00
<ClInclude Include="$(MSBuildThisFileDirectory)config.h" />
<ClInclude Include="$(MSBuildThisFileDirectory)strings.h" />
Add libass project
2012-11-17 23:47:33 +01:00
</ItemGroup>
<ItemGroup>
<ClCompile Include="$(LibassSrcDir)\libass\ass.c" />
<ClCompile Include="$(LibassSrcDir)\libass\ass_bitmap.c" />
Update to libass 0.13.1
2015-10-12 05:56:38 +02:00
<ClCompile Include="$(LibassSrcDir)\libass\ass_blur.c" />
Add libass project
2012-11-17 23:47:33 +01:00
<ClCompile Include="$(LibassSrcDir)\libass\ass_cache.c" />
Update libass Worth noting that this does NOT currently build, thanks to a few lines in libass that are not compatible with vc++. I'll bump the libass commit when MrSmile's pr gets merged and this is remedied. You can apply this commit to remedy that: https://github.com/libass/libass/pull/321/commits/5317a8dd897a1b6481c1d77e16443f8fdb7621df Also worth noting that while libass switched to nasm, I haven't done so here because it wasn't worth the effort, so I just made a questionable change to the yasm.targets to emulate nasm behavior
2019-01-08 03:23:56 +01:00
<ClCompile Include="$(LibassSrcDir)\libass\ass_directwrite.c" />
Add libass project
2012-11-17 23:47:33 +01:00
<ClCompile Include="$(LibassSrcDir)\libass\ass_drawing.c" />
<ClCompile Include="$(LibassSrcDir)\libass\ass_font.c" />
Update to libass 0.13.1
2015-10-12 05:56:38 +02:00
<ClCompile Include="$(LibassSrcDir)\libass\ass_fontselect.c" />
Add libass project
2012-11-17 23:47:33 +01:00
<ClCompile Include="$(LibassSrcDir)\libass\ass_library.c" />
Update libass Worth noting that this does NOT currently build, thanks to a few lines in libass that are not compatible with vc++. I'll bump the libass commit when MrSmile's pr gets merged and this is remedied. You can apply this commit to remedy that: https://github.com/libass/libass/pull/321/commits/5317a8dd897a1b6481c1d77e16443f8fdb7621df Also worth noting that while libass switched to nasm, I haven't done so here because it wasn't worth the effort, so I just made a questionable change to the yasm.targets to emulate nasm behavior
2019-01-08 03:23:56 +01:00
<ClCompile Include="$(LibassSrcDir)\libass\ass_outline.c" />
Add libass project
2012-11-17 23:47:33 +01:00
<ClCompile Include="$(LibassSrcDir)\libass\ass_parse.c" />
Update to libass 0.13.1
2015-10-12 05:56:38 +02:00
<ClCompile Include="$(LibassSrcDir)\libass\ass_rasterizer.c" />
<ClCompile Include="$(LibassSrcDir)\libass\ass_rasterizer_c.c" />
Add libass project
2012-11-17 23:47:33 +01:00
<ClCompile Include="$(LibassSrcDir)\libass\ass_render.c" />
<ClCompile Include="$(LibassSrcDir)\libass\ass_render_api.c" />
<ClCompile Include="$(LibassSrcDir)\libass\ass_shaper.c" />
Update to libass 0.13.1
2015-10-12 05:56:38 +02:00
<ClCompile Include="$(LibassSrcDir)\libass\ass_string.c" />
Add libass project
2012-11-17 23:47:33 +01:00
<ClCompile Include="$(LibassSrcDir)\libass\ass_strtod.c" />
<ClCompile Include="$(LibassSrcDir)\libass\ass_utils.c" />
Add a GDI-based font selector for libass This deliberately doesn't perform any font substitutions as the sort of people that use libass on Windows tend to perfer to manually pick fonts with the correctly glyphs.
2015-10-31 04:57:08 +01:00
<ClCompile Include="..\..\src\libass_gdi_fontselect.cpp" />
Add libass project
2012-11-17 23:47:33 +01:00
</ItemGroup>
<!-- Project References -->
<ItemGroup>
<ProjectReference Include="..\freetype2\freetype.vcxproj">
<Project>{78b079bd-9fc7-4b9e-b4a6-96da0f00248b}</Project>
</ProjectReference>
<ProjectReference Include="..\fribidi\fribidi.vcxproj">
<Project>{fb8e8d19-a4d6-4181-943c-282075f49b41}</Project>
</ProjectReference>
</ItemGroup>
Update VS project to properly locate fribidi headers
2018-10-06 02:56:13 +02:00
</Project>