feat: added registries to community section

[lolrobbe2]

What does this PR do?

This creates a new registries page (did no know where to put these otherwise?)

Anything else we should know?

Any Modules are welcome to be registered!

There is a public rate limited search api available if other projects wan't to integrate the public registry

You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!

[Jarod42]

It doesn't explain to users what it is.

Still unclear what it is for me ^_^

[lolrobbe2]

@Jarod42
Explanation:

common registry

common registry
A collection of public/popular libraries wich integrate with premake-manager.
These libraries can declare dependencies and ranges etc... Then a versions will be matched by premake-manager-cli and installed. these registries are created via github repo's.

Note

People can create their own common registries and add them to their workflow via premake-manager

public registry

registry
The public registry is for individual premake users who wan't to share their libraries and modules.
these can be registered via the UI and github login.
They also can integrate with premake-manager-cli but they also can be used standalone as git submodule etc..

premake manager:

the IDE extensions for:

1. visual studio
2. visual studio code
3. clion...
   might need some help to word this better :)

[lolrobbe2]

if there are popular libraries you can think about, that i should add. Let me know.

[Jarod42]

As I understand (and it seems it was not clear for whole premake team), registry are a collection of premake scripts for projects (not using premake originally?).
One concern, if it is the case, is the possibility for the scripts to become out of date quickly (without notice).

Unclear to me how to use them without Premake Manager.
Demo/example would probably make the thing more clear.

If purpose is only for Premake Manager, then enrich https://premake.github.io/community/extensions section with those information might be more appropriate.

As I understand, Premake Manager will download the project and the associated script.

Personally, I use submodules, and either use project build system for regular install, or rewrite premake script if simple to incorporate in my solution.

[lolrobbe2]

As I understand (and it seems it was not clear for whole premake team), registry are a collection of premake scripts for
projects (not using premake originally?). (yes this is the goal of the common-registry)

If purpose is only for Premake Manager, then enrich https://premake.github.io/community/extensions section with those >information might be more appropriate. (ill move the part about the common-registry there)

premake manager:

1. will download and version match the requested libraries and gather necesarry dependencies.
2. and define the versions in the premake-system.lua file. thus allowing specific version changes to be done

public registry (website)

1. allows people to share their libraries and modules
2. you can also use these as submodules if desired.
3. Meant for general use without premake-manager.

common-registries

1. meant for use with premake-manager-cli
2. can define dependencies (should make this more clear!)

[Jarod42]

From that description, I understand:

• premake manager looks like a source package manager, and seems unrelated to premake (alternative to Conan, vcpkg, submodules...).
• common-registries seems to be the "internal" database of premake manager.
• public registry: place to indicate (library) projects which use/provide premake scripts. (Might go in https://premake.github.io/community/showcase ?)

Demo/example would probably make the thing more clear.

[lolrobbe2]

@Jarod42 ill try and work out a comprehensive demo over the next couple days to make things more clear. but your understanding is pretty much on point.

the only exception is that the default common-registry (database) is also searchable from the public registry.

#common registry: goal:

Provide tailor made premake scripts for projects not initialy using premake, and add dependency resolution using semver ranges.

ill have to work something out for this:
One concern, if it is the case, is the possibility for the scripts to become out of date quickly (without notice).

DEMO

premakeDependencies.yml

this file defines what dependencies volk has:

libraries:
- name: KhronosGroup/Vulkan-Headers
  version: '@' #use parent version

premake5.lua

require "vulkan-headers"
project "volk"
	language    "C"
    kind        "StaticLib"  
	warnings    "Off"
    defines {
        "_LIB",
        "API_NAME=\"vulkan\"",
    }
    includedirs {
        ".",
    }
    files {
        "volk.c",
        "volk.h",
    }
    links {
        "Vulkan-Headers"
    }
    filter "platforms:Windows"
        defines {
            "VK_USE_PLATFORM_WIN32_KHR",
        }
    filter("platforms:Linux")
        defines {
            "VK_USE_PLATFORM_XCB_KHR",
        }

premakeLib.yml

name: volk
description: meta loader for vulkan api

premakeIndex.yml

this file is a collection of all the libraries and brief descriptions meant for searching etc.

remote: https://github.com/lolrobbe2/premake-common-registry
libraries:
  madler:
  - name: zlib
    description: a massively spiffy yet delicately unobtrusive compression library (also free, not to mention unencumbered by patents)
  cyan4973:
  - name: xxhash
    description: extremely fast non-cryptographic hash algorithm
  nothings:
  - name: stb
    description: stb single-file public domain libraries for c/c++
  khronosgroup:
  - name: vulkan-headers
    description: vulkan header files and api registry
  zeux:
  - name: volk
    description: meta loader for vulkan api
  nemtrif:
  - name: utfcpp
    description: utf-8 with c++ in a portable way

[samsinsane]

This is way too much information and reads like this is an official part of Premake - especially with the note at the end. This should follow the same format as Modules and Extensions, where each item is just a single line with just enough information to know what it is.

Something like this:

## Registries

- [premake-common-registry](https://github.com/lolrobbe2/premake-common-registry) : The common registry for [Premake Manager](https://github.com/lolrobbe2/premake-manager).