Before starting my answer, I must say that it is highly recommended to use CEF3. Reasons include:
- CEF3 is under active development, currently receiving support, improvements, and bug fixes.
- CEF3 uses modern versions of Chromium under the hood. For instance. 61 and 62 and the time of writing.
- CEF1 stuck in Chromium 27.
- CEF3 can be run in single process mode , similar to how CEF1 works. This is the biggest reason, in my opinion, it can be used. (Actually, I wonder why you want to use CEF1?)
My answer:
If you can find the branch number that you want in this archive (it has binaries for some older CEF1) or if you already have several binaries, then you cannot link them to the VS 2017 project without any problems.
If not, then you need to build CEF1 from the source. The easiest way is to satisfy the requirements for creating branch 1453 of the release (the latter to support CEF1):
- Availability VS2010
- SDK Windows 8
CEF1 VS2017. , , , .
VS2017 ++.