Hi Yashodhan, include dependencies to modules or third-party libraries (everything which is not a plugin/bundle) are not inherited. So your approach of explicitly adding the Boost include dirs to ParadigmView is the "correct" way right now.
You can add additional include dirs relative to your plugin, see for example the file "includes.cmake" in the org.blueberry.osgi plugin. I guess it wouldn't be very complicated to extend the plugin build-system to support third-party includes. I will keep you posted. Best, Sascha you can create a file named "includes.cmake" in the top-level directory of BaseParadigm, which lists additional include files On 10/05/2010 05:27 PM, Yashodhan Nevatia wrote: > Hi everyone, > > I have a question regarding dependency management in plugins. > > I have the case that one of my plugins (BaseParadigms) is dependent on Boost > (or for that matter some module). This builds fine. > > However, when another plugin (say ParadigmView) depends on BaseParadigm, and > includes a file from BaseParadigm, this does not work as the dependencies > from BaseParadigms are not included as dependencies for ParadigmView. > > Explicitly including Boost as a module dependency for ParadigmView solves the > problem. > > Am I doing something wrong? Is there any way (other than explicitly including > Boost in this case as a dependency for ParadigmView)? > > Thanks, > > Yashodhan > ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
