Re: compiling iso c++ code in Visual Studio environment
RS wrote:
Hi all,
My code compiles well with gcc on linux and OS X, but now I have to run
it at work, and my only choice is Visual Studio .Net 2003 environment on
windows, which I had never used before. I've noticed several obstacles
with the compilation. For example this environment insists that we put
all headers under a stdafx header, which I managed to find a way to get
around. But there are other issues. For example, Visual Studio claims
that there is no such thing as std::numeric_limits. Also, it gives a
bizarre error that there is something wrong with the stdio headers in my
files-- except that I don't use stdio, I use iostream.
I don't need all the fancy windows-specific C++ routines, but I need to
use Visual Studio as a compiler. I was wondering if anyone experienced
with it can give me a hint or two about compiling portable code with it
with minimum overhead. For example, is there an option to check to let
it know we are compiling iso code? Also, are there any online tutorials
or guides for people who need to migrate from gcc to visual Studio 2003?
If not, any good books that don't dwell on C++, but just teaches the
.Net 2003 environment?
Thanks,
RS
RS:
Start a new project and and choose Win32 Console Project. Select a
directory, and then on the next (and final) page, click Application
Settings on the left (yes, an outrageously bad piece of design...), and
select Empty project, then Finish. Now you have an empty project without
all the stdafx.h stuff.
Go to Project->Add Existing Item and add all your source files to the
project. You don't have to first physically copy the files to the
project directory (or a subdirectory of it), but it might be a good
idea, so you have everything in the same place.
Then go to Build->Build Solution, and hold your breath. It might just
work. VC7.1 is a pretty good compiler, so it will not generate errors
for good C++ code. I have a big console project that compiles under both
VC7.1 and gcc with no problems.
If you are getting standard library errors, you may be missing headers.
Different compilers may have standard library headers that include other
headers, making it seem that needed headers are not required.
David Wilkinson