[septag-sx] Add new port

[myd7349]

https://github.com/septag/sx
BTW, is the package name too short?
septag/sx#11

[Rastaban]

I see failures on uwp triplets and arm64-windows. Are those expected?

@vicroms do we have a policy regarding the length of names?

[vicroms]

There's no policy regarding specifically to name length, but searching in repology.org returns a bunch of similarly named sx packages.

In Fedora, sx refers to a reporting tool, but on Arch-Linux it refers to the septag/sx repo (same as this PR).

I don't see any other obvious name for this library, unless we make the package name septag-sx.

[vicroms]

More packages already named sx

https://pkgs.org/download/sx
https://packages.debian.org/search?searchon=names&keywords=sx

[Rastaban]

Okay, so go ahead and change the name (maybe septag-sx?)

[myd7349]

@Rastaban @vicroms Thanks for your helpful reply. Maybe we can document it somewhere(Also this: #5817 (comment)).
I think septag-sx is better.
I didn't test it with a real project yet, I will test it later. Then I maybe able to figure out what happens to UWP and ARM.

[NancyLi1013]

Hi @myd7349，here are the test results from the current CI system. Please refer to the attachment. Hope this will hep you.

arm64-windows	master	test	notes
septag-sx		Fail	New Port

x64-uwp	master	test	notes
septag-sx		Fail	New Port

arm-uwp	master	test	notes
septag-sx		Fail	New Port

failureLogs.zip

[myd7349]

Hi! @NancyLi1013 Thanks!
I will test it as soon as possible.

[Rastaban]

A step toward improving the docs: #6397

[myd7349]

Test with https://github.com/myd7349/Ongoing-Study/tree/master/cpp/CMake/vcpkg/sx_example. These triplets are tested:

• x86-windows
• x86-windows-static
• x64-windows
• x64-windows-static
• x64-linux

UWP/ARM/ARM64 are not supported currently: https://github.com/septag/sx/blob/master/CMakeLists.txt#L134-L141

[NancyLi1013]

@myd7349 ,thanks for your contribution. All test results are normal now except for uwp/arm/arm64 that are not supported.

[grdowns]

Thanks for the new port, @myd7349!