- This topic has 5 replies, 2 voices, and was last updated Jan 28-1:41 pm by Brian Masinick.
-
Posts
-
Brian Masinick
https://chromium.googlesource.com/chromium/src/+/master/docs/linux/build_instructions.md contains the instructions to build the Chromium Web browser for Linux. It is also possible to build Chromium from source code from other platforms. See the googlesource site for additional information.
--
Brian MasinickAnonymous
(thanks for sharing the link, but)
as stevo @ MX can confirm… specific to Chromium, it is now impractical (impossible, essentially) to attempt using a desktop computer to “build Chromium from source code”. Anyone hoping to do so should look into setting up a (free) OBS opensuse build service account and performing the build on their serverfarm.Brian Masinick
It does require a LOT of space and over 30 minutes just to get the components to put it together.
It is possible to build it for anyone determined to do so, but it is unnecessary with binary packages available.
One reason I made these available is so the paranoid people can examine the code.
The other reason is to show that it takes a lot of time and effort to build good software and these are examples of code that people have recently been questioning.
Source code is easy to find but it is helpful to have a powerful server on which to build your code!
--
Brian Masinickso the paranoid people can examine the code
Toward studying the source code (firefox has 60,000+ files) I can recommend:
install “recoll” full text indexer.
Do not enable automatic (daemon) indexing. Manually set the top-level directory of the {e.g. firefox} source code as the location to be indexed, and run the indexer. Using recoll to search “whereall in the code is thing suchandsuch mentioned” is much easier than grep()ingBrian Masinick
Even with the source code it isn’t easy to locate various features and that is why so few people work directly with source code. Your suggestion does make it easier to locate specific strings, thanks!
Those who build code all the time, especially if it is the same package almost undoubtedly automate as much of the process as possible; I certainly did when I built code on my systems. At one point I had three workstations in my office and access to many multiprocessor servers. I could use one workstation for everyday tasks, such as Email and Web browsing. I would also interact with the servers from the primary workstation. The second one was to test new daily image builds and localization. The third workstation had the current version of Windows to ensure interoperability between UNIX and Windows. It’s nice to have good hardware and software when you develop and test operating systems.
Regarding huge programs, when you have the right resources it’s possible to build multiple things at the same time. We’d do Nightly Builds of the entire OS and application teams would also build their application software on a regular basis.
--
Brian MasinickBrian Masinick
Most of us cannot build huge programs at home unless we own servers ourselves (I do know a few people who have, or at one point had servers in their home, usually in a basement or office room, not in a common living area). That’s not very common either.
--
Brian Masinick
- You must be logged in to reply to this topic.
