mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
0dac129770
This commit reverts much of the work @hwillson had put in place for meteor/meteor#9173, which made it possible for 32-bit and 64-bit Mongo versions to exist in harmony within the same dev-bundle. That hard work was not in vein though as it offered invaluable research. Ultimately, this showed that a more aggressive approach would be ideal, even if the proposed option would have worked great in the short-term. In the wake of the news that Mongo would no longer be supporting 32-bit versions, these changes are important so 32-bit users of Meteor can continue to have a functioning Mongo binary in development, while still allowing Meteor to ship newer Mongo (e.g. 3.4+) binaries for 64-bit users. This is particularly relevant for Windows users, who have previously only had 32-bit Meteor builds and represented a majority of "32-bit" development, despite the fact most of their hosts supported 64-bit. During another time in Meteor's life, this made sense. This commit takes improved functionality to the next level (and makes the aforementioned changes obsolete) by introducing support for building and shipping Meteor for Windows in a 64-bit flavor (in addition to 32-bit), which will hopefully solve a number of performance matters on Windows by using binaries which are pre-compiled for 64-bit, rather than forcing the Windows kernel to deal with 32-bit binaries. While Windows has shown it's quite capable of dealing with such a situation, it seems more and more clear (given improvements in underlying dependencies) that performance gains could be had by freeing Windows of its 32-bit work. This commit also further perpetuates the "archinfo" plot-line with more story (about Windows) and various spelling corrections.