Hi, Building a combination of ~latest versions has pretty consistently worked on github flows:
Windows Server 2019 OTP 24 Spidermonkey-91 But going backward tends to hit problems where solving one dependency conflict often creates another one. I think it would be straight forward to make a new version (3.3.0?) with updated dependencies, but that will leave open the problem of building an ~official windows 3.2.1 and a newest windows version that works with Clouseau as discussed in [4]. For locking down compiler version and switching openssl to building from source, I think it is technically straight forward to do either, but each task like this adds some run time. It is frequently better to add tasks like build openssl that can be separate jobs that deliver binaries than tasks like install an alternate compiler that slow each job that needs the change. -Will [4] https://lists.apache.org/thread/2ms31lw6ynlknnl8vpbdro1rd4y61ktv Am Mo., 14. März 2022 um 17:05 Uhr schrieb Ronny Berndt <ro...@kioskkinder.com.invalid>: > > Hi, > > some time ago, I started to play with the couchdb-glazier package because > there was never released an official windows binary release of couchdb for > version 3.2.1. > > A very short summary of the windows build (hell): > > After the VOTE for v3.2.1 Jan wrote that he wasn't able to release a > version for windows so i looked into couchdb-glazier [1]. Jan and I tried > to figure out the problems and we tried to resolve the compile and > dependency problems [2]. After a while Arek joined the discussion on Slack > and tried to generate a Windows build as well. Will also started a > discussion about automating Windows builds for CouchDB & dependencies [3]. > All build paths ended with some results but no result led to an official > release of CouchDB v3.2.1 for Windows. > > The question is now, what do we want to do with the windows build? > > I see the following possibilities (probably more that elude me at the > moment): > > 1. Update the "couchdb-glazier" scripts to successful build a windows > version for CouchDB > 2. Use Will's work to generate binaries (e.g. release and nightly) [3] > 3. Use a combination of both (1. and 2.). > 4. Generate a new release process in combination with Adams discussion "Erlang > version update process for convenience binaries" [4]. > > General questions about the windows build: > > 1. Should we compile all packages from source or should we rely on > pre-built packages (like OTP, OpenSSL, ICU, SM, ...) > 2. All scripts should do it's work without any user interaction (download > all packages, compile, generate installer, etc.) > 3. Which Windows VM do we use to build couchdb (every 3 months, MS release > new Developer VM's with other version of VisualStudio inside)? > > It often makes sense to use old habits and established procedures. But > sometimes it makes sense to break with old methods and start something new. > I hope we can collect ideas an turn it into action. > > - Ronny > > [1] https://lists.apache.org/thread/vk8pnrt5odn4hqf1wjhn7wq31qc3ggjd > [2] https://lists.apache.org/thread/t7ztznshh0r05vg8wtnzwn2lsfz92qy1 > [3] https://lists.apache.org/thread/z3tt721z399yz4c28fn4whvqyzdjm7c6 > [4] https://lists.apache.org/thread/2ms31lw6ynlknnl8vpbdro1rd4y61ktv
