This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-09
Channels
- # announcements (4)
- # aws (3)
- # babashka (86)
- # babashka-sci-dev (31)
- # beginners (171)
- # biff (15)
- # calva (3)
- # clerk (47)
- # cljdoc (11)
- # clojure (57)
- # clojure-dev (11)
- # clojure-europe (122)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-norway (4)
- # clojure-uk (2)
- # clojurescript (40)
- # cursive (5)
- # data-science (3)
- # datahike (1)
- # datomic (5)
- # fulcro (9)
- # graalvm (8)
- # hyperfiddle (17)
- # introduce-yourself (1)
- # java (28)
- # jobs (1)
- # malli (11)
- # membrane (9)
- # missionary (1)
- # nbb (1)
- # off-topic (5)
- # other-languages (1)
- # pedestal (1)
- # re-frame (4)
- # reagent (16)
- # releases (3)
- # remote-jobs (3)
- # shadow-cljs (83)
- # spacemacs (1)
- # sql (5)
- # tools-deps (28)
- # xtdb (15)
@ales.najmann I bumped the build of babashka in appveyor from the visual studio 2017 image to 2019. This may mean something for the required redistributable but not sure.
I updated depends to vcredist2019
It looks like they maintain some sort of binary compatibility on newer versions of these libs, so it maybe working even without being on the newest version.
the binary here: https://github.com/babashka/babashka-dev-builds/releases/tag/v1.2.175-SNAPSHOT should be the one compiled with vsstudio 2019
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>dumpbin /dependents C:\Users\borkdude\Downloads\bb.exe
Microsoft (R) COFF/PE Dumper Version 14.27.29111.0
Copyright (C) Microsoft Corporation. All rights reserved.
Dump of file C:\Users\borkdude\Downloads\bb.exe
File Type: EXECUTABLE IMAGE
Image has the following dependencies:
VERSION.dll
ADVAPI32.dll
WS2_32.dll
USERENV.dll
MSWSOCK.dll
USER32.dll
KERNEL32.dll
VCRUNTIME140.dll
VCRUNTIME140_1.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-filesystem-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
WINHTTP.dll
ncrypt.dll
CRYPT32.dll
Secur32.dll
IPHLPAPI.DLL
If I undestand what's written here: https://learn.microsoft.com/en-us/cpp/windows/determining-which-dlls-to-redistribute?view=msvc-170 yes, it should be working.
it's a bit problematic to test though, because our systems are usually already polluted by all the versions that are out there... or nothing at all.
and when you specify a dependency on redist 2019 and another package wants 2015, how does that work? since you can only have one of them installed
I guess we'll hear from bb users and change when necessary but perhaps the change wasn't necessary yet. 🤷
for example I have 2019 installed on system level already by some other application I don't know about right now
"Dev had a problem and thought he would solve it with dynamic linking. Since then he has had two problems."
I believe it is possible, there is a tutorial https://learn.microsoft.com/en-us/cpp/build/walkthrough-creating-and-using-a-static-library-cpp?view=msvc-170 for example. I just think it's not the common way to do on Windows.