If source code won't compile simply by running make, is it worth my time to load the source into an IDE (I have kdevelop4) and attempting to track down and fix potential errors?
I know that's a loaded question, but I'm open to any advice. I have hellabytes of evidence that there are giga-experts on this forum. (I would have used the prefix mega-, but I think some people are beyond that.)
Granted, I'm a n00b to Linux, but I do have some programming experience (I know the difference between a for...next loop and a while loop :blink:, and between a type and a structure :dance:, etc.). What I don't have is much practical experience. (i.e., deconstructing someone else's code and finding the glitches.)
When I have run a build on source through kdevelop, the errors that are found are, generally, simplistic, but how am I to know if making changes won't make the matter worse, without understanding the entire scheme? If it comes down to a trial and error scenario, I can accept that.
I guess it comes down to whether it's potentially fixable, or just a fool's errand to mess with someone's code. :bang:
I know that's a loaded question, but I'm open to any advice. I have hellabytes of evidence that there are giga-experts on this forum. (I would have used the prefix mega-, but I think some people are beyond that.)
Granted, I'm a n00b to Linux, but I do have some programming experience (I know the difference between a for...next loop and a while loop :blink:, and between a type and a structure :dance:, etc.). What I don't have is much practical experience. (i.e., deconstructing someone else's code and finding the glitches.)
When I have run a build on source through kdevelop, the errors that are found are, generally, simplistic, but how am I to know if making changes won't make the matter worse, without understanding the entire scheme? If it comes down to a trial and error scenario, I can accept that.
I guess it comes down to whether it's potentially fixable, or just a fool's errand to mess with someone's code. :bang:
