Bug 471386

Summary: Cannot build kwidgetsaddons in QT 5.15.8 due to DQT_NO_CAST_FROM_ASCII
Product: [I don't know] kde Reporter: greenscarf005
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED NOT A BUG    
Severity: normal CC: nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: build log for kwidgetsaddons
entire log file zipped

Description greenscarf005 2023-06-23 14:10:49 UTC
Created attachment 159858 [details]
build log for kwidgetsaddons

SUMMARY

cannot build half of kde dependencies as QString::QString(const char*) is private

STEPS TO REPRODUCE
1. run kdesrc-build spectacle 
2. run kdesrc-build kwidgetsaddons

OBSERVED RESULT

build fails with /home/username/repo/kde5/build/kwidgetsaddons/src/ui_kpassworddialog.h:107:41: error: ‘QString::QString(const char*)’ is private within this context

EXPECTED RESULT

it does not fail to build

SOFTWARE/OS VERSIONS

Operating System: Kubuntu 23.04
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.3.7-060307-generic (64-bit)
Graphics Platform: X11


ADDITIONAL INFORMATION

tried unsetting flags manually but there weren't such a way to unset cmake flags, only to set cmake flags
https://docs.kde.org/trunk5/en/kdesrc-build/kdesrc-build/conf-options-table.html#conf-cmake-options
Comment 1 greenscarf005 2023-06-23 14:13:43 UTC
Created attachment 159859 [details]
entire log file zipped
Comment 2 Nate Graham 2023-08-04 20:07:33 UTC
Hello! You've reached the KDE bug tracker, which is for tracking bugs in KDE software. Unfortunately here on the bug tracker, we cannot offer help with software development topics not clearly related to bugs in KDE software. This includes help setting up a dev environment, compiling specific projects, and so on. In this case, KWidgetsAddons is green on our CI without -DQT_NO_CAST_FROM_ASCII, so I think you're in uncharted territory by turning it on, and this isn't considered a bug. But if you'd like to help us support that option, fee free to submit patches to do so!

You can find appropriate ways to get in contact with the dev team for assistance at https://community.kde.org/Get_Involved/development#Communicate_with_the_dev_team.