I have cl.exe on my drive. I downloaded the vctoolkit you linked to anyways, which didnt help. I added that path that contains cl.exe to the PATH environment variable, which didnt help. I can call cl.exe from the command prompt exactly as it is listed in the error message.
Code:
C:\WINDOWS|► cl.exe "@C:\Docume~1\Tom\Locals~1\Temp\tmp59.tmp"
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86
Copyright (C) Microsoft Corporation 1984-2002. All rights reserved.
cl /c
/clr
/Fo"C:\VB\Cxx\bin\Debug/"
/nologo
/W"4"
/EHsc
/MT
/J
/GR
/Y-
/Gd
/TP
"C:\VB\Cxx\MainForm.cpp"
"C:\VB\Cxx\AssemblyInfo.cpp"
MainForm.cpp
AssemblyInfo.cpp
Generating Code...
C:\WINDOWS|►
I dont understand why if I can do it, #Develop cant...
Well... I edited the PATH environment to include the folder above the "Bin" folder, which includes a batch that will include the bin folder... which seems to have gotten me farther in compilation, up to this new error message.
When I tried to do it via commandline I got the following error:
Code:
C:\WINDOWS|► link.exe "@C:\Docume~1\Tom\Locals~1\Temp\tmp6E.tmp"
Microsoft (R) Incremental Linker Version 7.10.3077
Copyright (C) Microsoft Corporation. All rights reserved.
"/OUT:C:\VB\Cxx\bin\Debug\Cxx.exe"
"C:\VB\Cxx\bin\Debug\MainForm.obj"
"C:\VB\Cxx\bin\Debug\AssemblyInfo.obj"
LINK : fatal error LNK1104: cannot open file LIBCMT.lib
C:\WINDOWS|►
I checked and it seems the file does not exist. I dont know how to do a command line compile, though, Im just guessing here. Appearently, though, Im having no prob calling link.exe from the command prompt.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.