| 26 Jul 2018 |
 Yorick Peterse | Way back there was a `const` keyword, but I removed it | 17:56:52 |
| Yorick Peterse | I actually find having separate keywords rather annoying | 17:57:07 |
| 29 Jul 2018 |
| Yorick Peterse | codec_abc FYI I'm adopting your num-bigint changes | 14:48:35 |
| Yorick Peterse | I found a fairly simple way to fix the few issues you marked as "maybe broken" | 14:48:50 |
| Yorick Peterse | This will make cross compilation much easier | 14:49:04 |
| Yorick Peterse | MR here: https://gitlab.com/inko-lang/inko/merge_requests/7 | 15:07:14 |
 codec_abc | Thanks! I just tested it and I can confirm now that the VM is trivial to build on Windows. | 19:43:44 |
| Yorick Peterse | nice :) | 20:33:35 |
| 1 Aug 2018 |
| Yorick Peterse | I managed to get all tests to pass on Windows using AppVeyor. If I can get releaes to also work, that means pre-built binaries for Windows | 14:02:35 |
| Yorick Peterse | Though it's using visual studio 2017, and I have no idea how portable that is between Windows versions | 14:02:55 |
| codec_abc | Nice! I am not sure to understand the second sentence. What is using VS 2017? The compiler and/or VM or something else? Visual studio is portable across Windows version. You often only has to give the runtime library (the famous msvcpXXX.dll) with the software (or find a way to trigger the redistribuable install on the Windows machine) | 15:28:49 |
| 2 Aug 2018 |
| Yorick Peterse | The VM was compiled with it, though I abandoned precompiling windows releases | 00:06:25 |
| Yorick Peterse | making sure the manifest is up to date with a bunch of concurrent builds was too painful, at least for now | 00:06:43 |
| Yorick Peterse | but at least the tests run on Windows now | 00:06:49 |
| Yorick Peterse | IVM can now be built on stable Rust: https://gitlab.com/inko-lang/inko/commit/8cf6067428a4865b98c7dfb64eb46117c2f74263 | 17:57:42 |
| codec_abc | Nice! I am not sure to understand what issues you faced on Windows only which prevented you to get the prebuild working. Maybe I can help since I am mostly a Windows dev but I don't know what you are talking about when you refer to the manifest and the concurrent build. | 18:37:09 |
| Yorick Peterse | https://inko-lang.org/news/inko-now-supports-stable-rust/ Details on the stable Rust support | 18:43:04 |
 nickforall | 🎉🎉 | 18:43:43 |
| Yorick Peterse | codec_abc They're not really Windows related, it's more due to the lack of flexibility of AppVeyor | 18:43:44 |
| Yorick Peterse | Specifically it's because we have both GitLab CI and AppVeyor | 18:43:59 |
| Yorick Peterse | As part of the release process we build a manifest that contains all released versions. This isn't atomic, so we make sure it runs at the end of the CI pipeline | 18:44:19 |
| Yorick Peterse | But AppVeyor runs all builds in parallel (more or less), there's no "run this after everything passes" | 18:44:40 |
| Yorick Peterse | One hack is to write a script that waits for AppVeyor to pass, then run that before the CI build that generates the manifest | 18:44:57 |
| Yorick Peterse | But it's tricky to get that right (e.g. there's no guarantee the AppVeyor build is visible by that point), and I'd rather not spend time on that now | 18:45:21 |
| codec_abc | Ok, and when you are saying all the build, what does it mean? (Mingw/Msvc, 32/64, stable/nightly or something else ?) | 18:48:14 |
| codec_abc | Also, I agree with you that spending time on this right now is probably not the best idea, however do you need to have the manifest for windows? Can't the CI upload the whole thing without manifest and saying is not "really" official release. That way you provide an easy way to get started for Windows users but without having to commit fully to windows until later on? | 18:54:11 |
| Yorick Peterse | The manifest is required for "ienv" (and other tools) to know a package/version is available | 18:59:31 |
| Yorick Peterse | In this case "builds" means to 4 builds that run in parallel. 2 for building on msvc (stable and nightly), 2 for using GNU (whatever that is) | 19:00:09 |
| Yorick Peterse | I think Rust's "gnu" for Windows refers to mingw or some flavour, but I'm not 100% sure | 19:00:24 |
| Yorick Peterse | Either way, there are 4 tasks running in parallel, but AppVeyor offers nothing (easy) that you can run once all four are done | 19:00:47 |
