...run external tools as part of my build process?

Comments

4 comments

  • Avatar
    Gary Spivey

    This sounds wonderful. But I am apparently too thick-headed to find this. I have been all over my Crossworks options as well as properties, and I can't find the options you are referencing. In the properties area, I can find Compile Options and Linker Options, but neither of them have Pre and Post Build Command options. There is a Build Options, but it doesn't have any options for commands. I also have a User Build Step Options, and it has a Pre-Compile command, but it runs this before every file that has to be compiled. Which isn't what I want. Can anyone help me locate the correct options?

    0
    Comment actions Permalink
  • Avatar
    Simon Schwarz

    Hi,

    I also don't find this option!

    I have a similar problem. Atm I have a version-generation script in User Build Step Options->Pre-Compile Command. But this is run for every compilation unit. This significantly prolongs the compilation process - so an option to run the script only once before compilation would be nice.

    0
    Comment actions Permalink
  • Avatar
    Paul Curtis

    You can set a pre-compile on a file, a folder, or a project.  To run a single pre-compile command on a bunch of files, for instance, put those files in a project folder and set the pre-compile command for the folder.  The files in that folder then inherit the pre-compile (and any other user step) command.

    If you just want to run something on a single file, set the step parameters for that file only.

    0
    Comment actions Permalink
  • Avatar
    Gordon Scott

    I think this is slightly out-of-date.

    In CrossWorks  2.3 at least, these options are now collected together at the bottom of the properties under "User Build Step Options"

    0
    Comment actions Permalink

Please sign in to leave a comment.