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

Discussion: Autotools will be deprecated in v1.3.0 #431

Closed
xor-gate opened this issue Jun 7, 2016 · 4 comments · Fixed by #434
Closed

Discussion: Autotools will be deprecated in v1.3.0 #431

xor-gate opened this issue Jun 7, 2016 · 4 comments · Fixed by #434

Comments

@xor-gate
Copy link
Member

xor-gate commented Jun 7, 2016

As per 2.0.0 I will deprecate the use of autotools (autoconf, automake). As it is not as cross-platform minded as CMake. And I am unable to maintain two build systems. Installing on windows autotools is a pain and I want to create IDE or console projects. The reasons why I only want to support CMake:

  • No obsecure m4-macro system, and have a decent programming language (no wrapped shell commands) for the build system
    • Loops
    • Conditionals
    • Variables
  • Easy to maintain different targets with different compiler flags
  • Generate files (from templates) in a cross-platform fashion (not using sed,grep awk etc)
  • Builtin testing facility (CTest)
  • Builtin packaging facility (CPack)
  • Multiple output generators (Make, Xcode (OSX), Visual Studio)

One current use-case is:
Generate a version.h from version.h.in template and use it to notify users which version they run. Completely automatic created from git tags or version.txt file.

@xor-gate xor-gate added this to the v2.0.0 milestone Jun 7, 2016
@xor-gate xor-gate self-assigned this Jun 7, 2016
@texane
Copy link
Collaborator

texane commented Jun 7, 2016

I agree with you. So lets deprecate autotools, unless there is a strong
argument about keeping it.

2016-06-07 19:24 GMT+02:00 Jerry Jacobs [email protected]:

As per 2.0.0 I will deprecate the use of autotools (autoconf, automake).
As it is not as cross-platform minded as CMake. And I am unable to maintain
two build systems. Installing on windows autotools is a pain and I want to
create IDE or console projects. The reasons why I only want to support
CMake:

  • No obsecure m4-macro system, and have a decent programming language
    for the build system
  • Easy to maintain different targets with different compiler flags
  • Generate files (from templates) in a cross-platform fashion (not
    using sed,grep awk etc)
  • Builtin testing facility (CTest)
  • Builtin packaging facility (CPack)
  • Multiple output generators (Make, Xcode (OSX), Visual Studio)

One current use-case is:
Generate a version.h from version.h.in template and use it to notify
users which version they run. Completely automatic created from git tags or
version.txt file.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#431, or mute the thread
https://github.com/notifications/unsubscribe/AAEeH3XDBnmV08vu78bHzfUhaKTGUqO0ks5qJalfgaJpZM4IwKam
.

@xor-gate
Copy link
Member Author

xor-gate commented Jun 7, 2016

Thank you @texane for the feedback, there are tons of other nice features why we should stick with cmake (e.g dependency download during build). I will keep things posted here when I need some discussion.

@rikvdh
Copy link

rikvdh commented Jun 7, 2016

👍 for CMake, I see no point in keeping autotools as well.

@xor-gate
Copy link
Member Author

Fixed by PR #434

@xor-gate xor-gate changed the title Discussion: Autotools will be deprecated in 2.0.0 Discussion: Autotools will be deprecated in v1.3.0 Sep 25, 2016
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Apr 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants