Libxml2 VS TinyXML

Starting off, SVG is an XML encoding, which is a rather hairy thing to deal with. Just to get a feel for LOCs:

https://github.com/GNOME/libxml2

There's also the web's (horrible) tendency to make a diarrhea of special-purpose tags and attributes--many of which could be easily subsumed by basic turing-completeness. Compare to postscript, which was a relatively simple, turing complete, stack machine to begin with.

And of course, if we start special-purposing things, we're no longer compliant with the standard, and it would be chaos to call it SVG at that point.

If someone wants a decent example to learn CMake from, I rewrote the tinyxml2 build not so long ago. It's small, but it handles tricky cases regarding distributing both static and shared versions of the library. See here: https://github.com/leethomason/tinyxml2

Ah ok in that case variants are applicable. You could also consider using an xml parsing library such as https://github.com/leethomason/tinyxml2, given it’s a custom built api for dealing with xml it may be a bit less cumbersome than using variants.

I can't figure out how to compile the source code for the PSX port someone made. The Project's on Github, and I've been trying to figure out how to compile it for the past 2 hours. Compiling it requires 2 more files, nolibgs_hello_worlds and mkpsxiso, which itself seems to require tinyxml2, which I can't seem to compile in Visual studio. As is probably obvious by now, I ain't no coder, this is my first time trying to compile any GitHub source code. But damn it, I wanna play this game on my PS1, I will figure it out. does anyone have a straightforward guide that even an absolute monkey brain moron like me can understand, or better yet, an already compiled version of the room that I can burn to a CD and play on my modchiped PS1?