Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 03:17
    TidbitSoftware opened #113
  • 03:15
    TidbitSoftware commented #5632
  • 02:35
    mmottaghi commented #2353
  • 02:34
    mmottaghi commented #2353
  • 02:32
    mmottaghi commented #2353
  • 02:32
    mmottaghi commented #2353
  • 02:31
    mmottaghi commented #2353
  • Mar 04 23:04
    gbburkhardt commented #2361
  • Mar 04 22:14
    intvsteve commented #2353
  • Mar 04 19:20

    elieux on main

    HISTORY: Write down actual work… (compare)

  • Mar 04 19:14

    github-actions[bot] on srcinfo-cache

    Add libcue static lib Build bo… Merge pull request #8063 from d… (compare)

  • Mar 04 19:12

    github-actions[bot] on srcinfo-cache

    Add libreplaygain package Merge pull request #8064 from d… (compare)

  • Mar 04 19:10

    lazka on master

    Add libcue static lib Build bo… Merge pull request #8063 from d… (compare)

  • Mar 04 19:10
    lazka closed #8063
  • Mar 04 19:09

    github-actions[bot] on srcinfo-cache

    Add sidplayfp package Update mingw-w64-sidplayfp/PKGB… Merge pull request #8062 from d… (compare)

  • Mar 04 19:09

    lazka on master

    Add libreplaygain package Merge pull request #8064 from d… (compare)

  • Mar 04 19:09
    lazka closed #8064
  • Mar 04 19:07

    github-actions[bot] on srcinfo-cache

    hwloc: update Merge pull request #8060 from 3… (compare)

  • Mar 04 19:05

    lazka on master

    Add sidplayfp package Update mingw-w64-sidplayfp/PKGB… Merge pull request #8062 from d… (compare)

David Macek
@elieux
I agree.
I'm just saying using mingw-w64-cross won't solve everything.
Алексей
@Alexpux
@elieux im just about providing git-bash.exe and git-cmd.exe
David Macek
@elieux
I know.
Should git-bash then open MINGW32, or MINGW64?
Алексей
@Alexpux
for what reason they created at all @dscho ?
David Macek
@elieux
They are in the root directory because otherwise users would not discover them in, say, a Portable Git.
It opens MinTTY with Bash with mingw-w64-git.
(Or conhost with cmd, in case of git-cmd.)
Алексей
@Alexpux
ok
Christoph Reiter
@lazka
@dscho thanks for the info
Johannes Schindelin
@dscho

for what reason they created at all @dscho ?

As I mentioned before: so that users discover them easier.

Biswapriyo Nath
@Biswa96
Are we allowed to copy ideas from Fedora?
Алексей
@Alexpux
what you mean
Biswapriyo Nath
@Biswa96
I mean like build command, flags, patches etc.
Алексей
@Alexpux
why not
Ray Donnelly
@mingwandroid

@mingwandroid, WRT :point_up: January 10, 2021 11:27 PM no worries, I'm not in a rush to have it done, just slightly annoyed/frustrated because finding the workaround is being harder than packaging several other tools. Hope they let you out soon! (despite not having much outside to go to :S)

Thanks @umarcor , I am back now. I must say that the Spanish health service took good care of me, despite my sorely lacking Spanish language skills. I will not say too much about the food, because as my dear Mum often says "if you can't say something nice it's best to say nothing at all" ;-)

umarcor
@umarcor
@mingwandroid I'm at the north of spain, so kind of know what you mean :laughing: Glad they set you free!
Biswapriyo Nath
@Biswa96
Random thought. Is it possible to create a bot in github which will comment when a issue is fixed and the package is uploaded?
syarif-hsb
@syarif-hsb
Hello guys, I'm new here. Firstly, I want to thank you all for the great software. It really ease my workflow on windows (which I have to use at work). Secondly, is there any CLI image viewer available? I couldn't find in pacman, but just in case I miss something. Is it really hard to implement or create image viewer package. If not I would really like to try contributing :)
loonycyborg
@loonycyborg:matrix.org
[m]
try using display.exe from there
syarif-hsb
@syarif-hsb
Installing. I see it is a mingw package. Is it possible to use from msys?
syarif-hsb
@syarif-hsb
Thank you, btw @loonycyborg:matrix.org
loonycyborg
@loonycyborg:matrix.org
[m]
I don't see why not
I'm not sure what exact purpose of those three repos(like msys vs mingw-w64) but packages from them can be installed in parallel
Christopher Degawa
@1480c1
The mingw64 repo is for native 64 bit windows programs compiled by mingw-w64-x86_64-gcc (for the most part), mingw32 is native 32-bit windows program, msys is for cygwin like packages that is either tied too closely to posix that it won't compile or work as intended if compiled to windows (like bash) or programs that don't need a native equivalent (like nano, although there are exceptions such as cmake etc which are in there mainly because other things need them)
in order of preference on which to download, it should be mingw{64,32} and then msys
umarcor
@umarcor

Random thought. Is it possible to create a bot in github which will comment when a issue is fixed and the package is uploaded?

@Biswa96, it's pretty trivial to comment/open/close issues in GitHub using any library for interacting with the API, such as octokit (js) or pyGitHub (Python). However, I did not understand where do you want the comment to be posted. Can you please clarify?

umarcor
@umarcor
@syarif-hsb in https://hdl.github.io/MINGW-packages/#_usage a few quotes from msys2.org are shown and referred, which explain exactly what @1480c1 said. Even though it is explicitly explained in the docs, I find many users confused about that, so I tried to make it as short and direct as possible.
Ray Donnelly
@mingwandroid
@umarcor nicely written site! Very useful for any other project who'd like to upstream stuff too.
umarcor
@umarcor

