4 ms·
At Bloomberg, we just published our lowest-level C++ standard library (and plan to add more layers on top).[1] Everything we do is based upon this library and a
by apaprocki 14y ago
At Bloomberg, we just published our lowest-level C++ standard library (and plan to add more layers on top).[1] Everything we do is based upon this library and all the higher level layers which are not OSS yet. (i.e., No external 3rd party libs in any of these lowest layers) We CC-BY-SA'd our code standards as well if you're interested.[2]
[1]: https://github.com/bloomberg/bsl https://github.com/bloomberg/bsl
[2]: https://github.com/bloomberg/bsl/wiki/bdestds.pdf https://github.com/bloomberg/bsl/wiki/bdestds.pdf
- halostatue 14y agoCan I ask why the `gyp` build tool?
- drucken 14y agoI'd be interested to know what they used before gyp, which is relatively new compared to Bloomberg.
- matthavener 14y agoMe too. QMake can generate from visual studio, I think it also integrates with XCode.
- apaprocki 14y agoWe went with gyp because we wanted to natively support MSVC and XCode projects as well as standard GNU make environments. Our production build system actually has simple text metadata files that live along-side the code and it generates all the required files as well. We felt that it easier to provide a gyp based system instead of also open-sourcing the entire Perl-based build system which was tied to our custom data format and not generally useful to anyone else. We generate the gyp input files from the metadata on our end and then anyone using the open-source project can use gyp to do whatever they need. If we get to the point where OS distros want to package the libs, we may opt to generate autotools files, but that was too much work to be a roadblock from open-sourcing the lib.