The problem with updating or “patching” the files in Chromium comes later when we update our code base with new code from the Chromium project. This may sound straightforward, and in some ways it is. When we specify the GN files for Vivaldi, we can’t just write those files for Vivaldi source code tasks, we also have to update the configuration of related GN files in the Chromium code base so that the application components that those files specify can connect to the code Vivaldi adds to the application. GN is a compiler that reads the project’s configuration files and outputs files used by the “Ninja” build tool, which is then used to build the application. Other projects, in particular, those based on Chromium, can benefit from using these extensions and this is the reason we’re making them available in a GitHub repository as a fork of the GN project. When we update the configuration of related GN files in the Chromium code base – so that the application components can connect to the code Vivaldi adds to the application – some “merge conflicts” occur. As part of working around this problem, we added various extensions to the GN language and decided to share them with the community. In a Chromium-based browser, such as Vivaldi, this is done by using a tool developed by Chromium called GN. One of these tasks is to specify how to build the application. When building a browser there are many tasks, both large and small, that have to be done.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |