Yeah its definitely nice to avoid an annoying "binary" to source step and then have to waste a bunch of cycles to parse/compile said source. I do embedded work

Yeah its definitely nice to avoid an annoying "binary" to source step and then have to waste a bunch of cycles to parse/compile said source. I do embedded work and run into this all the time with C and C++. Its toolchain dependent on how to import binary blobs unfortunately in C/C++. You very quickly run into a wall on how large of a source file can be compiled around 100 MB or so. gcc is the best at handling huge source files, but its still slow. For example, you can do the import with gcc this way: https://balau82.wordpress.com/2012/02/19/linking-a-binary-blob-with-gcc/ https://balau82.wordpress.com/2012/02/19/linking-a-binary-bl... With Green Hills, there is a .rawimport directive.