I'm porting Eclipse C++ project builds (ugly) to something more reliable. My C++ projects consist of many-many libraries and executable files. So, as a test, I ported a few to to TUP, and it works great. However, a co-worker asked, "Why not just use make instead? It's in all the servers and works great." My reply was: "Auto-dependency detection and speed." Now, speed is very nice but it isn't much of an issue in our case. Then, he said that given the right inputs (.cpp, .h, .d files. etc.), make can deal with dependencies if used along with GNU -MD flag to generate the 'd' files, etc.
What's your take on this never-ending debate? (I.e. I couldn't convince him of tup's superiority). -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tup-users/7060f6d5-b72b-4389-99e9-ca945c2a7b11%40googlegroups.com.
