Sharing your Compiling Configurations
Posted: Sun 29 Apr 2012, 17:39
I've been doing some compiling here and there for a couple of months now and wish for a system where compiled configurations for pets can be easily shared amongst compilers.
Yes, there is the "Compiling" section in this forum, but if one goes there, you will find that there is only currently 2 pages of info in that thread, compared to the plethora of pets that have been compiled for Puppy. There were a few instances, while reading the forum I came across a message similar to: "The pet was compiled by ...so and so, but we cannot tell what compiling options he (or she) used."
Without knowing these compiling options, for the previously (well-built) pet, it leaves other compilers with the task of:
- doing the research, looking at all of the availiable compiling options
- enabling and disabling various compilation options
This is basically re-inventing the wheel.
While this process is great when you are starting out and learning, after time it becomes a chore.
And considering the amount of linux apps out there, I see this as incredible waste of time.
I think that if we adopted some sort of system, where compilers share their options/techniques, productivity for the entire community would be increased, as we wouldn't be spending so much time re-inventing the wheel.
So, by what method(s) can we adopt to encourage sharing of this information? Please see the next post...
Yes, there is the "Compiling" section in this forum, but if one goes there, you will find that there is only currently 2 pages of info in that thread, compared to the plethora of pets that have been compiled for Puppy. There were a few instances, while reading the forum I came across a message similar to: "The pet was compiled by ...so and so, but we cannot tell what compiling options he (or she) used."
Without knowing these compiling options, for the previously (well-built) pet, it leaves other compilers with the task of:
- doing the research, looking at all of the availiable compiling options
- enabling and disabling various compilation options
This is basically re-inventing the wheel.
While this process is great when you are starting out and learning, after time it becomes a chore.
And considering the amount of linux apps out there, I see this as incredible waste of time.
I think that if we adopted some sort of system, where compilers share their options/techniques, productivity for the entire community would be increased, as we wouldn't be spending so much time re-inventing the wheel.
So, by what method(s) can we adopt to encourage sharing of this information? Please see the next post...