leetnightshade/math.beta
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
21 commits 1 branch 0 tags 50 KiB
Find a file
Brian 1af797b1d8 Making the readme more clear on the design direction of this lib. In the future I'll have a more advanced version utilizing platform specific enhancements, this will be in a different repo entirely.
2014-02-20 18:55:04 -07:00
doc setting up directory structure 2014-02-19 20:40:09 -07:00
include Updated readme, and updated main so you don't need to run the test program on the commandline. 2014-02-20 12:52:11 -07:00
src Adding more file/folder stubs. 2014-02-19 21:13:56 -07:00
tests Updated readme, and updated main so you don't need to run the test program on the commandline. 2014-02-20 12:52:11 -07:00
.gitmodules adding external, or trying to anyway 2014-02-20 11:42:56 -07:00
README.md Making the readme more clear on the design direction of this lib. In the future I'll have a more advanced version utilizing platform specific enhancements, this will be in a different repo entirely. 2014-02-20 18:55:04 -07:00

README.md

math

C++ GameDev related math helpers. These helpers will be designed and written for ease of use, to be as simple as possible. In a commercial engine they would be designed out differently, and I would be utilizing architecture specific performance improvements (compiler intrinsics). These are primarily 3D math helpers, and do not contain any physics related code, collision, etc.

Requirements

Aside from a C++ compiler, there are no external dependencies outside of the stdlib. However, for running unit tests I use igloo, which is already referenced, and you'll need premake4.

Cloning

Since there's an external for testing, don't forget --recursive: git clone --recursive https://github.com/leetNightshade/math.beta.git.

Testing

You'll need premake4. On the commandline premake4 --help to see what project types are available for your platform, and pick the project type you want to use. For example, on Windows I'll use premake4 vs2010. From there build your project. When it's done building, run the program directly; for convenience you don't need to run it from the commandline.