Skip to content
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

Closed
Bodekaer opened this issue Oct 31, 2014 · 10 comments
Closed

CEF 2171.1899 update #20

Bodekaer opened this issue Oct 31, 2014 · 10 comments

Comments

@Bodekaer
Copy link
Contributor

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 :)

@amaitland
Copy link
Member

@Bodekaer Do you need VS2012 libs? If your only interested in VS2013 then you can always comment out

https://github.com/cefsharp/cef-binary/blob/cef/trunk/build.ps1#L430

@Bodekaer
Copy link
Contributor Author

Yeah, I just did it actually. Compiling as we speak :)
It just wouldn't feel right to create a PR without VS2012.

I'm re-installing VS2012 to see if that helps too.

@amaitland
Copy link
Member

It just wouldn't feel right to create a PR without VS2012

Just revert that change directly before creating the PR 😄

@amaitland
Copy link
Member

My guess is that you'll need the relevant Windows SDK to make it work properly.

@Bodekaer
Copy link
Contributor Author

Yeah, turns out I just had a faulty install of VS2012. (never use it anymore)
Just re-installed and it appears to be compiling perfectly fine now.

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?

@jornh
Copy link
Contributor

jornh commented Oct 31, 2014

In the VS NuGet dialog you can configure a NuGet source simply by pointing to a local path.

@jornh
Copy link
Contributor

jornh commented Oct 31, 2014

@amaitland
Copy link
Member

When testing with the MinimalExample I usually just put a entry in the Nuget.config file

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>

@Bodekaer
Copy link
Contributor Author

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! :)

@Bodekaer
Copy link
Contributor Author

Created PR #21
Not sure if this is relevant or not for others. Mainly for spell checking support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants