All

I can get Visual Studio to pick up <sqlite3.h> from my #include statement in my C++ program, but the Powershell and Command prompt window where I can run "cl" to compile C++ programs cannot find the same <sqlite3.h>. its in the same folder as the C++ program itself. I also cannot get the Dev C++ compiler to find it either. If I change or add #include "sqlite3.h" the command prompt and Dev C++ compilers seem to find it but then start complaining about my System namespace - as if it was unloaded or blown out of memory. I sometimes have the same problem with sqlite3.dll too. Any ideas on how to fix this?

sqllite3 is working great with Visual Studio C++. I even moved the exe to my desktop and put sqlite3.dll in my desktop folder too and it runs great.

"cl" to compile C++ programs cannot find the same <sqlite3.h>. its in the same folder as the C++ program itself.

You need to add to the CL.exe invocation another option, "-I<sqlite_dir>", where "<sqlite_dir>" is replaced by the path to the directory where sqlite3.h resides.

You might find it useful to run "CL.exe /help" and peruse the output sometime.

... I sometimes have the same problem with sqlite3.dll too.

No, you do not. DLLs are located for loading according to an entirely separate set of rules than those by which CL.exe locates #include targets. You can look them up with a simple web search. That could have led to this.

Yes, adding the -I<directory? option to the CL line and putting a few Sqlite objects in the same directory as my cpp source member solved all the Sqlite compile and runtime issues.

Adding an -I<directory> option for the Windows Reference Assembly fixed my namespace System issue as well.

I was also trying to compile under Dev C++ (it uses the gcc compiler) but Dev C++ does not like Windows Reference Assemblies at all. They claim to be incompatible with Visual Studio C++. But that's for another forum. I may try to remove the variable references to System and see if it will compile otherwise - Dev C++ seemed to have no issues with the Sqlite includes.

Thank for the help!

Files that are #include <filename> search for the file in the (system) include path directories and do not look anywhere else at all. This list of directories may be specified in the INCLUDE environment variable or otherwise magically defined by the compiler itself.

Files that are #include "filename" are expected to be in the current directory. The (system) include (and directories listed in the INCLUDE environment variable) are not searched.

You may "append" a directory to the include path by adding -I <directory> to the compiler command tail. Such a direcdtory will be appended to the directories in the (system) include path for the purpose of locating #include <filename> files. If the filename specified in #include "filename" is not found in the current directory the any appended (-I) directories will be searched.

Similarly, libraries can be specified either directly or via -l stem. Such libraries are looked for first in the current directory, and then in the (system) library path. This list of directories may be specified in the LIB environment variable or otherwise magically defined by the compiler itself.

Directories to be searched for link libraries may be specified (and are appended to the search order) by appending -L directory to the compiler command tail.

This has been the way of things since about 1966.

There are a number of places that are searched by the Operating System when it is looking for files. Some are magical, most are specified in environment variables. Examples are PATH (for executables), PATHEXT (the list of executable extensions), LIBPATH, and a few others.

For Dev C++ I was able to just replace Console::WriteLine lines with cout to get past the Windows Reference Assemblies issue. But then I received the dreaded "undefined reference" error on my sqlite functions. But it wasn't a "not found" or "cant open" issue. This suggested a problem with the linker (and not the compiler). So I worked on making sure the linker was looking in the right place.

I have found much of the C++ and associated documentation in digital documentation, on websites, and in books to be very lacking. gcc is no different. Real examples work best for me. I copied the folder sqlite to sqlite3 in case some header file had the sqlite3 hardcoded somewhere. Here is the exact command lines that worked for me.

Compiler

-I"C:sqlite3" -L"C:sqlite3"

Linker

-static-libgcc -lsqlite3 -lsqlite3-64

** Note for the linker command line: those are small cap "L's" after the dashes. And NO quotes around the file names, no folder/directory/path in the file names, and no .lib at the end of the filenames. These are the actual file names without the .lib. The folder/directory/path for libraries is handled in the Compiler argument L above.

This suggested a problem with the linker (and not the compiler). So I worked on making sure the linker was looking in the right place.

...

-static-libgcc -lsqlite3 -lsqlite3-64

For std::cout support, among other things, you'll want -lstdc++.