Hi, We are constantly running into a Visual Studio (both '10 and '12) issue where the compiler crashes with a buffer overflow if the include path gets too long. The limit seems to be somewhere below 30k characters.
CMake insisting on using absolute paths for everything does not help. So our work-around is usually to shorten the path where we store the source code and build directory on disc. But we are now down to "c:\a" and still run into this every once in a while. Looking at the include path for an mitk plugin, it's transitively inherited from all dependencies (other mitk modules, etc), even though most these are not needed. Do you have any thoughts on reducing the amount of header-dependencies? Say via forward-declarations? Or good old pimpl? A large part of the include paths listed are simply there because some mitk header depends on loads of other stuff. Forward-declarations for ITK are going to be difficult (and/or ugly) because of that MyClass::Pointer smart-pointer convention. VTK uses vtkSmartPointer<MyClass> so would be easier. Any plans or thoughts on this? Johannes ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
