SDK alternatives #897
Labels
No labels
bazel
bluetooth
board settings
boot_stage2
bug
build
c++
can't reproduce
clang
clib-interface
cmsis
code cleanliness
code size
compiler version issues
cyw43_driver
debug
discussion
documentation
duplicate
dynamic_clock
elf2uf2
enhancement
errata
filesystem
flash layout
floating point
FreeRTOS
hardware_adc
hardware_claim
hardware_clocks
hardware_dma
hardware_exception
hardware_flash
hardware_gpio
hardware_i2c
hardware_irq
hardware_pio
hardware_pwm
hardware_rcp
hardware_rtc
hardware_spi
hardware_sync
hardware_uart
hardware_vreg
hardware_watchdog
hardware_xosc
help wanted
host
IAR
installation
invalid
linker scripts
lto
lwip
mbedtls
missing API
needs reporter detail
networking
newlib
newlib-multicore
non-c
non-cmake
non-gcc
openocd
orphan PR
OS integration
pico_async_context
pico_base
pico_binary_info
pico_flash
picolibc
pico_lwip
pico_malloc
pico_multicore
pico_printf
pico_runtime
pico_stdio
pico_stdio_usb
pico_sync
pico_time
pico_util
pioasm
port
question
review
review2
rtos interop
runtime init
static library
svd
test
tinyusb
vscode
wifi integration
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-raspberrypi/pico-sdk#897
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've been making an alternative port of Pico SDK for a year and a half who has quite a following and fans
its difference from the official one is expressed in the replacement of CMAKE with SCons ( PlatformIO )
and restructuring of the file position in the folders ( I make no changes to the C code )
https://github.com/Wiz-IO/wizio-pico
Is it possible to post somewhere:
list of all C dependent definitions -D KEY_XXX with a short brief description ( for version )
and compiler verbose logs from 3, 4 basic and important examples
I need the latter for a quick orientation in building the build because I don't use and don't intend to use the official stuff.
I just have other things on my mind and I don't have a lot of free time, but I do it out of sports malice for those who like it (GIT statistic: ~10 new clones per day ... for 1.5 year )
The port currently works up to version 1.3.1 ... v1.4.0 is in progress - just waiting for the new W board to experiments
I have no direct connections with Pico Team, that's why I'm writing it here.
Thanks
We also have other things on our minds, and don't have a lot of free time?
FYI we would (in general) like to provide additional information/tooling to make it easier to build SDK code outside of our build system. I'm obviously not committing on any time frame atm.
ОК