3D Renderer using Hardware rendering w/Decals!
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 4d48e2653e Flying controls 2 years ago
.vscode Initial commit 2 years ago
C++/scripts Reference the w from inside the PGE to fix perspective 2 years ago
utils Initial commit 2 years ago
Body.png Mountain scene render 2 years ago
C++ProjectTemplate Flying controls 2 years ago
C++ProjectTemplate.html Initial commit 2 years ago
C++ProjectTemplate.js Initial commit 2 years ago
C++ProjectTemplate.wasm Initial commit 2 years ago
Image_6.png Include sorting of triangles 2 years ago
Lowpoly_City_Free_Pack.mtl Mountain scene render 2 years ago
Lowpoly_City_Free_Pack.obj Mountain scene render 2 years ago
Nia.obj Include sorting of triangles 2 years ago
Palette.jpg Mountain scene render 2 years ago
Palette.png Mountain scene render 2 years ago
README.md Initial commit 2 years ago
a.out Initial commit 2 years ago
buildtemplate.html Initial commit 2 years ago
car.png Initial commit 2 years ago
co2.png Initial commit 2 years ago
cube.obj Reference the w from inside the PGE to fix perspective 2 years ago
dependentClasses.zip Initial commit 2 years ago
diff Initial commit 2 years ago
dirtblock.png Initial commit 2 years ago
girl OBJ.obj Mountain scene render 2 years ago
grass.png Initial commit 2 years ago
main.cpp Flying controls 2 years ago
mountain.png Initial commit 2 years ago
obj_1.obj Mountain scene render 2 years ago
pixelGameEngine.h Reference the w from inside the PGE to fix perspective 2 years ago
road.png Initial commit 2 years ago
sig Reference the w from inside the PGE to fix perspective 2 years ago
start.png Initial commit 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