Bug 33398 - qhexedit2: add qt-designer plugin support and, maybe, swith to Qt6 build
Summary: qhexedit2: add qt-designer plugin support and, maybe, swith to Qt6 build
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: David GEIGER
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-13 21:46 CEST by Aurelian R
Modified: 2024-07-16 00:30 CEST (History)
0 users

See Also:
Source RPM: qhexedit2-0.8.9-6.mga10.src
CVE:
Status comment:


Attachments
patch to add Qt-plugin and switch to Qt6 (8.25 KB, patch)
2024-07-13 21:46 CEST, Aurelian R
Details | Diff
adds Qt6 backend support (5.67 KB, patch)
2024-07-13 21:47 CEST, Aurelian R
Details | Diff

Description Aurelian R 2024-07-13 21:46:10 CEST
Created attachment 14589 [details]
patch to add Qt-plugin and switch to Qt6

Description of problem:
qhexedit is missing its plugin that can be used with qt-creator/designer and qhexedit package could be build against Qt6 too.

Attached is a patch for qhexedit2 spec file that can pick/enable any of Qt5/Qt6 backends, builds the Qt plugin and runs the self tests; I will also post a modified qhexedit2_build.patch that adds support for Qt6.

Regards.
Comment 1 Aurelian R 2024-07-13 21:47:28 CEST
Created attachment 14590 [details]
adds Qt6 backend support
Comment 2 Lewis Smith 2024-07-15 21:33:47 CEST
Thank you Aurelian for the report and input.
Unsure whether what you have supplied includes the missing plugin, or whether that remains the request.

Assigning directly to DavidG because you are clearly the current maintainer for this package.

Assignee: bugsquad => geiger.david68210

Comment 3 Aurelian R 2024-07-16 00:30:57 CEST
(In reply to Lewis Smith from comment #2)
> Unsure whether what you have supplied includes the missing plugin, or
> whether that remains the request.

The proposed spec file patch enables building of the qt-plugin.

Cheers.

Note You need to log in before you can comment on or make changes to this bug.