home.social

#msys — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #msys, aggregated by home.social.

  1. @argv_minus_one You know... `autoconf` was for times, when we have several #Unix systems in the field, each significantly different from each other, especially in terms of `libc` support. Today we have 3, with one having two flavours - `musl` and `glibc`; third one from #Apple is not usually that strongly supported.

    Then keep in mind `autoconf` was practically non-existent on #Windows (and no, #Cygwin and #msys don't count).

  2. @argv_minus_one You know... `autoconf` was for times, when we have several #Unix systems in the field, each significantly different from each other, especially in terms of `libc` support. Today we have 3, with one having two flavours - `musl` and `glibc`; third one from #Apple is not usually that strongly supported.

    Then keep in mind `autoconf` was practically non-existent on #Windows (and no, #Cygwin and #msys don't count).

  3. @argv_minus_one You know... `autoconf` was for times, when we have several #Unix systems in the field, each significantly different from each other, especially in terms of `libc` support. Today we have 3, with one having two flavours - `musl` and `glibc`; third one from #Apple is not usually that strongly supported.

    Then keep in mind `autoconf` was practically non-existent on #Windows (and no, #Cygwin and #msys don't count).

  4. @argv_minus_one You know... `autoconf` was for times, when we have several #Unix systems in the field, each significantly different from each other, especially in terms of `libc` support. Today we have 3, with one having two flavours - `musl` and `glibc`; third one from #Apple is not usually that strongly supported.

    Then keep in mind `autoconf` was practically non-existent on #Windows (and no, #Cygwin and #msys don't count).

  5. @argv_minus_one You know... `autoconf` was for times, when we have several #Unix systems in the field, each significantly different from each other, especially in terms of `libc` support. Today we have 3, with one having two flavours - `musl` and `glibc`; third one from #Apple is not usually that strongly supported.

    Then keep in mind `autoconf` was practically non-existent on #Windows (and no, #Cygwin and #msys don't count).

  6. MSYS - Lucy Alugiero (My Style)
    MSYS - Cassiecutie145 (OC) - (My Style)

    #msys #mystyleyourstyle

  7. I've been checking out how projects like -w32, and handle links in their utility programs like ln & ls. The comparison is very interesting. I really like Busybox-w32's use of hard links and how they show up with ls -i. They've done a wonderful job getting Busybox working on Windows. I'm investigating if Busybox-w32 can be used in place of msys when building projects with .

  8. I've been checking out how projects like #Busybox-w32, #msys and #GNUWin32 handle links in their utility programs like ln & ls. The comparison is very interesting. I really like Busybox-w32's use of hard links and how they show up with ls -i. They've done a wonderful job getting Busybox working on Windows. I'm investigating if Busybox-w32 can be used in place of msys when building #FLOSS #C projects with #mingw.

  9. MSYS - Ember (My Style)
    MSYS - Raymanlover2018 (OC)
    MSYS - Amy (My Style)

    #msys #mystyleyourstyle

  10. MSYS - Sara (My Style)
    MSYS - Twinklecake (My Style)
    MSYS - Rabbidbot (My Style)
    MSYS - Dragonsona (My Slyle)

    #msys #mystyleyourstyle

  11. I build a lot of programs from source. I've been looking into replacing on with -w32 ash and some alternatives to core utilities. I've been wanting to get rid of msys for a while and use natively built utilities that don't require Cygwin style DLLs. There are projects like and . Anyone else interested in this sort of thing?

  12. I build a lot of #FLOSS #C programs from source. I've been looking into replacing #msys on #Windows with #busybox-w32 ash and some alternatives to core utilities. I've been wanting to get rid of msys for a while and use natively built utilities that don't require Cygwin style DLLs. There are projects like #gnuwin32 and #GOW. Anyone else interested in this sort of thing?

  13. I build a lot of #FLOSS #C programs from source. I've been looking into replacing #msys on #Windows with #busybox-w32 ash and some alternatives to core utilities. I've been wanting to get rid of msys for a while and use natively built utilities that don't require Cygwin style DLLs. There are projects like #gnuwin32 and #GOW. Anyone else interested in this sort of thing?

  14. I build a lot of #FLOSS #C programs from source. I've been looking into replacing #msys on #Windows with #busybox-w32 ash and some alternatives to core utilities. I've been wanting to get rid of msys for a while and use natively built utilities that don't require Cygwin style DLLs. There are projects like #gnuwin32 and #GOW. Anyone else interested in this sort of thing?

  15. I build a lot of #FLOSS #C programs from source. I've been looking into replacing #msys on #Windows with #busybox-w32 ash and some alternatives to core utilities. I've been wanting to get rid of msys for a while and use natively built utilities that don't require Cygwin style DLLs. There are projects like #gnuwin32 and #GOW. Anyone else interested in this sort of thing?

  16. MSYS - Becka The Ghost (My Style)
    MSYS - Milieta (My Style)
    MSYS - Likkia and Yimmia (My Style)
    MSYS - Daffa The Flower (My Style)

    #msys #mystyleyourstyle

  17. Another useful tool I almost forget to mention is wc. You'll find it on and distros. On Windows, and offer a version. There are several implementations of wc out there including versions in Busybox and Toybox. If you want to build it yourself or modify it, sbase has a straight forward version:
    git.suckless.org/sbase/file/wc
    Have a happy

  18. Another useful #writing tool I almost forget to mention is wc. You'll find it on #Linux and #BSD distros. On Windows, #msys and #cygwin offer a version. There are several implementations of wc out there including versions in Busybox and Toybox. If you want to build it yourself or modify it, sbase has a straight forward version:
    git.suckless.org/sbase/file/wc
    Have a happy #SoftwareFreedomDay2024 #SFD #SoftwareFreedomDay #DFF #OpenSource #FreeSoftware #FOSS #FLOSS

  19. Another useful #writing tool I almost forget to mention is wc. You'll find it on #Linux and #BSD distros. On Windows, #msys and #cygwin offer a version. There are several implementations of wc out there including versions in Busybox and Toybox. If you want to build it yourself or modify it, sbase has a straight forward version:
    git.suckless.org/sbase/file/wc
    Have a happy #SoftwareFreedomDay2024 #SFD #SoftwareFreedomDay #DFF #OpenSource #FreeSoftware #FOSS #FLOSS

  20. Another useful #writing tool I almost forget to mention is wc. You'll find it on #Linux and #BSD distros. On Windows, #msys and #cygwin offer a version. There are several implementations of wc out there including versions in Busybox and Toybox. If you want to build it yourself or modify it, sbase has a straight forward version:
    git.suckless.org/sbase/file/wc
    Have a happy #SoftwareFreedomDay2024 #SFD #SoftwareFreedomDay #DFF #OpenSource #FreeSoftware #FOSS #FLOSS

  21. Another useful #writing tool I almost forget to mention is wc. You'll find it on #Linux and #BSD distros. On Windows, #msys and #cygwin offer a version. There are several implementations of wc out there including versions in Busybox and Toybox. If you want to build it yourself or modify it, sbase has a straight forward version:
    git.suckless.org/sbase/file/wc
    Have a happy #SoftwareFreedomDay2024 #SFD #SoftwareFreedomDay #DFF #OpenSource #FreeSoftware #FOSS #FLOSS

  22. Smacked head-first into a stupid issue with the #libcurl package deployed by #MinGW / #MSYS / #MinGW64 - turns out that if you copy the DLLs out of the MinGW environment (you know, like if you want to actually *deploy* an application that uses them), libcurl suddenly starts freaking out about "SSL CA cert" problems.

    Someone on StackOverflow noticed there's an alternate "mingw-w64-x86_64-curl-winssl" package that doesn't seem to suffer from this issue (which I confirmed). What a damned mess!

  23. Smacked head-first into a stupid issue with the #libcurl package deployed by #MinGW / #MSYS / #MinGW64 - turns out that if you copy the DLLs out of the MinGW environment (you know, like if you want to actually *deploy* an application that uses them), libcurl suddenly starts freaking out about "SSL CA cert" problems.

    Someone on StackOverflow noticed there's an alternate "mingw-w64-x86_64-curl-winssl" package that doesn't seem to suffer from this issue (which I confirmed). What a damned mess!

  24. Smacked head-first into a stupid issue with the #libcurl package deployed by #MinGW / #MSYS / #MinGW64 - turns out that if you copy the DLLs out of the MinGW environment (you know, like if you want to actually *deploy* an application that uses them), libcurl suddenly starts freaking out about "SSL CA cert" problems.

    Someone on StackOverflow noticed there's an alternate "mingw-w64-x86_64-curl-winssl" package that doesn't seem to suffer from this issue (which I confirmed). What a damned mess!

  25. Smacked head-first into a stupid issue with the #libcurl package deployed by #MinGW / #MSYS / #MinGW64 - turns out that if you copy the DLLs out of the MinGW environment (you know, like if you want to actually *deploy* an application that uses them), libcurl suddenly starts freaking out about "SSL CA cert" problems.

    Someone on StackOverflow noticed there's an alternate "mingw-w64-x86_64-curl-winssl" package that doesn't seem to suffer from this issue (which I confirmed). What a damned mess!

  26. Smacked head-first into a stupid issue with the #libcurl package deployed by #MinGW / #MSYS / #MinGW64 - turns out that if you copy the DLLs out of the MinGW environment (you know, like if you want to actually *deploy* an application that uses them), libcurl suddenly starts freaking out about "SSL CA cert" problems.

    Someone on StackOverflow noticed there's an alternate "mingw-w64-x86_64-curl-winssl" package that doesn't seem to suffer from this issue (which I confirmed). What a damned mess!

  27. How good is #msys these days? The occasional times I have to use #windows for #nextest are so frustrating. cmd sucks, git bash is too basic for me.

  28. How good is #msys these days? The occasional times I have to use #windows for #nextest are so frustrating. cmd sucks, git bash is too basic for me.

  29. How good is these days? The occasional times I have to use for are so frustrating. cmd sucks, git bash is too basic for me.

  30. How good is #msys these days? The occasional times I have to use #windows for #nextest are so frustrating. cmd sucks, git bash is too basic for me.

  31. How good is #msys these days? The occasional times I have to use #windows for #nextest are so frustrating. cmd sucks, git bash is too basic for me.

  32. The version of #yaml-cpp currently shipped by #MSYS for #MinGW64 has a bug that prevents exporting a symbol to the shipped DLL. It's not MSYS' fault, because yaml-cpp hasn't put out an updated formal release since 10 months before fixing this: github.com/jbeder/yaml-cpp/iss

    #xp

  33. The version of #yaml-cpp currently shipped by #MSYS for #MinGW64 has a bug that prevents exporting a symbol to the shipped DLL. It's not MSYS' fault, because yaml-cpp hasn't put out an updated formal release since 10 months before fixing this: github.com/jbeder/yaml-cpp/iss

    #xp

  34. The version of #yaml-cpp currently shipped by #MSYS for #MinGW64 has a bug that prevents exporting a symbol to the shipped DLL. It's not MSYS' fault, because yaml-cpp hasn't put out an updated formal release since 10 months before fixing this: github.com/jbeder/yaml-cpp/iss

    #xp

  35. Trying to get #OpenXcom to build in #MSYS #MinGW64 using #CMake and #vscode, and of course it's a dumpster fire. *sigh*

    It builds but barfs up a massive series of linker errors at the end, even though I already found and fixed one CMakeLists.txt issue. Whee!

    #xp

  36. Trying to get #OpenXcom to build in #MSYS #MinGW64 using #CMake and #vscode, and of course it's a dumpster fire. *sigh*

    It builds but barfs up a massive series of linker errors at the end, even though I already found and fixed one CMakeLists.txt issue. Whee!

    #xp