Initial community commit

This commit is contained in:
Jef 2024-09-24 14:54:57 +02:00
parent 537bcbc862
commit fc06254474
16440 changed files with 4239995 additions and 2 deletions

View file

@ -0,0 +1,18 @@
---
name: Ask a question
about: Ask a general Premake-related question to the community
title: ''
labels: question
assignees: ''
---
_Before asking a new question, please [use the issue search feature](https://github.com/premake/premake-core/issues) to see if your question has already been asked. Help us help you!_
**What's your question?**
A short, concise question for the community. To get the best answers, be clear about what you're asking, what kind of responses you hope to receive, and how you intend to use the information.
**Anything else we should know?**
Add any other background or context about your question here.
*(You can now [support Premake on our OpenCollective](https://opencollective.com/premake). Your contributions help us spend more time responding to questions like these!)*

View file

@ -0,0 +1,27 @@
---
name: Get help
about: Get help using Premake and its scripting features
title: ''
labels: support-request
assignees: ''
---
_Before opening a new issue, please [use the issue search feature](https://github.com/premake/premake-core/issues) to see if a similar issue already exists. If not, please help us help you by filling in the template below._
**What are you trying to do?**
A short, concise description of the outcome you are trying to achieve, ex. "Add build settings to a specific file".
**What problem are you having?**
A clear and concise description of the problem that is blocking you from your desired outcome, ex. "Premake is crashing with this error message: ..." or "I don't know how to do it."
**What have you tried so far?**
Describe any steps you've already taken to try to get past this issue.
**What version of Premake are you using?**
`premake5 --version` will show you the version. If you are running a "-dev" version, please make sure you are up to date with the latest master branch.
**Anything else we should know?**
Add any other context about the problem here.
*(You can now [support Premake on our OpenCollective](https://opencollective.com/premake). Your contributions help us spend more time responding to issues like these!)*

View file

@ -0,0 +1,30 @@
---
name: Report a bug
about: Something need fixing or improvement? Let us know!
title: ''
labels: bug
assignees: ''
---
_Before opening a new bug report, please read [Reporting Bugs](https://github.com/premake/premake-core/blob/master/CONTRIBUTING.md#reporting-bugs) and consider if this is something [you can contribute](https://github.com/premake/premake-core/blob/master/CONTRIBUTING.md#contributing-a-fix-or-feature) yourself. If this a new bug, help us help you by filling in the template below._
**What seems to be the problem?**
A clear and concise description of the bug, ex. "It crashes when I try to run it" or "There doesn't seem to be any way to do ...". If you are reporting a crash, be sure to include any error messages and stack trace information. Use [code blocks](https://help.github.com/en/articles/creating-and-highlighting-code-blocks) to format code and console output nicely.
**What did you expect to happen?**
A clear and concise description of what you expected to happen.
**What have you tried so far?**
Describe any steps you've taken to try to solve or workaround the bug.
**How can we reproduce this?**
Please provide a [minimal, reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) we can use to replicate the problem in our own development environments. Use [code blocks](https://help.github.com/en/articles/creating-and-highlighting-code-blocks) to format code and console output nicely.
**What version of Premake are you using?**
`premake5 --version` will show you the version. If you are running a "-dev" version, please make sure you are up to date with the latest master branch.
**Anything else we should know?**
Add any other context about the problem here.
*(You can now [support Premake on our OpenCollective](https://opencollective.com/premake). Your contributions help us spend more time responding to issues like these!)*

View file

@ -0,0 +1,24 @@
---
name: Request a feature
about: Suggest a new feature or enhancement
title: ''
labels: enhancement
assignees: ''
---
_Before opening a new feature request, please read [Requesting New Features](https://github.com/premake/premake-core/blob/master/CONTRIBUTING.md#requesting-new-features) and consider if this is something [you can contribute](https://github.com/premake/premake-core/blob/master/CONTRIBUTING.md#contributing-a-fix-or-feature) yourself. If this a new request, help us help you by filling in the template below._
**What problem will this solve?**
A clear and concise description of the problem this new feature is meant to solve, ex. "I'm always frustrated when [...]" or "Add support for this new toolset [...]". Please limit your request to a single feature; create multiple feature requests instead.
**What might be a solution?**
A clear and concise description of what you want to happen. If you are proposing changes to Premake's scripting APIs, provide an example of how your new feature might look when scripted. Use [code blocks](https://help.github.com/en/articles/creating-and-highlighting-code-blocks) to format your examples nicely.
**What other alternatives have you already considered?**
A clear and concise description of any alternative solutions or features you've considered.
**Anything else we should know?**
Add any other context or screenshots about the feature request here.
*(You can now [support Premake on our OpenCollective](https://opencollective.com/premake). Your contributions help us spend more time responding to requests like these!)*

View file

@ -0,0 +1,22 @@
**What does this PR do?**
Thanks for the contribution! Please provide a concise description of the problem this request solves.
**How does this PR change Premake's behavior?**
Are there any breaking changes? Will any existing behavior change?
**Anything else we should know?**
Add any other context about your changes here.
**Did you check all the boxes?**
- [ ] Focus on a single fix or feature; remove any unrelated formatting or code changes
- [ ] Add unit tests showing fix or feature works; all tests pass
- [ ] Mention any [related issues](https://github.com/premake/premake-core/issues) (put `closes #XXXX` in comment to auto-close issue when PR is merged)
- [ ] Follow our [coding conventions](https://github.com/premake/premake-core/blob/master/CONTRIBUTING.md#coding-conventions)
- [ ] Minimize the number of commits
- [ ] Align [documentation](https://github.com/premake/premake-core/tree/master/website) to your changes
*You can now [support Premake on our OpenCollective](https://opencollective.com/premake). Your contributions help us spend more time responding to requests like these!*

View file

@ -0,0 +1,73 @@
name: CI Workflow
on: [push, pull_request]
jobs:
linux:
runs-on: ubuntu-latest
strategy:
matrix:
config: [debug, release]
platform: [x64]
steps:
- name: Checkout
uses: actions/checkout@v2
- name: Build
run: make -f Bootstrap.mak linux PLATFORM=${{ matrix.platform }} CONFIG=${{ matrix.config }}
- name: Test
run: bin/${{ matrix.config }}/premake5 test --test-all
- name: Docs check
run: bin/${{ matrix.config }}/premake5 docs-check
- name: Upload Artifacts
if: matrix.config == 'release'
uses: actions/upload-artifact@v2
with:
name: premake-linux-${{ matrix.platform }}
path: bin/${{ matrix.config }}/
macosx:
runs-on: macos-latest
strategy:
matrix:
config: [debug, release]
platform: [x64]
steps:
- name: Checkout
uses: actions/checkout@v2
- name: Build
run: make -f Bootstrap.mak macosx PLATFORM=${{ matrix.platform }} CONFIG=${{ matrix.config }}
- name: Test
run: bin/${{ matrix.config }}/premake5 test --test-all
- name: Docs check
run: bin/${{ matrix.config }}/premake5 docs-check
- name: Upload Artifacts
if: matrix.config == 'release'
uses: actions/upload-artifact@v2
with:
name: premake-macosx-${{ matrix.platform }}
path: bin/${{ matrix.config }}/
windows:
runs-on: windows-latest
strategy:
matrix:
config: [debug, release]
platform: [Win32, x64]
steps:
- name: Checkout
uses: actions/checkout@v2
- name: Build
run: |
call "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" x86_amd64
nmake -f Bootstrap.mak MSDEV=vs2019 windows-msbuild PLATFORM=${{ matrix.platform }} CONFIG=${{ matrix.config }}
shell: cmd
- name: Test
run: bin\${{ matrix.config }}\premake5 test --test-all
shell: cmd
- name: Docs check
run: bin\${{ matrix.config }}\premake5 docs-check
shell: cmd
- name: Upload Artifacts
if: matrix.config == 'release'
uses: actions/upload-artifact@v2
with:
name: premake-windows-${{ matrix.platform }}
path: bin\${{ matrix.config }}\

View file

@ -0,0 +1,55 @@
name: Website
on:
push:
paths: ['website/**']
pull_request:
paths: ['website/**']
jobs:
checks:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
with:
node-version: '14'
- name: Test Build
run: |
cd website
npm install
npm run build
publish:
if: github.repository_owner == 'premake' && github.event_name == 'push' && github.ref == 'refs/heads/master'
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
with:
fetch-depth: 0
- uses: actions/setup-node@v2
with:
node-version: '14'
- name: Add key to allow access to repository
env:
SSH_AUTH_SOCK: /tmp/ssh_agent.sock
run: |
mkdir -p ~/.ssh
ssh-keyscan github.com >> ~/.ssh/known_hosts
echo "${{ secrets.WEBSITE_DEPLOY_KEY }}" > ~/.ssh/id_rsa
chmod 600 ~/.ssh/id_rsa
cat <<EOT >> ~/.ssh/config
Host github.com
HostName github.com
IdentityFile ~/.ssh/id_rsa
EOT
- name: Release to premake.github.io
env:
USE_SSH: true
GIT_USER: git
DEPLOYMENT_BRANCH: master
run: |
git config --global user.email "actions@gihub.com"
git config --global user.name "gh-actions"
cd website
npm install
npx docusaurus deploy