OK, thanks Scott and Stefan. Perhaps I'll look for other tools to parse C++, then.
Stefan Seefeld wrote:
> Adam,
>
> On 02/10/2010 05:31 PM, Adam Richard wrote:
>> Hi,
>>
>> I've been considering using OpenC++ to write some static analyses.
>>
>> When I try to build it, I get errors that strlen (and other C string functions) can't be found. It looks like in several places there are missing "#include<cstring>" directives, which perhaps work on other platforms, but not on mine (Ubuntu Linux x86, gcc 4.3.2). I'm guessing they work elsewhere because the "#include<string>" directives are loosely interpreted as "#include<string.h>".
>>
>
> OpenC++ is very much outdated at this point, hasn't been worked on, or
> even maintained, for a couple of years. I believe I was the last one
> doing active work on / with it, as I branched from it to develop a C++
> parser for Synopsis (http://synopsis.fresco.org). You may want to look
> there, and try to see whether its C++ parser frontend is useful enough
> for your needs.
>
> Regards,
> Stefan
>
Scott D. Fleming wrote:
> Hi Adam,
> I used OpenC++ about 5 years ago, and the project was dying then. Not
> much appears to have changed (last major release was in 2004). Even if
> you get OpenC++ to build, I expect that you will find that it can't
> parse the GCC libraries (which essentially renders it broken). If you
> really want to use OpenC++, you can try using it with an older version
> of GCC (3.3, I think); that's how I got it to work in '05. However, I
> recall it being a big hassle (e.g., hard-coded file names needed to be
> changed, etc.).
> Cheers, Scott
>
>
> On Wed, Feb 10, 2010 at 2:31 PM, Adam Richard <ric...@gm...> wrote:
>> Hi,
>>
>> I've been considering using OpenC++ to write some static analyses.
>>
>> When I try to build it, I get errors that strlen (and other C string functions) can't be found. It looks like in several places there are missing "#include <cstring>" directives, which perhaps work on other platforms, but not on mine (Ubuntu Linux x86, gcc 4.3.2). I'm guessing they work elsewhere because the "#include <string>" directives are loosely interpreted as "#include <string.h>".
>>
|
