Hi Damien, Thanks for such a detailed response, that gives me exactly the info I was looking for. Unfortunately it is the base size of BGT I'm looking to reduce (an 850kb executable is a lot more than needed for 2kb of code). Do you happen to know if there's any development being done on it at all? I remember Philip had said a while ago he had some updates in the works, but that time to work on them was limited. Again, thank you for such a clear and helpful response. I can't say how refreshing it was to get this email, especially since I've been dealing with Microsoft support recently.
Best, John From: Damien Sykes-Lindley Sent: Wednesday, August 23, 2017 13:05 To: [email protected] Subject: Re: [blind-gamers] bgt exclude components Hi, Unfortunately this isn’t possible. These components are part of the BGT engine rather than included scripts. Of course since BGT itself is a compiled executable, you can’t tell it to reduce its own size. If it were a C or C++ library that would be different. Also, BGT’s version of AngelScript doesn’t do any size optimisation techniques like removing code that isn’t used. For instance including the sound_pool library and not using it would still include the sound_pool code to your final executable. AngelScript is updated much more regularly than BGT is, however, so later versions of AngelScript may or may not utilise these optimisations. This is one of the reasons I don’t use BGT half as often as I used to. Literally the only way to optimise BGT executable size, is to use less code, and compile in release rather than debug mode. Cheers. Damien. From: john Sent: Wednesday, August 23, 2017 5:54 PM To: [email protected] Subject: [blind-gamers] bgt exclude components Hi list, I've recently been trying to find ways to reduce the size of BGT executables. Specifically, I'm looking to exclude unused sections of the engine during compiletime; for example, if I'm writing a program to work entirely offline, then there's no need to include the network subsystem. Does anybody know if something like this is possible? I write a lot of small, single-purpose applications that don't need many features, so it'd be really useful to trim them down to size, per say. Best, John
