ansaurus

Question

Compiling differences in Visual C++ and *nix enviroments

Answer 1

A:

Perhaps try:

#include <stdafx.h> // note angle brackets

This is different from the page you linked, which looks for stdafx.h in the current directory.

Or have you tried replacing that with the #includes in the original file?

Inshallah 2009-07-19 20:01:23

The angled brackets didn't work and neither did my original includes. It's complaining that it can't even find the std namespace! I've added my compiler errors to the questions. This should make it more descriptive.

Mike 2009-07-19 20:06:53

Answer 2

+2 A:

The Visual C++ compiler treats include directives for precompiled headers in a special way, and often they are called stdafx.h, so I'll describe that treatment and see if that's the issue.

Each file using stdafx.h as the precompiled header will have this line at the top.

#include "stdafx.h"

Normally, this means the compiler looks for stdafx.h in the same source folder as the file that included it. However, when stdafx.h is the precompiled header, the Visual C++ compiler automatically includes the project's stdafx.h precompiled output, regardless of where the stdafx.h header or the output is. When the same project is compiled under GCC, GCC won't know where the file is if it's in another folder. You'll have to set the include path of the project appropriately so each preprocessor-related #include can find the proper file.

Normally, when an include file is located in an unknown folder specified only by a compiler [-I] directive, the include is written as:

#include <filename.h>

Unfortunately, Visual C++ doesn't let you use this notation for the precompiled header, and you have to rely on GCC following the include paths even for files specified with "" (double quotes). This behavior may or may not be in the C++ standard, but the one thing you'll want to make sure of is you don't have any extra/unintended stdafx.h files in the source tree, or you may run into even more unexpected compiled-code differences between VC++ and GCC.

280Z28 2009-07-19 20:09:59

Answer 3

+2 A:

Add the below headers in the refactored code,

#include <iostream>
#include <limits>
#include <map>
#include <list>
#include <queue>

Nick D 2009-07-19 20:17:51

Looks like the most likely solution. You can also try just removing the stdafx.h includes and compiling with g++.

Darryl 2009-07-19 21:04:45

Answer 4

A:

The refactored code is missing certain includes. More than likely they are included in the precompiled header, stdafx.h, which usually isn't a good idea. Add the following includes to the bfs.cpp file, in between the "stdafx.h" include and the "using" declaration:

#include "stdafx.h"

#include <set>
#include <list>
#include <map>
#include <queue>
#include <iostream>


using namespace std;

Compiling...
bfs - 0 error(s), 0 warning(s)

lrobb 2009-07-24 11:05:39

Yes, that was the issue. The "set" header wasn't included.Unfortunately, this question has turned more into a "help me debug"-type of question which I didn't intentionally want it to turn into. My apologies.

Mike 2009-07-24 17:34:21

Answer 5

A:

For creating a new project , I recommend this :

New Project-> Empty Project

Then,

Project->Add New Item...-> C++ File (.cpp)

It's different from Win32 Console Application.

Kamran 2010-07-21 22:04:32

ansaurus

tags:

views:

answers:

Compiling differences in Visual C++ and *nix enviroments

related questions