Skip to contentSkip to conversation

opkg and opkg-target aliases for the SDK

DISCUSSION Ilya Yanok 3 participants 5 messages May 4, 2011 – May 6, 2011

lore
Share & tools
lore

Ilya Yanok

author
#0 lore raw

Hello guys,

I've found that opkg and opkg-target aliases were removed from the SDK environment script by commit f09f8f4.
However I can't see any note about this in the commit comment. Was this removal intentional?

Regards, Ilya.

#1 lore raw

Hi Ilya,

The removal was part of the changes made for adt-installer which is a new feature for Yocto 1.0 release. The old opkg and opkg-target aliases in the environment script was for add packages to the locked location of toolchain(aka SDK) and target sysroot. With Yocto 1.0 and adt-installer, it's still using opkg to install toolchain under /opt/poky/ but the sysroot is now a customized location that can be anywhere, which is specified in the adt_intaller.conf file...

Thanks,
Jessica

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Ilya Yanok
Sent: Wednesday, May 04, 2011 10:03 AM
To: [email protected]
Subject: [poky] opkg and opkg-target aliases for the SDK

Hello guys,

I've found that opkg and opkg-target aliases were removed from the SDK environment script by commit f09f8f4.
However I can't see any note about this in the commit comment. Was this removal intentional?

Regards, Ilya.
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

author
#2 lore raw

Hi Jessica,

Quoted 1 line · Jessica

The removal was part of the changes made for adt-installer which is a new feature for Yocto 1.0 release. The old opkg and opkg-target aliases in the environment script was for add packages to the locked location of toolchain(aka SDK) and target sysroot. With Yocto 1.0 and adt-installer, it's still using opkg to install toolchain under /opt/poky/ but the sysroot is now a customized location that can be anywhere, which is specified in the adt_intaller.conf file...

I see. Still as we are meta-toolchain users we are going to miss them... Or is meta-toolchain going to be abandoned and we should move to adt-installer?

Thanks for your comments.

Regards, Ilya.

#3 lore raw

Ilya Yanok wrote on 2011-05-06:

Quoted 12 lines

Hi Jessica,

Quoted 2 lines · Jessica

The removal was part of the changes made for adt-installer which is a new

feature for Yocto 1.0 release. The old opkg and opkg-target aliases
in the environment script was for add packages to the locked location
of toolchain(aka
SDK) and target sysroot. With Yocto 1.0 and adt-installer, it's still
using opkg to install toolchain under /opt/poky/ but the sysroot is
now a customized location that can be anywhere, which is specified in the adt_intaller.conf file...

Quoted 4 lines

I see. Still as we are meta-toolchain users we are going to miss them... Or is meta-toolchain going to be abandoned and we should move to adt-installer?

Hi Ilya,

The meta-toolchain is still there for backward compatibilities. Another reason that the opkg-target and opkg were removed from the environment file in meta-toolchain is that now the meta-toolchain can be created not only by ipk, but by rpm/deb also, and the opkg/opkg-target is miss-leading for the rpm/deb cases.

Best Regards,
Lianhao

#4 lore raw

Re: poky and poky-target aliases for the SDK

Ilya,

As Lianhao mentioned we're not abandoning meta-toolchain, but since adt installer provide you the flexibility to setup your development sysroot at your customized location which we believe is a big gain in embedded application development. Again, since adt is using opkg, you're still able to manage the toolchain install location under /opt/poky, and sysroot location using opkg as you use to do with meta-toolchain, just the opkg and opkg-target need to be modified to reflect the new locations based on adt-installer.

Thanks,
Jessica

-----Original Message-----
From: Lu, Lianhao
Sent: Thursday, May 05, 2011 6:34 PM
To: Ilya Yanok; Zhang, Jessica
Cc: [email protected]
Subject: RE: [poky] opkg and opkg-target aliases for the SDK

Ilya Yanok wrote on 2011-05-06:

Quoted 12 lines

Hi Jessica,

Quoted 2 lines · Jessica

The removal was part of the changes made for adt-installer which is a new

feature for Yocto 1.0 release. The old opkg and opkg-target aliases
in the environment script was for add packages to the locked location
of toolchain(aka
SDK) and target sysroot. With Yocto 1.0 and adt-installer, it's still
using opkg to install toolchain under /opt/poky/ but the sysroot is
now a customized location that can be anywhere, which is specified in the adt_intaller.conf file...

Quoted 4 lines

I see. Still as we are meta-toolchain users we are going to miss them... Or is meta-toolchain going to be abandoned and we should move to adt-installer?

Hi Ilya,

The meta-toolchain is still there for backward compatibilities. Another reason that the opkg-target and opkg were removed from the environment file in meta-toolchain is that now the meta-toolchain can be created not only by ipk, but by rpm/deb also, and the opkg/opkg-target is miss-leading for the rpm/deb cases.

Best Regards,
Lianhao