Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    David Macek
    @elieux
    If the package is broken, then I agree.
    I don't think we should remove working packages just because they're old.
    Алексей
    @Alexpux
    @elieux well do you think someone still use library for example that not maintained since 2006 year?
    David Macek
    @elieux
    I think so, yes.
    Do these packages cause any issues?
    (One example of a program from 2003 that I use every day: http://users.telenet.be/jbosman/poweroff/poweroff.htm)
    Алексей
    @Alexpux
    ok lets then i make my list of packages that i want to remove and we vote for it
    i will create issue on mingw-packages
    Biswapriyo Nath
    @Biswa96
    In ArchLinux, libelf and elfutils are in same pkgbuild file.
    Christoph Reiter
    @lazka
    (I've added better instructions for the website build/dev process: https://github.com/msys2/msys2.github.io#msys2-website)
    David Macek
    @elieux
    Nice.
    There's too many repositories with zero instructions on how to get the damn thing running. It's nice not to create another one.
    Biswapriyo Nath
    @Biswa96
    Any use case of this repo https://github.com/msys2/MINGW-packages-dev? All were updated years ago.
    Christoph Reiter
    @lazka
    I think they were in the default repo, but no one maintained them, so they got moved into another one.
    Christoph Reiter
    @lazka
    and since they are vcs packages they don't have to be updated to build the latest release... but in many cases deps have probably changed.
    see https://wiki.archlinux.org/index.php/VCS_package_guidelines
    David Macek
    @elieux
    A while ago, Alexey wanted to clean up the repo.
    So we compromised and moved them to this other one in case someone might still find them useful.
    Biswapriyo Nath
    @Biswa96
    "someone might still find them useful" -- me too. Testing vlc.
    Biswapriyo Nath
    @Biswa96
    vlc can be built without the patch in mingw-w64-headers folder.
    Biswapriyo Nath
    @Biswa96
    Proposal: the qemu binary depends on slirp library. In current case, mingw-w64-qemu links qemu statically with slirp library but archlinux has a separate libslirp package. How about building libslirp separately in mingw-w64 packages and link it dynamically? libslirp can be built in mingw-w64 packages without any error (except 2 compiler warnings). This may decreases the qemu binary size and build time.
    David Macek
    @elieux
    Sounds good to me.
    Do you know why QEMU has its own copy?
    DaGiHu
    @DaGiHu
    Hi. I'm building a piece of software that at link time -lPropsys is required but the linker cannot find it. I can see Msys2 has the proper propsys.h file.
    Any hint would be really appreciated. Thank you!.
    David Macek
    @elieux
    Linking is a separate step from compiling.
    Did you look for libpropsys.a?
    DaGiHu
    @DaGiHu
    @elieux, thank you for your promptly reply.
    libpropsys.a is not preset at my \Msys64\mingw64\x86_64-w64-mingw32\lib directory.
    Could be it part of a Msys2 package I need to install?.
    David Macek
    @elieux
    I don't think it's supposed to be there.
    Or wait.
    Why are you trying -lpropsys?
    Okay, it seems it's supposed to exist.
    DaGiHu
    @DaGiHu
    The linker refers also to libssp.a referencing it like -lssp (this library is present in Msys2),
    so -lpropsys should point to libpropsys.a which is not present in Msys2 library directory.
    David Macek
    @elieux
    I suggest you ask over at #mingw-w64 IRC channel why it's missing.
    DaGiHu
    @DaGiHu
    Thank you, David.
    David Macek
    @elieux
    But note that it's Sunday.
    DaGiHu
    @DaGiHu
    I understand. Thanks!
    Biswapriyo Nath
    @Biswa96
    Why do -devel packages exist? -devel is not the concept of ArchLinux, it's in Debian/Ubuntu environment.
    Алексей
    @Alexpux
    @Biswa96 devel packages exists only for MSYS packages
    it allow to minimize size of MSYS2 installation fo users who dont need develop MSYS applications
    David Macek
    @elieux
    @DaGiHu
    I told you to ask in #mingw-w64, not #msys2. :)
    DaGiHu
    @DaGiHu

    David, you're right. I just realized propsys.h is in the /include folder of MinGw, not the one of Msys, sorry.

    By the way, I was able to link the library after downloading it from here:
    https://github.com/tpn/winsdk-7/blob/master/v7.1A/Lib/propsys.lib

    Thank you for your help and I hope my fix can help others on the same topic. THANKS!

    DaGiHu
    @DaGiHu
    (I just filed a ticket in the MinGW support desk)
    Biswapriyo Nath
    @Biswa96
    I just send a patch to add that library.
    Biswapriyo Nath
    @Biswa96
    Where is your issue? can you provide the link.
    DaGiHu
    @DaGiHu
    Thank you, @Biswa96
    My issue link:
    https://osdn.net/projects/mingw/ticket/40295
    Biswapriyo Nath
    @Biswa96
    What! aren't you using mingw-w64? MinGW and mingw-w64 are different projects and msys2 uses mingw-w64.
    danieltuzes
    @danieltuzes
    I successfully installed MYSYS2 to use tiffinfo, a program inculded in package libtiff. After successful installation I can cd to C:\msys64\mingw64\binand run the program, but why aren't all the programs in that folder in the PATH? Is it a good practice to add that folder to the PATH?
    Biswapriyo Nath
    @Biswa96
    "Is it a good practice to add that folder to the PATH?" -- One catastrophic downside will be if some has also cygwin installed. cygwin environment will be confused with same binaries. Also Windows now has bash.exe, curl.exe, tar.exe etc which also create confusion.
    DaGiHu
    @DaGiHu
    @Biswa96, ouch... thanks for all that help and info.