#Develop compiler issue

[snarfblam]

I am trying to compile C++ code with #Develop, but I'm getting this error:

 

http://www.geocities.com/marble_eater/err.JPG

[John]

Do you have Visual C++ installed? If not you can get the free command line version here:

http://msdn.microsoft.com/visualc/vctoolkit2003/

[snarfblam]

I have cl.exe on my drive. I downloaded the vctoolkit you linked to anyways, which didn't help. I added that path that contains cl.exe to the PATH environment variable, which didn't help. I can call cl.exe from the command prompt exactly as it is listed in the error message.

 

 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|►

[/Code]

 

I don't understand why if I can do it, #Develop can't...

Edited May 10, 2005 by snarfblam

[snarfblam]

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.

 

http://www.geocities.com/marble_eater/errr.jpg

 

When I tried to do it via commandline I got the following error:

 

 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|►

[/Code]

 

I checked and it seems the file does not exist. I don't know how to do a command line compile, though, I'm just guessing here. Appearently, though, I'm having no prob calling link.exe from the command prompt.

Edited May 10, 2005 by snarfblam