Trying to build an executable for a an embedded device. There is 135MB of space on the device. Debug build is 135MB, release build is 138MB...

I have questions and I am afraid of what the answers are. Gotta sort out my sketchy build environment tomorrow.

Maybe memory alignment?

@Hazarth I had built a another project that was supposed to the 8MB. It compiled to 171MB on release build. So there is definitely something wrong. release builds should be orders of magnitude smaller than debug builds because there are optimizations and no debug symbols.

Debug symbols? Unless you have lot of embedded resources, hard to see why only code would do that.

I would run it through some executable analyzer to dig further.

@Demolishun yeah, I know. Well now that you say it blew up by over 100mb Im gonna suggest it must be dependencies being packed with the release or something. The options for debug and release must be different.

@Hazarth it is just the exec. Which makes zero sense to me.

@Hazarth doh, had to run strip on it. I looked in our build script for building an image, but did not find the strip command. So we must be doing it somewhere I am just not seeing.

Yay, got stuff on the system and now I gotta fix everything I did wrong. Progress is good.