After Qt5 changes and GCC upgrade, Cutegram no longer works as intended (as in, it doesn't work..like at all). This is a known issue and I'm working towards resolving it.
Description
Description
Event Timeline
Comment Actions
Took a peek at this and seems we either have to downgrade telegramqml or upgrade cutegram to the 2.95-dev branch or master, the stable 2.7.1 branch uses deprecated code in the telegramqml package that is moved to the non-used "old" folder; unfortunately it's also out of the build tree so we can't just put it back together even if it is in the tree.
The build stuff also needed a couple tweaks
- pkgconfig(Qt5WebKit) in the builddeps
And
QMAKE_CFLAGS_ISYSTEM= to the build -> qmake section, to fix a bug with GCC 6.1+
@JoshStrobl let me know what do you think, I'm attaching the patch for the package.yml in case.
Comment Actions
Yea none of this is news. As stated, this is in progress, I'm assigned to it. It'll be fixed when it's fixed.
Comment Actions
So I ended up doing one big revert of all the stuff I was working on. Cutegram in its current state, alongside libqtelegram-ae, is just an outright disaster. Opted to go 2.7.1 until they sort things out. Honestly, it's what I should've done in the first place, just wanted all the latest goodies (primarily from telegramlqml). Oh well.
Either way, currently using Cutegram locally. Works in unstable as of https://git.solus-project.com/packages/cutegram/commit/?id=31243057f5dcc317fa0fa29896cc5b973b31d52a