The VC\include\ folder of my Visual Studio installations all have "unordered_map" and "unordered_set" C++ header files. My versions are later than Visual Studio 9 though. It may be that Microsoft Visual Studio 9 does not have the desired library file in VC\include\ by default since adding Boost library parts to the C++ Standard is relatively recent. If Boost is installed separately, a relative reference to VC\include\ may be incorrect and the INCLUDE search path should be set up properly for VC to find it.
- Dennis -----Original Message----- From: 郄宁 [mailto:[email protected]] Sent: Thursday, January 15, 2015 03:51 To: dev Subject: Compiling "sal" in cygwin references missing include folder >error C1083: Cannot open include file: '../../VC/include/unordered_set': > No such file or directory > dmake: Error code 2, while making '../../wntmsci12.pro/obj/hash.obj' > > 1 module(s): > sal > need(s) to be rebuilt > > Reason(s): > > ERROR: error 65280 occurred while making > /cygdrive/h/aoo-trunk/main/sal/rtl/source > > When you have fixed the errors in that module you can resume the build > by running: > > build --all:sal > ------------------------------------------------------------------------ > > I confirm that the hash_set file indeed has an include line referencing > the folder "../../VC/include/", which does not exist on my system: > [ ... ] > ------------------------------------------------------------------------ > > Can someone advise how to work around this? Do I need to somehow > specify an STL path in the "configure ..." step? Or do I need to give a > path to the boost library? Or did I miss a warning somewhere? > > My compiler resides at "/cygdrive/c/Program Files (x86)/Microsoft Visual > Studio 9.0/VC/bin", and the folder > "/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 9.0/VC/include" > has its own hash_set file, but no unordered_set file. > > Happy to supply any additional information that may help. > > Regards. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
