Thread: [CEDET-devel] semantic can't parse WindRiver c++ standard library headers
Brought to you by:
zappo
From: Mitchel H. <mit...@gm...> - 2011-05-27 00:37:43
|
Hello list! I'm working with an implementation of the c++ standard library by WindRiver (vxworks) and semantic I guess is having a hard time parsing the files... My project is finding the files (they're highlighted yellow, not ping) but semantic can't ever parse them. When I visit one of the files in question and do semantic-analyze-current-context I get: semantic-analyze-current-context: Cannot analyze buffers not supported by Semantic Any ideas what's up? I obviously can't supply the files because I don't think WindRiver would appreciate that :), so I guess this conversation is pointless unless you have access to those headers or have some other ideas for me to debug what's going on. -Mitch |
From: Mitchel H. <mit...@gm...> - 2011-05-27 00:40:37
|
*pink -- not ping (I need to get away from a command line more often)... On Thu, May 26, 2011 at 5:37 PM, Mitchel Humpherys <mit...@gm...> wrote: > Hello list! > > I'm working with an implementation of the c++ standard library by WindRiver > (vxworks) and semantic I guess is having a hard time parsing the files... My > project is finding the files (they're highlighted yellow, not ping) but > semantic can't ever parse them. When I visit one of the files in question > and do semantic-analyze-current-context I get: > > semantic-analyze-current-context: Cannot analyze buffers not supported by > Semantic > > Any ideas what's up? I obviously can't supply the files because I don't > think WindRiver would appreciate that :), so I guess this conversation is > pointless unless you have access to those headers or have some other ideas > for me to debug what's going on. > > > -Mitch > > |
From: Eric M. L. <er...@si...> - 2011-05-27 01:40:25
|
On 05/26/2011 08:37 PM, Mitchel Humpherys wrote: > Hello list! > > I'm working with an implementation of the c++ standard library by > WindRiver (vxworks) and semantic I guess is having a hard time parsing > the files... My project is finding the files (they're highlighted > yellow, not ping) but semantic can't ever parse them. When I visit one > of the files in question and do semantic-analyze-current-context I get: > > semantic-analyze-current-context: Cannot analyze buffers not supported > by Semantic > > Any ideas what's up? I obviously can't supply the files because I don't > think WindRiver would appreciate that :), so I guess this conversation > is pointless unless you have access to those headers or have some other > ideas for me to debug what's going on. The major mode of your files needs to be C++, or Semantic won't get the buffer set up for parsing. Alternately, if they are C++ files, an error may be thrown while the mode is being setup and it is being caught, but the buffer isn't setup. Doing "M-x c++-mode" in the buffer should force something to be revealed. Eric |
From: David E. <de...@ra...> - 2011-05-27 05:49:03
|
Eric M. Ludlam writes: > On 05/26/2011 08:37 PM, Mitchel Humpherys wrote: >> Hello list! >> >> I'm working with an implementation of the c++ standard library by > >> WindRiver (vxworks) and semantic I guess is having a hard time parsing >> the files... My project is finding the files (they're highlighted >> yellow, not ping) but semantic can't ever parse them. When I visit one >> of the files in question and do semantic-analyze-current-context I get: >> >> semantic-analyze-current-context: Cannot analyze buffers not supported >> by Semantic >> >> Any ideas what's up? I obviously can't supply the files because I don't >> think WindRiver would appreciate that :), so I guess this conversation >> is pointless unless you have access to those headers or have some other >> ideas for me to debug what's going on. > > The major mode of your files needs to be C++, or Semantic won't get the > buffer set up for parsing. Alternately, if they are C++ files, an error > may be thrown while the mode is being setup and it is being caught, but > the buffer isn't setup. This is a common problem with STL files like "algorithm" which don't have a file extension. There are several ways to deal with that: * Put // -*- C++ -*- in the first line of all the files (this is what GNU glibc has). * If all the files start with a C++ comment, use (add-to-list 'magic-fallback-mode-alist '("^// " . c++-mode)) * Frob auto-mode-alist to include the directory with the STL files, like (add-to-list 'auto-mode-alist '("^/usr/include/windriverSTL/" . c++-mode)) -David |
From: Mitchel H. <mit...@gm...> - 2011-05-27 05:57:50
|
> * If all the files start with a C++ comment, use > > (add-to-list 'magic-fallback-mode-alist '("^// " . c++-mode)) > > * Frob auto-mode-alist to include the directory with the STL files, like > > (add-to-list 'auto-mode-alist '("^/usr/include/windriverSTL/" . c++-mode)) I was just wondering how I was going to get emacs into c++ mode since I don't want to edit the source files. Thanks for these ideas. -Mitch |