Thanks again for the help in the past week.
I still have a question, we use the library only for the HTTP part. The HTTP component uses several other parts(ex. CKString) of the library and makes our application unnecessarily large. My question is, is it possible to get a leaner version of the library / HTTP component?
I like to hear what the possibilities are.
When linking with a C++ static library, the linker will only included code from the .lib that is directly or indirectly referenced. Therefore, it makes no difference if a .lib contains other classes or functions that are not referenced -- they are already not included in your .exe after linking.
Any serious HTTP implementation will certainly add significantly to the size of your EXE. It's because HTTP indirectly uses much of the underlying internal infrastructure within the Chilkat lib For example:
In summary, it's not possible to provide anything that would be leaner. The good news is that the size added to your EXE will not grow significantly over time as Chilkat continues to add more functionality. In fact, as each year passes, the size of the amount added to an EXE becomes less and less significant because mobile device memory capacities, cellular and network bandwidths, etc. continue to improve over time.