WIP: generalize makefile

[InfiniteVerma]

Description

Generalize makefile by adding variables for compiler, compiler flags, and c files and include directories.
Fixes #125

Motivation and Context

Previously, the makefile had hardcoded c files and paths. Now, with them being listed out in CFILES variable, new files can be added without changes required in the makefile. Also, additional compiler flags can be added by appending them to CFLAGS and SHAREDCFLAGS instead of changing them in all places.

How Has This Been Tested?

Ran make all without errors. Please let me know of any other ways to test this.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Test Coverage (Additional test(s) without any extra code)
• Documentation Improvements

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes. They do not dramatically decrease the test coverage metric
• All new and existing tests passed.
• I give my permission for my code to be used in this project under this license and any future license terms

[ianfhunter]

This is great, exactly what I was hoping for with that issue 👍

However, it looks like there's some problem with the final files as the automated checks for Python (proper test suite) & Go (basic test) fail.

I can't spot what's wrong from the diff, but it might be worth comparing a before and after of the build directory

Go log:

cp: cannot stat 'build/dice.so': No such file or directory

[ianfhunter]

Great! Passing once more & ready to merge!

[InfiniteVerma]

@ianfhunter Not sure what's the issue here. Strangely, the failing GitHub action worked the last time.

[ianfhunter]

@ianfhunter Not sure what's the issue here. Strangely, the failing GitHub action worked the last time.

The one failing GitHub action is just something to add labels to the PR. There's an issue with it, that it does not work when a pull request is from a fork. Bug Link
Not caused by your code!

I've only seen it recently because of new contributors, been meaning to make it ignore failures