{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreie7sxx5vnxseiqamjk5svgukbhmwpe76u4lrg3yfhehk5ll3teiza",
    "uri": "at://did:plc:yrn4rbgwenb6lfhhzjegbtnc/app.bsky.feed.post/3meb7crnviiz2"
  },
  "path": "/t/prebuilt-blobs-for-build-time-deps/11700#post_1",
  "publishedAt": "2026-02-07T08:38:11.000Z",
  "site": "https://discourse.flathub.org",
  "tags": [
    "interest",
    "sdk extension"
  ],
  "textContent": "Hi! I maintain a Proton/Wine extension that is often used as an add-on for Steam, and there is interest from my users in releasing it as a Flatpak to make installation (much) easier for that use case.\n\nThe issue is, the build process requires Wine and a mingw32(64) toolchain. Currently I have it building on GitHub Actions (with the relevant Ubuntu packages). Distributing the prebuilt binaries in Flatpak would be easiest, but I understand that’s frowned upon.\n\nWhat’s the best/allowed way to approach this? I think getting the build to work inside flatpak-builder is probably doable _if_ pulling in a prebuilt Wine as a build-time dependency is acceptable. I see there’s an sdk extension for MinGW, but not Wine itself (Wine itself is a Flatpak though). I don’t really want to maintain a Wine SDK extension just for this, I don’t have the bandwidth for that.",
  "title": "Prebuilt blobs for build-time deps?"
}