Welcome to Muddle’s documentation!¶
Contents:
- Introduction to Muddle
- Quick start: so you’ve been asked to work on a project using muddle
- Welcome to Muddle
- Labels
- Muddle’s view of the build process
- Build Descriptions and the muddle database
- Multiple Files and Inheritance in Build Descriptions
- Environment variables, sudo and instructions
- Use Of Libraries
- Version control
- The build process
- Available Muddle Commands
- DWIM
- Tips and tricks
- Licencing
- Any other queries?
- muddle and its directories
- About this chapter
- Notation in this chapter
- An overview of the directory structure
- A simple example build
- The
.muddle
directory - The
src/builds
directory - The mechanics of the build - the build description
- Some naming conventions
- Introspection of the dependency tree
- Checking out the source code
- The mechanics of the build - the makefile
- Building a package
- Deployment
- Rebuilding things
- Do what I say, not what I do
- Adding a new checkout/package
- Version stamps
- Domains
- Muddle workflows - or how to use muddle in real life
- Muddle and weld - how to use muddle with weld
- The muddle command line
- Repositories
- Instruction files
- Project lifecycle support: how to manage maintenance branches
- Distributions, licenses and
muddle distribute
- What we want to do
- The
muddle distribute
command - What is a distribution?
- Source distribution
- Binary distribution
- Deployment distribution
- Filtering the labels distributed
- Basic setting up of Licenses
- The other standard distributions
- Avoiding unnecessary GPL “propagation”
- Build descriptions
- Refining binary distributions
- Creating your own distributions
- Finding out about distributions
- Muddle commands
- More license stuff
- Questions
- The muddle release mechanism
- Jottings
bash: <toolchain>/bin/arm-none-linux-gnueabi-gcc: No such file or directory
./autogen.sh: line 3: autoreconf: command not found
- So what should I apt-get install?
- bash or dash?
- Why didn’t my
deploy
directory change? - How do I pull in a “meta” checkout?
- Build out-of-tree. Please.
- How do I get back to a clean checkout state?
- How do I build my kernel?
- How do I change my kernel configuation?
- How do I update a shallow checkout?
- How can I make sure the correct toolchain is available?
- Do you have a picture of a label?
- Mechanics: how “promotion” of subdomain labels works
- Issues with GNU autotools
- Muddle patch
- Useful
muddle
classes, methods and functions - The
muddled
package - The muddle documentation and sphinx and ReadTheDocs