there are a lot of errors generated so I attached the errors as a file. groups of errors like sections of a document got #included twice somehow, maybe with <windows.h> first?
#include <windows.h> //#include <winuser.h> //GetSystemMetrics #include <shlobj.h> //SHGetFolderPath(), SUCCEEDED() #include <string> #include <vector> #include <map> #include <iterator> #include <initializer_list> #include <cctype> #include <iostream> #include <fstream> #include <sstream> #include <ios> #include "stricmp.h" #include "strip-ws.h" #include "rnd.h" #include <shobjidl.h> #include <direct.h> //_mkdir() //#include <windows.h> #include <stdio.h> #include <Unknwn.h> //IUnknown QueryInterface,Release, AddRef #include <initguid.h> #include <wincodec.h> //IWICImagingFactory::CreateStream, IWICImagingFactory::CreateDecoderFromFilename,IWICStream::InitializeFromFilename, IWICBitmap Encoder::Initialize, etc. #include <objbase.h> //CoInitialize //#include <Stringapiset.h> //MultiByteToWideChar #include <comip.h> //MultiByteToWideChar #include <comdefsp.h> //#include <bidispl.h> //#include <objidl.h> //grasping at straws #include <Winbase.h> //HeapAlloc //#include "stdafx.h" #include <windows.h> #include <winnls.h> #include <shobjidl.h> #include <objbase.h> #include <objidl.h> #include <shlguid.h> #include <vfw.h> //IPersistFile #include <comdefsp.h> //IPersistFile #include <shlobj.h> //CoCreateInstance #include <objbase.h> //CoCreateInstance //#include "stdafx.h" #include <windows.h> #include <shobjidl.h> #include <shlguid.h> #include <strsafe.h> #include <objidl.h> //#include "windows.h" //#include "stdio.h" //#include "initguid.h" //#include "wincodec.h"
the program is outmoded, it sets the desktop wallpaper once per boot. now we have windows 10 and it's no longer useful. but it seems to make a good test rig for the compiler. it's about 99% com+ in C++.
clue on how to fix:
overview of header files:
grep -n "#" *.h
in header file:
Has anyone looked into this to see if it's a valid issue?
Ozkan, I stopped looking into op's reports ... I think it is save to close it as works-for-me. If we have here real issues, we will get sooner or later hopeful a report by a more responsive user.
OK then, closing as works-for-me.