For the moment I started from 3626 down, Windows builds only for the moment.
The idea is to have them available for various scenarios (at this time this is what I'm considering):
- users/coders needing a specific/older/legacy branch build which might or might not be up to date
- coders not having enough C++ knowledge, hardware or time to build themselves
- Mac and Linux builds (this will be quite hardware dependent, since my own falls in the category of not-so-great-hardware)
- other kind of builds (ARM, unsupported Linux distros etc.)
- libraries depending on CEF (such as CefSharp, JCef etc.)
At this time all builds will be done using standard build using vanilla command-line such as
- Code: Select all
python C:\cef\automate-git.py --download-dir=C:\cef\3578 --branch=3578 --x64-build --no-debug-build --client-distrib --sandbox-distrib
I won't do packaging and testing other than running cefclient, cefsimple and ceftests.
What I would like to hear from you guys:
- does it sounds like a good idea? (I know Spotify open source, Czarek, amaitland and others maintain such builds, but an extra help won't hurt)
- is there a need for custom/specific builds?
- are the debug builds needed?
- what should be the need and proportion for certain builds? (Meaning, maybe the branch 963 is not in high demand, but someone might have a legacy MFC/CEF1 app).
- what other wrappers/libraries/bindings are available/used (I know of a handful, but since I'm using only C++ there might be more than CefSharp, JCef, CefPython)
- anything else you can think of.