now with added cross compilation from linux to windows
it's also possible to generate a proper windows installer from linux, with nsis, not quite sure i'll be able to compile it there, but worth a shot
@carkh, I ask out of ignorance: do developers expect a gui installers these days? Is this a windows developer specific expectation?
well it depends on the dev i guess
it's idiomatic on windows i'd say
although i have many years of professional work under my belt, i was surprised with the ps installer, and having to work around execution policy etc
so i guess for a new dev it's even worst
though i had little experience with powershell i must admit
when I dipped my toe back into windows, I was happy to see and use scoop and friends - but that’s me bringing my macos and linux biases and habits back to windows.
i like chocolatey
but that's a very different proposition than our current installer
yep
no hassle, no thinking, type and go
probably due to my lack of knowledge of powershell, i was quite bewildered by those offered install paths
what to chose, will i mess it up ?
i don't have to do this for python
same ignorance and response for me, I relied on guidance in wiki
well it was an occasion for learning =) always fine by me =)
So i'm making another installer, which may be cross-compiling too... and it calls into powershell for some scripting ...That's a total mess, i have to first edit the registry, then call the script, then restore the registry
i don't know what they were thinking at microsoft
sounds like maintenance costs might be high for that one.
great that you are digging in and exploring @carkh!
not really, i had an installer based program i maintained for years and had to maybe edit the installer twice or thrice
the parameters are harder here, gotta make it cross-compilable, not introduce more compiled binaries etc
lotsa interesting data for @alexmiller to digest!
=)
it would be so easy to reach for a little dll and just do that stuff myself instead of relying on powershell
i already wasn't too keen on it, but now i'm starting to hate it with a passion =)
@carkh: Installing clojure
on Windows was quite the task for me. (As was installing Java) Some of it due to my inexperience with Windows and Powershell. But I can totally see why you want to help make it easier.
@alexmiller: When you look at this, please have us poor tool smiths in mind. 😃 I have just spent countless of hours (I don't want to count them) getting Calva to be able to Jack in to clojure-cli
, Leiningen and shadow-cljs
across both Mac/Linux and Windows. I think I have something that works now, but it will depend on that that clojure
command is installed in Powershell and can be invoked with the escaping suggested on the docs page for how to install clojure
on Windows. If this changes, I'd love me a heads up so that I can make Calva support both the current and whatever new CLI api.
certainly. I spent months asking for direction on this but never getting any feedback, glad to be seeing some now.
I started to think about my comment here, don't know why. but thought maybe it came out like ”I spent countless of hours because of something lacking in clojure-cli”. That is not the case. The hours is a result of Calva needing to support quite an array of combinations of operating systems and Clojure project setups, and added to that, Windows' quite messy quoting mechanisms.
not at the top of my list at the moment unfortunately, but hope to cycle through
If there are any Calva users in here, you can help me test that clojure-cli jack-in works in this test build. (It's a quite big change under the hood, so I'd love help with testing Leiningen and shadow-cljs projects as well.) To put it to a test: install the VSIX file in VS Code from the meatballs menu (`...`) in the Extensions pane.
see that's the trouble with those incompatibilities, some are adapting to powershell, some are not
and it's a lot of work, for more people
thanks for the feedback @pez