@mingwandroid thanks so much. I'm glad you liked it. In fact, I tried not to duplicate the content of msys2's docs, so that my "workflow guidelines" can be potentially moved there in the future. Yet, I'm still shaping and reworking my own workflow, so it's pretty organic work in progress for now. E.g. it was initially a fork of MINGW-packages, but then lazka could not edit the PRs because he was not a member of that org, so I had to fall back to using my personal fork for PRs. Overall, I think it can be interesting to create documentation for "packager camps" in the MSYS2 ecosystem, which can offload the main maintainers from niche issues related to multiple packages in some area. This is already done in larger teams, such as Debian or Fedora. In both cases, there is an EDA related group of tools and people.

Noticed a broken link though: https://github.com/hdl/smoke-tests/blob/main/CONTEXT.md

Thanks for pointing that out! 'HDL' is undergoing some fast and disruptive changes, because we are aiming at bringing together packagers from different EDA tooling camps. https://github.com/hdl/packages was a created a couple of days ago, and the context is now located there. I will fix the broken link.
BTW, you might find all the litex-conda-* packages interesting/exciting or maybe infuriating ( :laughing: ), due to your background. Those are soon to be transferred from litex-hub to hdl.

umarcor
@umarcor

@mingwandroid, personally, I would be happy to hear your thoughts about this parallel/concurrent packaging approach:

  • MINGW-packages (+ pip with a little mouth :blush: ).
  • Conda.
  • Containers (Docker/Podman).

My hope is that different people can take care of each of those approaches, but handle it so that users can pick any of them as their "system/tooling management solution". That is, "project management scripts for hdl designs" should be able to use tools installed using any of those methods/ecosystems.

Ray Donnelly
@mingwandroid
Yeah, interesting stuff. There's the R world and Julia also to consider! We have MSYS2 packages in conda to help with building stuff mostly, and also for R but it is out of date. Actually Anaconda Inc. are looking for people to work on this kind of thing if anyone was interested in doing it professionally.
I will check out litex-conda-*!
Conda-forge would probably love someone to update MSYS2-in-conda and automate the continual update of the same, too.
I lost the scripts I wrote in 2016 that I used to do the original import. I added libalpm packages to conda as I remember and parsed the MSYS2 metadata. Now-a-days, I'd rather conda-forge built MSYS2 packages from source using the PKGBUILDs.
Ray Donnelly
@mingwandroid
I worked with Tim Ansell before actually. He helped us to get our linux-64 compilers in shape in a few ways.
I do like the idea of having sub-teams contribute to MSYS2. I see gnome and HDL as two we kind of have already.
Then there's the real compiler engineers helping tremendously, so glad I don't have to mess with that stuff these days :-)
umarcor
@umarcor

@mingwandroid

There's the R world and Julia also to consider!

Yes. However, the language of choice in EDA is Python (probably for the following couple of decades at least). It was TCL for 2-3 decades, and many vendor tools do still only support TCL for scripting. Hence, there is a long way yet until "too modern" environments such as R or Julia meet EDA.

We have MSYS2 packages in conda to help with building stuff mostly, and also for R but it is out of date.
Conda-forge would probably love someone to update MSYS2-in-conda and automate the continual update of the same, too.
I lost the scripts I wrote in 2016 that I used to do the original import. I added libalpm packages to conda as I remember and parsed the MSYS2 metadata. Now-a-days, I'd rather conda-forge built MSYS2 packages from source using the PKGBUILDs.

I'm not following you completely, but it sounds quite exciting. Did I understand correctly and you are suggesting it's possible to use MSYS2 packages (or recipes), and have them wrapped in Conda? Is that for Windows targets only, or would the same apply for Linux targets (using Arch's recipes)?

I worked with Tim Ansell before actually. He helped us to get our linux-64 compilers in shape in a few ways.

The litex-conda stuff is actually being done by people from Antmicro, who are working with mithro in SymbiFlow. In fact, those litex-conda packages were located in SymbiFlow and Antmicro orgs, they were merged into litex-hub and now are to be moved into hdl.

Actually Anaconda Inc. are looking for people to work on this kind of thing if anyone was interested in doing it professionally.
Conda-forge would probably love someone to update MSYS2-in-conda and automate the continual update of the same, too.

Just to clarify, do you mean someone working on allowing any user to have Windows targets in Conda "for free" as long as the project/tools exists on MSYS2 repos?

Ray Donnelly
@mingwandroid
on conda on Windows you can already do e.g conda install m2-bash yeah.
But it installs really old packages so we need to fix that (both my company and conda-forge, the open source community effort who are our upstream).
umarcor
@umarcor
By looking at https://anaconda.org/search?q=m2-, essentially all the MSYS2 packages were "wrapped" 4 years ago?
So, you were not referring a manual procedure, but to something similar to MSYS2 autobuilder which would generate Conda m2- packages, isn't it?
Ray Donnelly
@mingwandroid
Something automatic yes. We call it binary-repackaged at my place but yes, wrapped works too.
We'd prefer from source builds of the PKGBUILDs inside the conda recipe to repackaging.
Christopher Degawa
@1480c1
I just realized something that might be something I have a problem against, in the start menu, msys2 shows up as MSYS2 MinGW {64,32}-bit referring to MinGW instead of mingw-w64
along with the MSYS2 MSYS one since technically msys also is from MinGW