Does it ever just amaze you how hard it is to simply move C code from one project to another I'm about to try this and project A uses makefiles and project B uses cmake and i'm expecting just the build system step to take forevverrr
-
-
Replying to @mcclure111
Just throw out the build system. I've literally found programs with horrible build monstrosities where "gcc *.c" worked.
1 reply 0 retweets 4 likes -
Replying to @RichFelker @mcclure111
Of course that's a a rare and lucky case, but the general procedure of "figure out what their awful build system intends to do and reproduce it with 10 lines of make" is fairly reliable.
1 reply 0 retweets 1 like -
Replying to @RichFelker @mcclure111
Yeah, half of the time it seems like all they're doing in a billion lines of autoconf is automatically setting up about three lines of cflags that it takes five minutes to configure manually.
1 reply 0 retweets 1 like -
And "detecting ncurses" - who doesn't have ncurses? Okay, the dev package, but... will this thing build without ncurses, or just shame me for not having it? Can't a linker error do the same thing?
1 reply 0 retweets 0 likes -
Replying to @Random832 @RichFelker
I don't think I had ncurses on old os x
2 replies 0 retweets 1 like
Absolutely. If you're able to support configurations with or without a library, or with one of several alts, configure-time test makes sense. Otherwise little value over link failure.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.