That is an idea. I'll take a look. Thanks ___________________________________________________________ Mike Jackson Principal Software Engineer BlueQuartz Software Dayton, Ohio [email protected] www.bluequartz.net
On Oct 18, 2011, at 5:21 PM, Eric Noulard wrote: > 2011/10/18 Michael Jackson <[email protected]>: >> Hello, I am the maintainer of the CMakeEd Eclipse plugin and I was finally >> going to update update the plugin to have the latest information for CMake >> 2.8.6. The process that I have used in the past to populate the "command >> completion" is to parse the DocBook file because it was reasonably well laid >> out and the XML nature of the file made it easy to pick out the parts that I >> needed. It would seem that with the latest version of CMake that file is >> gone. Is there another mechanism that I would have the same information? >> >> I know I can invoke CMake with the --help-command to get the documentation >> for each command but that is going to involve a whole lot of "screen >> scraping", even with the HTML formatted version. >> >> Does anyone have any suggestions? I can post that code that I have used in >> the past (it is C++ and requires Boost) if that would help. > > May be you can try to avoid the parsing and try to link your C++ code > directly with CMakeLib > then call > > cmake::GetXXXDocumentation (see in Sources/cmake.cxx) > > may be you'll get exactly what you want withour parsing? > -- > Erk > Membre de l'April - « promouvoir et défendre le logiciel libre » - > http://www.april.org -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
