git - Compiling workflow with version control -


up till i've used version control simple web-based projects don't have compile stage. i've forked relatively large project follows standard "./configure; make; make install" pattern. i'm unsure proper workflow type of project.

what do created files compile process?

  • add lots of stuff .gitignore? hard, because did not create build process , not understand created.
  • checkout project somewhere else each build? seems pain, given build every few minutes.
  • just make sure never add don't know about, i.e. never git add . if so, how cleanup , then?

obviously deals compiled code faces, i'm sure there's accepted pattern, not familiar yet.

i agree chrisf, don't store binaries generated build in repository. goal should have nice .gitignore file, @ time running git status should show no "untracked files". means git either ignoring or tracking files.

one procedure use build .gitignore this:

  1. add , commit source project (before built)

    cd project

    git add .

    git commit -m'initial import'

  2. add simple patterns of files ignored .gitignore; includes tings *.o, *.so.

    echo '*.o' > .gitignore

    echo '*.so' >> .gitignore

  3. then run build.

    make

  4. then run

    git ls-files -o >> .gitignore

    which pick outstanding files generated didn't specify glob patterns.

-bart


Comments

Popular posts from this blog

c++ - How do I get a multi line tooltip in MFC -

asp.net - In javascript how to find the height and width -

c# - DataTable to EnumerableRowCollection -