Re: SVG to PNG

On Mon, 23 Nov 2020, Pro Turm wrote:

>> The 'libxml' subdirectory is only useful for the Windows Visual Studio
> build.
> Is it expected to have some Compile/Preprocessor switches to build with the
> delivered libxml on Windows?
> One I had to use was /wd4996 (deprecated POSIX methods). I dont know if
> because of the libxml sources are from 2009.

I don't think that the libxml2 project places much priority on 
Microsoft's Visual Studio, or cares much about Microsoft's proprietary 
intentions such as to deprecate standard ANSI C and POSIX interfaces 
in favor of Microsoft's proprietary interfaces.

See the file VisualMagick/libxml/LIBRARY.txt (read by configure.exe) 
which turns off a bunch of warnings as well as provides a file 
exclusion list.

Integrating a new libxml2 is quite a lot of work with little to gain. 
In order to lessen the work for myself, the GraphicsMagick source tree 
has a 'patches' directory which contains some patches which were 
applied when the associated library was integrated.  These patch files 
are likely not complete any more due to subsequent edits to quench 
warnings.

> I couldnt find a cmake or something similar, determining which .c files are
> needed by GM. Tried to include use, had to exclude several. This could be a
> possible CMakeLists.txt in the libxml folder.
> cmake_minimum_required (VERSION 3.14)

You could just configure (via VisualMagick/configure/configure.exe) 
and compile GraphicsMagick as delivered and then look at the files 
which were included in the project file, as well as the project 
settings.

Bob
-- 
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
Public Key,     http://www.simplesystems.org/users/bfriesen/public-key.txt