Chiebot-Mirror
/
meson
mirror of https://github.com/mesonbuild/meson.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
The Meson Build System http://mesonbuild.com/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
7500 Commits
76 Branches
171 Tags
74 MiB
Tag: Branch: Tree: 7059c47aad
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7059c47aad'
${ noResults }
meson/docs/markdown/Comparisons.md

79 lines
2.1 KiB
Raw Normal View History Unescape

docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
---
doc: Fix several minor typos.
8 years ago
title: Comparisons
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
...
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
# Comparing Meson with other build systems
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
Rewrapped more files.
7 years ago
A common question is *Why should I choose Meson over a different build
system X?* There is no one true answer to this as it depends on the
use case. Almost all build systems have all the functionality needed
to build medium-to-large projects so the decision is usually made on
other points. Here we list some pros and cons of various build systems
to help you do the decision yourself.
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
## GNU Autotools
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
### Pros
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
Rewrapped more files.
7 years ago
Excellent support for legacy Unix platforms, large selection of
existing modules.
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
### Cons
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
Rewrapped more files.
7 years ago
Needlessly slow, complicated, hard to use correctly, unreliable,
painful to debug, incomprehensible for most people, poor support for
non-Unix platforms (especially Windows).
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
## CMake
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
### Pros
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
Great support for multiple backends (Visual Studio, XCode, etc).
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
### Cons
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
Rewrapped more files.
7 years ago
The scripting language is cumbersome to work with. Some simple things
are more complicated than necessary.
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
## SCons
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
### Pros
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
Full power of Python available for defining your build.
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
### Cons
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
Rewrapped more files.
7 years ago
Slow. Requires you to pass your configuration settings on every
invocation. That is, if you do `scons OPT1 OPT2` and then just
`scons`, it will reconfigure everything without settings `OPT1` and
`OPT2`. Every other build system remembers build options from the
previous invocation.
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
## Bazel
Fix inconsistent header levels
7 years ago
### Pros
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
Proven to scale to very large projects.
Fix inconsistent header levels
7 years ago
### Cons
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
Rewrapped more files.
7 years ago
Implemented in Java. Poor Windows support. Heavily focused on Google's
way of doing things (which may be a good or a bad thing). Contributing
code requires [signing a CLA](https://bazel.build/contributing.html).
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
## Meson
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
### Pros
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
Rewrapped more files.
7 years ago
The fastest build system [see
measurements](Performance-comparison.md), user friendly, designed to
be as invisible to the developer as possible, native support for
modern tools (precompiled headers, coverage, Valgrind etc). Not Turing
complete so build definition files are easy to read and understand.
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
docs: Markdown headers don't need trailing hash signs This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
7 years ago
### Cons
docs: Import the website and wiki and build with hotdoc This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.
8 years ago
Rewrapped more files.
7 years ago
Relatively new so it does not have a large user base yet, and may thus
contain some unknown bugs. Visual Studio and XCode backends not as
high quality as Ninja one.