Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is mklove already a drop in replacement for autoconf? #26

Open
ShalokShalom opened this issue Jun 25, 2017 · 6 comments
Open

Is mklove already a drop in replacement for autoconf? #26

ShalokShalom opened this issue Jun 25, 2017 · 6 comments
Labels

Comments

@ShalokShalom
Copy link

Is mklove already a drop in replacement for autoconf?

@edenhill
Copy link
Owner

For most cases I'd say yes, it is being used successfully for librdkafka, kafkacat and other projects.
It is surface-compatible enough with autoconf to be fool both Debian and RPM package creation programs ' autotool modes.

Users report it working on Linux (multitude of distros), OSX, FreeBSD, Solaris, ..).

There are most likely cases where autotools is more complete or provides better porting, but for most normal uses mklove is sufficient and by far simpler to work with, understand and faster than autotools.

If you decide to give it a try, dont hesitate to reach out for guidance or issues.

@ShalokShalom
Copy link
Author

I mean, can i package a distro with it?

@edenhill
Copy link
Owner

Not sure I understand what you mean by distro, can you elaborate?
Thanks

@ShalokShalom
Copy link
Author

Distribution. An operating system

@edenhill
Copy link
Owner

mklove is a portable build tool, much like autoconf, it is not used for packaging.

@ShalokShalom
Copy link
Author

You can package without a build tool?

@ShalokShalom ShalokShalom reopened this Jun 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants