Hey there!
A few things before we get started. The log contains a lot of useless information. Especially the part where it’s just running smoothly makes this wall of text a lot longer than it needs to be and therefore much harder to read and follow.
Only the unexpected elements, errors or possibly warnings, are of interest.
In this case, there are two interesting lines.
LINK : fatal error LNK1181: cannot open input file ‘C:\Program Files\Epic Games\UE_4.19\Engine\Plugins\UE4Duino\Binaries\Win64\UE4-UE4Duino.lib’
Alright, so a file can not be opened for some reason and we have an error code “LNK1181” ← This thing you can google with quite fair results. Alternatively, “ue4 cannot open input file” will also yield a lot of information.
See logfile for details: ‘xgConsole-2018.11.16-14.18.25.txt’ UATHelper: Packaging (Windows (64-bit)): (see C:\Users\ZAP\AppData\Roaming\Unreal Engine\AutomationTool\Logs\C+Program+Files+Epic+Games+UE_4.19
And this line tells you where you can find the actual logs, and not just the updates you get from the console / output log. These are only there to keep you informed about what’s happening in real time and not so much for information that can used to debug. Debugging may depend on tons of additional factors and instead of dumping tons upon tons of text at you, they keep this output smaller and more informative.
Meaning, if you can not find the error right away from the error code, check out the long version of the logs instead.
And of course, take the time to read your error messages. You can always look up the snippets you don’t understand on your search engine of choice!
As for your problem, it’s not quite obvious from the first few threads I’ve found. But you could attempt to delete your binaries, intermediate and saved folders and attempt to build again. That might fix it already.