The config.mk file is in crazyflie-firmware/.gitignore, so it's ignored by git and won't show you that it's a modified build even if config.mk is present. If you wanted to make sure a flag has an effect on the binary you could remove (or rename) your config.mk file, build the binary clean, checksum it, put back the config.mk file, build clean again, checksum the binary again and see if the two checksums are different. If they are, your change had an effect. If not, it didn't.nanobot9000 wrote:after I create the config.mk with the appropriate statement how do I know for sure that the build was correct aside from the behavior once I load it? Is there some number in this example that tells me it used my config.mk as part of enabling the experimental PID?
e.g. (on the VM):
Code: Select all
cd ~/projects/crazyflie-firmware
mv tools/make/config.mk tools/make/config.mk.bak
make clean
make
md5 cf2.bin > md5.clean.txt # md5 hash for non-experimental PIDs
mv tools/make/config.mk.bak tools/make/config.mk
make clean
make
md5 cf2.bin > md5.experimental.txt # md5 hash for experimental PIDs
diff --brief md5.clean.txt md5.experimental.txt # Differences found? Flag worked.
rm md5.*.txt