• State Not Answered
  • Locked Locked
  • Replies 19 replies
  • Subscribers 22 subscribers
  • Views 2908 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

uV3: Automated new project creation

Gary Lynch

Today I created 6 new projects to run under uVision 3.
Every time I had to:

  • Open a new file and name it,
  • Select a target manufacturer and device,
  • Rename the 'Target' and 'Source group 1' to names that
    mean something to me,
  • Open the 'Components, Environment and Books' dialog box,
    create several groups that I need, add files to them,
  • Open the 'Options for Target ...' dialog box, navigate
    through the tabs, changing settings all over the place,
    to get the environment I want.

All these initialization tasks are pretty much the same
thing every time. I can find no mention in the
documentation of a way to automate it, or create a template
that will allow me to override the default settings, or even
clone an old project file to steal its settings.

Has anyone pulled this off?

Thanks.
============================================================
Gary Lynch            |     To send mail, change no$pam in
lynchg@no$pam.com     |     my domain name to stacoenergy

Parents
  • 0 in reply to Andy Neil

    I've used Jam before in a much larger environment. It takes a little bit more startup effort than make, unless you're content with the "Jamrules" out of the box.

    The hardest thing to get used to is the quirk of their parser than means the terminating semicolons must be separated with a space, e.g.:

    Target1: Depend1 Depend2 ; // ok
    Target2: Depend1 Depend2; // bugged

    This makes sense only if you're a Jam developer working on the parser and you understand that these lines are really function calls with unusual syntax and that a semicolon is a perfectly legitimate third parameter. The rest of us just get used to it.

    On really big projects, you tend to have each file as well as the semicolon on a separate line anyway, so you can easily add and delete from the list without worrying about which file happens to be the last one, or the list in some variable.

    On the bright side, Jam is much more powerful than make, extensible and customizable, smarter about dependencies, and much much better at handling projects that live in nested directory structures.

    I haven't yet used it with my 8051 projects and the Keil tools. That set of projects is just barely teetering within the limits of what uVision can handle.

Reply
  • 0 in reply to Andy Neil

    I've used Jam before in a much larger environment. It takes a little bit more startup effort than make, unless you're content with the "Jamrules" out of the box.

    The hardest thing to get used to is the quirk of their parser than means the terminating semicolons must be separated with a space, e.g.:

    Target1: Depend1 Depend2 ; // ok
    Target2: Depend1 Depend2; // bugged

    This makes sense only if you're a Jam developer working on the parser and you understand that these lines are really function calls with unusual syntax and that a semicolon is a perfectly legitimate third parameter. The rest of us just get used to it.

    On really big projects, you tend to have each file as well as the semicolon on a separate line anyway, so you can easily add and delete from the list without worrying about which file happens to be the last one, or the list in some variable.

    On the bright side, Jam is much more powerful than make, extensible and customizable, smarter about dependencies, and much much better at handling projects that live in nested directory structures.

    I haven't yet used it with my 8051 projects and the Keil tools. That set of projects is just barely teetering within the limits of what uVision can handle.

Children
No data