> On Jul 23, 2021, at 3:26 AM, Khem Raj <[email protected]> wrote: > > Hi Randy > > Its not clear what you are looking for, perhaps you are looking to > build some Linux packages and dependencies that can run on Android. Most of like that. > meta-mingw does not build for windows target although it can be > extended, it builds SDK that can be used on windows hosts to build > packages for linux targets. What you need is perhaps meta-android > which can provide the android SDK environment into OE and then you can > leverage the build infra. But if you explain your usecase a bit more > that may bring more ways to solve your problem For example, if I want to build and setup a media service in a Android system(or a AI service), it could depend on a framework likes FFMpeg, Gstreamer or VideoLan, that framework would depend on more packages. Then I just create a image target, oe would build all those packages, install them into a stagging dir then pack in into a image. That image would not included some Android system library likes library C and C++, and the other library vendor should not have its own version(likes OpenGL ES, libjpeg ? OpenMAX) I think the first thing I need to care is how to use that external clang baesd toolchain from Android NDK. We can’t use our build one, it must follow Android’s ABI strictly or it can’t fix into Android update. meta-external-toolchain is for gcc, I am looking at how to add an clang version. > >> On Thu, Jul 22, 2021 at 6:39 AM Randy Li <[email protected]> wrote: >> >> Hello All >> >> I am working with video, graphics and AI stuff all the time, although >> Android has many good frameworks and published some good standards to >> following(as long as you could understand its documents). I am sure we would >> like still to use those packages that we are familiar with at GNU Linux. For >> example, if we want to use the Gstreamer on Android, you would need to >> compile a bulk of dependency packages. Although I don't know a vendor would >> like to ship those frameworks in their product, they are very useful at the >> development stage. I am sure AI staff would like this, there are too many >> neural network frameworks for different platforms. Those frameworks may >> depend on the other neural network framework for model parsing. >> >> There is a project from Gstreamer called Cerbero, people may have already >> known that. It has done the most of work I want, but I just don't want to >> port so many recipes to it. >> >> I am not sure what I need to do, what the meta-mingw did may not be enough >> for me. Do I need to start up a new distribution? There is not a library C >> nor linker loader in the vendor's partition and many install files for >> general Linux won't be used in Android. The meta-clang may need to be >> adopted as it would use an external Android NDK toolchain. And I don't need >> to support many target platforms based on Android One policy, only limited >> ABIs would be supported and no CPU variant tuning would be used. >> After we could run that software only depending on the kernel's API, I think >> I could move forward to support building those HAL modules(likes hardware >> decoders and encoders for codec2). That would require us to separate those >> codes from Android SDK repositories. Packing the APEX file should be in plan >> as well. >> >> ayaka >> >> >>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#154105): https://lists.openembedded.org/g/openembedded-core/message/154105 Mute This Topic: https://lists.openembedded.org/mt/84379033/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
