Check @WereCatf 's source directory, specially first_time_setup.sh and my docker project on info about how to build from LEDE.
The OnionIoT repository is not ready yet, they will publish the source code in the future*.

If you want to build C (etc) programs from source, you need a mipsel_24kc_gcc-5.4.0_musl-1.1.15 or similar toolchain - mipsel_24kc being the machine specification and musl being the C library used by LEDE.

One way to get one is to build a suitable LEDE image from source, though there may be places you can download it.

A crude approach is then to use command line environment variable overrides, ie

But this is crude because is assumes that your build system is looking for a GCC variable, if it is looking for a CC it will break and build for the development machine instead. And anything that uses autoconf or pkgconfig, etc will be broken.

The upstream cross-compilation instructions are at https://lede-project.org/docs/guide-developer/compile_packages_for_lede_with_the_sdk but are not particularly helpful either, as they inherit buildroot's spiritual assumption that you only want to build programs in connection with the setup for building a complete system - you can specify to only build a particular program, but you are still kind of expected to plug your program into the overall system's build system in order to do so.

So, no great answer, but between the first option of explicitly invoking the cross compiler and the second of merging your program into the system, you can at least get things accomplished.

@Gary-Saini It is possible to use other IDE's.
For example, I use Netbeans IDE running under Kubuntu.
For compiling C/C++ it is necessary to install the cross compilation environment and setup Netbeans to reference the environment. The resulting built binary file can then be transferred to the Omega (using e.g. scp) and run from there. While it is also possible to set up Netbeans to also transfer the binary automatically to the Omega.
Netbeans projects can be used to either use the standard C/C++ build methods or to use a specific hand crafted Makefile - I generally use the Makefile method (it is a bit easier to set up and I have a template Makefile that I tailor to any specific project). I have done this to build standalone programs and both static and dynamic libraries.
I have also used Netbeans to build Java programs (for running on the Omega under jamvm).