freebsd-ports
wasi-sdk
freebsd-ports | wasi-sdk | |
---|---|---|
39 | 11 | |
932 | 1,141 | |
1.1% | 3.5% | |
10.0 | 7.8 | |
about 13 hours ago | 11 days ago | |
Shell | ||
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
freebsd-ports
-
An Open Letter to the FreeBSD Foundation, Core Team, Committers, and Community
Agreed.
I don't think the PR reviewer is calling the author in the example, and provided useful info, pointing out the relevant example.
Also, the author notes:
> The very first comment in the thread from a reviewer was simply only one word: “Why?” - That’s it, just one word. Why did I do this? Why work with such old hardware? Why is the sky blue? How the hell am I to know the context of what they’re referring to when asking a one-worded question?
Its clear from https://github.com/freebsd/freebsd-ports/pull/189#discussion... that the author is asking why is this line needed, something a PR author should always be able to justify.
- OpenSSL 3.0 ported – security/openssl
-
Thoughts of a Linux diehard user that has migrated to FreeBSD
From https://github.com/freebsd/freebsd-ports/blob/main/UPDATING:
- I Need to create a FAMP stack with php74 on 13.1
-
Just saw KDE Plasma 5.27 available in ports!!
KDE: Update KDE Plasma Desktop to 5.26 · freebsd/freebsd-ports@d06d26f | https://cgit.freebsd.org/ports/commit/?id=d06d26f8c45e468021b1ec1def42fb1ce600a3dc
-
I want to move from linux to bsd
Say you really want to pin to Apache 2.5.54. Create a new empty repo, add a www/apache24 dir, and copy the files from that version of the ports tree into it.
-
Git archive checksums may change
They have not been stable
https://github.com/freebsd/freebsd-ports/commit/a43ec88422ee...
-
chromium disappeared from packages?
As for announcements: how would this information be delivered to you? :) Major breakages that impact users are expected to tracked in Ports (not pkgs) through review of /usr/ports/CHANGES and /usr/ports/UPDATING. If a port gets renamed (moved), you'll find it mentioned there, or possibly in /usr/ports/MOVED (not human-readable). You can view those on the GitHub mirror if you wish, since not everyone builds from Ports: https://github.com/freebsd/freebsd-ports
- How quickly is the port tree updated from freshports?
-
A Question: Gnome port for freebsd
at https://github.com/freebsd/freebsd-ports/tree/main/chinese/chinese-calendar (for the port to FreeBSD) the files and Makefile are not too complex.
wasi-sdk
-
Stop Hiding the Sharp Knives: The WebAssembly Linux Interface
I would really love being able to take any POSIX command line tool, compile that to WASI, and run it on (at least) Linux, Windows and macOS like a regular executable without having to install a separate WASI runtime.
I'm a 'WASI convert' since I was able to take an ancient 8-bit assembler written in the mid-90's (http://xi6.com/projects/asmx/), compile that as-is with the WASI SDK (https://github.com/WebAssembly/wasi-sdk), and then integrate it into a VSCode extension (https://marketplace.visualstudio.com/items?itemName=floooh.v...).
A similar problem is I have is a shader cross-compiler (https://github.com/floooh/sokol-tools) which needs to run Linux, macOS and Windows and takes too long to build locally, thus I currently need to distribute that as pre-built binaries. Compiling this to WASI works, but the filesystem access restrictions built into current wasm runtimes are a hassle to manage, and it would require a WASI runtime to be separately installed).
-
WASI: WebAssembly System Interface
There is the WASI SDK if you want to target WASI from C/C++:
https://github.com/WebAssembly/wasi-sdk
It may not have all the amenities of Emscripten, but it's way less bulky.
-
How to Debug WASI Pipelines with ITK-Wasm
The most direct way to debug WebAssembly is through the WebAssembly System Interface (WASI). In itk-wasm, we can build to WASI with the WASI SDK by specifying the itkwasm/wasi toolchain image. A backtrace can quickly be obtained with the itk-wasm CLI. Or, a fully fledged debugger session can be started with LLDB.
-
Hello Wasm World!
We use the add_executable command to build executables with itk-wasm. The Emscripten and WASI toolchains along with itk-wasm build and execution configurations are contained in itk-wasm dockcross Docker images invoked by the itk-wasm command line interface (CLI). Note that the same code can also be built and tested with native operating system toolchains. This is useful for development and debugging.
-
Wasmer takes WebAssembly libraries mainstream with WAI
A more lightweight tool than emscripten is the WASI SDK (https://github.com/WebAssembly/wasi-sdk/releases). However, it doesn't generate JS or HTML.
-
A First Look at Wasm and Docker
wget https://github.com/WebAssembly/wasi-sdk/releases/download/wasi-sdk-16/wasi-sdk-16.0-macos.tar.gz
-
Turbocharge your application development using WebAssembly with SingleStoreDB
First, we’ll download the wasi-sdk. We’ll use wasi-sdk-16.0-linux.tar.gz, the latest version available when writing this article. We’ll move the file to the /opt directory and unpack it as follows:
-
whats all the fuzz about wasi-libc?
I'm intrigued. Pretty good write-up about it here. One would need an ebuild for wasi-libc and an ebuild for wasi-sdk.
-
Store SQLite in Cloudflare Durable Objects
The previously mentioned PR for wasm32-unknown-unknown compatibility solved this by including libc .c files from OpenBSD. My go to solution is different though. I prefer to build using the wasi-sdk (a WASI-enabled WebAssembly C/C++ toolchain).
-
WebAssembly and Back Again: Fine-Grained Sandboxing in Firefox 95
There's also the https://github.com/WebAssembly/wasi-sdk repo which is kind of a meta-build-system for all this.
But in FreeBSD we build all the pieces directly, here's our build recipes (with some hacks due to llvm's cmake code being stupid sometimes):
compiler-rt (from llvm): https://github.com/freebsd/freebsd-ports/blob/main/devel/was...
libc (from what you linked): https://github.com/freebsd/freebsd-ports/blob/main/devel/was...
libc++ (from llvm): https://github.com/freebsd/freebsd-ports/blob/main/devel/was...
What are some alternatives?
core - OPNsense GUI, API and systems backend
wasi-libc - WASI libc implementation for WebAssembly
freebsd-git-docs - Draft copies of the FreeBSD git transition documents
binaryen - Optimizer and compiler/toolchain library for WebAssembly
sysz - An fzf terminal UI for systemctl
linux - Linux kernel source tree
freshports - The website part of FreshPorts
asyncify - Standalone Asyncify helper for Binaryen
wasm-sqlite - [Experimental] SQLite compiled to WASM with pluggable page storage.
rospo - 🐸 Simple and reliable ssh tunnels with embedded ssh server in Golang
nxdk - The cross-platform, open-source SDK to develop for original Xbox: *new* xdk