"Failed to inject DLL" on Windows

[tomeksowi]

Trying to build A First Tupfile returns an error encountered in #168 and #147:

[ tup ] [0.002s] Scanning filesystem...                            
[ tup ] [0.004s] Reading in new environment variables...           
[ tup ] [0.005s] No Tupfiles to parse.                             
[ tup ] [0.006s] No files to delete.                               
[ tup ] [0.007s] Executing Commands...                             
 [ ]   0%tup error: failed to inject dll: No such file or directory
 *** Command ID=26 failed: gcc hello.c -o hello.exe                
 [ ]   0%                                                          
 *** tup: 1 job failed.

Everything is according to the tutorial except my Tupfile is adjusted for the .exe suffix on Windows:

: hello.c |> gcc hello.c -o hello.exe |> hello.exe

Needless to say, the gcc command outside tup works fine and the tup directory with all the executables and tup-dllinject(32).dll is in path.

• Windows 10 Pro version 1803 build 17134.829
• tup v0.7.8-20-g1d2fd514 (v0.7.8 also doesn't work)

[Wetmelon]

This is probably related to the tup32detect.exe problem. Make sure it's not being quarantined by your AV

[gittup]

This is probably related to the tup32detect.exe problem. Make sure it's not being quarantined by your AV

It could be, though with that version of tup, if I remove tup32detect.exe from the system, I see a different error:

[ tup ] [0.250s] Executing Commands...
 [ ]   0%Unable to retrieve WOW64 info
tup error: failed to inject dll: No error
 *** Command ID=25 failed: gcc hello.c -o hello.exe
 [ ]   0%
 *** tup: 1 job failed.

I'm not sure if removing it is representative of what would happen with an AV blocking it, though.