Compare commits
No commits in common. "master" and "v0.2" have entirely different histories.
13
.circleci/config.yml
Normal file
13
.circleci/config.yml
Normal file
@ -0,0 +1,13 @@
|
|||||||
|
# Use the latest 2.1 version of CircleCI pipeline process engine. See: https://circleci.com/docs/2.0/configuration-reference
|
||||||
|
version: 2.1
|
||||||
|
# Use a package of configuration called an orb.
|
||||||
|
orbs:
|
||||||
|
# Declare a dependency on the welcome-orb
|
||||||
|
welcome: circleci/welcome-orb@0.4.1
|
||||||
|
# Orchestrate or schedule a set of jobs
|
||||||
|
workflows:
|
||||||
|
# Name the workflow "welcome"
|
||||||
|
welcome:
|
||||||
|
# Run the welcome/run job in its own container
|
||||||
|
jobs:
|
||||||
|
- welcome/run
|
@ -12,20 +12,11 @@ jobs:
|
|||||||
# well on Windows or Mac. You can convert this to a matrix build if you need
|
# well on Windows or Mac. You can convert this to a matrix build if you need
|
||||||
# cross-platform coverage.
|
# cross-platform coverage.
|
||||||
# See: https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix
|
# See: https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix
|
||||||
runs-on: ubuntu-gitea
|
runs-on: ubuntu-latest
|
||||||
|
|
||||||
steps:
|
steps:
|
||||||
|
|
||||||
- name: Prep For Local Builds
|
|
||||||
run: echo "${LOCIP} gitea.comnenos" >> /etc/hosts
|
|
||||||
|
|
||||||
- uses: actions/checkout@v2
|
- uses: actions/checkout@v2
|
||||||
|
|
||||||
- name: Install Build Tools
|
|
||||||
run: |
|
|
||||||
apt update
|
|
||||||
apt -y --no-install-recommends install build-essential clang cmake gdb git wget
|
|
||||||
|
|
||||||
- name: Create Build Environment
|
- name: Create Build Environment
|
||||||
# Some projects don't allow in-source building, so create a separate build directory
|
# Some projects don't allow in-source building, so create a separate build directory
|
||||||
# We'll use this as our working directory for all subsequent commands
|
# We'll use this as our working directory for all subsequent commands
|
@ -3,4 +3,4 @@ project(passwdgen)
|
|||||||
|
|
||||||
set(CMAKE_CXX_STANDARD 20)
|
set(CMAKE_CXX_STANDARD 20)
|
||||||
|
|
||||||
add_executable(passwdgen passwdgen.cpp)
|
add_executable(passwdgen passwdgen.cpp)
|
19
README.md
19
README.md
@ -1,22 +1,3 @@
|
|||||||
# passwdgen
|
# passwdgen
|
||||||
### a rudimentary random string password generator
|
### a rudimentary random string password generator
|
||||||
|
|
||||||
For demo purposes only
|
|
||||||
|
|
||||||
## Build
|
|
||||||
|
|
||||||
**Bare Bones**
|
|
||||||
```bash
|
|
||||||
mkdir build
|
|
||||||
g++ -o build/passwdgen ./passwdgen.cpp
|
|
||||||
```
|
|
||||||
|
|
||||||
**From CMAKE**
|
|
||||||
```bash
|
|
||||||
mkdir build
|
|
||||||
cd build
|
|
||||||
cmake ..
|
|
||||||
make
|
|
||||||
```
|
|
||||||
|
|
||||||
Then, just copy the compiled binary to somewhere on your $PATH
|
|
||||||
|
Loading…
Reference in New Issue
Block a user