Closed kimwalisch closed 8 years ago
Looks good! Maybe squash the README.md changes into one commit, and also the appveyor.yml changes into a separate commit?
I have now changed the build options for Linux testing to:
make debug DEBUG_FLAGS="-W -Wall -Wextra -Werror -pedantic ..."
This way the test will fail on any GCC or Clang compiler warning.
Looks good! Maybe squash the README.md changes into one commit, and also the appveyor.yml changes into a separate commit?
I guess you want only 1 commit per file instead of my many commits and I agree that would be nicer. But to be honest I have now idea how to change this now without destroying my forked libdivide repo, then re-forking and re-committing my code changes and finally creating a new pull request.
As requested I close this pull request a create a new one with fewer commits.
Hi fish,
I have added automated Windows (x86, x64) and Linux (GCC, Clang) testing. For Linux testing we use Travis and for Windows testing we use Appveyor. Both Travis & Appveyor are free for open source projects and work nicely with GitHub. I suggest that you create an account at both https://travis-ci.com and https://www.appveyor.com using your ridiculousfish GitHub account, then enable libdivide for testing in both Travis and Appveyor.
I have further renamed README.txt to README.md. Once you have created your Travis and Appveyor accounts at the top of README.md there will be 2 icons (for Travis and Appveyor) showing the current build status (Green: success, Red: failed). On each new commit to the repository your tester program will be compiled and executed (you can even watch that live on the Travis and Appveyor websites).
Best regards, Kim