I'm asking on this list since this is a pretty general question. If it's more appropriate for another venue, just let me know.
I'm trying to build a new package for my target which has never been ported to OpenEmbedded/Yocto/... (It's the Amanda backup server if anyone has ever looked at this). The code is a giant mass that I'd hoped not to have to delve into very deeply. Basic configuration (autoolized) went well, but one of the first things it wants to do is run a [target] program which has been linked against the [target] libraries that were just built. In this case, it's just a utility to interrogate the libraries and CONFIG.h files and print a user summary. What's the best way to handle this and how? I recall in the dark old days that there were many such things that relied on running QEMU to actually execute target code. Is this still possible (and being done)? If so, is that a solution and how might I force it to happen? It may turn out that this is just a small problem that I can patch my way through, but I fear there may be other such utilities that get built and used, so I'd like to understand my way forward. Thanks for any pointers/ideas -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
