Bench File Reading Error about lorina

[hriener]

Hello utdael,

I would run lorina as follows to parse a bench file:

#include <lorina/lorina.hpp>
#include <iostream>

int main()
{
  using namespace lorina;
  bench_reader reader;
  text_diagnostics consumer;
  diagnostic_engine diag( &consumer );

  if ( read_bench( "c432.bench", reader, &diag ) == return_code::success )
  {
    std::cout << "parsing successful" << std::endl;
  }
  else
  {
    std::cout << "parsing failed" << std::endl;
  }
}

On my system, this approach seems to be able to read all of Maksim's benchmarks.

What do you mean by "it isn't working"? Do you see a specific error message?

Edit: I should point out that lorina is a C++ library. It provides you with API to read bench files, but you still have to implement an executable that calls the API to process the file(s).

Best,
Heinz

[utdael]

Thank you for the quick response.
My main problem is compiling and running lorina on one of our cpp files in a linux environment. At the moment, we cloned the github in the same folder as our cpp file.
We attempted to compile it using gcc bench.cpp in one of the screenshots attached.

However, we get an error that says "no such file or directory" for the #include <lorina/lorina.hpp> library.

How can I go about compiling this design?

[hriener]

lorina uses CMake as a build system.

Try the following steps:

$ git clone [email protected]:hriener/lorina.git
Cloning into 'lorina'...
[...]
$ cd lorina
$ mkdir build
$ cd build
$ cmake .. -DLORINA_EXAMPLES=ON
-- The CXX compiler identification is ...
[...]
$ make
[ 50%] Building CXX object examples/CMakeFiles/pretty_print.dir/pretty_print.cpp.o
[100%] Linking CXX executable pretty_print
[100%] Built target pretty_print
$ ./example/pretty_print PATH_TO_YOUR_BENCH_FILE

Two more notes:

• You may have to install cmake and make on your system first. You will notice if you see error messages saying that cmake or make is not a valid command.
• All files ending with .cpp in the directory examples will be automatically build. Each time you add a new example, you have to run cmake again in the build directory. Each time you change one of the .cpp files, you have to run make again in the build directory.

[hriener]

Seems to be resolved.

If not, then the issue can be re-opened...