The dl (dll "a") I'm writing is going to be distributed to systems that may not have the other dll/lib (dll "b") files installed. I don't want to distribute .lib "b" as a separate file.
The software is for in-house use only. dll "b" adds some new functionality that wont be used by everyone, but there is additional new functionality in dll "a" that everyone will use. I want to make make my .dll compatible with older setups without changing the way people are used to upgrading to the new version. The usual upgrade path is to just copy the new version of the dll over the old one.
Anyway, I want to embed it as a resource. How do I do that?
Main Topics
Browse All Topics





by: waysidePosted on 2009-09-30 at 10:10:35ID: 25460977
What is it you are trying to do with the .lib file?
If you are just trying to carry it as payload, there are a couple of things you can do.
You could insert it as a resource when you build the dll.
Or you can just append it to the back of the dll, and then add the offset in the file where it starts as the last 4 bytes. Open the file, jump to the end-4 bytes, read the offset, jump to it, and then you can read/save out the .lib file.