Building heaptrack_gui

[sindhu krishnan]

Hi Milian,

Thank you !
This is one set of error am facing in kio:
==========
/home/smuthu545/heaptrack-llama/build-sky-llama-panel/tmp/work/x86_64-linux/kio-native/5.99.0-r0/kio-5.99.0/src/core/ktcpsocket.h:54:19:
error: ‘QSslKey’ does not name a type; did you mean ‘KSslKey’?
     KSslKey(const QSslKey &sslKey);
                   ^~~~~~~
                   KSslKey
/home/smuthu545/heaptrack-llama/build-sky-llama-panel/tmp/work/x86_64-linux/kio-native/5.99.0-r0/kio-5.99.0/src/core/ktcpsocket.h:77:22:
error: ‘QSslCipher’ does not name a type; did you mean ‘KSslCipher’?
     KSslCipher(const QSslCipher &);
                      ^~~~~~~~~~
                      KSslCipher
/home/smuthu545/heaptrack-llama/build-sky-llama-panel/tmp/work/x86_64-linux/kio-native/5.99.0-r0/kio-5.99.0/src/core/ktcpsocket.h:126:55:
error: ‘QSslCertificate’ does not name a type; did you mean
‘KSslKeyPrivate’?
     KSslError(KSslError::Error error = NoError, const QSslCertificate
&cert = QSslCertificate());
                                                       ^~~~~~~~~~~~~~~
                                                       KSslKeyPrivate
/home/smuthu545/heaptrack-llama/build-sky-llama-panel/tmp/work/x86_64-linux/kio-native/5.99.0-r0/kio-5.99.0/src/core/ktcpsocket.h:135:5:
error: ‘QSslCertificate’ does not name a type; did you mean
‘KSslKeyPrivate’?
     QSslCertificate certificate() const;
     ^~~~~~~~~~~~~~~
     KSslKeyPrivate
/home/smuthu545/heaptrack-llama/build-sky-llama-panel/tmp/work/x86_64-linux/kio-native/5.99.0-r0/kio-5.99.0/src/core/ktcpsocket.h:126:79:
error: ‘QSslCertificate’ was not declared in this scope
     KSslError(KSslError::Error error = NoError, const QSslCertificate
&cert = QSslCertificate());

        ^~~~~~~~~~~~~~~
/home/smuthu545/heaptrack-llama/build-sky-llama-panel/tmp/work/x86_64-linux/kio-native/5.99.0-r0/kio-5.99.0/src/core/ktcpsocket.h:126:79:
note: suggested alternative: ‘InvalidCertificate’
     KSslError(KSslError::Error error = NoError, const QSslCertificate
&cert = QSslCertificate());

        ^~~~~~~~~~~~~~~

        InvalidCertificate
/home/smuthu545/heaptrack-llama/build-sky-llama-panel/tmp/work/x86_64-linux/kio-native/5.99.0-r0/kio-5.99.0/src/core/ktcpsocket.h:317:33:
error: ‘QSslCertificate’ does not name a type; did you mean
‘KSslKeyPrivate’?
     void addCaCertificate(const QSslCertificate &certificate);
                                 ^~~~~~~~~~~~~~~
                                 KSslKeyPrivate
/home/smuthu545/heaptrack-llama/build-sky-llama-panel/tmp/work/x86_64-linux/kio-native/5.99.0-r0/kio-5.99.0/src/core/ktcpsocket.h:320:40:
error: ‘QSslCertificate’ was not declared in this scope
     void addCaCertificates(const QList<QSslCertificate> &certificates);
                                        ^~~~~~~~~~~~~~~
===========
Similarly, I do see errors like some of the files are not visible
though it is available in the kio recipe's sysroot.

tmp/work/x86_64-linux/kio-native/5.99.0-r0/kio-5.99.0/src/ioslaves/http/kcookiejar/kcookiewin.cpp:33:10:
fatal error: KUserTimestamp: No such file or directory
 #include <KUserTimestamp>

It is available in :
./recipe-sysroot-native/usr/include/KF5/KWindowSystem/KUserTimestamp
Looks like I have to include the path using CFLAGS.

Note : I'm using gcc 9.3.0.

Thank you.

On Thu, Oct 12, 2023 at 3:25 PM Milian Wolff <mail at milianw.de> wrote:
>
> On Donnerstag, 12. Oktober 2023 01:31:35 CEST sindhu krishnan wrote:
> > Hi,
> >
> > I am currently in the process of attempting to build Heaptrack_gui within
> > the Yocto build system. I have upgraded the Qt versions to 5.15 and am
> > using KDE libraries of version 5.99. However, I am encountering several
> > dependency errors during the build process of the KDE libraries.
> >
> > These errors in includes issues during compilation, where the dependent
> > files are not visible, as well as challenges in obtaining configuration
> > files. These errors persist across all the recipes.
>
> What errors exactly? Paste them somewhere so we can see what you are seeing.
>
> > I am inquiring whether it is feasible to build the Heaptrack_gui within the
> > Yocto build system.
>
> Sure, in principle there's nothing that makes heaptrack_gui or yocto special
> in any way. You simply must make sure that all the required bits and pieces
> are available and found.
>
> > We are planning to make custom modifications in the
> > GUI. Should we require assistance or collaboration from the KDE team to
> > facilitate changes in Heaptrack_gui, kindly advise.
>
> Please contribute your changes back upstream, if they are useful.
>
> > Note : I'm using dunfell version of yocto
> >
> > Thank you for your guidance.
>
>
> --
> Milian Wolff
> mail at milianw.de
> http://milianw.de