Re^3: How to install self written modules

I've not done a lot of modification to module installation scripts. There might be an easy and obvious solution (damn if I know though)

You could make a script to make and install them all. Not that good with Make but you could probably right a makefile as well to handle the task.

I'm getting the impression that you're after plugins. If so, 100 seems like a lot for any medium.

May I ask what exactly you're trying to do?

-Lee
"To be civilized is to deny one's nature."

Comment on Re^3: How to install self written modules

Replies are listed 'Best First'.
Re^4: How to install self written modules by jeanluca (Deacon) on Mar 03, 2006 at 15:45 UTC
Maybe plugins is the solutions, but Idon't know nothing about them. Anyway I'm writing a tool that can process data, different types of data. For each type of data I've a couple of modules which know how to deal with this data. So with time more and more types of data can be included, just by adding new modules that know how to deal with this data. Any suggestions what my approach for installing them should be ? Tnx Luca	[reply]
Re^5: How to install self written modules by shotgunefx (Parson) on Mar 03, 2006 at 19:20 UTC
Whether plugins are the right or wrong way, depends on your problem. Do you want to be able to have everything in one monolithic module or a number of smaller ones. A good example of were plugins make sense is playing music. No matter what type of file or hardware, you basically have one goal. DECODE -> DSP? -> PLAY This is ideal for plugins as you can just "plug-in" the code that knows how to decode the input format. New formats come along? Just write a new plugin. Same with outputting to the hardware. Whant to have some DSP effects? You set up common hooks and then can "just add" DSP plugins with the proper interface and it all just works (in theory). -Lee "To be civilized is to deny one's nature."	[reply]