A C++ wrapper library around the core functionality of Adblock Plus
C++ JavaScript Python Makefile C Batchfile Shell
Switch branches/tags
Nothing to show
Clone or download
Failed to load latest commit information.
.appveyor Issue 5133 - add CI for libadblockplus Sep 27, 2017
.travis Issue 6756 - fix build for android-ia32 Jun 21, 2018
include Issue 6596 - update to work with v8 Jun 14, 2018
lib Issue 6477 - separate done and error callbacks in IFileSystem::Read Mar 23, 2018
shell Issue 5617 - Provide with async executor bound to Platform in the future Sep 5, 2017
src Issue 6526 - Use Maybe<> version of soon to be deprecated API in v8 6.7 Aug 7, 2018
test Issue 6526 - Fix test by not exposing V8 Aug 7, 2018
third_party Issue 6596 - update to work with v8 Jun 14, 2018
v8-args Issue 6596 - update to work with v8 Jun 14, 2018
.eslintignore Issue 5685 - Pass ESLint Sep 15, 2017
.eslintrc.json Issue 5509 - add ESLint config Sep 15, 2017
.gitignore Issue 6695 - Allow automatically downloading V8 Jun 18, 2018
.hgignore Issue 6695 - Allow automatically downloading V8 Jun 18, 2018
.travis.yml Noissue - Use clang++ and libc++ on Linux Jun 28, 2018
Doxyfile Issue 116 - Document the API Aug 28, 2014
Makefile Noissue - fix the switching to clang++/libc++ Jul 10, 2018
README.md Noissue - Use clang++ and libc++ on Linux Jun 28, 2018
appveyor.yml Issue 6596 - update to work with v8 Jun 14, 2018
check_curl.py Issue 3952 - Fix whitespaces for compliance with PEP-8 Apr 19, 2016
common.gypi Noissue - Use clang++ and libc++ on Linux Jun 28, 2018
convert_js.py Issue 5378 - Stop using of jshydra in libadblockplus Jul 7, 2017
createsolution.bat Issue 6063, 6531 - Update V8 to, use C++14 and NDK-r16b Apr 18, 2018
dependencies Issue 6596 - update to work with v8 Jun 14, 2018
ensure_dependencies.py Issue 5119 - use own version of buildtools for ensure_dependencies.py… Jun 2, 2017
googletest.gyp Issue 4907 - Update v8 to 5.7.278 in libadblockplus Jul 4, 2017
libadblockplus.gyp Issue 6596 - update to work with v8 Jun 14, 2018
libadblockplus.gypi Issue 4907 - Update v8 to 5.7.278 in libadblockplus Jul 4, 2017
make_gyp_wrapper.py Issue 6236 - fix libraries order issue when linking of V8 mksnapshot … Jan 10, 2018
msvs_gyp_wrapper.py Issue 5698 - Update V8 to 6.1.534.41 Sep 29, 2017
package.json Issue 5509 - add ESLint config Sep 15, 2017
v8.gypi Issue 6596 - update to work with v8 Jun 14, 2018



A C++ library offering the core functionality of Adblock Plus.

Getting/updating the dependencies

libadblockplus has dependencies that aren't part of this repository. They are retrieved and updated during the build process, but you can also manually update them by running the following:


Additionally one should provide V8 headers in order to build libadblockplus library and V8 prebuilt libraries in order to link a binary (executable, shared object/DLL), even libadblockplus tests. The last time is was tested against V8 6.7. For more details see below.


Supported target platforms and prerequisites

You need a C++14 compatible compiler to build libadblockplus. Below there is the list of tested tools.


  • At least v141 Visual C++ toolset (available in Microsoft Visual Studio 2017).


  • clang 5.0 We use libc++ instead of the libstdc++ that gcc uses, since by default v8 build with libc++.


  • Apple LLVM 9.0.0 for OS X/macOS (Xcode should be installed and its developer tools should be "selected").


  • The host system should be Linux or OS X
  • android-ndk-r16b, here are the links for downloading OS X, Linux 64.
  • g++ multilib

If you have a compilation issue with another compiler please create an issue.

You also need Python 2.7 and ensure that python.exe is in your PATH.


You need V8 prior to building. Two options:

  • Use the default prebuild V8 by invoking the make target get-prebuilt-v8. This will download and extract the prebuilt V8 for your setup. The default environment will be set by the Makefile at build time. If you are cross compiling use the same options as below to invoke make.

If you switch the version of V8 using the same source tree, you should manually remove the third_party/prebuilt-v8 directory and redownload again with the right options.


  • Prepare V8 and set environment variables LIBV8_LIB_DIR and LIBV8_INCLUDE_DIR. LIBV8_INCLUDE_DIR should point to the include directory of V8, e.g. .../v8/include and there should be libv8_monolith.a in the directory LIBV8_LIB_DIR.

To build:

Using Make:


The default target architecture is the architecture of a host. In order to build for a different architecture pass ABP_TARGET_ARCH to make, e.g. run:


supported values are ia32 and x64.

To build and run the tests:

make test

Likewise, use the following with ABP_TARGET_ARCH:

make test ABP_TARGET_ARCH=ia32

To run specific tests, you can specify a filter:

