Don't run extra_scripts when unit testing

fr1 · July 22, 2020, 12:25pm

I have the following output script that gets run when I build my code (the script just does a couple of things like copying the binaries into a more friendly directory and renaming it).

However, I don’t want this to happen to run if I’m unit testing. I have used print(env.Dump()) to try and see if there’s anything that identifies it as a unit test but it doesn’t seem to work.

Any suggestions?

maxgerhardt · July 22, 2020, 2:09pm

When looking at the code

github.com

platformio/platformio-core/blob/22f1b94062191a7cfde125667071aafa174f5b5f/platformio/builder/tools/piomisc.py#L348


      
              optimization_flags = [
                  f for f in debug_flags.get("CCFLAGS", []) if f.startswith(("-O", "-g"))
              ]
          
          
    if optimization_flags:
                  env.AppendUnique(ASFLAGS=optimization_flags, LINKFLAGS=optimization_flags)
          
          

          
def ConfigureTestTarget(env):
              env.Append(
                  CPPDEFINES=["UNIT_TEST", "UNITY_INCLUDE_CONFIG_H"],
                  CPPPATH=[os.path.join("$BUILD_DIR", "UnityTestLib")],
              )
              unitylib = env.BuildLibrary(
                  os.path.join("$BUILD_DIR", "UnityTestLib"), get_core_package_dir("tool-unity")
              )
              env.Prepend(LIBS=[unitylib])
          
          
    src_filter = ["+<*.cpp>", "+<*.c>"]
              if "PIOTEST_RUNNING_NAME" in env:
                  src_filter.append("+<%s%s>" % (env["PIOTEST_RUNNING_NAME"], os.path.sep))

PIO defines the UNIT_TEST in env["CPPDEFINES"] for you, so you can differentiate it by that.

fr1 · July 22, 2020, 3:17pm

Ahh cool, thanks for that! It was hard to dig through all the defines