3 ms·
We built cross platform tools with shared libs long before libtools existed. Removal would be best. Flex is OK. It doesn't produce clean warning-free idiomatic
by burfog 7y ago
We built cross platform tools with shared libs long before libtools existed. Removal would be best.
Flex is OK. It doesn't produce clean warning-free idiomatic C99 (or even C11) source code. The historical defaults, for lex compatibility that isn't needed anymore, are not good.
- hrgiger 7y agoI am currently digging around build tools, can you give some examples how did you manage your builds without libtools? Currently messing with LFS, its heavily using as far as I understand. Only openssl explained their decision why they didnt choose libtool path[0] [https://www.openssl.org/docs/faq.html#MISC5 https://www.openssl.org/docs/faq.html#MISC5] (Why aren't tools like 'autoconf' and 'libtool' or 'cmake' used?)
- burfog 7y agoPlain old make will work. The older style would have a separate target for each platform that is supported. The newer style is more like how the Linux kernel build system works, with += operators in the Makefile to add options and put things in lists. Last time I used it, I found libtool to be a real mess. It had shell scripts pretending to be object files. That is simply not acceptable. There were way too many layers of gunk, making it difficult to have good control over what was being created.
- rurban 7y agoNo, removal would be worst. You cannot harm thousands of projects just because you think you won't need it. I'm also annoyed for needing to do libtool -mode=execute gdb..., but that's life. It can be aliased to something shorter maybe.