Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 12:14

    lazka on master

    Update PKGBUILD Merge pull request #9780 from r… (compare)

  • 12:14
    lazka closed #9780
  • 11:46
    raedrizqie commented #9780
  • 11:37
    Biswa96 commented #9780
  • 11:18
    MehdiChinoune synchronize #9778
  • 11:08
    MehdiChinoune commented #9778
  • 10:42
    raedrizqie opened #9780
  • 09:20
    MehdiChinoune synchronize #9778
  • 09:18
    MehdiChinoune synchronize #9778
  • 09:17
    lazka synchronize #9770
  • 09:16

    lazka on master

    pywin32-ctypes 0.2.0 added clang Merge pull request #9772 from r… (compare)

  • 09:16
    lazka closed #9772
  • 09:06
    MehdiChinoune synchronize #9778
  • 08:51
    MehdiChinoune synchronize #9778
  • 08:47
    raedrizqie synchronize #9770
  • 08:42
    MehdiChinoune synchronize #9778
  • 08:31
    MehdiChinoune synchronize #9778
  • 08:10
    lazka commented #9771
  • 08:09
    lazka commented #9771
  • 07:45
    raedrizqie commented #9778
Naveen M K
@naveen521kk
Possibly add MINGW64 python as a make dependency in MINGW32. See if that works?
Biswapriyo Nath
@Biswa96
I would suggest not to mix those.
Naveen M K
@naveen521kk
If you do so the python library there will not work.
If its only a makedep then it is ok.
Ray Donnelly
@mingwandroid
You could setup a new sysconfig_blah.py for this cross scenario too ..
easily enough done
Unai Martinez-Corral
@umarcor
@naveen521kk mingw-w64-x86_64-python is already installed, because it's a dependency of mingw-w64-x86_64-prjtrellis: https://github.com/msys2/MINGW-packages/pull/7568/checks?check_run_id=1677639388#step:5:1106

I would suggest not to mix those.

@Biswa96, honestly, I don't like doing it like this. But I think this is better than pushing an intermediate package to MSYS2 which is just to be used while building nextpnr.

So, I thought about creating nextpnr-chipdbs and then make mingw-w64-nextpnr depend on that.

You could setup a new sysconfig_blah.py for this cross scenario too ..

@mingwandroid, there is already a helper script for executing this step (https://github.com/msys2/MINGW-packages/pull/7568/files#diff-5525f40256b3131d3d3c52f57815fb1ca64d76f2bcc3a94cbf41ac9705fe2afd). Yet, I don't see where would sysconfig_blah.py fit in there, since those are just calls to cmake.

Ray Donnelly
@mingwandroid
If you want me to take a look I can, but CMake asks distutils for the details basically
But they keep reworking FindPython.cmake so yeah, YMMV!
I can't look until I get out of this place and back home though
In fact, everything that interfaces with CPython correctly from a build POV asks distutils at the end of the day since that's the only source of truth for how to compile stuff
well, there's numpy too, it has its own stuff but that gets 'copied' from distutils when you build numpy (to a certain extent)
the only other avenue things can reasonably use is to call python-config
Алексей
@Alexpux
Hi!
I start new discussion for Python users here https://github.com/msys2/MINGW-packages/discussions/7646
Алексей
@Alexpux
@lazka hi
Christoph Reiter
@lazka
hi
Алексей
@Alexpux
why CI start building only last commit if I push multiple commits?
Christoph Reiter
@lazka
it only triggers on push
I don't think appveyor was different here, but not 100% sure
@Alexpux fyi, we have package file diffs in CI now: https://github.com/msys2/MINGW-packages/runs/1680015924#step:5:4342
Алексей
@Alexpux
ok so i nedd push commits one buy one seems
Christoph Reiter
@lazka
yes, that would work.
but CI should still build everything inbetween, shouldn't it?
Алексей
@Alexpux
yes
Christoph Reiter
@lazka
oh, looks like it doesn't
Алексей
@Alexpux
yes it doesnt build everything
it build only last commit
if i push multiple commits
Christoph Reiter
@lazka
ok, we should fix that
it should work if you create a branch or PR though
Christoph Reiter
@lazka
seems like github provides a "${{ github.event.before }}" reference for the previous push
Christoph Reiter
@lazka
@mingwandroid note that distutils is getting removed from python, so things are about to change -> PEP 632
Ray Donnelly
@mingwandroid
OK. I think few used distutils directly, usually done via setuptools .. so most will not care; yeah, we will have to care!
This leads nowhere: "(1, 2) Porting from Distutils ( https://setuptools.readthedocs.io/en/latest/distutils-legacy.html )" unfortunately.
Astrum-polaris
@Astrum-polaris
Christoph Reiter
@lazka
yeah, setuptools should be fine, after we patch it to support MSYS2 like distutils
Christoph Reiter
@lazka
I need to make generate-srcinfo retry.. git crashes too often
Ray Donnelly
@mingwandroid
Is it time to consider moving to mingw-w64 git?
I run with Johannes' repo having precedence usually so that is the git I run by and large.
or just provide both and let the user pick? make them conflict?
David Macek
@elieux
Moving away would be hard regarding dependencies.
Providing both seems okay.
No conflicts please.
Ray Donnelly
@mingwandroid
Another discussion time?
Алексей
@Alexpux
@lazka hey
how are rebuilds work for updated packages?