[SOLVED] Error on buildsuper.bat

I literally have just unzipped 4coder and ran the buildsuper.bat file to find:

1
c1xx: fatal error C1083: Cannot open source file: '4coder_default_bindings.cpp': No such file or directory


I've tried with 64 and 32 bit versions.

I don't know what else I can say? I'm on windows 10 using VS2017.

Edited by Aled Jones on
This sounds like the problem in this thread.
Could you try to solution near the end (we don't know if it worked) ? Maybe try disabling your antivirus for the 4coder directory.
Okay, I'll try some solutions.

Some more things to note:
I don't have an antivirus.
4coder_default_bindings.cpp is DEFINITELY there
I've got both a hard drive and an SSD, I've tried running on both the hard drive and the SSD, there is no change in result.

Here's a big one that I just found out from messing about. I have both an SSD and a Hard Drive, I store only my OS and VS on my SSD and I tried to run 4coder on my hard drive, which resulted in the "Cannot open source file". Now I've tried running 4coder from my SSD and I get the following error:
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
PS C:\Users\Aled J\Desktop\4coder> .\buildsuper.bat
'C:\Users\Aled' is not recognized as an internal or external command,
operable program or batch file.
'cl' is not recognized as an internal or external command,
operable program or batch file.
'metadata_generator' is not recognized as an internal or external command,
operable program or batch file.
'cl' is not recognized as an internal or external command,
operable program or batch file.
Could Not Find C:\Users\Aled J\Desktop\4coder\metadata_generator*
Could Not Find C:\Users\Aled J\Desktop\4coder\*.exp
Could Not Find C:\Users\Aled J\Desktop\4coder\*.obj
Could Not Find C:\Users\Aled J\Desktop\4coder\*.lib


As for your solution, I assume this one:
1
cl /I"C:\Users\Oliver\source\ " /W4 /wd4310 /wd4100 /wd4201 /wd4505 /wd4996 /wd4127 /wd4510 /wd4512 /wd4610 /wd4457 /WX /GR- /nologo /FC /Zi 4coder_default_bindings.cpp /Fecustom_4coder /LD /link /INCREMENTAL:NO /OPT:REF /EXPORT:get_bindings /EXPORT:get_alpha_4coder_version


I change it to my appropriate path:
1
cl /I"A:\Documents\4coder" /W4 /wd4310 /wd4100 /wd4201 /wd4505 /wd4996 /wd4127 /wd4510 /wd4512 /wd4610 /wd4457 /WX /GR- /nologo /FC /Zi 4coder_default_bindings.cpp /Fecustom_4coder /LD /link /INCREMENTAL:NO /OPT:REF /EXPORT:get_bindings /EXPORT:get_alpha_4coder_version


And I get a cl not recognized returned.

So this is a problem with Visual Studio?
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
PS C:\Users\Aled J\Desktop\4coder> .\buildsuper.bat
'C:\Users\Aled' is not recognized as an internal or external command,
operable program or batch file.
'cl' is not recognized as an internal or external command,
operable program or batch file.
'metadata_generator' is not recognized as an internal or external command,
operable program or batch file.
'cl' is not recognized as an internal or external command,
operable program or batch file.
Could Not Find C:\Users\Aled J\Desktop\4coder\metadata_generator*
Could Not Find C:\Users\Aled J\Desktop\4coder\*.exp
Could Not Find C:\Users\Aled J\Desktop\4coder\*.obj
Could Not Find C:\Users\Aled J\Desktop\4coder\*.lib

Here it seems that the space in your user name is causing an issue. Try to put it in another folder e.g. C:\4coder\.

To run the the cl command, you need to call vcvarall.bat before. buildsuper.bat does it for you, but when you run the command yourself you need to call it once before. And you need to pass it "x64" for to compile 64bi (x86 for 32bit). For VS2017 the file is in
1
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat

Another possible fix would be to create a copy of 4coder_default_bindings.cpp and pass the name of the copy to buildsuper.bat.
1
2
3
// Assuming you are in the 4coder directory
copy 4coder_default_bindings.cpp custom_layer.cpp
buildsuper.bat custom_layer.cpp
I don't know what finally did it, but I did all of what you suggested and it works!

Thanks a bunch!
Thanks for posting! I've noticed a couple of bugs here that look like my fault and I will try to track them down and address them in the next build. Glad you got it working already though.

Thanks for the help mrmixer.