Re: [yocto] [PATCHv3 0/8][eclipse-poky] Add target profile quick switch
Hi Jessica, Zhang, Jessica wrote, On 26.06.2013 00:07: Hi Timo, Now it look much better and also with these patch set, I don't see the multiple selection of radio buttons, so I don't think we need the last patch of the series which enable the debugging. The only thing that's not clear to me is, after define the project specific settings which is different from profiles. From the menu bar, the project menu, when I toggled between profile and project specific setting, by checking into the project property window, I can see the correct setting is showing. But if I stayed inside the project property window, if I uncheck my project specific setting box, click on ok. Then I reopen my project property window, recheck project specific setting box, I noticed that instead of restoring my project specific settings, it copied the prior profile setting. Which is different behavior than other cases that it always able to restore the defined project specific settings once I defined it. So is this a bug or intentional behavior? That is a bug and it's fixed by the patch "plugin/sdk.ide: Pre-populate project specific profile form". With this patch this patch series needs some small adjustments (in the refactoring part). Once it is merged, I'll rework this series and also remove the debugging patch. Except for this case, everything else looks great to me. Cheers, Jessica -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Timo Mueller Sent: Tuesday, June 25, 2013 8:34 AM To: yocto@yoctoproject.org Cc: Timo Mueller Subject: [yocto] [PATCHv3 0/8][eclipse-poky] Add target profile quick switch From: Timo Mueller Hi, in conclusion to the previous discussion, we've agreed that the quick switch menu will enable the user to select only configured profiles. An unconfigured project specific profile will be shown as a greyed out option in the menu. There also has been a bug where the projects specific settings and one profile could be marked as selected at the same time. I could only reproduce by naming the target profile "project-specific" which collides with the radioParamter used for the menu. This case is resolved in this patch set. I've additionally merged the two places where the state of the menu was set so have one consistent place. In any case, I've added one patch marked as TESTING to enable tracing in the relevant components. In case the problem prevails, please enable the tracing for th org.yocto.sdk.ide plugin and send me the output. Changes in v3: - Only grey out project specific profile if not configured. - Fix Bug where multiple menu item could be selected at the same time Changes in v2: Handle error when project specific profile is not configure more gracefully. Instead of showing an error message the button is now greyed out. Patches 01..07 contain the implementation with the greyed out menu button. After playing around with the two options discussed in the first patch series, I started to prefer inserting a different button in the menu allowing the user to quickly navigate to the project preferences instead of just greying it out. I've added this in the last patch of the series, so you can compare yourself. From original cover letter if a user wants to change the used target profile of a project he currently has to open the project preferences. This can be tedious if he has to switch the profile often. This is a small addition which allows the user to quickly switch the used target profile of a project. Instead of having to open the project preferences the user can select the project in the navigator and then choose the desired target profile from a drop-down menu in the toolbar or from the project menu. 01: Small i18n fix 02..04: Refactoring the project specific utils 05..06: Introduce the target profile toolbar switch 07: Adds the target profile switch to the project menu 08: TESTING: Enalbe tracing to pin down the multi-select problem Best regards, Timo Timo Mueller (8): plugins/sdk.ide: Use an internationalized dialog title plugins/sdk.ide: Extract project specific util methods plugins/sdk.ide: Move project specific util methods plugins/sdk.ide: Remove project context from method names plugins/sdk.ide: Add command to switch the target profile plugins/sdk.ide: Add profile switch menu to the toolbar plugins/sdk.ide: Add profile switch menu to the project menu TESTING: add tracing for radio menu plugins/org.yocto.sdk.ide/.options | 2 + .../OSGI-INF/l10n/bundle.properties| 4 + plugins/org.yocto.sdk.ide/plugin.xml | 100 - .../sdk/ide/ProjectSpecificContributionItem.java | 69 ++ .../sdk/ide/TargetProfileContributionItem.java | 139 .../org/yocto/sdk/ide/YoctoSDKMessages.properties | 4 + .../src/org/yocto/sdk/ide/YoctoUISetting.java | 3 +- .../sdk/ide/actions/ProfileSwitchHand
Re: [yocto] [meta-intel][PATCH] intel-gpu-tools: add new package
On 25 June 2013 23:23, Tom Zanussi wrote: > On Tue, 2013-06-25 at 17:43 +0100, Ross Burton wrote: >> This package contains numerous useful tools for working with Intel GPUs. >> Add a >> patch to install intel_panel_fitter as it's genuinely useful and not just a >> debugging tool. >> >> Signed-off-by: Ross Burton > > Nice addition. The debugging tools will be useful, but my new 10" HDMI touchscreen is and always overscans about 1/2 inch without an option to turn it off. The panel fitter tool is the only way of getting the Intel driver to compensate for that. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Installing .deb file in Build
Ok I did remove the stuff and I modified as you mentioned... I have two
aims here,
1. To start the bootstraper at the start of the boot, it means it has to be
in every runlevel and I am successfull in that.
2. To install a /opt directory which I am faling at..
I don't have any install errors but please tell me why the /opt directory
no more exists in the rootfs
S*UMMARY = "Bootstrapper from Skidata"*
*DESCRIPTION = "For the moment it just installs the .deb file"*
*LICENSE = "CLOSED"*
*
*
*SRC_URI[md5sum] = "7835334732d1704765e52168994b09a6"*
*SRC_URI[sha256sum] =
"11bda24a487da08ef6d3133cc0bf55862e6ae75891c7d08433341f2f3a0dc740"*
*
*
*
*
*SRC_URI =
"file:///home/damarla/openYocto/downloads/skidata-bootstraploader-1.0.0.14.deb"
*
*
*
*inherit bin_package pkgconfig update-rc.d*
*
*
*INITSCRIPT_PACKAGES = "${PN}"*
*INITSCRIPT_NAME_${PN} = "bootstraploader"*
*INITSCRIPT_PARAMS_${PN} = "defaults 85"*
*
*
*do_install() {*
*
*
* install -d ${D}${sysconfdir}/init.d/*
* install -m 0755 ${WORKDIR}/etc/init.d/bootstraploader
${D}${sysconfdir}/init.d/bootstraploader*
*
*
* install -d ${D}/opt/skidata/bootstraploader/*
* echo -e ${D}*
* for f in ${WORKDIR}/opt/skidata/bootstraploader/*.pm*
* do*
* install -m 0755 $f ${D}/opt/skidata/bootstraploader/*
* done*
*
*
* for ff in ${WORKDIR}/opt/skidata/bootstraploader/*.sh*
* do*
* install -m 0755 ${ff} ${D}/opt/skidata/bootstraploader/*
* done*
}
*
*
*FILES_${PN} = "${base_libdir}/udev ${systemd_unitdir}"*
*FILES_${PN} += "${sysconfdir}/init.d/bootstraploader"*
*FILES_${PN} += "${D}/opt/skidata/bootstraploader/*.sh
${D}/opt/skidata/bootstraploader/*.pm"*
*
*
Any reasons why its failing is deeply appreciated
Greets,
Satya
On Tue, Jun 25, 2013 at 5:16 PM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:
> On Tuesday 25 June 2013 15:20:19 DAMARLA Satya Swaroop wrote:
> > I am trying to install .deb file and the recipe is as follows... may I
> ask
> > you what is the mistake that is not allowing it to build it into the
> > rootfilesystem
> >
> > *UMMARY = "Bootstrapper from Skidata"*
> > *DESCRIPTION = "For the moment it just installs the .deb file"*
> > *LICENSE = "CLOSED"*
> > *
> > *
> > *SRC_URI[md5sum] = "7835334732d1704765e52168994b09a6"*
> > *SRC_URI[sha256sum] =
> > "11bda24a487da08ef6d3133cc0bf55862e6ae75891c7d08433341f2f3a0dc740"*
> > *
> > *
> > *
> > *
> > *SRC_URI =
> >
> "file:///home/damarla/openYocto/downloads/skidata-bootstraploader-1.0.0.14.d
> > eb" *
> > *
> > *
> > *inherit bin_package*
> > *
> > *
> > *INITSCRIPT_PACKAGES = "${PN}-bsd"*
> > *INITSCRIPT_NAME_${PN}-bsp = "bootstraploader"*
> > *INITSCRIPT_PARAMS_${PN}-bsp = "defaults 90"*
>
> You have a mismatch here, "bsp" in the last two lines and "bsd" everywhere
> else.
>
> > *PACKAGES =+ "${PN} ${PN}-bsd"*
> > *
> > *
> > *FILES_${PN}-bsd = "${sysconfdir}/init.d/bootstraploader"*
> > *FILES_${PN} = "${D}/usr/skidata/bootstraploader/*.sh
> > ${D}/usr/skidata/bootstraploader/*.pm"*
>
> You should not include ${D} in FILES values. Because of the invalid path
> the
> desired files are not being picked up.
>
> The reason you're likely getting an error at do_rootfs is that because of
> the
> above, the package is empty and therefore is not produced, thus it can't be
> found when it comes to installing it into the image.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Installing .deb file in Build
On Wed, Jun 26, 2013 at 11:16 AM, DAMARLA Satya Swaroop
wrote:
> Ok I did remove the stuff and I modified as you mentioned... I have two aims
> here,
>
> 1. To start the bootstraper at the start of the boot, it means it has to be
> in every runlevel and I am successfull in that.
>
> 2. To install a /opt directory which I am faling at..
>
> I don't have any install errors but please tell me why the /opt directory no
> more exists in the rootfs
>
> SUMMARY = "Bootstrapper from Skidata"
> DESCRIPTION = "For the moment it just installs the .deb file"
> LICENSE = "CLOSED"
>
> SRC_URI[md5sum] = "7835334732d1704765e52168994b09a6"
> SRC_URI[sha256sum] =
> "11bda24a487da08ef6d3133cc0bf55862e6ae75891c7d08433341f2f3a0dc740"
>
>
> SRC_URI =
> "file:///home/damarla/openYocto/downloads/skidata-bootstraploader-1.0.0.14.deb"
>
> inherit bin_package pkgconfig update-rc.d
>
> INITSCRIPT_PACKAGES = "${PN}"
> INITSCRIPT_NAME_${PN} = "bootstraploader"
> INITSCRIPT_PARAMS_${PN} = "defaults 85"
>
> do_install() {
>
> install -d ${D}${sysconfdir}/init.d/
> install -m 0755 ${WORKDIR}/etc/init.d/bootstraploader
> ${D}${sysconfdir}/init.d/bootstraploader
>
> install -d ${D}/opt/skidata/bootstraploader/
> echo -e ${D}
> for f in ${WORKDIR}/opt/skidata/bootstraploader/*.pm
> do
> install -m 0755 $f ${D}/opt/skidata/bootstraploader/
> done
>
> for ff in ${WORKDIR}/opt/skidata/bootstraploader/*.sh
> do
> install -m 0755 ${ff} ${D}/opt/skidata/bootstraploader/
> done
>
>
> }
>
> FILES_${PN} = "${base_libdir}/udev ${systemd_unitdir}"
> FILES_${PN} += "${sysconfdir}/init.d/bootstraploader"
> FILES_${PN} += "${D}/opt/skidata/bootstraploader/*.sh
> ${D}/opt/skidata/bootstraploader/*.pm"
>
> Any reasons why its failing is deeply appreciated
You still have ${D} in FILES_${PN}, so the files in /opt is not
included in the package.
Cheers,
Erik Botö
>
> Greets,
> Satya
>
>
> On Tue, Jun 25, 2013 at 5:16 PM, Paul Eggleton
> wrote:
>>
>> On Tuesday 25 June 2013 15:20:19 DAMARLA Satya Swaroop wrote:
>> > I am trying to install .deb file and the recipe is as follows... may I
>> > ask
>> > you what is the mistake that is not allowing it to build it into the
>> > rootfilesystem
>> >
>> > *UMMARY = "Bootstrapper from Skidata"*
>> > *DESCRIPTION = "For the moment it just installs the .deb file"*
>> > *LICENSE = "CLOSED"*
>> > *
>> > *
>> > *SRC_URI[md5sum] = "7835334732d1704765e52168994b09a6"*
>> > *SRC_URI[sha256sum] =
>> > "11bda24a487da08ef6d3133cc0bf55862e6ae75891c7d08433341f2f3a0dc740"*
>> > *
>> > *
>> > *
>> > *
>> > *SRC_URI =
>> >
>> > "file:///home/damarla/openYocto/downloads/skidata-bootstraploader-1.0.0.14.d
>> > eb" *
>> > *
>> > *
>> > *inherit bin_package*
>> > *
>> > *
>> > *INITSCRIPT_PACKAGES = "${PN}-bsd"*
>> > *INITSCRIPT_NAME_${PN}-bsp = "bootstraploader"*
>> > *INITSCRIPT_PARAMS_${PN}-bsp = "defaults 90"*
>>
>> You have a mismatch here, "bsp" in the last two lines and "bsd" everywhere
>> else.
>>
>> > *PACKAGES =+ "${PN} ${PN}-bsd"*
>> > *
>> > *
>> > *FILES_${PN}-bsd = "${sysconfdir}/init.d/bootstraploader"*
>> > *FILES_${PN} = "${D}/usr/skidata/bootstraploader/*.sh
>> > ${D}/usr/skidata/bootstraploader/*.pm"*
>>
>> You should not include ${D} in FILES values. Because of the invalid path
>> the
>> desired files are not being picked up.
>>
>> The reason you're likely getting an error at do_rootfs is that because of
>> the
>> above, the package is empty and therefore is not produced, thus it can't
>> be
>> found when it comes to installing it into the image.
>>
>> Cheers,
>> Paul
>>
>> --
>>
>> Paul Eggleton
>> Intel Open Source Technology Centre
>
>
>
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Installing .deb file in Build
Yes, I think something wrong happened to my eyes and now its working ..
Cheers,
Satya
On Wed, Jun 26, 2013 at 1:16 PM, Erik Botö wrote:
> On Wed, Jun 26, 2013 at 11:16 AM, DAMARLA Satya Swaroop
> wrote:
> > Ok I did remove the stuff and I modified as you mentioned... I have two
> aims
> > here,
> >
> > 1. To start the bootstraper at the start of the boot, it means it has to
> be
> > in every runlevel and I am successfull in that.
> >
> > 2. To install a /opt directory which I am faling at..
> >
> > I don't have any install errors but please tell me why the /opt
> directory no
> > more exists in the rootfs
> >
> > SUMMARY = "Bootstrapper from Skidata"
> > DESCRIPTION = "For the moment it just installs the .deb file"
> > LICENSE = "CLOSED"
> >
> > SRC_URI[md5sum] = "7835334732d1704765e52168994b09a6"
> > SRC_URI[sha256sum] =
> > "11bda24a487da08ef6d3133cc0bf55862e6ae75891c7d08433341f2f3a0dc740"
> >
> >
> > SRC_URI =
> >
> "file:///home/damarla/openYocto/downloads/skidata-bootstraploader-1.0.0.14.deb"
> >
> > inherit bin_package pkgconfig update-rc.d
> >
> > INITSCRIPT_PACKAGES = "${PN}"
> > INITSCRIPT_NAME_${PN} = "bootstraploader"
> > INITSCRIPT_PARAMS_${PN} = "defaults 85"
> >
> > do_install() {
> >
> > install -d ${D}${sysconfdir}/init.d/
> > install -m 0755 ${WORKDIR}/etc/init.d/bootstraploader
> > ${D}${sysconfdir}/init.d/bootstraploader
> >
> > install -d ${D}/opt/skidata/bootstraploader/
> > echo -e ${D}
> > for f in ${WORKDIR}/opt/skidata/bootstraploader/*.pm
> > do
> > install -m 0755 $f ${D}/opt/skidata/bootstraploader/
> > done
> >
> > for ff in ${WORKDIR}/opt/skidata/bootstraploader/*.sh
> > do
> > install -m 0755 ${ff} ${D}/opt/skidata/bootstraploader/
> > done
> >
> >
> > }
> >
> > FILES_${PN} = "${base_libdir}/udev ${systemd_unitdir}"
> > FILES_${PN} += "${sysconfdir}/init.d/bootstraploader"
> > FILES_${PN} += "${D}/opt/skidata/bootstraploader/*.sh
> > ${D}/opt/skidata/bootstraploader/*.pm"
> >
> > Any reasons why its failing is deeply appreciated
>
> You still have ${D} in FILES_${PN}, so the files in /opt is not
> included in the package.
>
> Cheers,
> Erik Botö
>
> >
> > Greets,
> > Satya
> >
> >
> > On Tue, Jun 25, 2013 at 5:16 PM, Paul Eggleton
> > wrote:
> >>
> >> On Tuesday 25 June 2013 15:20:19 DAMARLA Satya Swaroop wrote:
> >> > I am trying to install .deb file and the recipe is as follows... may I
> >> > ask
> >> > you what is the mistake that is not allowing it to build it into the
> >> > rootfilesystem
> >> >
> >> > *UMMARY = "Bootstrapper from Skidata"*
> >> > *DESCRIPTION = "For the moment it just installs the .deb file"*
> >> > *LICENSE = "CLOSED"*
> >> > *
> >> > *
> >> > *SRC_URI[md5sum] = "7835334732d1704765e52168994b09a6"*
> >> > *SRC_URI[sha256sum] =
> >> > "11bda24a487da08ef6d3133cc0bf55862e6ae75891c7d08433341f2f3a0dc740"*
> >> > *
> >> > *
> >> > *
> >> > *
> >> > *SRC_URI =
> >> >
> >> >
> "file:///home/damarla/openYocto/downloads/skidata-bootstraploader-1.0.0.14.d
> >> > eb" *
> >> > *
> >> > *
> >> > *inherit bin_package*
> >> > *
> >> > *
> >> > *INITSCRIPT_PACKAGES = "${PN}-bsd"*
> >> > *INITSCRIPT_NAME_${PN}-bsp = "bootstraploader"*
> >> > *INITSCRIPT_PARAMS_${PN}-bsp = "defaults 90"*
> >>
> >> You have a mismatch here, "bsp" in the last two lines and "bsd"
> everywhere
> >> else.
> >>
> >> > *PACKAGES =+ "${PN} ${PN}-bsd"*
> >> > *
> >> > *
> >> > *FILES_${PN}-bsd = "${sysconfdir}/init.d/bootstraploader"*
> >> > *FILES_${PN} = "${D}/usr/skidata/bootstraploader/*.sh
> >> > ${D}/usr/skidata/bootstraploader/*.pm"*
> >>
> >> You should not include ${D} in FILES values. Because of the invalid path
> >> the
> >> desired files are not being picked up.
> >>
> >> The reason you're likely getting an error at do_rootfs is that because
> of
> >> the
> >> above, the package is empty and therefore is not produced, thus it can't
> >> be
> >> found when it comes to installing it into the image.
> >>
> >> Cheers,
> >> Paul
> >>
> >> --
> >>
> >> Paul Eggleton
> >> Intel Open Source Technology Centre
> >
> >
> >
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] run commands after installation
Hi, I want to create a user after adding the snmp recipe. The command to do that is: net-snmp-config --create-snmpv3-user -a "my_password" myuser What's the best way to do it? I have tried from do_install_append and also from ROOTFS_POSTPROCESS_COMMAND but no luck so far. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] FW: cannot bitbake/build.compile tcf-agent for use with fsl-image-gui-sdk
On 25 June 2013 09:58, Thanassis Silis wrote: > I have rebuilt an image with "IMAGE_INSTALL_append = " openssh" in my > local.conf > which led to the generation of the image with openssh as expected. > > However, the sftp-server executable was never included in the deployed > image. I am wondering why this is. Does it work if you have: IMAGE_INSTALL_append = " openssh openssh-sftp-server" ? ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] NAND Filesystems
Hi Guys, Google doesnot provide a good link but may I ask you where can I search for NAND filesystems that yocto supports for the target Greets, Satya ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] run commands after installation
On 26/06/13 15:32, Katu Txakur wrote: > I want to create a user after adding the snmp recipe. The command to do > that is: > > net-snmp-config --create-snmpv3-user -a "my_password" myuser > > What's the best way to do it? I have tried from do_install_append and > also from ROOTFS_POSTPROCESS_COMMAND but no luck so far. You need a postinst script for that sort of a thing. Tomas -- http://sleepfive.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Strange IPK naming
I have a target machine whose name contains a '-', e.g. MACHINE="xyz-99" When I build packages, the tmp/deploy/ipk directory is munged to be tmp/deploy/ipk/xyz_99 Can someone tell me why this happens (where)? and can I do something about it? It makes it hard to set up the package database (/etc/opkg/base-feeds.conf) automatically in my image. Thanks -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Strange IPK naming
On Wed, Jun 26, 2013 at 10:12:40AM -0600, Gary Thomas wrote: > I have a target machine whose name contains a '-', e.g. MACHINE="xyz-99" > When I build packages, the tmp/deploy/ipk directory is munged to be > tmp/deploy/ipk/xyz_99 > > Can someone tell me why this happens (where)? and can I do something > about it? It makes it hard to set up the package database > (/etc/opkg/base-feeds.conf) > automatically in my image. xyz_99 is MACHINE_ARCH, rpm doesn't like dashes in architectures -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCHv3 0/8][eclipse-poky] Add target profile quick switch
Hi Timo, That patch is merged to eclipse-poky master. Please adjust your patch series and resend. Thanks, Jessica -Original Message- From: Timo Müller [mailto:m...@timomueller.eu] Sent: Wednesday, June 26, 2013 12:03 AM To: Zhang, Jessica Cc: yocto@yoctoproject.org; Timo Mueller Subject: Re: [yocto] [PATCHv3 0/8][eclipse-poky] Add target profile quick switch Hi Jessica, Zhang, Jessica wrote, On 26.06.2013 00:07: > Hi Timo, > > Now it look much better and also with these patch set, I don't see the > multiple selection of radio buttons, so I don't think we need the last > patch of the series which enable the debugging. > > The only thing that's not clear to me is, after define the project > specific settings which is different from profiles. From the menu bar, > the project menu, when I toggled between profile and project specific > setting, by checking into the project property window, I can see the > correct setting is showing. But if I stayed inside the project > property window, if I uncheck my project specific setting box, click > on ok. Then I reopen my project property window, recheck project > specific setting box, I noticed that instead of restoring my project > specific settings, it copied the prior profile setting. > Which is different behavior than other cases that it always able to > restore the defined project specific settings once I defined it. So > is this a bug or intentional behavior? That is a bug and it's fixed by the patch "plugin/sdk.ide: Pre-populate project specific profile form". With this patch this patch series needs some small adjustments (in the refactoring part). Once it is merged, I'll rework this series and also remove the debugging patch. > > Except for this case, everything else looks great to me. > > Cheers, Jessica > > -Original Message- > From: yocto-boun...@yoctoproject.org > [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Timo Mueller > Sent: Tuesday, June 25, 2013 8:34 AM > To: yocto@yoctoproject.org > Cc: Timo Mueller > Subject: [yocto] [PATCHv3 0/8][eclipse-poky] Add target profile quick > switch > > From: Timo Mueller > > Hi, > > in conclusion to the previous discussion, we've agreed that the quick switch > menu will enable the user to select only configured profiles. > An unconfigured project specific profile will be shown as a greyed out option > in the menu. > > There also has been a bug where the projects specific settings and one > profile could be marked as selected at the same time. I could only reproduce > by naming the target profile "project-specific" which collides with the > radioParamter used for the menu. This case is resolved in this patch set. > I've additionally merged the two places where the state of the menu was set > so have one consistent place. > > In any case, I've added one patch marked as TESTING to enable tracing in the > relevant components. In case the problem prevails, please enable the tracing > for th org.yocto.sdk.ide plugin and send me the output. > > Changes in v3: > - Only grey out project specific profile if not configured. > - Fix Bug where multiple menu item could be selected at the same time > > Changes in v2: > Handle error when project specific profile is not configure more gracefully. > Instead of showing an error message the button is now greyed out. > > Patches 01..07 contain the implementation with the greyed out menu button. > > After playing around with the two options discussed in the first patch > series, I started to prefer inserting a different button in the menu allowing > the user to quickly navigate to the project preferences instead of just > greying it out. I've added this in the last patch of the series, so you can > compare yourself. > > From original cover letter > > if a user wants to change the used target profile of a project he currently > has to open the project preferences. This can be tedious if he has to switch > the profile often. > > This is a small addition which allows the user to quickly switch the used > target profile of a project. Instead of having to open the project > preferences the user can select the project in the navigator and then choose > the desired target profile from a drop-down menu in the toolbar or from the > project menu. > > > 01: Small i18n fix > 02..04: Refactoring the project specific utils > 05..06: Introduce the target profile toolbar switch > 07: Adds the target profile switch to the project menu > 08: TESTING: Enalbe tracing to pin down the multi-select problem > > Best regards, > Timo > > Timo Mueller (8): >plugins/sdk.ide: Use an internationalized dialog title >plugins/sdk.ide: Extract project specific util methods >plugins/sdk.ide: Move project specific util methods >plugins/sdk.ide: Remove project context from method names >plugins/sdk.ide: Add command to switch the target profile >plugins/sdk.ide: Add profile switch menu to the toolbar >plugins/sdk.ide: Add profile switch men
Re: [yocto] [PATCH 1/1][eclipse-poky] systemtap: add button to browse to build folder
Hi Adrian,
Without changing ShellSession signature, the statement:
+ this.builddir = builddir;
Is meaningless, also, you should get an eclipse build error for this line.
Thanks,
Jessica
-Original Message-
From: Adrian Dudau [mailto:adrian.du...@enea.com]
Sent: Monday, June 17, 2013 5:38 AM
To: Zhang, Jessica
Cc: yocto@yoctoproject.org; Adrian Dudau
Subject: [PATCH 1/1][eclipse-poky] systemtap: add button to browse to build
folder
[Yocto #4223]
Signed-off-by: Adrian Dudau
---
.../src/org/yocto/remote/utils/ShellSession.java |4 ++-
.../src/org/yocto/sdk/remotetools/Messages.java|1 +
.../sdk/remotetools/actions/SystemtapHandler.java |3 ++-
.../sdk/remotetools/actions/SystemtapModel.java|6 +++--
.../actions/SystemtapSettingDialog.java| 28
.../org/yocto/sdk/remotetools/messages.properties |1 +
6 files changed, 39 insertions(+), 4 deletions(-)
diff --git
a/plugins/org.yocto.remote.utils/src/org/yocto/remote/utils/ShellSession.java
b/plugins/org.yocto.remote.utils/src/org/yocto/remote/utils/ShellSession.java
index 4ac8001..10cdf94 100644
---
a/plugins/org.yocto.remote.utils/src/org/yocto/remote/utils/ShellSession.java
+++ b/plugins/org.yocto.remote.utils/src/org/yocto/remote/utils/ShellSes
+++ sion.java
@@ -46,6 +46,7 @@ public class ShellSession {
private String shellPath = null;
private final String initCmd;
private final File root;
+ private final File builddir;
private OutputStreamWriter out;
@@ -70,6 +71,7 @@ public class ShellSession {
public ShellSession(int shellType, File root, String initCmd,
OutputStream out) throws IOException {
this.root = root;
+ this.builddir = builddir;
this.initCmd = initCmd;
if (out == null) {
this.out = new OutputStreamWriter(null); @@ -93,7 +95,7
@@ public class ShellSession {
}
if (initCmd != null) {
- execute("source " + initCmd);
+ execute("source " + initCmd + " " +
builddir.getAbsolutePath());
}
}
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/Messages.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/Messages.java
index 66ba62b..cbf2b05 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/Messages.java
+++ b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/Me
+++ ssages.java
@@ -40,6 +40,7 @@ public class Messages extends NLS {
public static String TerminalViewer_text;
//public static String Systemtap_KO_Text;
public static String Metadata_Location;
+ public static String Builddir_Location;
public static String User_ID;
public static String Remote_Host;
public static String Systemtap_Script; diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapHandler.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapHandler.java
index 9d27e5a..9f45d05 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapHandler.java
+++ b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/ac
+++ tions/SystemtapHandler.java
@@ -34,6 +34,7 @@ public class SystemtapHandler extends AbstractHandler {
);
String metadata_location =
((SystemtapSettingDialog)setting).getMetadataLocation();
+ String builddir_location =
+((SystemtapSettingDialog)setting).getBuilddirLocation();
String remote_host =
((SystemtapSettingDialog)setting).getRemoteHost();
String user_id = ((SystemtapSettingDialog)setting).getUserID();
String systemtap_script =
((SystemtapSettingDialog)setting).getSystemtapScript();
@@ -41,7 +42,7 @@ public class SystemtapHandler extends AbstractHandler {
if(setting.open() == BaseSettingDialog.OK) {
IProgressService progressService =
PlatformUI.getWorkbench().getProgressService();
- SystemtapModel op = new
SystemtapModel(metadata_location,remote_host, user_id, systemtap_script,
+ SystemtapModel op = new
SystemtapModel(metadata_location,
+builddir_location, remote_host, user_id, systemtap_script,
systemtap_args,window.getShell().getDisplay());
try {
progressService.busyCursorWhile(op);
diff --git
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapModel.java
b/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/SystemtapModel.java
index f443e00..bb2fa2d 100644
---
a/plugins/org.yocto.sdk.remotetools/src/org/yocto/sdk/remotetools/actions/Sy
[yocto] Using meta-fsl-arm with 'danny'
I'm trying to get core-image-minimal to build using meta-fsl-arm / meta-fsl-arm-extras under 'danny' for the 'wandboard-dual' machine. However, I can't find a tag/branch that works with 'danny'. Specifically, when I use the 'danny' branch there is a udev_173.bbappend in meta-fsl-arm, but 'danny' only supports udev_164. I also find a similar problem with meta-fsl-arm-extras. I must be missing something here... Chris Tapp opensou...@keylevel.com www.keylevel.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] eglibc (would be 2.18) recipes
Hi All I have put together eglibc recipes for upcoming 2.18 release and pushed to a contrib tree here http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.18 They built angstrom/systemd-images fine and booted OK on all supported qemu machines on OE-Core Please test them out in your configurations and machines and provide feedback, lets weed out the issue early Thanks -Khem ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Using meta-fsl-arm with 'danny'
On Wed, Jun 26, 2013 at 1:59 PM, Chris Tapp wrote: > I'm trying to get core-image-minimal to build using meta-fsl-arm / > meta-fsl-arm-extras under 'danny' for the 'wandboard-dual' machine. > > However, I can't find a tag/branch that works with 'danny'. Specifically, > when I use the 'danny' branch there is a udev_173.bbappend in meta-fsl-arm, > but 'danny' only supports udev_164. Is this perhaps what you are hitting? from the meta-fsl-arm danny branch: http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/README?h=danny To avoid the meta-oe dependency add to local.conf: BBMASK = "udev_.*\.bbappend$" -b > > I also find a similar problem with meta-fsl-arm-extras. > > I must be missing something here... > > Chris Tapp > > opensou...@keylevel.com > www.keylevel.com > > > > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- Elizabeth Flanagan Yocto Project Build and Release ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Using meta-fsl-arm with 'danny'
On 26 Jun 2013, at 22:17, Flanagan, Elizabeth wrote: > On Wed, Jun 26, 2013 at 1:59 PM, Chris Tapp wrote: >> I'm trying to get core-image-minimal to build using meta-fsl-arm / >> meta-fsl-arm-extras under 'danny' for the 'wandboard-dual' machine. >> >> However, I can't find a tag/branch that works with 'danny'. Specifically, >> when I use the 'danny' branch there is a udev_173.bbappend in meta-fsl-arm, >> but 'danny' only supports udev_164. > > > Is this perhaps what you are hitting? > > from the meta-fsl-arm danny branch: > > http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/README?h=danny > > To avoid the meta-oe dependency add to local.conf: > > BBMASK = "udev_.*\.bbappend$" Thanks, that's it. Not sure how I missed that one ! > -b > >> >> I also find a similar problem with meta-fsl-arm-extras. >> >> I must be missing something here... >> >> Chris Tapp >> >> opensou...@keylevel.com >> www.keylevel.com >> >> >> >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > > > > -- > Elizabeth Flanagan > Yocto Project > Build and Release Chris Tapp opensou...@keylevel.com www.keylevel.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] eglibc (would be 2.18) recipes
On Wed, Jun 26, 2013 at 6:06 PM, Khem Raj wrote: > Hi All > > I have put together eglibc recipes for upcoming 2.18 release and pushed to a > contrib tree here > > http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.18 > > They built angstrom/systemd-images fine and booted OK on all supported qemu > machines > on OE-Core > > Please test them out in your configurations and machines and provide > feedback, lets weed out > the issue early Could you also make a tree based on poky? -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://projetos.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] eglibc (would be 2.18) recipes
On 06/26/2013 06:46 PM, Otavio Salvador wrote: > On Wed, Jun 26, 2013 at 6:06 PM, Khem Raj wrote: >> Hi All >> >> I have put together eglibc recipes for upcoming 2.18 release and pushed to a >> contrib tree here >> >> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.18 >> >> They built angstrom/systemd-images fine and booted OK on all supported qemu >> machines >> on OE-Core >> >> Please test them out in your configurations and machines and provide >> feedback, lets weed out >> the issue early > > Could you also make a tree based on poky? the patches should apply on top of poky as it is. > > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.brhttp://projetos.ossystems.com.br > Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Kernel patch is unpacked but not applied
I am building a custom Linux kernel under poky-dylan and I am having an issue
with patches being unpacked but not applied. I have two layers that have a
bbappend file for the kernel. Generally, this is what each bbappend file looks
like:
#First .bbappend
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_mach1 = "mach1"
COMPATIBLE_MACHINE_mach2 = "mach2"
SRC_URI_append_mach2 = " file://${MACHINE}/${KBRANCH}/0001-blah.patch \
file://${MACHINE}/${KBRANCH}/0002-blah.patch \
"
# Increment the recipe revision
PRINC := "${@int(PRINC) + 1}"
# Second .bbappend
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_mach1 = "mach1"
COMPATIBLE_MACHINE_mach2 = "mach2"
SRC_URI_append_mach2 = " file://${MACHINE}/${KBRANCH}/0003-blah.patch \
file://${MACHINE}/${KBRANCH}/0004-blah.patch \
"
# Increment the recipe revision
PRINC := "${@int(PRINC) + 1}"
All of the patch files are properly unpacked, but the last two patches are not
being applied. If I open the devshell for the kernel (bitbake -c devshell
linux-yocto-custom) I can see in the git log that the first patch set was
applied. The second patch set exists but is not applied. If I call "guilt
push" repeatedly from the devshell, the patches from the second set are cleanly
applied. My guess is that something doesn't like the second SRC_URI_append
call. Any ideas on how to fix it?
Thanks,
Bryan
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel patch is unpacked but not applied
On 13-06-26 11:08 PM, Bryan Evenson wrote:
I am building a custom Linux kernel under poky-dylan and I am having an issue
with patches being unpacked but not applied. I have two layers that have a
bbappend file for the kernel. Generally, this is what each bbappend file looks
like:
#First .bbappend
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_mach1 = "mach1"
COMPATIBLE_MACHINE_mach2 = "mach2"
SRC_URI_append_mach2 = " file://${MACHINE}/${KBRANCH}/0001-blah.patch \
file://${MACHINE}/${KBRANCH}/0002-blah.patch \
"
# Increment the recipe revision
PRINC := "${@int(PRINC) + 1}"
# Second .bbappend
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_mach1 = "mach1"
COMPATIBLE_MACHINE_mach2 = "mach2"
SRC_URI_append_mach2 = " file://${MACHINE}/${KBRANCH}/0003-blah.patch \
file://${MACHINE}/${KBRANCH}/0004-blah.patch \
"
# Increment the recipe revision
PRINC := "${@int(PRINC) + 1}"
All of the patch files are properly unpacked, but the last two patches are not being
applied. If I open the devshell for the kernel (bitbake -c devshell linux-yocto-custom)
I can see in the git log that the first patch set was applied. The second patch set
exists but is not applied. If I call "guilt push" repeatedly from the
devshell, the patches from the second set are cleanly applied. My guess is that
something doesn't like the second SRC_URI_append call. Any ideas on how to fix it?
It shouldn't matter. Let me try and set up something that reproduces the
problem and get back to you.
Strangely .. I'm actively debugging something similar here already, so I
may be able to re-use it.
Stay tuned.
Out of curiosity, have you tried this on master ?
Cheers,
Bruce
Thanks,
Bryan
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel patch is unpacked but not applied
On 13-06-26 11:42 PM, Bruce Ashfield wrote:
On 13-06-26 11:08 PM, Bryan Evenson wrote:
I am building a custom Linux kernel under poky-dylan and I am having
an issue with patches being unpacked but not applied. I have two
layers that have a bbappend file for the kernel. Generally, this is
what each bbappend file looks like:
#First .bbappend
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_mach1 = "mach1"
COMPATIBLE_MACHINE_mach2 = "mach2"
SRC_URI_append_mach2 = " file://${MACHINE}/${KBRANCH}/0001-blah.patch \
file://${MACHINE}/${KBRANCH}/0002-blah.patch \
"
# Increment the recipe revision
PRINC := "${@int(PRINC) + 1}"
# Second .bbappend
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
COMPATIBLE_MACHINE_mach1 = "mach1"
COMPATIBLE_MACHINE_mach2 = "mach2"
SRC_URI_append_mach2 = " file://${MACHINE}/${KBRANCH}/0003-blah.patch \
file://${MACHINE}/${KBRANCH}/0004-blah.patch \
"
# Increment the recipe revision
PRINC := "${@int(PRINC) + 1}"
All of the patch files are properly unpacked, but the last two patches
are not being applied. If I open the devshell for the kernel (bitbake
-c devshell linux-yocto-custom) I can see in the git log that the
first patch set was applied. The second patch set exists but is not
applied. If I call "guilt push" repeatedly from the devshell, the
patches from the second set are cleanly applied. My guess is that
something doesn't like the second SRC_URI_append call. Any ideas on
how to fix it?
It shouldn't matter. Let me try and set up something that reproduces the
problem and get back to you.
Strangely .. I'm actively debugging something similar here already, so I
may be able to re-use it.
Stay tuned.
Out of curiosity, have you tried this on master ?
So I tried to recreate this on master, and things worked for me. Which
I figured would happen, since this will make it harder to fix ... and
that's how it always works out.
I created two layers, with four patches to the main linux Makefile. They
all add something to the description:
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI_append = " file://0001-makefile-one.patch \
file://0002-makefile-two.patch"
PRINC := "${@int(PRINC) + 1}"
and
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI_append = " file://0003-makefile-three.patch \
file://0004-makefile-four.patch"
PRINC := "${@int(PRINC) + 1}"
.. and alas, the all were applied:
> grep NAME Makefile
NAME = Displaced Humerus Anterior one two three four
Can you send me the exact names of your patches ? I'm wondering if
an already applied check is triggering and preventing the auto push.
Bruce
Cheers,
Bruce
Thanks,
Bryan
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] NAND Filesystems
I think I found the solution... Its in image_types.bbclass On Wed, Jun 26, 2013 at 5:08 PM, DAMARLA Satya Swaroop < satyaswaroop.dama...@gmail.com> wrote: > Hi Guys, > > Google doesnot provide a good link but may I ask you where can I search > for NAND filesystems that yocto supports for the target > > Greets, > Satya > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] run commands after installation
Hi,
You need to do something like below:
pkg_postinst() {
net-snmp-config --create-snmpv3-user -a "my_password" myuser
}
try with above and it should work :)
//Gaurang Shastri
On Wed, Jun 26, 2013 at 9:07 PM, Tomas Frydrych wrote:
> On 26/06/13 15:32, Katu Txakur wrote:
> > I want to create a user after adding the snmp recipe. The command to do
> > that is:
> >
> > net-snmp-config --create-snmpv3-user -a "my_password" myuser
> >
> > What's the best way to do it? I have tried from do_install_append and
> > also from ROOTFS_POSTPROCESS_COMMAND but no luck so far.
>
> You need a postinst script for that sort of a thing.
>
> Tomas
>
> --
> http://sleepfive.com
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
