Timeline for What are good ways to organize input files (Makefiles, SConstruct, CMakeLists.txt, etc.) to build automation software?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 5, 2012 at 19:48 | comment | added | Geoff Oxberry | I've added examples to illustrate what I'm working with right now. | |
| Feb 5, 2012 at 6:42 | comment | added | user1249 | Then consider showing some of your actual problems and why your current solution isn't good enough. Also, it is actually important that this is in academia. | |
| Feb 5, 2012 at 0:54 | comment | added | Geoff Oxberry | I agree that GNU Autoconf was made for portability and maintainability of builds. At one point, I investigated learning Autoconf and found that it was going to take more time than I was willing to invest. (I'm finishing my PhD, so building this software needs to happen sooner rather than later.) Perhaps in the future? Portability isn't even the main issue for me, it's the length and lack of modularity in the build scripts, and I'm not sure that porting to Autoconf will solve those problems. | |
| Feb 4, 2012 at 7:43 | history | answered | user1249 | CC BY-SA 3.0 |