Sorry - I'm not familiar with OE yet, so I'll have to let somebody
> The .ipk file is 200k, and the unpacked "helloworld" package is 400k for a total of 600k (until I delete the .ipk)
> First, how would I go about linking dynamically instead of statically using bitbake (not buildroot)?
> Do I use the arm-angstrom-linux-gnueabi-c++ compiler istead of making the cumbersome package and recipe combination?
else answer that one.
You probably can't use the buildroot toolchain with an OE system.
> Second, If I was to use buildroot, then how would I be able to run the programs on the gumstix (which is currently running the OE filesystem and kernel) without having /bin/bash to execute them?
Normally, the toolchain defaults to dynamic. To force it to use
> Flashing the gumstix with a buildroot kernel and filesystem nets me a corrupt terminal.
> Also, how would I perform static vs dynamic linking with the buildroot (arm-linux-g++) cross compiler?
> I suppose it would be the same was as the arm-angstrom-linux-gnueabi-c++ one.
static, you pass -static on the command line to gcc/g++ when compiling
and when linking. Similarly to force dynamic, you use -dynamic.