Re:C++ Dev Ecosystem 2021
by saurik on Tuesday July 20, 2021 @08:53AM
(#27893118)
I mean, good luck building typical Unix projects in a directory mounted non-executable... having build steps that generate binaries that build other binaries is like, "the name of the game". Is this your experience, or are you just surmising this? If the former, how did that even work? In my long experience (which has included working on embedded systems for a large highly-boring multinational company: Bosch) it is more likely that the organization will literally vendor the compiler--which is the best strategy for making sure that your code will still be compilable forever--than insist that their engineers not be able to run code on their laptop (though they certainly had extremely tight control over networking and data movement).
[ Parent
| on HN ]
Yes, that was my experience back when stuff like HP-UX, Aix and Solaris was commonly deployed.
There is no laptop to run code on, laptop is only for SSH and X Windows server, or cloud shell in modern "mainframes".
Nowadays one can make it one level up my having a CI/CD wall between the development environment and the actual stages, thus whatever one uses to develop must also be available on the stages, which contractors can only access with the help of hands from internal employees.