Hi, Jan Möbius, Thanks for sharing your ideas.
The Plugin Collection is a good concept to deal with this case, if the cmake can automatically recognize how many plugins in the collection and generate the corresponding binaries, because, from a developers viewpoint, we DO want to maintain them in a single project.
If the cmake cannot, we prefer the SINGAL and SLOT mode, the business relationship looks clear even we have to sacrifice more code lines.
Regards,
Xianyong Liu Shanghai JiaoTong University Office: +86 021 34204586 E-mail: xyliu80@gmail.com Address: 504 Room, SEIEE buiding 3#, 800 Dongchuan Rd,Min Hang,Shanghai,200240,China
Zeige Antworten nach Diskussionsstrang
Hi,
the collection has been implemented and is now available via svn. As an example you can take the collection for the selection Plugins.
The Plugin Collection is a good concept to deal with this case, if the cmake can automatically recognize how many plugins in the collection and generate the corresponding binaries, because, from a developers viewpoint, we DO want to maintain them in a single project.
Yes, the toplevel directory has to be named as
PluginCollection-<Name of your collection> and the subdirectories have to be named with Plugin-<Plugin Name>
The system will automatically detect the number of plugins in each collection folder and generate the corresponding binaries.
Best, Jan Möbius
openflipper@lists.rwth-aachen.de