On 23 Aug 2005 22:30:42 +0100, seventh guardian wrote: > > I'm trying to learn how to write fvwm modules, so I read all the info > I could find on the fvwm page, and also a great C module programming > guide from Nick Fortune (at fvwm lair). Also, following the sugestion > from the fvwm's page, I went through the source of some of the oficial > modules to see how they looked. > > What I found: most of them use the Module lib (Module.h header). Also > fvwm's module guide refer this lib. On the other hand, Nick doesn't > use the lib, what is great for learning, but not so good for > programming (why to reinvent the wheel when all is there in > Module.h?). > > Well, Module.h definitely saves us work, but isn't that easy to use. > Partly because no documentation exists on it, other than the .h file > itself. And I really did google around. > > But what makes things even harder, is that it depends on other fvwm > libs, which in case depend on config.h. And config.h is generated by > the configure script... > > > Is there an easy way of using Module.h without needing the whole fvwm > source etc etc? > I mean something like using <include fvwm/Module.h>. Also, is there a > way of installing these libs while installing fvwm? > > I mean: how do you use Module.h?
It is only meant to be used inside the fvwm build tree. The fvwm lib is neither specifically designed nor has a stable API. Currently it is not easily possible to separate it from the build tree and to install a header plus a shared library. Maybe in the future... I don't think however there is a serious problem to maintain your C module inside the fvwm tree. It will be even easier to be built and installed this way. (Not to speak about adapting to API changes.) Regards, Mikhael.
