'''Answer 3''': Before cloning the repository,
you set the core.autocrlf to true by using the following line.
git config --global core.autocrlf
Afterwards, you can freely clone the repository and the build should now work.
Greg: How do I resolve the error where CL cannot be found?=== this is the error that comes up:
'''checking whether the C compiler (cl ) works... no
the correct batch file and if you get this error check the path in the file to make sure it goes to the right place.
Greg: How do I resolve the atlbase.h being missing?===
While running the make command, you get an error saying that atlbase.h file is missing!
After you install it close and open the bat file again and rerun the make file.
Discussion= = ''' NorthWind87:''' With regard to the "windows line error" question, is it not enough to simply set core.autocrlf to false and core. eol to lf?
git config --unset core.autocrlf git config --global --unset core.autocrlf git config --global core.autocrlf false
git config - -unset core.eol git config --global --unset core.eol git config --global core.eol lf
git ls-files -z | xargs - 0 rm; git checkout .
That should be enough to avoid checking out crlf in the future and to checkout the repo again with lf line endings for all files .