Closed headupinclouds closed 6 years ago
GIT_SELF
should be used only when we are building from drishti/src/examples
(which is useful for testing or as a template for new project). Usually drishti
should be used as a starting directory and GIT_SELF
will not be applied. I have checked Android Studio build and it seems to work with this fix from master.
I think a conservative changes is to allow
??
Option HUNTER_GIT_SELF_IGNORE_UNTRACKED
added to Hunter:
Set to ON
by default in Drishti here: https://github.com/elucideye/drishti/pull/710
Addressed in #710
Reported here: https://github.com/elucideye/drishti/issues/696#issuecomment-411934091
Relevant code: https://github.com/ruslo/hunter/blob/master/cmake/modules/hunter_pack_git_submodule.cmake#L81-L103
The basic command is:
From the top
drishti
repository.Current solution: remove the new/offending files.
Long term solution: If practical, it would be nice to allow
GIT_SELF
to work with some extra local files. It may be worth making a distinction between local changes to committed files and new files in the repository (i.e., my_notes.txt).Notes: https://www.stefanjudis.com/today-i-learned/the-short-version-of-git-status-and-the-close-but-different-porcelain-mode/
I think a conservative changes is to allow
??
but bark aboutM
changes.