Closed ADiea closed 7 years ago
it looks like git apply looks for
<SPACE>MFORCE32 := $(shell $(CC) --hel...
but in the Makefile the string is without leading space. Looking for way to ignore the leading space in the patches
No I think that the error is beacause git searches for "line1 \n line2" and my sources are cloned using windows style "line1 \r\n line2" -> so this is probably from a setting on my side, will test and close the issue but should be present as a warn on getting started page
Still having issues here applying the patch. It says it does not find a section of 7 lines at the begining of axtls/src/Makefile starting from line 7 but I look in the Makefile and the section is there...anyone had this issue before? I also started a bash console with Administrator rights fearing that it cannot read Makefile same error, still investigating. Line endings and trailing spaces seem not to be related to this
Just for the test try to apply the patch manually with the patch
command instead of git apply ..
and tell me if it works for you.
It finally worked with --ignore-whitespace
--ignore-whitespace
When applying a patch, ignore changes in whitespace in context lines if necessary. Context lines will preserve their whitespace, and they will not undergo whitespace fixing regardless of the value of the --whitespace option. New lines will still be fixed, though.
The thing is I compared the Makefile with the patch hunk and there were no differences so this is really strange.
using patch command or using git apply --reject applied libc.c and mem.c patches in /replacements but still failed on Makefile and subsequent files. I will make again a clean clone and test with modified makefile with whitespace option included and if it works will submit a PR. Strange noone elese has this issue
My system is now a Win10 Home edition + UDK 2.2.1
Later Edit: It works with squelched whitespace errors
Applied patch replacements/libc.c cleanly.
Applied patch replacements/mem.c cleanly.
Applied patch Makefile cleanly.
Applied patch ssl/os_port.h cleanly.
Applied patch ssl/tls1.c cleanly.
Applied patch ssl/tls1.h cleanly.
Applied patch tools/make_certs.sh cleanly.
warning: squelched 175 whitespace errors
warning: 180 lines add whitespace errors.
Fixed by setting global CRLF config for windows. This should be added to appropiate getting started section for windows
git config --global core.autocrlf input
now patches apply cleanly
Checking patch replacements/libc.c...
Checking patch replacements/mem.c...
Checking patch Makefile...
Checking patch ssl/os_port.h...
Checking patch ssl/tls1.c...
Checking patch ssl/tls1.h...
Checking patch tools/make_certs.sh...
Applied patch replacements/libc.c cleanly.
Applied patch replacements/mem.c cleanly.
Applied patch Makefile cleanly.
Applied patch ssl/os_port.h cleanly.
Applied patch ssl/tls1.c cleanly.
Applied patch ssl/tls1.h cleanly.
Applied patch tools/make_certs.sh cleanly.
warning: 2 lines add whitespace errors.
This should be added to appropiate getting started section for windows
@ADiea Can you please do this?
Done, put it in wiki -> getting started for windows page.
Done, put it in wiki -> getting started for windows page.
@ADiea Great! Thanks a lot.
Hi, Building on Windows with UDK [v2.2.1] Clean sming clone, develop branch.
Looks like axtls patch cannot be applied because the search string is not found. Is this working on windows? Could it be some parameter for git apply patch to ignore whitespaces etc?
Is anyone still building on windows/udk can you confirm sming building OK with ENABLE_SSL=1
Output