February 12th, 2003, 02:26 PM
making a library? DLL or .o file
I am very solid in ANSI/ISO C and C++, but know very little proprietary library-oriented and API stuff (like the UNIX APIs for sockets and pipes or true Win32 programming).
I have long searched casually on bookstore shelves and the net for a simple introduction into the process.
I have learned MFC to some degree for making windows programs and gave tk a casual glance in Linux.
Okay, my question:
Do you know where I can find a good starting place to learn more about doing the following?
1) make a library in unix that I can dynamically bind to. This would be the notion of haveing a .h file and a .c or .cpp file that provides an implementation for the interface described in the .h file. I would then be able to compile a .o that can be used so long as the .h file is present?
2) Making DLLs. I believe this is roughly the windows equivalent of what I am getting at in point #1 above.
Again, I am strong in my ANSI/ISO-level skillset that covers the core of both C and C++, but need to move to the next level by learning things like making libraries. I really don't care for Windows programming as MS code looks really weird to me (LPSTR and that kinda thing).
Anyhow, if anyone has a nice nudge for me in the proper direction I would be grateful and I promise to RTFM as soon as I can find out where the FM is on these topics.
Thanks very much,
February 12th, 2003, 07:03 PM
February 13th, 2003, 12:36 AM
BTW, do you have any info on making the DLL the VC++ way?
Thanks a million!
February 13th, 2003, 03:00 PM