anonymous
  • anonymous
C/C++ :: In a previous question, i've asked if it was a good idea to #include ALL sources in one big file and compile that single file, and now I know it isn't. What is the best way to engineer a large C/C++ program in general?
Computer Science
  • Stacey Warren - Expert brainly.com
Hey! We 've verified this expert answer for you, click below to unlock the details :)
SOLVED
At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate non provident, similique sunt in culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga. Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus, omnis voluptas assumenda est, omnis dolor repellendus. Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat.
jamiebookeater
  • jamiebookeater
I got my questions answered at brainly.com in under 10 minutes. Go to brainly.com now for free help!
anonymous
  • anonymous
autoconf and automake?
anonymous
  • anonymous
but that's if you have a large development enviroment
anonymous
  • anonymous
or using "make" sorry for the chain responses lol

Looking for something else?

Not the answer you are looking for? Search for more explanations.

More answers

anonymous
  • anonymous
I like cmake a lot. It's trivial to whip up a cmake configuration file for a small project, but still not difficult to extend it as the project grows. It can generate *nix makefiles, MSVC solutions and XCode projects, integrates well with Qt and other frameworks, and has good documentation. More generally, the answer to your question is modularity. Identify things that belong together and develop them as a library for a particular purpose from the start. Imagine someone else using the library in a project different from yours and try to anticipate problems they might have with your libraries' API. This will make sure code for each purpose (each library) stays contained and maintainable. Splitting things up into libraries is one of the best things you can do for maintainability and reusability - and it helps build times, too ;)

Looking for something else?

Not the answer you are looking for? Search for more explanations.