X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/4f3b37fd0e60dcdf61c951e3c220fe267e8257f8..82ac3b0a423b755c6329c2ae2faaab9576a3f647:/docs/html/faqmsw.htm?ds=sidebyside diff --git a/docs/html/faqmsw.htm b/docs/html/faqmsw.htm index 2c56fedb31..346e9de28d 100644 --- a/docs/html/faqmsw.htm +++ b/docs/html/faqmsw.htm @@ -1,3 +1,4 @@ +
@@ -201,7 +202,8 @@ Statically-linked wxWindows 2 programs are smaller than wxWindows 1.xx programs, wxWindows 2 has been designed to reduce dependencies between classes, and other techniques. The linker will not include code from the library that is not (directly or indirectly) referenced -by your application. So for example, the 'minimal' sample is less than 300KB using VC++ 6.+by your application. So for example, the 'minimal' sample is less than 500KB using VC++ 6 +(note that this figure may be greater for the latest version of wxWindows).
If you want to distribute really small executables, you can use Petite @@ -210,6 +212,12 @@ will shrink to a mere 250KB. With this sort of size, there is reduced incentive use DLLs. Another good compression tool is UPX.
+Please do not be surprised if MinGW produces a statically-linked minimal executable of 1 MB. Firstly, gcc +produces larger executables than some compilers. Secondly, this figure will +include most of the overhead of wxWindows, so as your application becomes more +complex, the overhead becomes proportionaly less significant. And thirdly, trading executable compactness +for the enormous increase in productivity you get with wxWindows is almost always well worth it. +
+ +It can also happen if you append the submenu to the parent +menu {\it before} you have added your menu items. Do the append {\it after} adding +your items, or accelerators may not be registered properly.