Hello, all. I have created dll's with the bloodshed compiler and would now like to compile a static lib. Unfortunately, there seams to be no documentation on this, for this compiler and even in general. Can someone point me in the right direction?
Also, with regard to lib's, how does one handle the matter of hiding template interface implementation from the user, since template compilation must "see" everything to work? This has been perplexing me for some time now.
Any advice on either general or specific information on creating a statically linked lib would be appreciated.
Thanks.
- Sebastian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can't believe I overlooked that. Thank you very much. One more question. At one point I naively tried just renaming an object file from ".o" to ".lib". It didn't work. Can you explain to me why this isn't possible?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok. Figured it out. I started an empty project, and then went to Project->Project Options->Project Type->Create A DLL.
Unlike starting a DLL Project, this actually produced a ".a" file.
Thanks again for the help.
- Sebastian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sure it's an .a file cause you're working with gcc :-)
MS-VC would produce .lib files while gcc's are allways .a (stands for archive, I guess).
Renaming an object file doesn't work because a .a file is a library or an archive that consists of objects files. It's not an object file itself...
Bye!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, all. I have created dll's with the bloodshed compiler and would now like to compile a static lib. Unfortunately, there seams to be no documentation on this, for this compiler and even in general. Can someone point me in the right direction?
Also, with regard to lib's, how does one handle the matter of hiding template interface implementation from the user, since template compilation must "see" everything to work? This has been perplexing me for some time now.
Any advice on either general or specific information on creating a statically linked lib would be appreciated.
Thanks.
- Sebastian
Yes, you can create a static lib. Just create a new project and select the static lib option.
I can't believe I overlooked that. Thank you very much. One more question. At one point I naively tried just renaming an object file from ".o" to ".lib". It didn't work. Can you explain to me why this isn't possible?
Ok. I do not see any option for this after all. Are you sure there's a tab for that?
- Sebastian
Ok. Figured it out. I started an empty project, and then went to Project->Project Options->Project Type->Create A DLL.
Unlike starting a DLL Project, this actually produced a ".a" file.
Thanks again for the help.
- Sebastian
Sure it's an .a file cause you're working with gcc :-)
MS-VC would produce .lib files while gcc's are allways .a (stands for archive, I guess).
Renaming an object file doesn't work because a .a file is a library or an archive that consists of objects files. It's not an object file itself...
Bye!