Author Topic: MSVS 2005 released...  (Read 17825 times)

Offline Jerubaal

  • Single posting newcomer
  • *
  • Posts: 6
MSVS 2005 released...
« on: October 30, 2005, 01:17:10 am »
Microsoft just released Visual Studio 2005(http://www.gamedev.net/community/forums/topic.asp?topic_id=354463). My main question is, when the free 05 VC++ compliler comes out, will code::blocks as it is currently be able to support it, or will that functionality have to be added? Let me hear your ideas, thoughts, opinions, etc...

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: MSVS 2005 released...
« Reply #1 on: October 30, 2005, 02:32:08 am »
That's an easy one. Has Microsoft introduced new incompatibilities with their latest compiler?

If not, we're all set. :)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5192
Re: MSVS 2005 released...
« Reply #2 on: October 30, 2005, 10:45:10 am »
knowing M$ .... we are not set   :twisted:

There is certainly one great addition, they provide know a console dump (or how should it be called), so even within GUI progs you can send stuff towards cout and cerr and see it in a little pane in the bottom.

I already played around a bit with the beta, and I am in for a though job, all project and workspace files change again, very nice for a version control system ...

Next week I'll even get a free copy @ devconnections in vegas. No, I am not there for the M$ talks, but for the c++ gurus.

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: MSVS 2005 released...
« Reply #3 on: October 31, 2005, 01:31:27 am »
Hey, perhaps you could do some publicity for us ;-)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5192
Re: MSVS 2005 released...
« Reply #4 on: October 31, 2005, 08:49:08 am »
Yes, I will do that. Currently on my laptop there's not even Visual Studio anymore, just Dev-Cpp and Code::Blocks.
So every code stuff will be in CB.   8)

Planning to convince my collegues also, I managed to get them to switch to dev-cpp for an embedded platform a few years ago, planning to this again now for CB, just a few bugs need to be gone and some extra functionality needed (which I can implement some parts of it).

But will need that RC3 or RC2bis first, too many show stoppers (like the right click loses the selection).

Lieven

Offline zieQ

  • Almost regular
  • **
  • Posts: 155
Re: MSVS 2005 released...
« Reply #5 on: October 31, 2005, 11:09:57 am »
I just can try it out, use VS2005 with C::B to see if there are some problems. But i think it will work. Even if the binaries are not the same, the command-lines for compiler/linker are quite the same from version to version. But the auto-detection will fail anyway  :P

royalbox

  • Guest
Re: MSVS 2005 released...
« Reply #6 on: November 12, 2005, 12:57:32 am »
I just downloaded the free express edition of VS 2005. I installed it on another partition I use for testing stuff. I wasn't interested in trying it out I just wanted to try the compiler in code::blocks so I copied the bin folder to a partition, re-started my main partition and went to the bin folder. I opened a command prompt and typed cl /? to have a look to see the commands and got an error message that it wasn't installed properly.

I don't know whether it's registry values or files it's looking for but it certainly is looking for something outside the bin folder. Anyone know? I don't want to install the whole app on my main partition just to try the compiler.

Offline Storkman

  • Single posting newcomer
  • *
  • Posts: 5
    • SchultzNet
Re: MSVS 2005 released...
« Reply #7 on: November 25, 2005, 04:28:01 pm »
Good morning...

I just tried pointing the 2003 config to my 2005 Express installation directories and didn't work.  I forget the exact error message when I told C::B to rebuild, but the essence was the it could not execute cl.exe

