[Buildroot] Question about pkg-config pc files

[Buildroot] Question about pkg-config pc files

[Patricia Holden]

[-- Attachment #1.1: Type: text/plain, Size: 472 bytes --]

I am adding a package that has dependencies on QT pkg-config pc files.  I
see the pkg-config pc files in
output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/share/pkgconfig/, but
I don't see any pkg-config files installed to target.  the QQmlApplication
code is trying to include multiple qt packages but they are not found.
Running "pkg-config --list-all" results in none found at all.

How do I get pkg-config pc files installed to the target?

-- 
Patricia A. Holden

[-- Attachment #1.2: Type: text/html, Size: 667 bytes --]

[-- Attachment #2: Type: text/plain, Size: 145 bytes --]

_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] Question about pkg-config pc files

[Patricia Holden]

I am adding a package that has dependencies on QT pkg-config pc files.  I
see the pkg-config pc files in
output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/share/pkgconfig/, but
I don't see any pkg-config files installed to target.  the QQmlApplication
code is trying to include multiple qt packages but they are not found.
Running "pkg-config --list-all" results in none found at all.

How do I get pkg-config pc files installed to the target?

-- 
Patricia A. Holden
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210720/f76f6b20/attachment-0001.html>

Re: [Buildroot] Question about pkg-config pc files

[Thomas Petazzoni]

Hello Patricia,

On Tue, 20 Jul 2021 16:41:40 -0400
Patricia Holden <pholden@nklabs.com> wrote:

> I am adding a package that has dependencies on QT pkg-config pc files.  I
> see the pkg-config pc files in
> output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/share/pkgconfig/, but
> I don't see any pkg-config files installed to target.  the QQmlApplication
> code is trying to include multiple qt packages but they are not found.
> Running "pkg-config --list-all" results in none found at all.
> 
> How do I get pkg-config pc files installed to the target?

You don't: Buildroot doesn't support doing development on the target.
Why would you need .pc files on the target ? Is QQmlApplication using
pkg-config at run-time on the target ?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] Question about pkg-config pc files

[Thomas Petazzoni]

Hello Patricia,

On Tue, 20 Jul 2021 16:41:40 -0400
Patricia Holden <pholden@nklabs.com> wrote:

> I am adding a package that has dependencies on QT pkg-config pc files.  I
> see the pkg-config pc files in
> output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/share/pkgconfig/, but
> I don't see any pkg-config files installed to target.  the QQmlApplication
> code is trying to include multiple qt packages but they are not found.
> Running "pkg-config --list-all" results in none found at all.
> 
> How do I get pkg-config pc files installed to the target?

You don't: Buildroot doesn't support doing development on the target.
Why would you need .pc files on the target ? Is QQmlApplication using
pkg-config at run-time on the target ?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Re: [Buildroot] Question about pkg-config pc files

[Patricia Holden]

Yes, QQmlApplucation I am porting for a client it is using pc at runtime.  Would it help to see what they are doing?

Sent from my iPhone

> On Jul 20, 2021, at 4:48 PM, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> 
> Hello Patricia,
> 
>> On Tue, 20 Jul 2021 16:41:40 -0400
>> Patricia Holden <pholden@nklabs.com> wrote:
>> 
>> I am adding a package that has dependencies on QT pkg-config pc files.  I
>> see the pkg-config pc files in
>> output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/share/pkgconfig/, but
>> I don't see any pkg-config files installed to target.  the QQmlApplication
>> code is trying to include multiple qt packages but they are not found.
>> Running "pkg-config --list-all" results in none found at all.
>> 
>> How do I get pkg-config pc files installed to the target?
> 
> You don't: Buildroot doesn't support doing development on the target.
> Why would you need .pc files on the target ? Is QQmlApplication using
> pkg-config at run-time on the target ?
> 
> Thomas
> -- 
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Re: [Buildroot] Question about pkg-config pc files

[Thomas Petazzoni]

Hello,

On Wed, 21 Jul 2021 02:23:55 -0400
Patricia Holden <pholden@nklabs.com> wrote:

> Yes, QQmlApplucation I am porting for a client it is using pc at
> runtime.  Would it help to see what they are doing?

Ah, it is your customer-specific application that is using the .pc
files, not QT itself ?

If it's your customer-specific application, then it would be useful to
check why they are doing this, as it feels odd.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Re: [Buildroot] Question about pkg-config pc files

[Patricia Holden]

[-- Attachment #1.1: Type: text/plain, Size: 1122 bytes --]

I looked into QQmlApplication examples, they all use pc files.

I'm attaching the files that are doing the import of pkg-config pc files.
This is the customer's implementation.

The attached URL provides examples that use the same implementation.  Note
all their examples use the "import" statement at top, this is what is
looking for pc files:

https://doc.qt.io/qt-5/qtmultimedia-multimedia-video-qmlvideo-example.html

On Wed, Jul 21, 2021 at 3:41 AM Thomas Petazzoni <
thomas.petazzoni@bootlin.com> wrote:

> Hello,
>
> On Wed, 21 Jul 2021 02:23:55 -0400
> Patricia Holden <pholden@nklabs.com> wrote:
>
> > Yes, QQmlApplucation I am porting for a client it is using pc at
> > runtime.  Would it help to see what they are doing?
>
> Ah, it is your customer-specific application that is using the .pc
> files, not QT itself ?
>
> If it's your customer-specific application, then it would be useful to
> check why they are doing this, as it feels odd.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>


-- 
Patricia A. Holden

[-- Attachment #1.2: Type: text/html, Size: 1901 bytes --]

[-- Attachment #2: main.cpp --]
[-- Type: text/x-c++src, Size: 3083 bytes --]

#include <QGuiApplication>
#include <QQmlApplicationEngine>
#include <QtGui/QGuiApplication>
#include <QtQuick/QQuickView>
#include <QtQml/QQmlContext>
#include <QtQml/QQmlEngine>
#include <QtMultimedia/QAbstractVideoSurface>
#include "manualcalibration.h"
#include "videostream.h"
#include "videoadapter.h"
#include "signalhandler.h"
#include <QProcess>
#include <gst/gst.h>
#include <QtCore/qobject.h>

int main(int argc, char *argv[])
{
    QProcess process;

    qInfo()<<"VPA Calibration App ID : "<<QCoreApplication::applicationPid();
    QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling);

    QGuiApplication app(argc, argv);
    QQmlApplicationEngine engine;
    QQmlDebuggingEnabler enabler;

    VideoAdapter adapter;
    SignalHandler *signalHandler = SignalHandler::getInstance();

    engine.rootContext()->setContextProperty(QLatin1String("videoAdapter"), &adapter);

    const QUrl url(QUrl::fromLocalFile("main.qml"));
    QObject::connect(&engine, &QQmlApplicationEngine::objectCreated,
		     &app, [url](QObject *obj, const QUrl &objUrl) {
		       if (!obj && url == objUrl)
			 QCoreApplication::exit(-1);
		     }, Qt::QueuedConnection);
    engine.load(url);
    if (engine.rootObjects().isEmpty())
        return -1;

    ManualCalibration manualCalibration;
    VideoStream *videoStream = VideoStream::getInstance();
    QObject *rootObject = engine.rootObjects().first();

    QObject::connect(&manualCalibration,SIGNAL(sigChangeVideoPosition(ReticuleLUT)),videoStream,SLOT(onChangeVideoPosition(ReticuleLUT)));
    QObject::connect(rootObject, SIGNAL(sigIncVideoDiameter()),&manualCalibration, SLOT(onIncVideoDiameter()));
    QObject::connect(rootObject, SIGNAL(sigDecVideoDiameter()),&manualCalibration, SLOT(onDecVideoDiameter()));
    QObject::connect(rootObject, SIGNAL(sigUp()),&manualCalibration, SLOT(onUp()));
    QObject::connect(rootObject, SIGNAL(sigDown()),&manualCalibration, SLOT(onDown()));
    QObject::connect(rootObject, SIGNAL(sigRight()),&manualCalibration, SLOT(onRight()));
    QObject::connect(rootObject, SIGNAL(sigLeft()),&manualCalibration, SLOT(onLeft()));
    QObject::connect(rootObject, SIGNAL(sigSaveData()),&manualCalibration, SLOT(onSaveData()));
    QObject::connect(rootObject, SIGNAL(sigChangeDistance(int)),&manualCalibration, SLOT(onChangeDistance(int)));

    QObject::connect(signalHandler, SIGNAL(sigCalibrationControl(ECommandID)),&manualCalibration, SLOT(onCalibrationControl(ECommandID)));

    QObject::connect(&manualCalibration, SIGNAL(sigChangeDistanceUI(QVariant)),rootObject, SLOT(changeDistanceUI(QVariant)));
    QObject::connect(&manualCalibration, SIGNAL(sigAddDistance(QVariant)),rootObject, SLOT(onAddDistance(QVariant)));
    QObject::connect(videoStream, SIGNAL(sigEnableControl(QVariant)), rootObject, SLOT(onEnableControls(QVariant)));
    QObject::connect(&app,SIGNAL(aboutToQuit()),videoStream,SLOT(cls()));
    manualCalibration.init();

    GstElement *videoSink = gst_element_factory_make("qtvideosink", NULL);
    videoStream->startSteaming(videoSink);
    return app.exec();
}

[-- Attachment #3: main.qml --]
[-- Type: text/x-qml, Size: 4785 bytes --]

import QtQuick 2.9
import QtQuick.Window 2.0
import QtQuick.Controls 2.0
import QtMultimedia 5.0

Window {
    signal sigUp();
    signal sigDown();
    signal sigRight();
    signal sigLeft();
    signal sigIncVideoDiameter();
    signal sigDecVideoDiameter();
    signal sigChangeDistance(int dist);
    signal sigSaveData();

    function onEnableControls(isEnabled){
        cmbDistance.enabled = isEnabled;
        btnDecVideoDiameter.enabled = isEnabled;
        btnIncVideoDiameter.enabled = isEnabled;
        btnDown.enabled = isEnabled;
        btnLeft.enabled = isEnabled;
        btnRight.enabled = isEnabled;
        btnUp.enabled = isEnabled;
        btnSave.enabled = isEnabled;
    }

    function onAddDistance( distance){
        var arr = distance.split(",");
        model.clear();
        for(var i=0;i<3;i++){
            console.log('arr : '+arr[i]);
            model.append({text:arr[i]});
        }
        cmbDistance.currentIndex = 0;
    }

    function changeDistanceUI(index){
        cmbDistance.currentIndex = index;
    }

    id:window
    visible: true
    width: 320
    height: 240
    x:0
    y:0
    color:"#ffffff"
    flags: Qt.FramelessWindowHint|Qt.Window
    Video {
        id: video
        x:0
        y:0
        width: 320
        height: 240
        surface: videoSurface1 //bound on the context from main()
    }

    Rectangle {
        id: manualCalibration
        color: 'transparent'
        width: 320
        height: 240
        ComboBox {
            x:5
            id: cmbDistance
            y:5
            width:90
            height: 30
            editable: false
            font.pixelSize: 16

            model: ListModel {
                id: model

            }
            onAccepted: {
                if (find(editText) === -1)
                    model.append({text: editText})
            }
            Component.onCompleted: {
                contentItem.height = 30
                cmbDistance.popup.width  = 90
                cmbDistance.popup.height = 120;
                font.pixelSize = 16

            }
            popup.font.pixelSize: 16
            popup.contentItem.height: 20
            onCurrentIndexChanged: {
                console.log("currentIndex changed");
                sigChangeDistance(cmbDistance.currentIndex);
            }
        }

        Button {
            id:btnDecVideoDiameter
            x:10
            y:185
            width:30
            height: 30
            autoRepeat:true
            text: "-"
            font.pixelSize: 16
            onClicked: {
                sigDecVideoDiameter();
            }
        }
        Button {
            id:btnIncVideoDiameter
            x:50
            y:185
            width:30
            height: 30
            autoRepeat:true
            text: "+"
            font.pixelSize: 16
            onClicked: {
                sigIncVideoDiameter();
            }
        }
        Text {
            x:10
            y:220
            width:30
            font.pixelSize: 14
            color: 'white'
            text: qsTr("Video Diameter")
        }

        Text {
            x:220
            y:5
            color: 'white'
            font.pixelSize: 14
            text: qsTr("Laser Position")
        }

        Button {
            id:btnUp
            x:275
            y:25
            width:20
            height:20
            font.pixelSize: 16
            autoRepeat:true
            text: "<font color='#000000'>\u25B4</font>"
            onClicked: {
                sigUp();
            }
        }
        Button {
            id:btnDown
            x:275
            y:65
            width:20
            height:20
            font.pixelSize: 16
            autoRepeat:true
            text: "<font color='#000000'>\u25BE</font>"
            onClicked: {
                sigDown();
            }
        }
        Button {
            id:btnLeft
            x:254
            y:45
            width:20
            height:20
            autoRepeat:true
            font.pixelSize: 16
            text: "<font color='#000000'>\u25C2</font>"
            onClicked: {
                sigLeft()
            }
        }
        Button {
            id:btnRight
            x:294
            y:45
            width:20
            height:20
            autoRepeat:true
            font.pixelSize: 16
            text: "<font color='#000000'>\u25B8</font>"
            onClicked: {
                sigRight()
            }
        }

        Button{
            id:btnSave
            x:230
            y:200
            width:80
            height:30
            text: "Calibrate"
            font.pixelSize: 14
            onClicked: {
                sigSaveData();
            }
        }
    }
}

[-- Attachment #4: Type: text/plain, Size: 145 bytes --]

_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Re: [Buildroot] Question about pkg-config pc files

[Patricia Holden]

[-- Attachment #1.1: Type: text/plain, Size: 1563 bytes --]

I think I found my problem, I stumbled upon it in stackoverflow.  I needed
to use the engine function addImportPath().  "import" in the qml is for a
module in /usr/qml/Qt*, not pkg-config.  Took some digging.  Their
documentation is a bit misleading at times & I'm not an expert in Qt.

On Wed, Jul 21, 2021 at 3:07 PM Patricia Holden <pholden@nklabs.com> wrote:

> I looked into QQmlApplication examples, they all use pc files.
>
> I'm attaching the files that are doing the import of pkg-config pc files.
> This is the customer's implementation.
>
> The attached URL provides examples that use the same implementation.  Note
> all their examples use the "import" statement at top, this is what is
> looking for pc files:
>
> https://doc.qt.io/qt-5/qtmultimedia-multimedia-video-qmlvideo-example.html
>
> On Wed, Jul 21, 2021 at 3:41 AM Thomas Petazzoni <
> thomas.petazzoni@bootlin.com> wrote:
>
>> Hello,
>>
>> On Wed, 21 Jul 2021 02:23:55 -0400
>> Patricia Holden <pholden@nklabs.com> wrote:
>>
>> > Yes, QQmlApplucation I am porting for a client it is using pc at
>> > runtime.  Would it help to see what they are doing?
>>
>> Ah, it is your customer-specific application that is using the .pc
>> files, not QT itself ?
>>
>> If it's your customer-specific application, then it would be useful to
>> check why they are doing this, as it feels odd.
>>
>> Best regards,
>>
>> Thomas
>> --
>> Thomas Petazzoni, co-owner and CEO, Bootlin
>> Embedded Linux and Kernel engineering
>> https://bootlin.com
>>
>
>
> --
> Patricia A. Holden
>


-- 
Patricia A. Holden

[-- Attachment #1.2: Type: text/html, Size: 2687 bytes --]

[-- Attachment #2: Type: text/plain, Size: 145 bytes --]

_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Re: [Buildroot] Question about pkg-config pc files

[Patricia Holden]

[-- Attachment #1.1: Type: text/plain, Size: 2919 bytes --]

Hi Thomas,

The saga continues.  I found that multimedia is not added
because BR2_PACKAGE_QT5_GL_AVAILABLE is not set.  In order to configure QT
OpenGL, I enabled ti-gfx since our board is a beaglebone-x15.  Now I can't
get past building ti-gfx.  I have a local source directory for the kernel,
since we had to add our own drivers for some proprietary devices on the
design based on beaglebone X15.  I also use the local source directory to
generate linux-headers.  We based the kernel from TI's SDK.  I checked the
kernel config, fbdev omap is selected.  But I get the following error:

 CC [M]
 /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-gfx-5_01_01_02/GFX_Linux_KM/services4/srvkm/common/pvrsrv.o
  CC [M]
 /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-gfx-5_01_01_02/GFX_Linux_KM/services4/srvkm/common/handle.o
/home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-gfx-5_01_01_02/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_linux.c:133:10:
fatal error: omapfb/omapfb.h: No such file or directory
  133 | #include <omapfb/omapfb.h>
      |          ^~~~~~~~~~~~~~~~~


The file "omapfb.h" is in drivers/video/fbdev/omap2/omapfb, but for some
reason the ti-gfx package does not find it.  We are using
buildroot-2020-20.02.12.

I did not see this error in the buildroot issues, I am wondering why it is
causing problems.  My only guess is that it may have something to do with
the fact that I have a local kernel source directory.

Thanks for any help!


Sent from my iPhone

On Jul 21, 2021, at 3:07 PM, Patricia Holden <pholden@nklabs.com> wrote:


I looked into QQmlApplication examples, they all use pc files.

I'm attaching the files that are doing the import of pkg-config pc files.
This is the customer's implementation.

The attached URL provides examples that use the same implementation.  Note
all their examples use the "import" statement at top, this is what is
looking for pc files:

https://doc.qt.io/qt-5/qtmultimedia-multimedia-video-qmlvideo-example.html

On Wed, Jul 21, 2021 at 3:41 AM Thomas Petazzoni <
thomas.petazzoni@bootlin.com> wrote:

> Hello,
>
> On Wed, 21 Jul 2021 02:23:55 -0400
> Patricia Holden <pholden@nklabs.com> wrote:
>
> > Yes, QQmlApplucation I am porting for a client it is using pc at
> > runtime.  Would it help to see what they are doing?
>
> Ah, it is your customer-specific application that is using the .pc
> files, not QT itself ?
>
> If it's your customer-specific application, then it would be useful to
> check why they are doing this, as it feels odd.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>


-- 
Patricia A. Holden
<main.cpp>
<main.qml>

[-- Attachment #1.2: Type: text/html, Size: 4149 bytes --]

[-- Attachment #2: Type: text/plain, Size: 145 bytes --]

_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Re: [Buildroot] Question about pkg-config pc files

[Arnout Vandecappelle]

On 22/07/2021 19:36, Patricia Holden wrote:
> Hi Thomas,
> 
> The saga continues.  I found that multimedia is not added
> because BR2_PACKAGE_QT5_GL_AVAILABLE is not set.  In order to configure QT
> OpenGL, I enabled ti-gfx since our board is a beaglebone-x15.

 Not that I've ever used this board, but AFAIK for AM57xx you should use ti-sgx,
not ti-gfx.

 Regards,
 Arnout


>  Now I can't get
> past building ti-gfx.  I have a local source directory for the kernel, since we
> had to add our own drivers for some proprietary devices on the design based on
> beaglebone X15.  I also use the local source directory to generate
> linux-headers.  We based the kernel from TI's SDK.  I checked the kernel config,
> fbdev omap is selected.  But I get the following error:
> 
>  CC [M]
>  /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-gfx-5_01_01_02/GFX_Linux_KM/services4/srvkm/common/pvrsrv.o
>   CC [M]
>  /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-gfx-5_01_01_02/GFX_Linux_KM/services4/srvkm/common/handle.o
> /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-gfx-5_01_01_02/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_linux.c:133:10:
> fatal error: omapfb/omapfb.h: No such file or directory
>   133 | #include <omapfb/omapfb.h>
>       |          ^~~~~~~~~~~~~~~~~
> 
> 
> The file "omapfb.h" is in drivers/video/fbdev/omap2/omapfb, but for some reason
> the ti-gfx package does not find it.  We are using buildroot-2020-20.02.12.
> 
> I did not see this error in the buildroot issues, I am wondering why it is
> causing problems.  My only guess is that it may have something to do with the
> fact that I have a local kernel source directory.

[snip]
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Re: [Buildroot] Question about pkg-config pc files

[Patricia Holden]

[-- Attachment #1.1: Type: text/plain, Size: 2023 bytes --]

Thanks, I will try that!

On Thu, Jul 22, 2021 at 3:40 PM Arnout Vandecappelle <arnout@mind.be> wrote:

>
>
> On 22/07/2021 19:36, Patricia Holden wrote:
> > Hi Thomas,
> >
> > The saga continues.  I found that multimedia is not added
> > because BR2_PACKAGE_QT5_GL_AVAILABLE is not set.  In order to configure
> QT
> > OpenGL, I enabled ti-gfx since our board is a beaglebone-x15.
>
>  Not that I've ever used this board, but AFAIK for AM57xx you should use
> ti-sgx,
> not ti-gfx.
>
>  Regards,
>  Arnout
>
>
> >  Now I can't get
> > past building ti-gfx.  I have a local source directory for the kernel,
> since we
> > had to add our own drivers for some proprietary devices on the design
> based on
> > beaglebone X15.  I also use the local source directory to generate
> > linux-headers.  We based the kernel from TI's SDK.  I checked the kernel
> config,
> > fbdev omap is selected.  But I get the following error:
> >
> >  CC [M]
> >
>  /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-gfx-5_01_01_02/GFX_Linux_KM/services4/srvkm/common/pvrsrv.o
> >   CC [M]
> >
>  /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-gfx-5_01_01_02/GFX_Linux_KM/services4/srvkm/common/handle.o
> >
> /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-gfx-5_01_01_02/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_linux.c:133:10:
> > fatal error: omapfb/omapfb.h: No such file or directory
> >   133 | #include <omapfb/omapfb.h>
> >       |          ^~~~~~~~~~~~~~~~~
> >
> >
> > The file "omapfb.h" is in drivers/video/fbdev/omap2/omapfb, but for some
> reason
> > the ti-gfx package does not find it.  We are using
> buildroot-2020-20.02.12.
> >
> > I did not see this error in the buildroot issues, I am wondering why it
> is
> > causing problems.  My only guess is that it may have something to do
> with the
> > fact that I have a local kernel source directory.
>
> [snip]
>


-- 
Patricia A. Holden

[-- Attachment #1.2: Type: text/html, Size: 2643 bytes --]

[-- Attachment #2: Type: text/plain, Size: 145 bytes --]

_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Re: [Buildroot] Question about pkg-config pc files

[Patricia Holden]

[-- Attachment #1.1: Type: text/plain, Size: 2897 bytes --]

I switched from ti-gfx to ti-sgx, now I get another error:

/home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-sgx-km-4519ed3b83d1d72207ddc2874c7eb5e5a7f20d8d/eurasia_km/eurasiacon/binary_omap_linux_xorg_release/target_armhf/kbuild/services4/srvkm/env/linux/mm.c:69:10:
fatal error: linux/dma-direct.h: No such file or directory
   69 | #include <linux/dma-direct.h>
      |          ^~~~~~~~~~~~~~~~~~~~


I checked linux-headers and only see "include/linux/dma-direction.h", no
"include/linux/dma-direct.h".

Not sure if this is the same file this package is looking for, but just
renamed.  Looking through config for the kernel to see if I missed
something.



On Thu, Jul 22, 2021 at 3:52 PM Patricia Holden <pholden@nklabs.com> wrote:

> Thanks, I will try that!
>
> On Thu, Jul 22, 2021 at 3:40 PM Arnout Vandecappelle <arnout@mind.be>
> wrote:
>
>>
>>
>> On 22/07/2021 19:36, Patricia Holden wrote:
>> > Hi Thomas,
>> >
>> > The saga continues.  I found that multimedia is not added
>> > because BR2_PACKAGE_QT5_GL_AVAILABLE is not set.  In order to configure
>> QT
>> > OpenGL, I enabled ti-gfx since our board is a beaglebone-x15.
>>
>>  Not that I've ever used this board, but AFAIK for AM57xx you should use
>> ti-sgx,
>> not ti-gfx.
>>
>>  Regards,
>>  Arnout
>>
>>
>> >  Now I can't get
>> > past building ti-gfx.  I have a local source directory for the kernel,
>> since we
>> > had to add our own drivers for some proprietary devices on the design
>> based on
>> > beaglebone X15.  I also use the local source directory to generate
>> > linux-headers.  We based the kernel from TI's SDK.  I checked the
>> kernel config,
>> > fbdev omap is selected.  But I get the following error:
>> >
>> >  CC [M]
>> >
>>  /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-gfx-5_01_01_02/GFX_Linux_KM/services4/srvkm/common/pvrsrv.o
>> >   CC [M]
>> >
>>  /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-gfx-5_01_01_02/GFX_Linux_KM/services4/srvkm/common/handle.o
>> >
>> /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-gfx-5_01_01_02/GFX_Linux_KM/services4/3rdparty/dc_omapfb3_linux/omaplfb_linux.c:133:10:
>> > fatal error: omapfb/omapfb.h: No such file or directory
>> >   133 | #include <omapfb/omapfb.h>
>> >       |          ^~~~~~~~~~~~~~~~~
>> >
>> >
>> > The file "omapfb.h" is in drivers/video/fbdev/omap2/omapfb, but for
>> some reason
>> > the ti-gfx package does not find it.  We are using
>> buildroot-2020-20.02.12.
>> >
>> > I did not see this error in the buildroot issues, I am wondering why it
>> is
>> > causing problems.  My only guess is that it may have something to do
>> with the
>> > fact that I have a local kernel source directory.
>>
>> [snip]
>>
>
>
> --
> Patricia A. Holden
>


-- 
Patricia A. Holden

[-- Attachment #1.2: Type: text/html, Size: 3965 bytes --]

[-- Attachment #2: Type: text/plain, Size: 145 bytes --]

_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Re: [Buildroot] Question about pkg-config pc files

[Baruch Siach]

Hi Patricia,

On Fri, Jul 23 2021, Patricia Holden wrote:
> I switched from ti-gfx to ti-sgx, now I get another error:
>
> /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-sgx-km-4519ed3b83d1d72207ddc2874c7eb5e5a7f20d8d/eurasia_km/eurasiacon/binary_omap_linux_xorg_release/target_armhf/kbuild/services4/srvkm/env/linux/mm.c:69:10:
> fatal error: linux/dma-direct.h: No such file or directory
>    69 | #include <linux/dma-direct.h>
>       |          ^~~~~~~~~~~~~~~~~~~~
>
>
> I checked linux-headers and only see "include/linux/dma-direction.h", no
> "include/linux/dma-direct.h".

The linux-headers package is for userspace API (uapi) headers that are
part of the toolchain. dma-direction.h is for kernel code. The 'kbuild'
part in the path above indicates that you are building a kernel module.

linux/dma-direct.h was introduced in kernel version 4.16 (commit
ea8c64ace866). But ti-sgx-km commit cf7f48cb30a predates this kernel by
few years. So this it probably a TI kernel that carries the header.

The BR2_PACKAGE_TI_SGX_KM help text says this:

          Note: it needs a TI specific kernel to build properly.

baruch

> Not sure if this is the same file this package is looking for, but just
> renamed.  Looking through config for the kernel to see if I missed
> something.

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Re: [Buildroot] Question about pkg-config pc files

[Patricia Holden]

[-- Attachment #1.1: Type: text/plain, Size: 2037 bytes --]

I have a TI specific kernel, I got it directly from a TI SDK.   The
comments in ti-sgx-km Config.in says to use ti-sgx, however, there is no
choice in packages for ti-sgx.  I can only choose "ti-sgx-km" or "ti-gfx".
I guess I can pull ti-sgx & create package for it.  Unless someone else has
a better suggestion.

On Thu, Jul 22, 2021 at 11:39 PM Baruch Siach <baruch@tkos.co.il> wrote:

> Hi Patricia,
>
> On Fri, Jul 23 2021, Patricia Holden wrote:
> > I switched from ti-gfx to ti-sgx, now I get another error:
> >
> >
> /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-sgx-km-4519ed3b83d1d72207ddc2874c7eb5e5a7f20d8d/eurasia_km/eurasiacon/binary_omap_linux_xorg_release/target_armhf/kbuild/services4/srvkm/env/linux/mm.c:69:10:
> > fatal error: linux/dma-direct.h: No such file or directory
> >    69 | #include <linux/dma-direct.h>
> >       |          ^~~~~~~~~~~~~~~~~~~~
> >
> >
> > I checked linux-headers and only see "include/linux/dma-direction.h", no
> > "include/linux/dma-direct.h".
>
> The linux-headers package is for userspace API (uapi) headers that are
> part of the toolchain. dma-direction.h is for kernel code. The 'kbuild'
> part in the path above indicates that you are building a kernel module.
>
> linux/dma-direct.h was introduced in kernel version 4.16 (commit
> ea8c64ace866). But ti-sgx-km commit cf7f48cb30a predates this kernel by
> few years. So this it probably a TI kernel that carries the header.
>
> The BR2_PACKAGE_TI_SGX_KM help text says this:
>
>           Note: it needs a TI specific kernel to build properly.
>
> baruch
>
> > Not sure if this is the same file this package is looking for, but just
> > renamed.  Looking through config for the kernel to see if I missed
> > something.
>
> --
>                                                      ~. .~   Tk Open
> Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
>    - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
>


-- 
Patricia A. Holden

[-- Attachment #1.2: Type: text/html, Size: 2797 bytes --]

[-- Attachment #2: Type: text/plain, Size: 145 bytes --]

_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Re: [Buildroot] Question about pkg-config pc files

[Arnout Vandecappelle]

On 23/07/2021 20:52, Patricia Holden wrote:
> I have a TI specific kernel, I got it directly from a TI SDK.   The comments in
> ti-sgx-km Config.in says to use ti-sgx, however, there is no choice in packages
> for ti-sgx.  I can only choose "ti-sgx-km" or "ti-gfx".  I guess I can pull
> ti-sgx & create package for it.  Unless someone else has a better suggestion.

 ti-sgx consists of two separate packages: ti-sgx-km which is the kernel module,
and ti-sgx-um which is the userspace library.

> 
> On Thu, Jul 22, 2021 at 11:39 PM Baruch Siach <baruch@tkos.co.il
> <mailto:baruch@tkos.co.il>> wrote:
> 
>     Hi Patricia,
> 
>     On Fri, Jul 23 2021, Patricia Holden wrote:
>     > I switched from ti-gfx to ti-sgx, now I get another error:
>     >
>     >
>     /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-sgx-km-4519ed3b83d1d72207ddc2874c7eb5e5a7f20d8d/eurasia_km/eurasiacon/binary_omap_linux_xorg_release/target_armhf/kbuild/services4/srvkm/env/linux/mm.c:69:10:
>     > fatal error: linux/dma-direct.h: No such file or directory
>     >    69 | #include <linux/dma-direct.h>
>     >       |          ^~~~~~~~~~~~~~~~~~~~
>     >
>     >
>     > I checked linux-headers and only see "include/linux/dma-direction.h", no
>     > "include/linux/dma-direct.h".
> 
>     The linux-headers package is for userspace API (uapi) headers that are
>     part of the toolchain. dma-direction.h is for kernel code. The 'kbuild'
>     part in the path above indicates that you are building a kernel module.
> 
>     linux/dma-direct.h was introduced in kernel version 4.16 (commit
>     ea8c64ace866). But ti-sgx-km commit cf7f48cb30a predates this kernel by
>     few years. So this it probably a TI kernel that carries the header.

 More precisely, the current Buildroot master version corresponds to TI SDK
06.01.00.08, so you'll probably need a kernel from the same SDK version.

 Regards,
 Arnout

> 
>     The BR2_PACKAGE_TI_SGX_KM help text says this:
> 
>               Note: it needs a TI specific kernel to build properly.
> 
>     baruch
> 
>     > Not sure if this is the same file this package is looking for, but just
>     > renamed.  Looking through config for the kernel to see if I missed
>     > something.
> 
>     -- 
>                                                          ~. .~   Tk Open Systems
>     =}------------------------------------------------ooO--U--Ooo------------{=
>        - baruch@tkos.co.il <mailto:baruch@tkos.co.il> - tel: +972.52.368.4656,
>     http://www.tkos.co.il <http://www.tkos.co.il> -
> 
> 
> 
> -- 
> Patricia A. Holden
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Re: [Buildroot] Question about pkg-config pc files

[Patricia Holden]

[-- Attachment #1.1: Type: text/plain, Size: 3484 bytes --]

 > More precisely, the current Buildroot master version corresponds to TI
SDK
> 06.01.00.08, so you'll probably need a kernel from the same SDK version.

 > Regards,
 > Arnout
Arnout, thanks for the help.  I am at kernel version 4.9.147-ti-rt-121,
from an older TI-SDK for the Beaglebone X15.  Multiple people have added
quite a few drivers and configs to this code, it's locally stored for
Buildroot to use.  We have already tested quite a bit of our product
with what we have.  I really can't migrate to a new kernel at this point.
This whole exercise is all to get QT5-OpenGL enabled.  Any ideas on what
else I can do?

Thanks!

On Fri, Jul 23, 2021 at 4:57 PM Arnout Vandecappelle <arnout@mind.be> wrote:

>
>
> On 23/07/2021 20:52, Patricia Holden wrote:
> > I have a TI specific kernel, I got it directly from a TI SDK.   The
> comments in
> > ti-sgx-km Config.in says to use ti-sgx, however, there is no choice in
> packages
> > for ti-sgx.  I can only choose "ti-sgx-km" or "ti-gfx".  I guess I can
> pull
> > ti-sgx & create package for it.  Unless someone else has a better
> suggestion.
>
>  ti-sgx consists of two separate packages: ti-sgx-km which is the kernel
> module,
> and ti-sgx-um which is the userspace library.
>
> >
> > On Thu, Jul 22, 2021 at 11:39 PM Baruch Siach <baruch@tkos.co.il
> > <mailto:baruch@tkos.co.il>> wrote:
> >
> >     Hi Patricia,
> >
> >     On Fri, Jul 23 2021, Patricia Holden wrote:
> >     > I switched from ti-gfx to ti-sgx, now I get another error:
> >     >
> >     >
> >
>  /home/patricaholden/williamson/build07062021/Pro3-Linux/buildroot-2020.02/output/build/ti-sgx-km-4519ed3b83d1d72207ddc2874c7eb5e5a7f20d8d/eurasia_km/eurasiacon/binary_omap_linux_xorg_release/target_armhf/kbuild/services4/srvkm/env/linux/mm.c:69:10:
> >     > fatal error: linux/dma-direct.h: No such file or directory
> >     >    69 | #include <linux/dma-direct.h>
> >     >       |          ^~~~~~~~~~~~~~~~~~~~
> >     >
> >     >
> >     > I checked linux-headers and only see
> "include/linux/dma-direction.h", no
> >     > "include/linux/dma-direct.h".
> >
> >     The linux-headers package is for userspace API (uapi) headers that
> are
> >     part of the toolchain. dma-direction.h is for kernel code. The
> 'kbuild'
> >     part in the path above indicates that you are building a kernel
> module.
> >
> >     linux/dma-direct.h was introduced in kernel version 4.16 (commit
> >     ea8c64ace866). But ti-sgx-km commit cf7f48cb30a predates this kernel
> by
> >     few years. So this it probably a TI kernel that carries the header.
>
>  More precisely, the current Buildroot master version corresponds to TI SDK
> 06.01.00.08, so you'll probably need a kernel from the same SDK version.
>
>  Regards,
>  Arnout
>
> >
> >     The BR2_PACKAGE_TI_SGX_KM help text says this:
> >
> >               Note: it needs a TI specific kernel to build properly.
> >
> >     baruch
> >
> >     > Not sure if this is the same file this package is looking for, but
> just
> >     > renamed.  Looking through config for the kernel to see if I missed
> >     > something.
> >
> >     --
> >                                                          ~. .~   Tk Open
> Systems
> >
>  =}------------------------------------------------ooO--U--Ooo------------{=
> >        - baruch@tkos.co.il <mailto:baruch@tkos.co.il> - tel:
> +972.52.368.4656,
> >     http://www.tkos.co.il <http://www.tkos.co.il> -
> >
> >
> >
> > --
> > Patricia A. Holden
>


-- 
Patricia A. Holden

[-- Attachment #1.2: Type: text/html, Size: 5029 bytes --]

[-- Attachment #2: Type: text/plain, Size: 145 bytes --]

_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot