#2 Automate plugin creation from executable code
Currently the method of creating plugins from existing executable code
requires manually importing the relevant files into the correct folder in
Eclipse.
Problems:
- Developer needs to know what the different folder names mean. These
correspond to the supported architectures. However, we can't possibly
expect a scientist to know what 'x86' or 'ppc' or 'ia64' mean.
- Copying code into the wrong folders will basically not throw any kind of
error until something is run. Even then, the error is most likely going to
be something that the developer may not understand. For example, if an
executable cannot find dynamic library 'x', the message usually is 'cannot
find x.DLL' (or x.so). Now if the library was put in *some* folder but not
the right one, this requires the developer to go through documentation
for how the ivcsf searches through library paths - definitely not
something a normal user would do.
---
Some sort of framework is needed to automate this process. It would be
very useful to be able to identify what libraries an application requires. We
could possibly talk to NCSA about using their Siege project's host
configuration service since it does some things that will be useful for this.
