Compiling C++ Static Libraries in Visual Studios .NET...help!!!

Shemsi en Tehuti · (#1 (**permalink**))

I havemy own collection of C++ functions with sophisticated algorthms and routines that I developed in platform standard C++ to run on Unix/Linux G++ compiler, Borland compilers up to 5.5, and Visual Studios 6.0. With Microsofts unremitting additions of the .NET platform, I need to create a static library of my old tried-and-true functions so that I can use it in any future .NET application.

When I try to compile the library, I get the following error:

fatal error C1083: Cannot open include file

...for eachsource and header file. If any of you are programmers, you are probably like, "duh, you aren't specifying the directory for the compiler to build the files". I know this already. I have specified it where it seems most intuitive, and searched and even specified this in not so intuitive places...but with no success.

I could easily build a library in the older Borland, G++, or Visual Studio 6.0 environments, but I want this to be compiled the most efficiently for more modern processors.

Does anyone know how to compile a static library in Visual Studios .NET???

huzzah1 · (#2 (**permalink**))

Haven't used Visual Studio .NET in over a year. The C1083 error may be caused by the following

Cannot open filetype file: 'file': message

Possible causes

File does not exist.
File, subdirectory, or disk is read-only.
No access permission for file or directory.
Not enough file handles. Close some applications and recompile.
The INCLUDE environment variable is set incorrectly.
An #include directive uses double quotation marks around a path specification, which causes the standard directories to be skipped.
You did not specify/clrand your program uses managed constructs.
In Visual C++.NET (version 1300 of the compiler), there is a bug that requires the user locale to be set correctly when the file name (or directory path to the file name) contains MBCS characters. Setting the system locale is not sufficient; the user locale must be set to process MBCS characters.

The following sample generates C1083:
// C1083.cpp
#include "test.h" // C1083, test.h does not exist

int main() {
}[/code]