How do I add a (staging/combining) project to a solution, that runs a batch file... nothing else?

Follow

Darcy Williams

• July 05, 2011 23:12

Okay, so we have a number of solutions and to each one we want to add a new (common/shared) project.  The purpose of this project will be to run a batch file...  so far so simple. 

It looks as though either a Staging or Combining project should do this job... 

The staging project (the name which makes the most sense, since this is a stage in the build process) just won't run the command and so the batch file never executes. 

The combining project can be made to run the batch file but it insists on calling "chmod" at the end of it.  I really don't want it to do anything other than run the batch file...  end of story.  Part of the problem here is that chmod doesn't exist in Win7 installs...  well, at least not on 64bit anyway.  Secondly, I don't want it to make directories writable or read only, I just want it to run the batch file.

Is there a way to do this that I haven't realised?

I know I can set up pre/post build options in the original projects but that's not what I want to do.  This is to be a common project shared by seven solutions, each with their own "private" project.

I guess by fixing the chmod issue this would probably work as a combining project, and that might do the trick...  but I'm not sure why chmod is required in the first place.

Any thoughts?

Thanks

1

• 

  strawbot

  • July 06, 2015 19:08

  Exactly 4 years later and I ran into the same bug!!! Windows does not have a chmod command! So when running a combine project on Windows, issue the equivalent to chmod or give me the option to not run the chmod command.

  0

  Comment actions Permalink
• 

  strawbot

  • July 06, 2015 19:08

  Exactly 4 years later and I ran into the same bug!!! Windows does not have a chmod command! So when running a combine project on Windows, issue the equivalent to chmod or give me the option to not run the chmod command.

  0

  Comment actions Permalink
• 

  strawbot

  • July 07, 2015 23:03

  not sure how that got repeated repeated. But what is in the output window is not truly command line runnable. The chmod command runs but it is having a problem making the directory not writeable even tho it is read only. Odd. Now if I put the solution on a network drive which happens to be a Mac and then try it from Windows, then there is no problem. Something fishy about the Windows file permissions. But at the root of it all, why even chmod at all?

  0

  Comment actions Permalink
• 

  Michael Johnson

  • July 08, 2015 04:41

  A combining project requires a file to be created, this is what is attempting to be chmoded (which is a built-in). This file is specified in the output filename property. We can do better with an error if this isn't specified.

  0

  Comment actions Permalink
• 

  strawbot

  • July 12, 2015 03:00

  For my purposes, I need to run a Python script which will check a text file for change and then regenerate a C header file and Python file if need be. Perhaps I'm using the combining project oddly but it suited my purposes. I then force the project to run each time I build.

  0

  Comment actions Permalink
• 

  Michael Johnson

  • July 12, 2015 07:46

  Set the output filename to the C header file that will be generated. Make the combining project a dependency of the project that uses the header file.

  0

  Comment actions Permalink
• 

  Darcy Williams

  • July 12, 2015 22:28

  Okay, this makes more sense now...  We got around this by running a pre-compile command on a single .c file, the one that cares about the externally built header.  We also set this specific file to "Always Rebuild"...  problem solved (for us).  Hope that helps

  0

  Comment actions Permalink

Please sign in to leave a comment.