• State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 22 subscribers
  • Views 7983 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

using batch file to build project

t c

Trying to use the uVision generated batch file to build the project. The batch file is generated fine, but running it produces an error for every call to armcc:

C:\ARM\LPC23xx_24xxSampleSoftware.r5\Keil\NewTest1>"C:\Keil\ARM\BIN31\ArmCC" --Via ".\obj\irq.__i"
Fatal error: C3904U: Could not open via file '.\obj\irq.__i'.

There are no files in my project with '.__i' or '.__ia' extensions.

Parents
  • 0 in reply to Andy Neil

    I did look at that, thanks, but it isn't really what I am after.

    I have a large legacy project being ported to Keil, and even though the IDE is great for dev&debug, it is desirable to also be able to build the project via make files or batch files using the raw tools. This is better for production&ongoing support, easier to document - just simple, easy to read text files with all the info in one place - no need to navigate dialogs to figure it out.

    The other thing is with make files you have detailed control over the build&link order which can be important. It isn't clear in what order uVision builds my large project and if it will give me the same level of control. I suspect it does, I just have not dug into it.

    For instance is my project always built in the same order in which my file groups appear in the workspace window (top to bottom)? Is the .dep file generated and then used during the build, or is it strictly a record of what happened?

    thanks

Reply
  • 0 in reply to Andy Neil

    I did look at that, thanks, but it isn't really what I am after.

    I have a large legacy project being ported to Keil, and even though the IDE is great for dev&debug, it is desirable to also be able to build the project via make files or batch files using the raw tools. This is better for production&ongoing support, easier to document - just simple, easy to read text files with all the info in one place - no need to navigate dialogs to figure it out.

    The other thing is with make files you have detailed control over the build&link order which can be important. It isn't clear in what order uVision builds my large project and if it will give me the same level of control. I suspect it does, I just have not dug into it.

    For instance is my project always built in the same order in which my file groups appear in the workspace window (top to bottom)? Is the .dep file generated and then used during the build, or is it strictly a record of what happened?

    thanks

Children
  • 0 in reply to t c

    "easier to document - just simple, easy to read text files with all the info in one place - no need to navigate dialogs to figure it out."

    Yes, I thoroughly agree: that is the fundamental flaw with GUI IDEs!

    The only way to fully document a project to a Client is to take screenshots of evey single dialogue!

    Hopeless!

    " is my project always built in the same order in which my file groups appear in the workspace window (top to bottom)?"

    Yes, that is true - though I'm not sure where (or even whether) that is clearly documented.

    Note that the full command-line used to compile each source file is recorded in the compiler listing file.
    The compiler listing file has a '.txt' extension.

    Note that uVision has a bug in that it puts the compiler listing files into the Objects folder!

  • 0 in reply to Andy Neil

    Hello,

    I did a quick test for the batch file in an old project.

    Everything seems to work correctly.

    I did not anything speacial...

    Next issue are just to program and start debugger automaticly.

    Kasper