tinkerer | Python blogging engine | Blog library

Here is a crude example of the type of code I would like to use libtool's libltdl dlpreopening with:

https://github.com/EmmaJaneBonestell/dlopen-sample

I wish to be able to rewrite various projects that use libdl functions ( dlopen, dlsym, etc ), to instead use libtool's libltdl dlpreopening/preloading mechanism. From libtool's documentation, it will instead link the objects at compile time, resulting in truly static executables. It was intended for systems that do not support dynamic loading.

If you use it to compile and link these objects, libtool will run some of its scripts, and create the necessary data structures, and I believe perform mangling and demangling, to allow for duplicate symbol names.

Even after looking at the examples in libtool's source code, reading its entire documentation, and looking at relevant tests from the test-suite (e.g. tests 118 & 120), I've been unable to do so.

Outside of libtool itself, there is essentially no mention of this functionality anywhere I could find. I did manage to see it used in a too-complex-for-me manner in Graphviz, but there's little documentation on that either.

I'm really not much of a programmer, more of a tinkerer. It's easy enough for me to use libltdl for a wrapper for standard dlopen/dlsym.

I think my main issue is figuring out how I can return a proper handle for a preopened object, though I may be doing other things incorrectly.

The documentation states that lt_dlopen can work on preloaded static modules, but it doesn't seem to accept any possible reference to it I could imagine.

I would also prefer not to have to even invoke libtool, but c'est la vie.

I didn't bother including any of what I've tried code wise (on the example) because I've tried such a mess of things that I feel it would really just be confusing to show it.

Current libtool documentation: https://www.gnu.org/software/libtool/manual/libtool.html

I would like that when a user orders items, a special unique key is generated for each item. These keys / This key should then be visible in ALL order mails (admin and customer). Here is what I tried to do after some research around the web :