update libpng

update libpng, the repo now requires a vcpkg setup for integrating but skipping the install step should allow it to work for windows an linux, mac might need more
This commit is contained in:
marauder2k7 2025-12-31 20:11:14 +00:00
parent c593d860a0
commit 5d644b4ffb
300 changed files with 25573 additions and 17698 deletions

View file

@ -0,0 +1,3 @@
# https://editorconfig.org
root = true

View file

@ -1,7 +1,7 @@
Instructions for building libpng using Microsoft Visual Studio
==============================================================
Copyright (c) 2018 Cosmin Truta
Copyright (c) 2018,2022 Cosmin Truta
Copyright (c) 2010,2013,2015 Glenn Randers-Pehrson
This code is released under the libpng license.
@ -9,9 +9,9 @@ For conditions of distribution and use, see the disclaimer and license
in png.h
This directory contains a solution for building libpng under Microsoft
Visual Studio 2010. It may also work under later versions of Visual
Studio. You should be familiar with Visual Studio before using this
solution.
Visual Studio 2019. It may also work under earlier or later versions
of Visual Studio. You should be familiar with Visual Studio before
using this solution.
Initial preparations
--------------------

View file

@ -0,0 +1,25 @@
@echo off
@setlocal enableextensions
if "%~1" == "/?" goto :help
if "%~1" == "-?" goto :help
if "%~1" == "/help" goto :help
if "%~1" == "-help" goto :help
if "%~1" == "--help" goto :help
goto :run
:help
echo Usage:
echo %~nx0 [SOLUTION_CONFIG]
echo Examples:
echo %~nx0 "Release|Win32" (default)
echo %~nx0 "Debug|Win32"
echo %~nx0 "Release|ARM64"
echo %~nx0 "Debug|ARM64"
echo etc.
exit /b 2
:run
set _SOLUTION_CONFIG="%~1"
if %_SOLUTION_CONFIG% == "" set _SOLUTION_CONFIG="Release|Win32"
devenv "%~dp0.\vstudio.sln" /build %_SOLUTION_CONFIG%

View file

@ -2,7 +2,7 @@
<!--
* zlib.props - location of zlib source
*
* Copyright (c) 2018 Cosmin Truta
* Copyright (c) 2018-2024 Cosmin Truta
* Copyright (c) 1998-2011 Glenn Randers-Pehrson
*
* This code is released under the libpng license.
@ -14,44 +14,43 @@
-->
<Project ToolsVersion="4.0"
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup Label="Globals">
<!-- Place the name of the directory containing the source of zlib used for
debugging in this property.
debugging in this property.
The directory need only contain the '.c' and '.h' files from the
source.
source.
If you use a relative directory name (as below) then it must be
relative to the project directories; these are one level deeper than
the directories containing this file.
If you use a relative directory name (as below) then it must be
relative to the project directories; these are one level deeper than
the directories containing this file.
If the version of zlib you use does not match that used when the
distribution was built you will get warnings from pngtest that the zlib
versions do not match. The zlib version used in this build is recorded
below:
If the version of zlib you use does not match that used when the
distribution was built you will get warnings from pngtest that the
zlib versions do not match. The zlib version used in this build is
recorded below:
-->
<ZLibSrcDir>..\..\..\..\zlib</ZLibSrcDir>
<!-- The following line allows compilation for an ARM target with Visual
Studio 2012. Notice that this is not supported by the Visual Studio
2012 IDE and that the programs that result cannot be run unless they
signed by Microsoft. This is therefore untested; only Microsoft can
test it:
are signed by Microsoft. This is therefore untested; only Microsoft
can test it:
-->
<WindowsSDKDesktopARMSupport>true</WindowsSDKDesktopARMSupport>
<!-- The following lines provide a global (solution level) control of the
warnings issued by the compiler, these are used in the individual
project files (*/*.vcxproj) with, for zlib, some extra disables.
<!-- The following lines provide a global (solution-level) control of the
warnings issued by the compiler.
Different versions of Visual Studio may require different settings,
these settings work with Visual Studio 2013. Just set
TreatWarningAsError to false to check the build without failing on
errors.
Considering how different versions of Visual Studio sometimes require
different settings, and their compilers issue different warnings, we
set TreatWarningAsError to false to avoid unforeseen and undesirable
build failures for the users who upgrade to a newer Visual Studio that
might bring along a more pedantic compiler:
-->
<WarningLevel>EnableAllWarnings</WarningLevel>
<TreatWarningAsError>true</TreatWarningAsError>
<DisableSpecificWarnings>4255;4668;4710;4711;4746;4820;4996</DisableSpecificWarnings>
<WarningLevel>Level3</WarningLevel>
<TreatWarningAsError>false</TreatWarningAsError>
</PropertyGroup>
</Project>