-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CEF 2171.1899 update #20
Comments
@Bodekaer Do you need https://github.com/cefsharp/cef-binary/blob/cef/trunk/build.ps1#L430 |
Yeah, I just did it actually. Compiling as we speak :) I'm re-installing VS2012 to see if that helps too. |
Just revert that change directly before creating the PR 😄 |
My guess is that you'll need the relevant |
Yeah, turns out I just had a faulty install of VS2012. (never use it anymore) Question: What's the next step? Do I need to wait for you to upload the NuGet somehow, or can I somehow locally start using the NuGet right away? |
In the VS NuGet dialog you can configure a NuGet source simply by pointing to a local path. |
When testing with the https://github.com/cefsharp/CefSharp.MinimalExample/blob/master/NuGet.config Sample <?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="nuget.org" value="https://nuget.org/api/v2/" />
<add key="staging.nuget.org" value="https://staging.nuget.org/api/v2/" />
<add key="localPackages" value="c:\projects\cef-binary\nuget" />
</packageSources>
<activePackageSource>
<add key="All" value="(Aggregate source)" />
</activePackageSource>
</configuration>
|
Works! Thanks a lot. Everything seems to be fine. I just had to make a minor update to CefSharp.Core to support the "Inspect Element At" feature for DevTools, which I assume was a new feature recently added to CEF. We now have native spell checker! Yeah! :) |
Created PR #21 |
Hey,
I've successfully compiled the VS 2013 build (both x86 and x64).
However VS 2012 fails in build.ps1, with:
CL.exe exited with code -1073741515
I found this info, which might help:
http://stackoverflow.com/questions/22038660/visual-studio-2013-cl-exe-exited-with-code-1073741515
Any ideas/suggestions @peters and @jornh? It's probably an easy fix for you guys :)
The text was updated successfully, but these errors were encountered: