8.4 Demonstrate the ability to dynamically load a shared object, call its functions, and reference its symbols using the dlopen family of functions
There's no objectives for this line item, but I have an idea.
Utilizing production code in SKID's devops_code library brought with it a ton of linking dependencies. I "helped" the issue by creating a Makefile variable with a running list of all the devops_code dependencies... but it would be easier if the build system just "released" SKID production code as a shared object. Then, and optional rule could "install" SKID's shared object. Finally, some manual test code to link against functions defined in the new shared object. That should be enough (and super useful so I can link against SKID features in future projects).
Add a Makefile rule that automatically "releases" SKID as a shared object
Add an optional rule to "install" SKID's headers and shared object in Linux-appropriate ways
Write some manual test code to utilize functionality defined in the shared object
There's no objectives for this line item, but I have an idea.
Utilizing production code in SKID's
devops_codelibrary brought with it a ton of linking dependencies. I "helped" the issue by creating a Makefile variable with a running list of all thedevops_codedependencies... but it would be easier if the build system just "released" SKID production code as a shared object. Then, and optional rule could "install" SKID's shared object. Finally, some manual test code to link against functions defined in the new shared object. That should be enough (and super useful so I can link against SKID features in future projects).