A repository that sets up a C++ Project with the olcPixelGameEngine already loaded.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
sigonasr2 c93cefbe9d Update project template to include debugging script 2 years ago
.vscode Update PGE header 2 years ago
C++/scripts Update project template to include debugging script 2 years ago
art Magnarune wanted circles 2 years ago
utils Update directories now includes C++ 2 years ago
Block.cpp Default Constructors required for template classes 2 years ago
Block.h Default Constructors required for template classes 2 years ago
C++ProjectTemplate Update project template to include debugging script 2 years ago
C++ProjectTemplate.html CustomControls configuring example 2 years ago
C++ProjectTemplate.js Racing with any key press functionality 2 years ago
C++ProjectTemplate.wasm Racing with any key press functionality 2 years ago
Map.cpp Dependent Classes Example 2 years ago
Map.h Dependent Classes Example 2 years ago
Player.cpp Dependent Classes Example 2 years ago
Player.h Dependent Classes Example 2 years ago
README.md Setup project 2 years ago
a.out Update PGE header 2 years ago
buildtemplate.html Update web.sh 2 years ago
car.png Magnarune wanted circles 2 years ago
co2.png Turn orders work, move selection works 2 years ago
dependentClasses.zip Dependent Classes Example 2 years ago
diff Turn orders work, move selection works 2 years ago
dirtblock.png Include a launch.json and tasks.json example files 2 years ago
grass.png Magnarune wanted circles 2 years ago
hills.png Magnarune wanted circles 2 years ago
main.cpp std::unique example 2 years ago
pixelGameEngine.h Update PGE header 2 years ago
road.png Magnarune wanted circles 2 years ago
sig Update project template to include debugging script 2 years ago
start.png Magnarune wanted circles 2 years ago

README.md

This repository contains general build scripts and pipelines for all languages that I incorporate in my projects. The goal is to provide an easy retrieval and update system for the project. Each script will be a shell script containing the following template:

    #Short description about what I do
    #Language[Folder]
    # #The script's code goes in here.
    # rm -Rf out/*
    # javac -Xlint:unchecked -cp ${PROJECT_DIR}/.. -d ${OUT_DIR} ${PROJECT_DIR}/*.java
    # printf "\n\n\nRunning Program...\n\n"
    # cd $OUT_DIR
    # java ${MAIN_CLASS} "$@"
    # ../scripts/clean.sh
    

Each language will be in the following structure:

    -<Language>
    --<scripts>
    ---[script files.sh]

The sig script will display by default any scripts in the scripts folder, therefore when creating a project, copy over the scripts folder of the desired language into your project then the sig script handles the rest appropriately. If your project requires multiple languages and build setups, then you can use the sig2 command, which has an additional parameter to specify the language when running it. When setting up a multi-language setup, you'll just copy the entire folder to include the programming language itself. So a multi-language project structure may look something like this:

    -C
    --scripts
    ---build.sh
    ---clean.sh
    ---make.sh
    -Java
    --scripts
    ---build.sh
    ---clean.sh
    ---jar.sh