I tried just double-clicking on cl.exe from an explorer window and that gave me a missing DLL error (mspdb80.dll, which is in the /common7/IDE subdirectory of the 2005 Express install).  Copying the DLL to various locations (next to cl.exe, to C::B's install directory, etc. - never tried system32 though) didn't solve the problem.  So I'm not sure what the other dependancies are.
Headed for the second star to the right and straight on 'til morning...

  Eric Schultz   (aka Storkman)  Photos: http://community.webshots.com/user/schultznet Homepage: http://www.schultznet.ca Blog: http://schultznet.blogspot.com/

Offline Michael

  • Lives here!
  • ****
  • Posts: 1608
Re: MSVS 2005 released...
« Reply #8 on: November 25, 2005, 04:57:03 pm »
Copying the DLL to various locations (next to cl.exe, to C::B's install directory, etc. - never tried system32 though) didn't solve the problem.  So I'm not sure what the other dependencies are.

Strange. Copying the DLL in the same location as the cl.exe should work or at least give the next missing DLL if any. Have you had a look at what VS C++ 2005 Express Edition installation has put in your env. variables (e.g., PATH)? Look also at which directories (e.g., include, lib) are set in VS C++ 2005 Express edition.

Best wishes,
Michael

Offline takeshi miya

  • Lives here!
  • ****
  • Posts: 1487
Re: MSVS 2005 released...
« Reply #9 on: December 01, 2005, 02:37:32 am »
Hi! Some compiler switches have changed in MSVC 2005.

Here's a list of breaking changes from the previos version:
http://msdn2.microsoft.com/en-us/library/ms177253.aspx

And here's a list of command switches:

C:\Programme\Microsoft Visual Studio 8\VC>cl -? > C:\cl.txt
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.42 for 80x86
Copyright (C) Microsoft Corporation.  All rights reserved.

                         C/C++ COMPILER OPTIONS


                              -OPTIMIZATION-

/O1 minimize space                      /O2 maximize speed
/Ob<n> inline expansion (default n=0)   /Od disable optimizations (default)
/Og enable global optimization          /Oi[-] enable intrinsic functions
/Os favor code space                    /Ot favor code speed
/Ox maximum optimizations               /Oy[-] enable frame pointer omission

                             -CODE GENERATION-

/GF enable read-only string pooling     /Gm[-] enable minimal rebuild
/Gy[-] separate functions for linker    /GS[-] enable security checks
/GR[-] enable C++ RTTI                  /GX[-] enable C++ EH (same as /EHsc)
/EHs enable C++ EH (no SEH exceptions)  /EHa enable C++ EH (w/ SEH exceptions)
/EHc extern "C" defaults to nothrow     
/fp:<except[-]|fast|precise|strict> choose floating-point model:
    except[-] - consider floating-point exceptions when generating code
    fast - "fast" floating-point model; results are less predictable
    precise - "precise" floating-point model; results are predictable
    strict - "strict" floating-point model (implies /fp:except)
/GL[-] enable link-time code generation /GA optimize for Windows Application
/Ge force stack checking for all funcs  /Gs[num] control stack checking calls
/Gh enable _penter function call        /GH enable _pexit function call
/GT generate fiber-safe TLS accesses    /RTC1 Enable fast checks (/RTCsu)
/RTCc Convert to smaller type checks    /RTCs Stack Frame runtime checking
/RTCu Uninitialized local usage checks 
/clr[:option] compile for common language runtime, where option is:
    pure - produce IL-only output file (no native executable code)
    safe - produce IL-only verifiable output file
    oldSyntax - accept the Managed Extensions syntax from Visual C++ 2002/2003
    initialAppDomain - enable initial AppDomain behavior of Visual C++ 2002
    noAssembly - do not produce an assembly
/Gd __cdecl calling convention          /Gr __fastcall calling convention
/Gz __stdcall calling convention        /GZ Enable stack checks (/RTCs)
/QIfist[-] use FIST instead of ftol()   
/hotpatch ensure function padding for hotpatchable images
/arch:<SSE|SSE2> minimum CPU architecture requirements, one of:
    SSE - enable use of instructions available with SSE enabled CPUs
    SSE2 - enable use of instructions available with SSE2 enabled CPUs

                              -OUTPUT FILES-

/Fa[file] name assembly listing file    /FA[scu] configure assembly listing
/Fd[file] name .PDB file                /Fe<file> name executable file
/Fm[file] name map file                 /Fo<file> name object file
/Fp<file> name precompiled header file  /Fr[file] name source browser file
/FR[file] name extended .SBR file       
/doc[file] process XML documentation comments and optionally name the .xdc file

                              -PREPROCESSOR-

/AI<dir> add to assembly search path    /FU<file> forced using assembly/module
/C don't strip comments                 /D<name>{=|#}<text> define macro
/E preprocess to stdout                 /EP preprocess to stdout, no #line
/P preprocess to file                   /Fx merge injected code to file
/FI<file> name forced include file      /U<name> remove predefined macro
/u remove all predefined macros         /I<dir> add to include search path
/X ignore "standard places"             

                                -LANGUAGE-

/Zi enable debugging information        /Z7 enable old-style debug info
/Zp[n] pack structs on n-byte boundary  /Za disable extensions
/Ze enable extensions (default)         /Zl omit default library name in .OBJ
/Zg generate function prototypes        /Zs syntax check only
/vd{0|1|2} disable/enable vtordisp      /vm<x> type of pointers to members
/Zc:arg1[,arg2] C++ language conformance, where arguments can be:
    forScope[-] - enforce Standard C++ for scoping rules
    wchar_t[-] - wchar_t is the native type, not a typedef
/ZI enable Edit and Continue debug info
/openmp enable OpenMP 2.0 language extensions

                              -MISCELLANEOUS-

@<file> options response file           /?, /help print this help message
/bigobj generate extended object format /c compile only, no link
/errorReport:option Report internal compiler errors to Microsoft
    none - do not send report               
    prompt - prompt to immediately send report
    queue - at next admin logon, prompt to send report (default)
    send - send report automatically         
/FC use full pathnames in diagnostics   /H<num> max external name length
/J default char type is unsigned        /nologo suppress copyright message
/showIncludes show include file names   /Tc<source file> compile file as .c
/Tp<source file> compile file as .cpp   /TC compile all files as .c
/TP compile all files as .cpp           /V<string> set version string
/w disable all warnings                 /wd<n> disable warning n
/we<n> treat warning n as an error      /wo<n> issue warning n once
/w<l><n> set warning level 1-4 for n    /W<n> set warning level (default n=1)
/Wall enable all warnings               /WL enable one line diagnostics
/WX treat warnings as errors            /Yc[file] create .PCH file
/Yd put debug info in every .OBJ        /Yl[sym] inject .PCH ref for debug lib
/Yu[file] use .PCH file                 /Y- disable all PCH options
/Zm<n> max memory alloc (% of default)  /Wp64 enable 64 bit porting warnings

                                -LINKING-

/LD Create .DLL                         /LDd Create .DLL debug library
/LN Create a .netmodule                 /F<num> set stack size
/link [linker options and libraries]    /MD link with MSVCRT.LIB
/MT link with LIBCMT.LIB                /MDd link with MSVCRTD.LIB debug lib
/MTd link with LIBCMTD.LIB debug lib   

Offline duncanka

  • Multiple posting newcomer
  • *
  • Posts: 53
Re: MSVS 2005 released...
« Reply #10 on: December 01, 2005, 06:24:41 am »
I tried just double-clicking on cl.exe from an explorer window and that gave me a missing DLL error (mspdb80.dll, which is in the /common7/IDE subdirectory of the 2005 Express install).  Copying the DLL to various locations (next to cl.exe, to C::B's install directory, etc. - never tried system32 though) didn't solve the problem.  So I'm not sure what the other dependancies are.

I had the same problem with the MSVC6 Introductory Edition compiler.  I found that going to Compiler Options --> Select VC++ compiler --> Programs tab --> Additional Paths subtab, and adding the path containing the missing DLL to that list, solved the problem.

royalbox

  • Guest
Re: MSVS 2005 released...
« Reply #11 on: December 01, 2005, 02:27:08 pm »
If anyone works out how to get this compiler working "without" having the whole Visual Studio installed -- similar to toolkit 2003 -- please let us know.

Offline Michael

  • Lives here!
  • ****
  • Posts: 1608
Re: MSVS 2005 released...
« Reply #12 on: December 01, 2005, 02:32:40 pm »
If anyone works out how to get this compiler working "without" having the whole Visual Studio installed -- similar to toolkit 2003 -- please let us know.
IMHO, I am not sure, due to license issues, that you can simply get the compiler/linker (similar to MS Toolkit 2003) without installing at least the "free" Express Edition (and may be deleting later the unwished components).

Best wishes,
Michael

Offline Storkman

  • Single posting newcomer
  • *
  • Posts: 5
    • SchultzNet
Re: MSVS 2005 released...
« Reply #13 on: December 10, 2005, 11:26:02 pm »
If anyone works out how to get this compiler working "without" having the whole Visual Studio installed -- similar to toolkit 2003 -- please let us know.

Good evening...

I was running through the usual cvtres.exe issues with the 2k3 toolkit; and tried to use the cvtres that came with the VC++ Express install; and I get the impression it's a .NET app now. 

Microsoft released 2k3 toolkit to be used from the command line; and C::B just wraps that.  But no 2k5 toolkit has been released.  There is a 2k5 command prompt though so it could be possible.
Headed for the second star to the right and straight on 'til morning...

  Eric Schultz   (aka Storkman)  Photos: http://community.webshots.com/user/schultznet Homepage: http://www.schultznet.ca Blog: http://schultznet.blogspot.com/

royalbox

  • Guest
Re: MSVS 2005 released...
« Reply #14 on: December 13, 2005, 02:30:32 pm »
Thanks for the answers. Maybe Microsoft will release a 2005 toolkit.