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

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
  • "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!

Reply
  • "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!

Children