Build time
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Build time
For those of you who are building Pale Moon, for whatever release, who long does it take to build (not package)?
On my Mac I have found that it takes over 2 hours.
Building on a QuadCore it took an hour an an hour and 44 mins.
Building on an i7 with 32 GB RAM took 43 mins.
How does your machine fare?
On my Mac I have found that it takes over 2 hours.
Building on a QuadCore it took an hour an an hour and 44 mins.
Building on an i7 with 32 GB RAM took 43 mins.
How does your machine fare?
Last edited by Kendo on 2021-02-02, 08:44, edited 1 time in total.
Re: Build time
Sorry but that answer is not helpful.
Re: Build time
It depends on what you are building as well as your hardware. I hardly see a reason for this thread to exist. How does build time relate to development.
Re: Build time
I didn't say I didn't understand it I just don't see the relevance.
Re: Build time
The revlevance is "build time" as the topic is aptly named. When developing or modifying the source we need to build and test, right?New Tobin Paradigm wrote: ↑2021-02-02, 08:52I didn't say I didn't understand it I just don't see the relevance.
I used to type in "./mach build' and have enough time to go and mow the lawn which is 4 acres.
Comprendez?
Re: Build time
Yeah but what are other people's build times gonna do for you?
Re: Build time
(ryzen 7-2700 & 32Gb ram)23:03.44 We know it took a while, but your build finally finished successfully!
..now can I have my participation cookie, pretty please :shh:
voidlinux_x64 glibc-2.38 / Palemoon_latest release (gcc-13.2.0) / GTK2
Re: Build time
If you need to know, wait and find out.New Tobin Paradigm wrote: ↑2021-02-02, 09:14Yeah but what are other people's build times gonna do for you?
Re: Build time
In that case you're talking about a few minutes unless you clobber every time (which you shouldn't). My incremental build times tend to be 2.5-5 minutes depending on how much of the tree needs to be rebuilt due to the code change. Sometimes more if I touch e.g. broadly-used C++ headers.
The initial build will take longer if you just made a new checkout.
Build time depends on many factors. Having people just spout their hardware and their latest clobber build time is no indication of when you are developing.
Build time can take from a few minutes (incremental) to a number of hours (clobber) depending on:
- What you are building
- Your buildconfig
- Incremental or clobber
- How many threads you tell it to use
- The number of cores you have available
- The amount of RAM you have available
- How fast your disk is
- Which O.S. you are building for (and which compiler you are using as a result)
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Build time
I do every time because it prevents over write problems. It doesn't happen often, but on odd occasion I get complaints about write permissions on existing files and either have to reboot or build into a different folder. No files or folders were open in any other application.
Re: Build time
You should fix your build box so you don't run into that kind of issue when doing an incremental build.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Build time
Not sure what else I can do because I do use a specific folder and not the auto generated oen at "object blah blah" so that I can set write permissions for "everyone". Also have UAC disabled, but occasionally (not often) do get build errors because a "file" is not writable.
Re: Build time
Do you have other processes "monitoring" your file system? antivirus or the likes? That can interfere.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite