Any objections, concerns, comments? The migration to cmake is naturally to let us stop manually maintaining msvc build files. If there's something that the current build files do that the cmake build doesn't do, please speak up so we can resolve any remaining issues.
The only matters I can think of that need to be resolved are: 1) MSVC is hooked into kicking off NSIS for producing our pretty .exe installer. 2) coreInterface (aka GE) is getting bundled into a brlcad.dll along with a subset of the core libs. Since we have a more comprehensive Windows build now with cmake, the NSIS installer will need updating. As it will be desirable for the GE API to have a single .dll/.so/.dylib product, I'm thinking this might be best achieved by using svn:external in the GE sources, checking out the bu, bn, rt, etc sources that it intends to bundle. That way, we only build what we need for both the GE API and the main sources without compiling everything multiple times. Cheers! Sean ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
