Switch to gyp

installer/adblockplusie.wxs

 <?xml version="1.0" encoding="UTF-8"?>
 <!--
   Compilation Note:
   You may see linking errors that look like these:
     <quote>LGHT0217 : Error executing ICE action 'ICExx' [...] The error code is 2738.</quote>
   The documentation for this error code talks about custom actions,
     even though the CustomAction keyword does not appear in this source.
   Certain WiX elements are implemented by MSI custom actions,
     which means this source implicitly declares some insofar as the Windows Installer sees it.
   These errors are benign and can be avoided by some fiddling with the registry on the development machine.
@@ skipping 196 matching lines @@
       The present installer is a per-machine installer.
       That means it writes to HKEY_LOCAL_MACHINE, so that all users on the machine will have the BHO installed.
       It's possible to write keys to HKEY_CURRENT_USER in a situation where that's not desirable, if needed.
     -->
     <ComponentGroup Id="Binaries" Directory="INSTALLFOLDER">
       <!--
         The 32-bit version of the DLL is included in both 32- and 64-bit installers.
         We need an explicit value for attribute @Win64 so that the ARCH argument does not override its implicit value.
       -->
       <Component Id="AdblockPlus32.dll" Guid="d9a35780-d712-11e2-8b8b-0800200c9a66" Win64="no">
-        <File Id="AdblockPlus32.dll" Source="..\build\ia32\$(var.Configuration)\AdblockPlus.dll" KeyPath="yes" Checksum="yes">
+        <File Id="AdblockPlus32.dll" Name="AdblockPlus32.dll" Source="..\build\ia32\$(var.Configuration)\AdblockPlus.dll" KeyPath="yes" Checksum="yes">
           <?include dll_class.wxi ?>
         </File>
         <?include bho_registry_value.wxi ?>
       </Component>
       <!--
         The 64-bit version of the DLL is only included in the 64-bit installer.
         We don't really need an explicit value for attribute @Win64, but it's there for resilience.
 
         Note that the <Class> element and the <RegistryKey> element are duplicated from the 32-bit version.
         We use "include" directives to ensure that they are identical.
         They have to be the same to support both the 32- and 64-bit versions of Internet Explorer on a 64-bit system.
         IE uses the same algorithm to search for BHO regardless of platform,
           so with two versions of IE, we need two identical registrations.
         The 32-bit version on a 64-bit system will be registered under "Wow6432Node" translated keys,
           while the 64-bit version will be under the keys as they appear in this source, not translated.
         We don't need to put in the "Wow6432Node" registry key explicitly;
           something in Windows Installer takes care of the mapping transparently.
       -->
       <?if $(sys.BUILDARCH)="x64"?>
         <Component Id="AdblockPlus64.dll" Guid="ed77a2c0-d712-11e2-8b8b-0800200c9a66" Win64="yes">
-          <File Id="AdblockPlus64.dll" Source="..\build\x64\$(var.Configuration)\AdblockPlusx64.dll" KeyPath="yes" Checksum="yes">
+          <File Id="AdblockPlus64.dll" Name="AdblockPlus64.dll" Source="..\build\x64\$(var.Configuration)\AdblockPlus.dll" KeyPath="yes" Checksum="yes">
             <?include dll_class.wxi ?>
           </File>
           <?include bho_registry_value.wxi ?>
         </Component>
       <?endif?>
 
       <!--
         The engine must go into the same directory as the DLL, since that location is searched explicitly (and uniquely).
       -->
       <?if $(sys.BUILDARCH)="x86"?>
@@ skipping 26 matching lines @@
       <ComponentRef Id="html_static_img_social_gplus.png"/>
       <ComponentRef Id="html_static_img_social_twitter.png"/>
       <ComponentRef Id="html_static_js_IESettings.js"/>
       <ComponentRef Id="html_static_js_settings.js"/>
       <ComponentRef Id="html_static_js_vendor_DD.belatedPNG.js"/>
       <ComponentRef Id="html_static_js_vendor_html5shiv.js"/>
       <ComponentRef Id="html_templates_index.html"/>
     </ComponentGroup>
 
     <DirectoryRef Id="HTML_Folder">
-      <Directory Id="html" FileSource="SourceDir\..\html">
+      <Directory Id="html" FileSource="..\html">
         <Directory Name="static" Id="html_static">
           <Directory Name="css" Id="html_static_css">
             <Component Id="html_static_css_settings.css" Guid="07173c90-d713-11e2-8b8b-0800200c9a66">
               <File Name="settings.css"/>
             </Component>
           </Directory>
           <Directory Name="img" Id="html_static_img">
             <Component Id="html_static_img_abp.128.png" Guid="0d86ba60-d713-11e2-8b8b-0800200c9a66">
               <File Name="abp-128.png"/>
             </Component>
@@ skipping 60 matching lines @@
     </DirectoryRef>
 
     <!--
       Locale files
     -->
     <ComponentGroup Id="Locale_Files">
       <ComponentRef Id="locales_en.ini"/>
       <ComponentRef Id="locales_ru.ini"/>
     </ComponentGroup>
     <DirectoryRef Id="Locales_Folder">
-      <Directory Id="locales" FileSource="SourceDir\..\locales">
+      <Directory Id="locales" FileSource="..\locales">
         <Component Id="locales_en.ini" Guid="c5622430-d713-11e2-8b8b-0800200c9a66">
           <File Name="en.ini"/>
         </Component>
         <Component Id="locales_ru.ini" Guid="d06e3490-d713-11e2-8b8b-0800200c9a66">
           <File Name="ru.ini"/>
         </Component>
       </Directory>
     </DirectoryRef>
 
     <!--
       INI files
 
       The settings.ini file should not be installed this way, since it contains user-generated data.
       A component in Windows Installer represents a fixed piece of data with the MSI, not a changing one.
       The present method of making settings.ini a component is simply an expedient for the present,
         not a permanent solution.
       The correct solution requires the application to manage this file; the installer can't do it right.
       See http://stackoverflow.com/questions/357911/manage-configuration-files-with-wix
     -->
     <ComponentGroup Id="INI_Files">
       <ComponentRef Id="ini_settings.ini"/>
     </ComponentGroup>
     <DirectoryRef Id="ABP_APPDATA_FOLDER">
-      <Directory Id="ini" FileSource="SourceDir\..\files">
+      <Directory Id="ini" FileSource="..\files">
         <Component Id="ini_settings.ini" Guid="dc30c3b0-d713-11e2-8b8b-0800200c9a66">
           <File Name="settings.ini"/>
         </Component>
       </Directory>
     </DirectoryRef>
   </Product>
 </Wix>