GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Qt6 on macos: missing generated_cpp · Issue #276 · MeVisLab/pythonqt

Qt6 on macos: missing generated_cpp #276

New issue
Copy link
New issue
Copy link
Closed
Bug
#302
Closed
Qt6 on macos: missing generated_cpp#276
Bug
#302
Copy link

Description

@nim65s
nim65s
opened on Aug 28, 2025
Issue body actions

Hi again,

I am trying to build pythonqt for Qt6 on linux and macos to update the package on nixpkgs, but I am not able to generate the cpp on macos.

This issue can already be seen in the current CI:
https://github.com/MeVisLab/pythonqt/actions/runs/16336586053/job/46149827921 :

Run cd generator
Please wait while source files are being generated...
Parsing typesystem file [:/trolltech/generator/build_all.txt]
"is not set. " Assuming standard binary install using frameworks.
WARNING(Generate) :: ShellImplGenerator: no java classes, skipping
WARNING(Generate) :: ShellHeaderGenerator: no java classes, skipping
PreProcessing - Generate [.preprocessed.tmp] using [:/trolltech/generator/qtscript_masterinclude.h] and include-paths [/Users/runner/work/pythonqt/Qt/5.9.9/clang_64/lib]
Building model using [.preprocessed.tmp]
Classes in typesystem: 0
Generated:
  - header....: 0 (0)
  - impl......: 0 (0)
  - modules...: 0 (0)
  - pri.......: 0 (0)

Done, 2 warnings (1851 known issues)
0s
Run actions/upload-artifact@v4
Warning: No files were found with the provided path: generated_cpp. No artifacts will be uploaded.

But this does not trigger any failure, so I guess this was not seen.

I tried to add a more explicit CI failure in #275 and #277, but that failed.

Anyways, could this be done ? In that case, I guess we should add macos to the "check generated_cpp" CI. Otherwise, we should probably add the generated_cpp for qt 6 to git.

Activity

  1. mrbean-bremen
    added the
    Bug
    issue type on Aug 28, 2025

  2. mrbean-bremen commented on Aug 28, 2025

    @mrbean-bremen
    mrbean-bremen
    on Aug 28, 2025
    Contributor
    More actions

    Thanks - that should certainly trigger an error in the CI, looks like nobody has noticed this so far.
    We don't build under macOS, and I don't own a Mac, so it would be good if somebody with a Mac could have a closer look.
    The CI should be fixed anyway to see this as an error.

  3. mrbean-bremen commented on Aug 28, 2025

    @mrbean-bremen
    mrbean-bremen
    on Aug 28, 2025
    Contributor
    More actions

    See this comment.

    Reacted by Guilhem Saurel
  4. mrbean-bremen
    added 4 commits that reference this issue on Aug 28, 2025

    Let the CI fail if no wrappers are generated

    e3e056b

    Let the CI fail if no wrappers are generated

    acd0b26

    Let the CI fail if no wrappers are generated

    c9587e2

    Let the CI fail if no wrappers are generated

    d2c4505
  5. mrbean-bremen
    closed this as completedin #302on Sep 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Bug

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions
      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.