Why is the empty bag of Unity5 17mb?

Today on the forum to see someone mentioned Unity5 's many "counts", one of which is to call out the empty package unexpectedly has 17MB, and the previous version is 9MB. I'm curious, is it Il2cpp's ghost?

Because of curiosity, I deliberately prepared the Android environment (before the environment too old, had to re-get), hit an empty package under test. In fact, the reason is very simple, because the compatibility Unity5 by default while playing the ARMV7A and x86 dynamic library. So the size of the empty bag increases almost one times.

As shown, the fat in device filter is modified to ARMV7 in playersetting.

In general, the Android platform does not need to compile x86 version, because there are too few devices, you need to consider the corresponding platform when you can play a x86 version of the package. Fat compatibility is only selected when the APK package size is not considered.

Finally, the extra gripe, the programmer will only see XXX does not work, there are XXX problems (the level of the root of the problem can not be seen), and a little with a little heart will be able to "know it but know its why." This is actually a bit of technical content is not, play an empty bag to see where the larger, it is easy to know the problem, intentions only.

Why is the empty bag of Unity5 17mb?