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

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
  • Erik, we're all wlel aware that you're pretty much dead-set against the IDE, so it's probably pointless to tell you this, but FWIW:

    My "variants" use ~20 common files and ~3 files are "picked" e.g. for variant 3 copy ralph.cvar3 ralph.c

    Yes, you can do this kind of "dynamic" build with uVision. You don't even have to copy files. Instead you select which files form a target on a per-group or per-file basis. I.e. you would have the union of all files of all variants of the project listed in the project sources, and each target gets to choose which files it wants to use, and which not.

Reply
  • Erik, we're all wlel aware that you're pretty much dead-set against the IDE, so it's probably pointless to tell you this, but FWIW:

    My "variants" use ~20 common files and ~3 files are "picked" e.g. for variant 3 copy ralph.cvar3 ralph.c

    Yes, you can do this kind of "dynamic" build with uVision. You don't even have to copy files. Instead you select which files form a target on a per-group or per-file basis. I.e. you would have the union of all files of all variants of the project listed in the project sources, and each target gets to choose which files it wants to use, and which not.

Children
  • Erik, we're all wlel aware that you're pretty much dead-set against the IDE, so it's probably pointless to tell you this

    Were I to only work with one variant of one program, I would be in the IDE except for the editor and ICE issues below.

    I would love to use an IDE, However, for me as things are it is mandatory for me that
    1) It allows any editor to be integrated
    2) it allows integration of your favourite ICE.
    3) It allows "scripts" to do "abnormal" things
    4) It is easier to do the above than in a .bat file
    5) It allows build x, build group y, build all
    6) it allows an organized directory structrue for those of us that maintain and enhance several variant of several products.
    7) THE BIGGIE: it allow all the above without EVER requiring a change to be made in more than one place.

    please do not waste your time telling me that one of the above is possible, if not all, forget it

    I achieve all the above with my setup and why should I give that up just to "get in the fold".

    Also, as I said: You get (maybe with a new release) one step ahead, just to run into the next block.

    Yes, you can do this kind of "dynamic" build with uVision. You don't even have to copy files. Instead you select which files form a target
    and have 27 targets for the variants of one product? no, thank you (see 7) above)

    the real issue is that in "my world" I need, in order to keep my snity to have to specify
    a) what is so for all I do
    b) what is so for a group of what I do
    c) what is so for a subgroup of what I do
    d) what is so for a a thing I do

    I absolytotally abhore anything that in any way require that you have to do something in 2 or more places, I have seen more problems from "you just do that in all 27 target specifications" than anything else.

    Erik

    In case someone want an example: I yesterday added a version (#28) for another sign and, to achieve that, I added a few things in the common files. While debugging the new variant, I build that variant only, but every 10th build or so I built all to see if the added code had advers affects for some other variant. (my typical problem is DATA overrun when variables are not #if'ed out properly). When that was done, I had to do some work on the unit driving the above to implement the ability to drive a new capability that sign has.

  • Erik, we're all wlel aware that you're pretty much dead-set against the IDE, so it's probably pointless to tell you this

    Hans-Bernhard,
    I will gladly send you one of my .bat files and if you can make the IDE do as I do in these files, I will print this entire thread on paper and eat it.

    Erik