From: Per W. <pw...@ia...> - 2005-02-21 14:21:06
|
Dev-Cpp doesn't find them on it's own because it is specified not to. It doesn't add any library files to the linker on it's own for the same reason that it doesn't include any header files on it's own either. If you want to include a header file, you _have_ to use an #include statement. If you want to add a library when linking, you _have_ to use the -lname option. Notice that it isn't so easy to auto-locate which libraries that are needed, since there are often multiple libraries that exports the same symbol. You might have debug libraries, single-threaded libraries, multi-threaded libraries, stand-alone "lite" libraries, stub libraries for dynamic loading, etc, etc, etc. The header file specifies the prototypes of functions, variables or types that may be used. The library statement specifies what actual implementations to link into the application. /Per W On Sun, 20 Feb 2005, Alfred P. Reaud wrote: > I have no clue as to why Dev-Cpp doesn't find them on it's own. |