Werner, After I had replied here asking for help, you know the statement: for the love of God could someone help me, I got a reply back in the Visual C++ forums, and I realize that I think the whole project is not set properly. Someone has mentioned that I should be creating a DLL project, but the freetype project is something else, and I have not figured out what type it is yet. However, in the mean time, speaking in any compiler terms again, how many dlls and libs should the compiler produce or does this depend on what you are looking to do with Freetype? If it depends on what you are doing with FreeType, then maybe I can shed some more light to you about BrutalChess. I downloaded the demo game, (already compiled), to see how it should fall into place. The DLL's that are included in the game are as follows.... FreeType6.dll jpeg.dll sdl.dll sdl_image.dll zLib1.dll
... Now let me explain what I have. Firstly, with the SDL library, which includes sdl.lib sdl.dll, sdl_image.lib, and sdl_image.dll, already comes compiled, so all you have to do is include the libs to the compiler and dll's stay in the project folder. Second, I am not sure what jpeg.dll and zlib.dll are as of yet. Third with FreeType6.dll, it appears that the dll name is different from what the linker error had mentioned when I went to compile BrutalChess. The linker error was that it could not find the freetype.lib. This is what is confusing the heck out of me. Does this help explain my confusions? Werner LEMBERG wrote: > > >> So are you saying that, since you do not know how Visual C++ works, >> but by running a compiler that would not give any problems, it >> should create the files, or are there more procedure steps then just >> compiling the src files? > > The steps, regardless which compiler, are > > . compile FreeType to get a library > . compile the application and link the FreeType library with it > >> If it is as simple as just compiling the files, then what compiler >> would you suggest that you know of, Borland C++? > > While FreeType should compile with a wide variety of compilers (both C > and C++ -- for the latter you should use the current CVS), this isn't > probably true for your application. > > A guess: What about modifying FreeType's VC++ project file, renaming > the library to `FreeType.lib' as you need it? Perhaps a simple > renaming will do the trick also... > >> as for thinking you wrote the stuff, I was refering to this link >> http://www.mail-archive.com/[EMAIL PROTECTED]/msg00064.html > > Well, someone sent me the project files, and I've added them blindly > to the CVS. > > > Werner > > > _______________________________________________ > Freetype mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/freetype > > -- View this message in context: http://www.nabble.com/Link-Error%3A-could-not-open-FreeType.lib-tf4167684.html#a11936290 Sent from the Freetype - User mailing list archive at Nabble.com. _______________________________________________ Freetype mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/freetype
