CCS/TMS320F28379D: Create Project With Only Post Build Step

Hi!

I'm not saying that's not possible, but just curios, if there is no build step, what event then would trigger post-build step?

rrlagic said:

if there is no build step, what event then would trigger post-build step?

Nothing.

Ed - rrlagic is correct, for a pre/post build step to get triggered there needs to be something to build. 

Can you summarize what your current use case is? You may have mentioned it in previous posts when you were looking for answers on having CCS identifying your pre/post build step errors but if you don't mind summarizing the whole picture here, that'd be great. Hopefully I can suggest a solution for you.

Thanks

ki

Hi Ki,

I hadn't put the use case in previous posts.  I was picking off various pieces which I needed and I knew would give me greater insight into CCS.

We have several projects, each of which produces an abs file.  These abs files are used, in various combinations, to produce a number of <Outputs> which do essentially the same thing.  Each <Output> is created for a unique customer environment.  The uniqueness is being achieved in a Post build step.

To ensure compatibility with other tools in our development, test, and customer environments, each output has the same name.  And when we do our builds, we build all the versions of our code.  So it is necessary to have a unique top level project for each <Output>.  Each of these top level projects has two components.

1. The dependencies for the specific collection of abs files which are needed to produce its <Output>.
2. The Post build step which combines the abs files into the <Output>.

So each top level projects is really a project of projects. The lower level projects do the builds, and the top level project produces the <Output> from the results of the lower level projects.

Does this help?

Thanks,

Ed

Ed Sanders said:

To ensure compatibility with other tools in our development, test, and customer environments, each output has the same name.  And when we do our builds, we build all the versions of our code.  So it is necessary to have a unique top level project for each <Output>.  Each of these top level projects has two components.

1. The dependencies for the specific collection of abs files which are needed to produce its <Output>.
2. The Post build step which combines the abs files into the <Output>.

So each top level projects is really a project of projects. The lower level projects do the builds, and the top level project produces the <Output> from the results of the lower level projects.

Does this help?

Thanks Ed. I think I have an understanding now. Hence why you asked if you can have a project with just a post-build step executed. This project would be a parent project with a bunch of associated subprojects which generate an abs file when built. After the abs files are built by the subprojects, you wish the main project to just run a post-build step to generate the output. 

hmmm...

SInce the parent project would need actual source to build to trigger the post-build step, I'm wondering if something like this would work:

You have a batch file (assuming you are on Windows), which uses the CCS project CLI command to build each of the projects that generate the abs file. After those commands, you can then execute the command that you wanted as the post-build step for the proposed parent project to generate the output. Hence you can build everything by running one batch file.

Would that work?

ki

Hi Ki,

    If we were to run a batch file, wouldn’t we forego the use of the IDE?  It seems that tracking down errors would be much more difficult.

    The solution I am using, for now, is working nicely.  I created a new CCS project using the “Empty Project (with main.c)” option.  I added the dependencies and Post build step to it.  This works fine.  It does a short build and goes on to the Post build step.  My concern is that the build will be confusing to others who will use it after me.

Thanks,

Ed

Exactly my plan.  Thanks Ki.

Ed