[nyan-lang] Add new port nyan-lang

[duanqn]

Fixes 32249

• Changes comply with the maintainer guide
• The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
• Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx
• The versioning scheme in vcpkg.json matches what upstream says.
• The license declaration in vcpkg.json matches what upstream says.
• The installed as the "copyright" file matches what upstream says.
• The source code of the component installed comes from an authoritative source.
• The generated "usage text" is accurate. See adding-usage for context.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is in the new port's versions file.
• Only one version is added to each modified port's versions file.

[duanqn]

Name should be nyan-lang

[duanqn]

Let me figure out what this means

warning: The following EXEs were found in /bin or /debug/bin. EXEs are not valid distribution targets.

    D:\packages\nyan-lang_x86-windows\bin\nyancat.exe

warning: The following EXEs were found in /bin or /debug/bin. EXEs are not valid distribution targets.

    D:\packages\nyan-lang_x86-windows\debug\bin\nyancat.exe

[duanqn]

Hi @Adela0814 , how should I handle these exe files? Should I put them under tools\ instead of bin\ ?

[Adela0814]

Hi @Adela0814 , how should I handle these exe files? Should I put them under tools\ instead of bin\ ?

Yes, please move the executable file to the tools\.

[duanqn]

Will contact upstream for build failures

[duanqn]

UWP builds are failing because SymInitialize is not available.

[duanqn]

Hi @Adela0814 , is there a way to detect UWP builds? I contacted upstream and the maintainers want to remove the usage of SymInitialize in UWP builds.

[dg0yt]

I would still recommend switching to setting FLEX_EXECUTABLE.

[dg0yt]

If upstream really needs to export all symbols on Windows, can it really work without that on UWP?

[duanqn]

I'm not entirely sure about the purpose of setting up symbols. It could be a "because we can" scenario here...

[duanqn]

I would still recommend switching to setting FLEX_EXECUTABLE.

@dg0yt nyan/CMakeLists.txt has find_package(FLEX 2.6 REQUIRED). Does setting FLEX_EXECUTABLE work for find_package?

[Adela0814]

Suggested change

	cmake_path(GET FLEX PARENT_PATH FLEX_PATH)
	vcpkg_cmake_configure(
	SOURCE_PATH "${SOURCE_PATH}"
	OPTIONS
	"-DFLEX_ROOT=${FLEX_PATH}"
	-DCMAKE_POLICY_DEFAULT_CMP0074=NEW
	vcpkg_cmake_configure(
	SOURCE_PATH "${SOURCE_PATH}"
	OPTIONS
	"-DFLEX_EXECUTABLE=${FLEX}"

[Adela0814]

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review". That way, I can be aware that you've responded since you can't modify the tags.

[dg0yt]

I would still recommend switching to setting FLEX_EXECUTABLE.

@dg0yt nyan/CMakeLists.txt has find_package(FLEX 2.6 REQUIRED). Does setting FLEX_EXECUTABLE work for find_package?

Yes. The package does a find_program(FLEX_EXECUTABLE ...), and setting this cache variable (aka input variable) in advance is a public interface. In vcpkg, it is used in five other ports.

[duanqn]

Applied suggested changes and rebased to latest master branch.