MeshBench 0.1.0

What changed in this release: the changelog

Installing

See the quick start for each platform.

platform	download	notes
Linux	.AppImage	one file, any distribution
Debian, Ubuntu	.deb	sudo apt install ./meshbench_*.deb
Linux	.tar.gz	unpack it anywhere and run meshbench
macOS (Apple Silicon)	.dmg	drag MeshBench onto Applications, then right-click Open once: unsigned
Windows	.msi	installs to Program Files, Start menu entry, upgrades in place
Windows	.zip	no installer: unpack it and run meshbench.exe

Bundled, or compact

Every download above comes two ways, and the name says which:

	what is in it	when to take it
-bundled	the application and the QEMU and Renode emulators	you want to run an emulated board straight away, or the machine has no network
-compact	the application on its own	you are only simulating, or you would rather fetch the emulators once, on first use

A compact build fetches the emulators the first time something needs
one, into the same place a bundled build already has them, so the two
end up identical in what they can do. The difference is when the
download happens and whether it happens at all.

Neither the macOS nor the Windows build is code-signed yet, so both
operating systems will object the first time. The README says exactly
what they say and how to proceed.

SHA256SUMS covers every file here. MeshBench is GPL-3.0-or-later,
so the source for these binaries is this repository at v0.1.0; the
source archive beside them is that same tree, pinned, so a copy of
the bundle carries its own source wherever it ends up.

MeshBench 0.0.11

What changed in this release: the changelog

Installing

See the quick start for each platform.

platform	download	notes
Linux	.AppImage	one file, any distribution
Debian, Ubuntu	.deb	sudo apt install ./meshbench_*.deb
Linux	.tar.gz	unpack it anywhere and run meshbench
macOS (Apple Silicon)	.dmg	drag MeshBench onto Applications, then right-click Open once: unsigned
Windows	.msi	installs to Program Files, Start menu entry, upgrades in place
Windows	.zip	no installer: unpack it and run meshbench.exe

Bundled, or compact

Every download above comes two ways, and the name says which:

	what is in it	when to take it
-bundled	the application and the QEMU and Renode emulators	you want to run an emulated board straight away, or the machine has no network
-compact	the application on its own	you are only simulating, or you would rather fetch the emulators once, on first use

A compact build fetches the emulators the first time something needs
one, into the same place a bundled build already has them, so the two
end up identical in what they can do. The difference is when the
download happens and whether it happens at all.

Neither the macOS nor the Windows build is code-signed yet, so both
operating systems will object the first time. The README says exactly
what they say and how to proceed.

SHA256SUMS covers every file here. MeshBench is GPL-3.0-or-later,
so the source for these binaries is this repository at v0.0.11; the
source archive beside them is that same tree, pinned, so a copy of
the bundle carries its own source wherever it ends up.

MeshBench 0.0.11-dev.4

A development build, cut from main ahead of the next stable release. What has changed since the last one: the Unreleased section of the changelog. It may change again before that release ships, and the stable channel will not offer it.

Installing

See the quick start for each platform.

platform	download	notes
Linux	.AppImage	one file, any distribution
Debian, Ubuntu	.deb	sudo apt install ./meshbench_*.deb
Linux	.tar.gz	unpack it anywhere and run meshbench
macOS (Apple Silicon)	.dmg	drag MeshBench onto Applications, then right-click Open once: unsigned
Windows	.msi	installs to Program Files, Start menu entry, upgrades in place
Windows	.zip	no installer: unpack it and run meshbench.exe

Bundled, or compact

Every download above comes two ways, and the name says which:

	what is in it	when to take it
-bundled	the application and the QEMU and Renode emulators	you want to run an emulated board straight away, or the machine has no network
-compact	the application on its own	you are only simulating, or you would rather fetch the emulators once, on first use

A compact build fetches the emulators the first time something needs
one, into the same place a bundled build already has them, so the two
end up identical in what they can do. The difference is when the
download happens and whether it happens at all.

Neither the macOS nor the Windows build is code-signed yet, so both
operating systems will object the first time. The README says exactly
what they say and how to proceed.

SHA256SUMS covers every file here. MeshBench is GPL-3.0-or-later,
so the source for these binaries is this repository at v0.0.11-dev.4; the
source archive beside them is that same tree, pinned, so a copy of
the bundle carries its own source wherever it ends up.

MeshBench 0.0.11-dev.3

A development build, cut from main ahead of the next stable release. What has changed since the last one: the Unreleased section of the changelog. It may change again before that release ships, and the stable channel will not offer it.

Installing

See the quick start for each platform.

platform	download	notes
Linux	.AppImage	one file, any distribution
Debian, Ubuntu	.deb	sudo apt install ./meshbench_*.deb
Linux	.tar.gz	unpack it anywhere and run meshbench
macOS (Apple Silicon)	.dmg	drag MeshBench onto Applications, then right-click Open once: unsigned
Windows	.msi	installs to Program Files, Start menu entry, upgrades in place
Windows	.zip	no installer: unpack it and run meshbench.exe

