mirror-github-bspeice/libcvautomation
1
0
Fork 0
mirror of https://github.com/bspeice/libcvautomation synced 2024-12-03 21:38:12 -05:00
Code Issues Releases Wiki Activity

Update the README to link to documentation

Browse Source
This commit is contained in:
Bradlee Speice 2013-07-10 20:48:59 -04:00
parent 78893bc975
commit 50c2412454
2 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README
View File

@ -34,9 +34,12 @@ Place the following lines into your `/etc/apt/sources.list`:
The tarball can be downloaded from the [downloads](https://github.com/DjBushido/libcvautomation/downloads) page.
Once you have it, just `./configure; make; make install`
## API Documentation ##
Github hosts the documentation, and it can be found [here](https://djbushido.github.com/libcvautomation/)
## Where we're headed ##
At this point, most everything is functionally done. I'll develop python bindings to make interfacing with the library simpler, but it will be mostly bugfixes until I can get to those. If there are any suggestions, please let me know!
At this point, pretty much everything is functionally done. Python bindings to make interfacing with the library simpler have been developed, and it should mostly be bugfixes from here out. If there are any suggestions, please let me know!
## Get in contact ##
If you have a suggestion, comment, question, concern, or otherwise, feel free to email me at <bspeice@uncc.edu>. This product is developed with the community in mind, so if there's any feedback to be had I welcome it.

3
README.md
View File

@ -34,6 +34,9 @@ Place the following lines into your `/etc/apt/sources.list`:
The tarball can be downloaded from the [downloads](https://github.com/DjBushido/libcvautomation/downloads) page.
Once you have it, just `./configure; make; make install`
## API Documentation ##
Github hosts the documentation, and it can be found [here](https://djbushido.github.com/libcvautomation/)
## Where we're headed ##
At this point, pretty much everything is functionally done. Python bindings to make interfacing with the library simpler have been developed, and it should mostly be bugfixes from here out. If there are any suggestions, please let me know!