Working on feature/wl.posix
The POSIX layer is now shifted completely out of the libc code in the btdk repository and directly exposed at the user/kernel mode boundary interface.
This has 2 really great advantages, it makes the libc port layers simple (essentially the same for both compilers, 1 calls e.g. bt_sys_write() as a function, the other as a trap).
The portable layer is the same in both versions, and the syscalls are more maintainable being directly in the kernel. This means that software compiled for kernels from now on should work mostly as the syscall layer gets improved in future kernel versions. (As long as the syscall numbers remain frozen).
Working on feature/wl.posix The POSIX layer is now shifted completely out of the libc code in the btdk repository and directly exposed at the user/kernel mode boundary interface.
This has 2 really great advantages, it makes the libc port layers simple (essentially the same for both compilers, 1 calls e.g. bt_sys_write() as a function, the other as a trap).
The portable layer is the same in both versions, and the syscalls are more maintainable being directly in the kernel. This means that software compiled for kernels from now on should work mostly as the syscall layer gets improved in future kernel versions. (As long as the syscall numbers remain frozen).