mcrun tool enhancement wishlist

[willend]

It would be nice with these additions / improved features for mcrun / mxrun:

• Honouring CFLAGS and LDFLAGS from surrounding environment
• A commandline-switch for further CFLAGS, e.g. --CFLAGS="enable some profiling/debugging feature" that would add to CFLAGS (the thinking is here that these are added, not replacing the configuration-settings read from the toolchain json file
• A commandline-switch --dprefix that can be used to define a directory pattern to be used together with a time-stamp (default behaviour is to use the instrument name, this would replace the instrument name in the directory)

[ebknudsen]

I have a feeling we have discussed this at length before but:
Another suggestion would be to add an option to one-off add a specific directory to the component search path.
This would avoid cluttering when dealing with custom comps. There are obviously possible undesireable sideeffects, but if McWhatever is run in a subshell we could perhaps avoid contanminating the environ

[willend]

@ebknudsen mcrun and mxrun now have -I which is forwarded to the code-generator (implies -c)

mcrun --help
Usage: mcrun.py [-cpnN] Instr [-sndftgahi] params={val|min,max|min,guess,max}...

Options:
  --version             show program's version number and exit
  -h, --help            show this help message and exit

  mcrun options:
    -c, --force-compile
                        force rebuilding of instrument
    -I I                Append to McCode search path (implies -c)
    --D1=D1             Set extra -D args (implies -c)
    --D2=D2             Set extra -D args (implies -c)
    --D3=D3             Set extra -D args (implies -c)

[ebknudsen]

Roger that - scratch that suggestion.
I'll make it into another, which is actually what we needed at this point in time:
In some cases it could be convenient to have yet another flag which could send some flags on to the compiler. Like what gcc -Wl,option does is what I mean.

OT: Also I think exposing "-I" in the GUI would be useful