Bundled, or compact

Every download above comes two ways, and the name says which:

	what is in it	when to take it
-bundled	the application and the QEMU and Renode emulators	you want to run an emulated board straight away, or the machine has no network
-compact	the application on its own	you are only simulating, or you would rather fetch the emulators once, on first use

A compact build fetches the emulators the first time something needs
one, into the same place a bundled build already has them, so the two
end up identical in what they can do. The difference is when the
download happens and whether it happens at all.

Neither the macOS nor the Windows build is code-signed yet, so both
operating systems will object the first time. The README says exactly
what they say and how to proceed.

SHA256SUMS covers every file here. MeshBench is GPL-3.0-or-later,
so the source for these binaries is this repository at v0.0.11-dev.3; the
source archive beside them is that same tree, pinned, so a copy of
the bundle carries its own source wherever it ends up.

MeshBench 0.0.11-dev.2

A development build, cut from main ahead of the next stable release. What has changed since the last one: the Unreleased section of the changelog. It may change again before that release ships, and the stable channel will not offer it.

Installing

See the quick start for each platform.

platform	download	notes
Linux	.AppImage	one file, any distribution
Debian, Ubuntu	.deb	sudo apt install ./meshbench_*.deb
Linux	.tar.gz	unpack it anywhere and run meshbench
macOS (Apple Silicon)	.dmg	drag MeshBench onto Applications, then right-click Open once: unsigned
Windows	.msi	installs to Program Files, Start menu entry, upgrades in place
Windows	.zip	no installer: unpack it and run meshbench.exe

Bundled, or compact

Every download above comes two ways, and the name says which:

	what is in it	when to take it
-bundled	the application and the QEMU and Renode emulators	you want to run an emulated board straight away, or the machine has no network
-compact	the application on its own	you are only simulating, or you would rather fetch the emulators once, on first use

A compact build fetches the emulators the first time something needs
one, into the same place a bundled build already has them, so the two
end up identical in what they can do. The difference is when the
download happens and whether it happens at all.

Neither the macOS nor the Windows build is code-signed yet, so both
operating systems will object the first time. The README says exactly
what they say and how to proceed.

SHA256SUMS covers every file here. MeshBench is GPL-3.0-or-later,
so the source for these binaries is this repository at v0.0.11-dev.2; the
source archive beside them is that same tree, pinned, so a copy of
the bundle carries its own source wherever it ends up.

MeshBench 0.0.11-dev.1

A development build, cut from main ahead of the next stable release. What has changed since the last one: the Unreleased section of the changelog. It may change again before that release ships, and the stable channel will not offer it.

Installing

See the quick start for each platform.

platform	download	notes
Linux	.AppImage	one file, any distribution
Debian, Ubuntu	.deb	sudo apt install ./meshbench_*.deb
Linux	.tar.gz	unpack it anywhere and run meshbench
macOS (Apple Silicon)	.dmg	drag MeshBench onto Applications, then right-click Open once: unsigned
Windows	.msi	installs to Program Files, Start menu entry, upgrades in place
Windows	.zip	no installer: unpack it and run meshbench.exe

Bundled, or compact

Every download above comes two ways, and the name says which:

	what is in it	when to take it
-bundled	the application and the QEMU and Renode emulators	you want to run an emulated board straight away, or the machine has no network
-compact	the application on its own	you are only simulating, or you would rather fetch the emulators once, on first use

A compact build fetches the emulators the first time something needs
one, into the same place a bundled build already has them, so the two
end up identical in what they can do. The difference is when the
download happens and whether it happens at all.

Neither the macOS nor the Windows build is code-signed yet, so both
operating systems will object the first time. The README says exactly
what they say and how to proceed.

SHA256SUMS covers every file here. MeshBench is GPL-3.0-or-later,
so the source for these binaries is this repository at v0.0.11-dev.1; the
source archive beside them is that same tree, pinned, so a copy of
the bundle carries its own source wherever it ends up.

MeshBench 0.0.10

What changed in this release: the changelog

Installing

See the quick start for each platform.

platform	download	notes
Linux	.AppImage	one file, any distribution
Debian, Ubuntu	.deb	sudo apt install ./meshbench_*.deb
Linux	.tar.gz	unpack it anywhere and run meshbench
macOS (Apple Silicon)	.dmg	drag MeshBench onto Applications, then right-click Open once: unsigned
Windows	.msi	installs to Program Files, Start menu entry, upgrades in place
Windows	.zip	no installer: unpack it and run meshbench.exe

Bundled, or compact

Every download above comes two ways, and the name says which:

	what is in it	when to take it
