I'm attempting to build the boost library set with Intel C++ v8.0.
Given the nature of this product I guess I'm still using msvc 6.0 sp5, which is on my system.
I also am attempting to use STLPort-4.5 with this build.
Luckly, the boost build has an intel-win32-stlport tool set.
With some tweaking, probably (maybe) because of v8.0, I'm done to one problem.
This is all dll builds fail for want of a _declspec(dllimport) symbol.
The way I interprete this is that your compiler doesn't use Microsoft's propritary __declspec(dllimport/dllexport) stuff.
If this is true is it because your xilink component doesn't simply call link for making dlls?
I hope it is because this is the primary reason I'm investigating this compiler.
I want to find a way around the dll usage limits present with Microsoft's msvc v6.0 product. With it, for instance, the only thing you could use across a dll boundary in a Cpp program was abstract interfaces (no more than what COM is capable of).
My experience with linux and the capacity of shared libraries tells me vendors can to much better than this.
Am I going to find what I'm looking for with this compiler?