I reached out via IRC to the app developer, obfuscated, who didn't like that by default the IDE doesn't have access to development tools and libraries on the host, and he didn't seem please with just Flatpak SDK access.
Maybe a few wrappers around flatpak-spawn and injecting custom project/workspace for host development could mitigate this limitation, but this is not on the top of my to-do list.
I would need to actually make use of the IDE to investigate this, my previous experience was years ago in a basic C course.
Users can always set up host development as a remote development setup, we have everything needed, including ssh client so I don't think it's a major issue.
Specifically, the developer mentioned access to wxWidgets environment so I guess we should make sure we have at least the wxGTK3 sources available or at least the headers and all optional features enabled in the shared libs.
Maybe also add wxPython.
I reached out via IRC to the app developer, obfuscated, who didn't like that by default the IDE doesn't have access to development tools and libraries on the host, and he didn't seem please with just Flatpak SDK access.
Maybe a few wrappers around flatpak-spawn and injecting custom project/workspace for host development could mitigate this limitation, but this is not on the top of my to-do list.
I would need to actually make use of the IDE to investigate this, my previous experience was years ago in a basic C course.
Users can always set up host development as a remote development setup, we have everything needed, including ssh client so I don't think it's a major issue.
Specifically, the developer mentioned access to wxWidgets environment so I guess we should make sure we have at least the wxGTK3 sources available or at least the headers and all optional features enabled in the shared libs.
Maybe also add wxPython.