-bundled	the application and the QEMU and Renode emulators	you want to run an emulated board straight away, or the machine has no network
-compact	the application on its own	you are only simulating, or you would rather fetch the emulators once, on first use

A compact build fetches the emulators the first time something needs
one, into the same place a bundled build already has them, so the two
end up identical in what they can do. The difference is when the
download happens and whether it happens at all.

Neither the macOS nor the Windows build is code-signed yet, so both
operating systems will object the first time. The README says exactly
what they say and how to proceed.

SHA256SUMS covers every file here. MeshBench is GPL-3.0-or-later,
so the source for these binaries is this repository at v0.0.10; the
source archive beside them is that same tree, pinned, so a copy of
the bundle carries its own source wherever it ends up.

MeshBench 0.0.9

What changed in this release: the changelog

Installing

See the quick start for each platform.

platform	download	notes
Linux	.AppImage	one file, any distribution
Debian, Ubuntu	.deb	sudo apt install ./meshbench_*.deb
Linux	.tar.gz	unpack it anywhere and run meshbench
macOS (Apple Silicon)	.dmg	drag MeshBench onto Applications, then right-click Open once: unsigned
Windows	.msi	installs to Program Files, Start menu entry, upgrades in place
Windows	.zip	no installer: unpack it and run meshbench.exe

Bundled, or compact

Every download above comes two ways, and the name says which:

	what is in it	when to take it
-bundled	the application and the QEMU and Renode emulators	you want to run an emulated board straight away, or the machine has no network
-compact	the application on its own	you are only simulating, or you would rather fetch the emulators once, on first use

A compact build fetches the emulators the first time something needs
one, into the same place a bundled build already has them, so the two
end up identical in what they can do. The difference is when the
download happens and whether it happens at all.

Neither the macOS nor the Windows build is code-signed yet, so both
operating systems will object the first time. The README says exactly
what they say and how to proceed.

SHA256SUMS covers every file here. MeshBench is GPL-3.0-or-later,
so the source for these binaries is this repository at v0.0.9; the
source archive beside them is that same tree, pinned, so a copy of
the bundle carries its own source wherever it ends up.

MeshBench 0.0.8

What changed in this release: the changelog

Installing

See the quick start for each platform.

platform	download	notes
Linux	.AppImage	one file, any distribution
Debian, Ubuntu	.deb	sudo apt install ./meshbench_*.deb
Linux	.tar.gz	unpack it anywhere and run meshbench
macOS (Apple Silicon)	.dmg	drag MeshBench onto Applications, then right-click Open once: unsigned
Windows	.msi	installs to Program Files, Start menu entry, upgrades in place
Windows	.zip	no installer: unpack it and run meshbench.exe

Bundled, or compact

Every download above comes two ways, and the name says which:

	what is in it	when to take it
-bundled	the application and the QEMU and Renode emulators	you want to run an emulated board straight away, or the machine has no network
-compact	the application on its own	you are only simulating, or you would rather fetch the emulators once, on first use

A compact build fetches the emulators the first time something needs
one, into the same place a bundled build already has them, so the two
end up identical in what they can do. The difference is when the
download happens and whether it happens at all.

Neither the macOS nor the Windows build is code-signed yet, so both
operating systems will object the first time. The README says exactly
what they say and how to proceed.

SHA256SUMS covers every file here. MeshBench is GPL-3.0-or-later,
so the source for these binaries is this repository at v0.0.8; the
source archive beside them is that same tree, pinned, so a copy of
the bundle carries its own source wherever it ends up.

MeshBench 0.0.7

What changed in this release: the changelog

Installing

See the quick start for each platform.

platform	download	notes
Linux	.AppImage	one file, any distribution
Debian, Ubuntu	.deb	sudo apt install ./meshbench_*.deb
Linux	.tar.gz	unpack it anywhere and run meshbench
macOS (Apple Silicon)	.dmg	drag MeshBench onto Applications, then right-click Open once: unsigned
Windows	.msi	installs to Program Files, Start menu entry, upgrades in place
Windows	.zip	no installer: unpack it and run meshbench.exe

Bundled, or compact

Every download above comes two ways, and the name says which:

	what is in it	when to take it
-bundled	the application and the QEMU and Renode emulators	you want to run an emulated board straight away, or the machine has no network
-compact	the application on its own	you are only simulating, or you would rather fetch the emulators once, on first use

A compact build fetches the emulators the first time something needs
one, into the same place a bundled build already has them, so the two
end up identical in what they can do. The difference is when the
download happens and whether it happens at all.

Neither the macOS nor the Windows build is code-signed yet, so both
operating systems will object the first time. The README says exactly
what they say and how to proceed.

SHA256SUMS covers every file here. MeshBench is GPL-3.0-or-later,
so the source for these binaries is this repository at v0.0.7; the
source archive beside them is that same tree, pinned, so a copy of
the bundle carries its own source wherever it ends up.