我已经使用Chromium代码库一段时间了，并习惯了它的基础库（又名libchrome） 。 问题在于，虽然这个库很棒且功能多样，但并不打算在Chromium之外使用，因此将它用作独立库是非常有问题的。
图书馆的页面指出，对于其他Google的项目，他们要么发布了一些内部包，要么使用了可用于构建库的scons构建脚本 。 不幸的是，这个脚本和它的更新版本都不允许我编译它。 我遇到了一些关于错误标志或缺少输入文件的错误。 可能有些补丁放在与脚本相同的目录中可能有所帮助，但没有描述使用哪个和按什么顺序。
在一些博客上，我发现有人建议可以获取整个Chromium，连同其工具链，并将其配置为仅构建一个库。 但是那样会很慢，而且不够便携。 如果我有一天会发展一些严重的事情，它会迫使人们下载许多不必要的东西。
你们中的任何人都知道建立这个库的快速可靠的方法吗？ 它可能会更复杂，只要它可以通过脚本自动化并且不会创建一个PATH变量并下载几GB的开销数据。
I've been working with Chromium codebase for some time and get accustomed to its great base library (aka libchrome). The problem is that while great and versatile this library wasn't intended to be used outside of Chromium so it is really problematic to use it as a standalone library.
Library's page states that for other Google's projects they either released some inner packages or used scons build script which can be used for building the library. Unfortunately neither this script nor its more recent version allowed me to compile it. I'v got some errors either about wrong flags or missing input files. Possibly some of patches placed in the same directory as script could help but there is not description which to use and in what order.
On some blog I found suggestion that one could fetch whole Chromium instead, together with its toolchain and configure it to build just that one library. But that would be really slow and not very portable. If I were to develop something serious one day it would force people to download a lot of unnecessary stuff.
Do any of you know some fast and reliable way to build that library? It might be more complicated as long as it could be automated by a script and don't make one setup PATH variables and download several GB of overhead data.
最满意答案
mini_chromium提供了基本库的独立版本，但不提供Windows版本。 如果你需要这些，你必须添加自己。
mini_chromium provides a standalone build of the base lib but does not provide Windows builds. If you need those you'll have to add yourself.
更多推荐
发布评论