Complete.Org: Mailing Lists: Archives: freeciv-dev: June 1999:
Re: [Freeciv-Dev] File Naming Conflict
Home

Re: [Freeciv-Dev] File Naming Conflict

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: ablack@xxxxxxxxxxxxxx
Cc: freeciv-dev@xxxxxxxxxxx
Subject: Re: [Freeciv-Dev] File Naming Conflict
From: David Pfitzner <dwp@xxxxxxxxxxxxxx>
Date: Wed, 16 Jun 1999 16:53:48 +1000 (EST)

Andy Black wrote:

> I recently discovered a naming conflict.  Metroworks Codewarior 10 and
> probably all C++ compiliers (g--?) have this conflict.  The file map.h in
> freeciv conflicts with the map.h used in the Standard Template Library,
> part of ANSI C++ standard (I think).  This conflict also is caused by my
> prevous noted problem with people useing #include <...> insted of #include
> "..." for project files. 

Well, on a Unix system, with the configure-produced makefiles
we use, this isn't a problem, because freeciv is compiled with 
flags like "-I. -I../common" which cause _both_ #include <> and 
#include "" look in the freeciv source directories _before_ 
looking in the system directories.  

But in any case the freeciv sources in CVS now use #include "",
so if you use the CVS sources you won't have this problem.

(With some exceptions, such as #include <config.h> instead of 
#include "config.h".  This (and the -I flags) makes sure the
right config.h is included even if there happened to be a different
config.h in one of the source directories.)

Regards,
-- David

[Prev in Thread] Current Thread [Next in Thread]