Le 24/05/2011 16:31, Romain Beauxis a écrit :
Hmm.. You mean build a cmxs for sdl at build-time? First, this would give the same error and it would also increase the complexity of the dynamic loading, in order to resolve dependencies etc..
I meant building sdl.cmxs in ocaml-sdl package. It's quite easy and can be done in debian/rules. Have a look at postgresql-ocaml, for example. Then the META, *.cmxs and *.cma should be moved to the runtime package. dh_ocaml should then infer the right dependencies.
Unfortunately, I would need to use dh_ocaml at least for bytecode modules, to get the right dependency against the corresponding implementation..
You said in your original e-mail that you didn't want any ocaml dependencies. Did you try the --nodefined-map command-line option of dh_ocaml, then?
All in all, I still do not understand your point. What is wrong with a plugin containing module Foo and being the only one loading this unit in the whole program?
What do you do when someone else wants to make a plugin that can be concurrently loaded and depends on Foo? You seem to forbid that in your specific case, but it can happen in general.
Cheers, -- Stéphane