|
Ruel Haldi
|
 |
« on: April 22, 2006, 09:34:06 pm » |
|
The subject title is vague, because I don't know the correct words for what I'm trying to describe. I will explain:
Yesterday, I put together a distribution of a CrystalSpace application to send to a friend for testing on their computer. They didn't need to see the code, they were just going to run it and tell me what they see. All I needed to send was the compiled programs and the DLLs (for a Windows compile), and various other small things like vfs.cfg, the world file and textures.
Simple enough? Yes, but it ended up being 180 something meg. That's just silly. So, I started paring it down. Only about a third of the DLLs are actually used by my program. Unfortunately, the quickest way to figure out which ones was by trial and error (deleting one at a time, and seeing if the program still functions correctly). In the end, the program was down to 50 something meg (16 meg zipped). That's not half so bad.
What would be nice is a way to output a script at the end of a CrystalSpace program that tells you exactly which DLLs the program loaded. That way, when it's time to write a distribution copy (or commercial copy?), you don't have to resort to trial and error. Maybe there is already something like this, but I didn't see it in the documentation.
|