This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-06
Channels
- # adventofcode (99)
- # announcements (9)
- # aws (3)
- # babashka (22)
- # beginners (90)
- # boot (2)
- # calva (22)
- # cider (8)
- # clj-kondo (14)
- # cljsrn (20)
- # clojure (24)
- # clojure-europe (4)
- # clojure-italy (3)
- # clojure-losangeles (1)
- # clojure-nl (83)
- # clojure-spain (1)
- # clojure-spec (46)
- # clojure-uk (43)
- # clojuredesign-podcast (70)
- # clojurescript (40)
- # cursive (25)
- # datomic (9)
- # duct (3)
- # emacs (14)
- # figwheel-main (2)
- # fulcro (61)
- # graalvm (8)
- # juxt (7)
- # kaocha (2)
- # leiningen (19)
- # luminus (5)
- # malli (58)
- # off-topic (4)
- # re-frame (11)
- # reitit (5)
- # rewrite-clj (3)
- # shadow-cljs (63)
- # sql (5)
- # testing (5)
- # tools-deps (26)
- # uncomplicate (2)
- # vim (4)
had some success compiling a somewhat reduced-in-capability babashka using graal 19.3.0 java 11 on windows 10 it does appear that vs 2017 (+ a couple of options via the installer) are necessary for building (unlike for java 8 based graal things which have so far used windows 7.1 sdk) there are some steps regarding the vs 2017 setup starting here: <https://github.com/borkdude/babashka/issues/138#issuecomment-562369045> haven't figured out the automation part, but there is a lead among the comments ^ @borkdude @lee
Thanks! It was @filipematossilva who is interested in the Windows build as well
Preliminary docs for sci vars: https://github.com/borkdude/sci/tree/var#vars
oh wow I did not expect so much movement on the bb windows binary issue!
so like a nucleation point
you're having trouble installing vs in an automated way?
I think at some point I did something of the sort... let me see
choco install visualstudio2019buildtools --version 16.1.2.0 --no-progress --package-parameters "--add Microsoft.VisualStudio.Workload.VCTools --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 --add Microsoft.Component.VC.Runtime.UCRTSDK --add Microsoft.VisualStudio.Component.Windows10SDK.17763"
I used this once to get VS installed on a CI
this was just the built tools though, not the full VS
but that seems to be the syntax to do it with choco
the list of addable stuff for VS2017 is https://docs.microsoft.com/en-us/visualstudio/install/workload-and-component-ids?view=vs-2017
btw you testing bb on windows? I can help you get a windows ci going
@filipematossilva it's really good to hear you've got this sort of thing working before :thumbsup: we came across those or similar docs, but (afaik) haven't tried yet.
@borkdude adapting @filipematossilva's info, here's a sketch of a command:
choco install visualstudio2017community --no-progress --package-parameters "--add Microsoft.VisualStudio.Component.VC.Tools.ARM64 --add Microsoft.VisualStudio.Component.VC.CMake.Project"
there might be something missing, but that's a startpossibly it is better to have version info, in which case:
choco install visualstudio2017community --version 15.9.17.0 --no-progress --package-parameters "--add Microsoft.VisualStudio.Component.VC.Tools.ARM64 --add Microsoft.VisualStudio.Component.VC.CMake.Project"
nice!