sandboxed-api/oss-internship-2020/sapi_lodepng
2020-08-14 15:56:57 +00:00
..
examples moved code in examples directory, modified README 2020-08-14 15:56:57 +00:00
lodepng@aa6cc42db7 added submodules, modified the tests to use the current path 2020-08-12 13:59:17 +00:00
.gitignore moved .gitmodules to lodepng project folder 2020-08-12 14:09:26 +00:00
CMakeLists.txt moved code in examples directory, modified README 2020-08-14 15:56:57 +00:00
README.md moved code in examples directory, modified README 2020-08-14 15:56:57 +00:00

LodePng Sandboxed

Sandboxed version of the lodepng library, using Sandboxed API

Details

With Sandboxed API, many of the library's functions can be sandboxed. However, they need the extern "C" keyword defined so that name mangling does not happen, which is why a fork of the lodepng library is used. The only differences are found in the header file. An alternative to this is to define another library that wraps every needed function, specifying the required keyword.

Even if many of the functions from the library can be sandboxed, there are some that are not supported (those which have std::vector parameters, overloaded functions etc.). If you really need these functions, a solution is to implement a custom library that wraps around these functions in order to make them compatible.

Examples

The code found in the examples folder features a basic use case of the library. An image is generated, encoded into a file and then decoded to check that the values are the same. The encoding part was based on this example while decoding was based on this.

This folder is structured as:

  • main.cc - unsandboxed example
  • sandbox.h - custom sandbox policy
  • main_sandboxed.cc - sandboxed version of the example
  • main_unit_test.cc - testing file using Google Test.

The executables generated from these files will create the png files in the current directory. However, for the main_sandboxed.cc file there is also the images_path flag which can be used to specify a different directory.