make test FILTER=*.Matches


  • Prepare V8. Let's say V8 is prepared in build/v8. There should be V8 headers in build/v8/include and binaries in build/v8/win-%PLATFORM%.%CONFIGURATION%, e.g ensure that there is v8_monolith.lib available as build/v8/win-x64.release/v8_monolith.lib.

  • Set GYP variable v8_dir pointing to the prepared V8, <path to build/v8>. E.g. set "GYP_DEFINES=v8_dir=e:/v8-6.7" and execute createsolution.bat to generate project files, this will create build\ia32\libadblockplus.sln (solution for the 32 bit build) and build\x64\libadblockplus.sln (solution for the 64 bit build).

  • Open build\ia32\libadblockplus.sln or build\x64\libadblockplus.sln in Visual Studio and build the solution there. Alternatively you can use the msbuild command line tool, e.g. run msbuild /m build\ia32\libadblockplus.sln from the Visual Studio Developer Command Prompt to create a 32 bit debug build.

Tested on Microsoft Visual Studio 2017 Community Edition.

For more details see CI configuration for appveyor.

Building for Android

Configure V8 as for Unix and set ANDROID_NDK_ROOT environment variable to your Android NDK directory.

To build for x86 arch run:

make TARGET_OS=android ABP_TARGET_ARCH=ia32

To build for arm or arm64 arch run:

make TARGET_OS=android ABP_TARGET_ARCH=arm

or make TARGET_OS=android ABP_TARGET_ARCH=arm64


You can use libadblockplus to build an ad blocker. Or, strictly speaking, a web content filter. Just like Adblock Plus, it can detect resources that should be blocked based on their URL and context information, and generate CSS selectors to hide DOM elements.

The basic usage is explained below, see the API documentation for more information. See the filter documentation to learn more about Adblock Plus filters.

Initialising the engine

All the types and functions in libadblockplus are in the AdblockPlus namespace. For brevity's sake, we'll assume the following using declaration:

using namespace AdblockPlus;

Most of the functionality of libadblockplus is available via the FilterEngine class. Since libadblockplus uses the Adblock Plus core code under the hood, you first need to create a JsEngine instance and pass some information about your application to it.

AppInfo appInfo;
appInfo.name = "awesomewebfilter";
appInfo.version = "0.1";
appInfo.locale = "en-US";
JsEngine jsEngine(appInfo);

JsEngine needs to store files, make web requests and write log messages. This normally works out of the box because it is using DefaultFileSystem, DefaultWebRequest and DefaultLogSystem by default.

Depending on your application and platform, you might want to supply your own implementations for these - see FilterEngine::SetFileSystem, FilterEngine::SetWebRequest and FilterEngine::SetLogSystem respectively.

With the JsEngine instance created, you can create a FilterEngine instance:

auto filterEngine = FilterEngine::Create(jsEngine);

Please also pay attention to asynchronous version of factory method FilterEngine::CreateAsync and to optional creationParameters.

When initialised, FilterEngine will automatically select a suitable ad blocking subscription based on AppInfo::locale and download the filters for it.

Managing subscriptions

libadblockplus takes care of storing and updating subscriptions.

You can add more:

SubscriptionPtr subscription =

Retrieving an existing subscription works the same way, use Subscription::IsListed to check if the subscription has been added or not.

SubscriptionPtr subscription =
if (subscription->IsListed())

Removing a subscription is not rocket science either:


You can also get a list of all subscriptions that were added:

std::vector<SubscriptionPtr> subscriptions =

Managing custom filters

Working with custom filters is very similar to working with subscriptions:

FilterPtr filter = filterEngine.GetFilter("||example.com/ad.png");

Note that applications should only do this to manage a user's custom filters. In general, filter lists should be hosted somewhere and added as a subscription.

Matching blocking filters

As mentioned above, one of the two main tasks of libadblockplus is to check if a URL matches any of the active blocking filters.

To demonstrate this, we'll add a custom filter:

FilterPtr filter = filterEngine.GetFilter("||example.com/ad.png");

Now we'll call matches on an URL that should be blocked:

FilterPtr match =
  filterEngine.Matches("http://example.com/ad.png", "DOCUMENT", "");

Since we've added a matching filter, match will point to the same filter object as filter.

Note that we've ignored the third parameter of FilterEngine::Matches here to keep things simple. Real applications should pass the frame structure in here - this is necessary because many filters and exception rules are domain specific.

Generating CSS from element hiding filters

Aside from blocking requests, ad blockers typically also hide elements. This is done via a second type of filter that is completely ignored when matching URLs: element hiding rules.

You can retrieve a list of all CSS selectors for elements that should be hidden using FilterEngine::GetElementHidingSelectors.

What libadblockplus clients typically do with this is to generate a CSS style sheet that is injected into each page.

Disabling network requests from Adblock Plus on current connection

At any moment you can call FilterEngine::SetAllowedConnectionType to change the settings indicating what connection types are allowed in your application. However to have it working you should also pass a callback function into factory method of FilterEngine. This callback is being called before each request and the value of argument is earlier passed string into FilterEngine::SetAllowedConnectionType, what allows to query the system and check whether the current connection is in accordance with earlier stored value in settings. For example, you can pass "not_metered" into FilterEngine::SetAllowedConnectionType and on each request you can check whether the current connection is "not_metered" and return true or false from you implementation of callback AdblockPlus::FilterEngine::CreateParameters::isConnectionAllowed.


The shell subdirectory contains an example application using libadblockplus.

It's a simple shell that loads subscriptions into memory and checks whether a specified resource would be blocked or not.

To see the available commands, type help.


The shell is automatically built by make, you can run it as follows:



Just run the project abpshell.

Building V8

Just in case one can find args files to build V8 in v8-args directory.


You can lint the code using ESLint.

npm run eslint

In order to set up ESLint and configuration eslint-config-eyeo you need Node.js 7 or higher and once it is installed please run npm install in the repository directory.