title: No dependency HTML (CSS, JS) Rendering Engine
body: <p><strong><em>I am using c++</em></strong></p>
  
  <p>I am developing an in-game ui to be used in any arbitrary process that I want it to run on. Basically I want it to be able to work on any application that uses lets say DX9.</p>
  
  <p>But that really isn't my question, what I want to be able to do is use HTML and (JS, CSS) to render my UI. </p>
  
  <p>I would love to use something like Awesomium or the Chromium Embedded Framework but both seem to require you to have 5+ dependencies (dlls, etc) and require you to have to have them the same directory as the parent application.</p>
  
  <p>Now because I will be injecting a dll that does this, I don't exactly want to or have a way to get the dependencies in the right location for it to work properly.</p>
  
  <p><em>I definitely do not want all the misc dependencies to be lying in the same folder as the target process</em></p>
  
  <p>I would like to use something that is possibly either a static lib or one dll as a dependency.</p>
  
  <p>The other issue is, it seems that CEF and Awesomium are some of the only ones that actually have a decent callback system between javascript and C++. </p>
  
  <p>I guess what I need to know is, Is their a way to keep all the Awesomium  / CEF dependencies in one folder and reference them from any application? Or are there any better solutions to use. </p>
  
  <p><em>I have also seen Sciter, which seems to be a good option, but uses something similar to JavaScript but not exactly, which is not ideal.</em></p>
  
  <p>A bit more info, based on these remarks : </p>
  
  <blockquote>
    <p>The directory from which the application loaded.
    The system directory. Use the GetSystemDirectory function to get the path of this directory.
    The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched.
    The Windows directory. Use the GetWindowsDirectory function to get the path of this directory.
    The current directory.
    The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key. The App Paths key is not used when computing the DLL search path.</p>
  </blockquote>
  
  <p>Dlls should not be too much of an issue, but I'll have to look into some of the other stuff.</p>