On 2020-06-25 9:40 a.m., Ragavan wrote:
Hello Randy,
Thanks for the response.
Perhaps you can explain your higher level goals here and someone might
comment on whether it makes sense to use Yocto at all.
[R]The intent here is to maintain all dependent libraries that my
Application requires as recipes so that I can create an APP+Library for
a specific Distribution.
Are you only targeting one Ubuntu distro?
If so then I recommend using the ubuntu native build tools:
https://askubuntu.com/questions/1345/what-is-the-simplest-debian-packaging-guide
If you are trying to create packages for a variety of distos,
that's more work but again, unless you are willing to use
containers, it's not a typical use of Yocto/OE, IMO.
You could use Yocto to build and maintain the packages you
are interested in and the put them in a container to be run on Ubuntu.
[R] While containerization is one approach to go about, I am looking at
ways by which I can achieve the above mentioned without having
containerized infrastructure.
Why can't you use the native Ubuntu tools to build software for Ubuntu?
[R] Are you referring to apt and automation above it ?
The usual way of doing that would be to use a supported BSP such as one
from:
https://git.yoctoproject.org/cgit.cgi/meta-intel/
[R] I was trying APPS which are not really target dependent (Intel/Arm).
Eg: The sqlite which I mentioned in the problem statement in the thread.
While applications are not typically tied to specific hardware, they
are loosely coupled to versions of glibc and maybe other lower
level libraries.
I suppose you could use a similar approach to how we generate the
buildtools tarball:
https://www.yoctoproject.org/docs/3.1/ref-manual/ref-manual.html#building-your-own-buildtools-tarball
I haven't been directly involved in that so someone else will have to
reply if that's the direction that you decide to undertake.
I do know that these buildtools are generated on a system with the
oldest version of glibc and therefore continue to work with newer glibcs
as long as the glibc devs don't change an ABI.
You'd have to post-process to generate .deb files and somehow handle
the low level package dependencies so it would require some work.
I don't know of anyone who has done the .deb part; we just use
the buildtools tarball.
Good luck,
../Randy
Regards,
Ragavan.
--
# Randy MacLeod
# Wind River Linux
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8776):
https://lists.yoctoproject.org/g/linux-yocto/message/8776
Mute This Topic: https://lists.yoctoproject.org/mt/75036337/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
