Hi Hossein, Hossein Nourikhah wrote: > How to automate (from command-line) the installation of a Visual Studio > Build Tools build environment, for C++, .NET, C#, etc > https://stackoverflow.com/q/62551793 > I think that's a _really_ great idea, adding that to lode - pulling in just the build tools, and putting them into a non-standard path via --installPath (so as to not interfere with any existing install). That should make for a much more standardized build env on Windows, with fewer opportunities to get it wrong. > 2-4 Dropping some of the huge dependencies > There was disagreements in this area, but it is actually possible to drop > some of the huge dependencies to simplify the build process. It is also a > big task. This is an example patch from me: > > Drop boost dependency for writerfilter > https://gerrit.libreoffice.org/c/core/+/139279 > For this one, I'm not convinced that is the right approach. You'll have a hard time replacing boost/spirit, the json parser and the various specialized containers with something equivalent. As Stephan said, the useful bits out of boost will eventually appear in std c++ - and that is the way, we'll eventually get rid of boost. If boost is a drag (is it really? we only build a tiny fraction of it, no?), perhaps cutting the tarball down to the absolute minimum is a better plan. Their git repo is already quite modular... Cheers, -- Thorsten
Attachment:
signature.asc
Description: PGP signature
