I am using your library in a project and find it very useful. I use your repo as a git submodule as well as a autoconf subproject. Each time I build my project I see in my git status that the submodule tree is dirty. Indeed, you have automatically generated files tracked in your repo that changes each time I build mine. I propose to you to remove (and so cleanup) all these auto generated files from the repository to avoid git keeping track of them.
libcrafter can still be build from the Git repo with: ./autogen.sh && make
Sounds good. The only difference is that the crafter.h should not be deleted (although crafter.h.in exists, crafter.h is not generated after autogen.sh is executed).
Hello,
I am using your library in a project and find it very useful. I use your repo as a git submodule as well as a autoconf subproject. Each time I build my project I see in my git status that the submodule tree is dirty. Indeed, you have automatically generated files tracked in your repo that changes each time I build mine. I propose to you to remove (and so cleanup) all these auto generated files from the repository to avoid git keeping track of them.
libcrafter can still be build from the Git repo with: ./autogen.sh && make