Let’s see, what the installation consists of. Below the installation prefix, for example “/usr/local”, you have this structure-content:
A shell script similar to e.g. gtk-config which makes compiling of own plugins easy. It generates compiler-flags, extracts system-paths, and more. “icewing-config --help” shows all available options of the script. See section 7.2 for more details.
A shell script which collects help messages of all plugins which are installed under ${PREFIX}/lib/iceWing and all plugins which are integrated in iceWing. The script creates the files “Readme.txt” and “Readme.html” in the current directory and the file “${PREFIX}/share/iceWing/plugins.help”. This last file is used by iceWing to display additional information about plugins on the “Plugins” page in the “Plugin Info” window. See section 5.2.4 for information about this window. See section 7.4 for more information about the script.
A plugin template generator. The script generates in the current directory a basic C or C++ plugin including a Makefile to compile it. “icewing-plugingen --help” gives more information. See section 7.5 for the details.
’icewing-config --bindir’ gives this directory, whereas ’icewing-config --prefix’ gives the installation directory, i.e. this directory without the “/bin” part.
Besides other options, ’icewing-config --cflags’ contains this directory.
If your plugin publishes new structures to be used by other plugins, you probably want to put them here.
’icewing-config --pincludedir’ gives this directory.
’icewing-config --libdir’ gives this directory.
’icewing-config --datadir’ gives this directory.
TODO