First of all you need this things :

1. Prerequisite software:
   • Windows 7 or later.
     • A 64 bit OS is highly recommended as building on 32 bit OS is constantly becoming harder, is a lot slower and is not actively maintained.
     • At least 60 GB of free space in an NTFS volume. Tip: having the chromium source in a SSD drive greatly speeds build times.
   • Visual Studio 2010 Professional or Standard.
   • Windows 8 SDK.
   • June 2010 DirectX SDK.
   • (Optional) Cygwin
2. Install Visual Studio 2010
   1. Make sure “X64 Compilers and Tools” are installed.
   2. Install VS2010 SP1.

3. Install the Windows 8 SDK.

   Note: If you install the SDK in a path different than C:Program Files (x86)Windows Kits8.0 you need to set the following following environment variable:

   GYP_DEFINES=windows_sdk_path=”path to sdk”

4. Install the June 2010 DirectX SDK
   Note: If your install fails with the “Error Code: S1023” you may need to uninstall “Microsoft Visual C++ 2010 x64 Redistributable”. See this tip from stackoverflow: http://stackoverflow.com/questions/4102259/directx-sdk-june-2010-installation-problems-error-code-s1023

Next you’ll need to patch Windows 8 SDK

1. Parts of Chromium build using the winrt headers included with the Windows 8 SDK. All the headers we use, including the WRL, can be compiled with Visual C++ 2010 with the exception of one file, asyncinfo.h. This file uses a strongly typed enum which the VS2010 compiler doesn’t understand. To workaround this for the time being, a small patch needs to be applied to the Windows 8 SDK to build with the winrt headers in VS2010:

   Patch for Includewinrtasyncinfo.h

   Index: asyncinfo.h

   ===================================================================

   — asyncinfo.h

   +++ asyncinfo.h

   @@ -63,7 +63,7 @@

    #pragma once

    #ifdef __cplusplus

    namespace ABI { namespace Windows { namespace Foundation {

   -enum class AsyncStatus {

   +enum /*class*/ AsyncStatus {

      Started = 0,

      Completed, 

      Canceled, 
   This patch should be applied to the file “Includewinrtasyncinfo.h” located in your Windows 8 SDK directory. If this patch is not applied, the parts of Chromium that use the Winrt headers will not compile.
   Note: By default the Windows 8 SDK will install to C:Program Files (x86)Windows Kits8.0. This directory will require admin privileges to write to. Easiest way to do apply this patch is tostart an administrative command prompt, cd to C:Program Files (x86)Windows Kits8.0Includewinrt, run notepad.exe asyncinfo.h and comment out or delete the word “class” on line 66.
   Note: For Googlers, this patch has already been applied to your SDK, everything should Just Work.
1. (Optional) Install cygwin

Next Build Chromium.

First of all you need to download the depot_tools from here . or the installer ( the installer is not from The Chromium Authors but I creatd it for you to easily extract it without have to waiting for a long time

After you have download it extract it to C: . Next you will need to :

1. Check out the source code using a direct svn or git checkout. Do not use a tarball since it is not compatible with Windows’ svn client.
2. Set up the component build (or else creating chrome_dll.pdb may fail laterl) and then regenerate the build files by running “gclient runhooks –force” in a cygwin/cmd window.
3. Install API keys.
4. Open the chrome/chrome.sln solution file in Visual Studio and build the solution. This can take from 10 minutes to 2 hours. More likely 1 hour.
5. If you just want the Chromium browser, and none of the tests, you can speed up your build by right-clicking the chrome project in the solution explorer and selecting Build. You may want to make sure this project is the Startup project (which will display as bold) by right-clicking it and selecting Set as Startup Project. This will make Chromium (as opposed to some random test) build and run when you press F5.

[alert style=”yellow”] This Step was originally taken from Chromium Project Page. [/alert]

How does Adblock Plus block addresses?

The hard work here is actually done by Gecko, the engine on top of which Firefox, Thunderbird and other applications are built. It allows something called “content policies”. A content policy is simply a JavaScript (or C++) object that gets called whenever the browser needs to load something. It can then look at the address that should be loaded and some other data and decide whether it should be allowed. There is a number of built-in content policies (when you define which sites shouldn’t be allowed to load images in Firefox or SeaMonkey, you are actually configuring one of these built-in content policies) and any extension can register one. So all that Adblock Plus has to do is to register its content policy, other than that there is only application logic to decide which addresses to block and user interface code to allow configuration of filters.

For developers: to register a content policy you have to write an XPCOM component that should implement the nsIContentPolicy interface. Make sure to adjust the module’s registerSelf method to register your component in the “content-policy” category (use the category manager for this). That’s it, now your component’s shouldLoad method will be called and you can decide whether the specific request should be accepted or not.

How does Adblock Plus process its filters and which filters are faster?

All filters a translated into regular expressions internally, even the ones that haven’t been specified as such. For example, the filter adbanner.gif| will be translated into the regular expression/ad.banner.gif$/. However, when Adblock Plus is given an address that should be checked against all filters it doesn’t simply test all filters one after another — that would slow down the browsing unnecessarily.

Besides of translating filters into regular expressions Adblock Plus also tries to extract text information from them. What it needs is a unique string of eight characters (a “shortcut”) that must be present in every address matched by the filter (the length is arbitrary, eight just seems reasonable here). For example, if you have a filter |http://ad.* then Adblock Plus has the choice between “http://a”, “ttp://ad” and “tp://ad.”, any of these strings will always be present in whatever this filter will match. Unfortunately finding a shortcut for filters that simply don’t have eight characters unbroken by wildcards or for filters that have been specified as regular expressions is impossible.

All shortcuts are put into a lookup table, Adblock Plus can find the filter by its shortcut very efficiently. Then, when a specific address has to be tested Adblock Plus will first look for known shortcuts there (this can be done very fast, the time needed is almost independent from the number of shortcuts). Only when a shortcut is found the string will be tested against the regular expression of the corresponding filter. However, filters without a shortcut still have to be tested one after another which is slow.

To sum up: which filters should be used to make a filter list fast? You should use as few regular expressions as possible, those are always slow. You also should make sure that simple filters have at least eight characters of unbroken text (meaning that these don’t contain any characters with a special meaning like *), otherwise they will be just as slow as regular expressions. But with filters that qualify it doesn’t matter how many filters you have, the processing time is always the same. That means that if you need 20 simple filters to replace one regular expression then it is still worth it. Speaking of which — the deregifier is very recommendable.

The filter matching algorithm in detail

How does element hiding work?

Element hiding rules are translated into CSS and applied to all web pages the user is visiting. A rule like example.com#div(evil_ad) then looks like:

@-moz-document domain(example.com)
{
  div#evil_ad, div.evil_ad
  {
    display: none !important;
  }
}

@-moz-document is a proposed extension to the CSS standard, you can read more about it in theMozilla Developer Center.

Rules that are not restricted to a certain domain will be restricted to the protocols http:// and https:// to prevent them from hiding elements of the browser’s user interface (it is using the chrome:// protocol scheme). For example the rule #div(evil_ad) will be translated into:

@-moz-document url-prefix(http://),url-prefix(https://)
{
  div#evil_ad, div.evil_ad
  {
    display: none !important;
  }
}

For developers: Adblock Plus is using the stylesheet service here. This interface came with Gecko 1.8 and allows extensions to add user stylesheets dynamically (before that you could only modify userContent.css which requires you to restart the browser). User stylesheets will overwrite CSS code of all web sites, they have the highest possible importance.

[alert style=”yellow”] This is what we found on adblockplus wiki[/alert]

[alert style=”yellow”] Source : adblockplus wiki[/alert]

How AdBlockPlus give effect to bloggers

With Adblock many users wanted to block ads from youtube,but meanwhile when you surf website example my website the advertisement in this website also will be hidden.In this case the adblock will make our revenue decreased and hard to earn money from that ads.