   STLport and mixed linking
  Just wanting to make sure of something here so it doesn't come back to haunt me later. It's a trivial issue, but I'm interested in opinions here.I've got my main application, and the renderer DLL (RTL). I'm using STLport. I decided to test the program out on another computer with different specs, and was presented with an error saying that computer didn't have the specific STLport DLL that was being used.Now, my first reaction is "Eww, that should be static linked! I don't want extra DLLs to keep track of! It must be tidy!" And, based on STLport's default behavior, I thought it was already supposed to be statically linked. Turns out that the renderer DLL, just by being a DLL, made STLport default to linking to it as a dynamic library. So I changed it and forced static linking, and happily everything was as I expected it to be, without the DLL.My question is, is there any particular reason that STLport defaulted to being a dynamic library for the DLL? Will there be any issues with my DLL using a static version, or with both my application and renderer together using separate static copies of the library? I suppose there will be a size overhead for making them both static, since they won't be sharing the library. Or am I just being overly picky in wanting to remove the extra DLL requirement? :P   