summaryrefslogtreecommitdiff
path: root/.configurations
AgeCommit message (Collapse)Author
2024-10-11Fix typoAndrea Gelmini
Change-Id: Ia7e162526621b8c6613e59d1bab6712e2d65dbc9 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/174811 Tested-by: Julien Nabet <serval2412@yahoo.fr> Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
2024-10-10further winget configuration files to complete the setupChristian Lohmaier
this is still a chicken-and-egg situation, since the steps are meant to run before the repository is cloned, however it makes some sense to have that in the repo since deps and similar are tied to the code after all. The user-side makes use of all script resources, which of course is not ideal, but still better than nothing. Unfortunately the admin side uses hardcoded paths - can be switched to also using script resources instead of the xRemoteFile DSC, but that is trading one bad thing for another… Future tweaks might include setting up a Dev Drive and/or whitelisting directories to be excluded from AV-checks Change-Id: Ide1f0efb94264a6c72a9e87c2c212aa527d7d330 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/173676 Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com> Tested-by: Jenkins
2024-10-10winget configuration files for installing Visual Studio Community 2022Christian Lohmaier
A first step into streamlining the dependency installation process using winget / DevHome You can apply winget configurations with DevHome or from commandline by running winget configure -f path-to-configuration.yaml The *.vsconfig files can also be manually imported into Visual Studio Installer to install missing components into an existing installation Two variants are provided in this commit, one set including the components needed to cross-compile for ARM64 (uses around 1GB) The version of the Windows SDK chosen is the one that matches the SDK from the recommended packages, to avoid installing two different SDKs when using the configuration that includes the recommended packages The *.vsconfig files don't include the implied packages/the ones required by the workload. For a list of the components and their corresponding friendly names, see https://learn.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-community Change-Id: Ie44ee3dd39c3e61fb2d7c597b71a4a81e0e6b8d3 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/173336 Tested-by: Jenkins Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>