4coder » Forums » Unable to build using buildsuper.bat
Zarickan
Frederik
2 posts
#15188 Unable to build using buildsuper.bat
3 months, 1 week ago Edited by Frederik on May 8, 2018, 5:40 p.m. Reason: Initial post

I am unable to build using buildsuper.bat, I get the following error when I try to build it:

1
2
3
4
5
6
7
8
9
4coder_metadata_generator.cpp
LINK : fatal error LNK1104: cannot open file 'LIBCMT.lib'
'metadata_generator' is not recognized as an internal or external command,
operable program or batch file.
4coder_default_bindings.cpp
LINK : fatal error LNK1104: cannot open file 'LIBCMT.lib'
Could Not Find C:\4coder_test\metadata_generator*
Could Not Find C:\4coder_test\*.exp
Could Not Find C:\4coder_test\*.lib


The contents of the directory are exactly those of the zip with the latest x64 windows build, and looks like this:
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
 Directory of C:\4coder_test

08-05-2018  19:37    <DIR>          .
08-05-2018  19:37    <DIR>          ..
08-05-2018  19:37    <DIR>          4coder_API
08-05-2018  19:36            31.166 4coder_auto_indent.cpp
08-05-2018  19:36            43.281 4coder_base_commands.cpp
08-05-2018  19:37             8.702 4coder_build_commands.cpp
08-05-2018  19:37             5.079 4coder_clipboard.cpp
08-05-2018  19:37               946 4coder_default_bindings.cpp
08-05-2018  19:37            45.360 4coder_default_framework.h
08-05-2018  19:37            17.172 4coder_default_hooks.cpp
08-05-2018  19:37            29.402 4coder_default_include.cpp
08-05-2018  19:37            14.989 4coder_file.h
08-05-2018  19:37            14.064 4coder_function_list.cpp
08-05-2018  19:37    <DIR>          4coder_generated
08-05-2018  19:37    <DIR>          4coder_helper
08-05-2018  19:37            13.933 4coder_jumping.h
08-05-2018  19:37             5.276 4coder_jump_direct.cpp
08-05-2018  19:37            24.075 4coder_jump_sticky.cpp
08-05-2018  19:37    <DIR>          4coder_lib
08-05-2018  19:37            22.918 4coder_metadata_generator.cpp
08-05-2018  19:37             1.171 4coder_os_comp_cracking.h
08-05-2018  19:37            32.235 4coder_project_commands.cpp
08-05-2018  19:37             2.044 4coder_remapping_commands.cpp
08-05-2018  19:37            29.521 4coder_scope_commands.cpp
08-05-2018  19:37            35.870 4coder_search.cpp
08-05-2018  19:37             1.201 4coder_search.h
08-05-2018  19:37             1.792 4coder_system_command.cpp
08-05-2018  19:37           684.544 4ed.exe
08-05-2018  19:37           306.688 4ed_app.dll
08-05-2018  19:37             1.058 buildsuper.bat
08-05-2018  19:37             1.335 config.4coder
08-05-2018  19:37    <DIR>          fonts
08-05-2018  19:37    <DIR>          languages
08-05-2018  19:37             1.294 LICENSE.txt
08-05-2018  19:37               315 README.txt
08-05-2018  19:36    <DIR>          themes
08-05-2018  19:37           241.664 vc120.pdb
08-05-2018  19:36    <DIR>          windows_scripts
              28 File(s)      1.617.095 bytes
              10 Dir(s)  23.906.037.760 bytes free
Mr4thDimention
Allen Webster
402 posts / 2 projects

Heyo

#15189 Unable to build using buildsuper.bat
3 months, 1 week ago

Hmmm what could that be...

Well a few things to get straight first:
1. What versions of Visual Studio do you have installed?
2. Which version do you use normally?
3. Do you setup the environment variables yourself before your run the script? (i.e. Do you run vcvarsall.bat or whatever the batch file is for your version before running buildsuper?)
4. Just to be sure, is this the 64bit version?
Zarickan
Frederik
2 posts
#15227 Unable to build using buildsuper.bat
3 months, 1 week ago

1/2. Visual Studio 2017
3. Just buildsuper.bat
4. 64-bit

It seems "manually" calling vcvarsall.bat before running buildsuper.bat fixes this.
Mr4thDimention
Allen Webster
402 posts / 2 projects

Heyo

#15234 Unable to build using buildsuper.bat
3 months, 1 week ago

Hmm okay. The script tries to figure out which visual studio version to use and initializes it, but it may not have 2017 in it's list or something. Thanks for taking a look at that, I'll try to fix it in the next build.