• AVR Freaks

"New Project" Option in H3 vs. H2.06

Author
BillP
Super Member
  • Total Posts : 303
  • Reward points : 0
  • Joined: 2014/09/28 07:53:35
  • Location: CA
  • Status: offline
2019/05/15 16:35:37 (permalink)
0

"New Project" Option in H3 vs. H2.06

I just discovered a problematic difference in the way MPLABX/Harmony creates a new Harmony project.  Apparently in H3, the Project name is only used as a name on the project menu in MPLABX.  The project directory does not contain that name (as it used to do in Hv2).  See the attached screenshots that show where the project folders are created.

What is disturbing (to me) is that Harmony places the project in a folder named "firmware" and places the ".X" and the "src" directories under "firmware.  This means that all new projects share the same src directory.  I do not think that is a good idea. ;)

What I have done is to create a new folder under the "apps" directory with the same name as the project name.  After the project is created with the Harmony wizard, move the entire firmware directory under the project name directory.  This makes it look like the way Hv2 created new projects.

If there is a good reason why Hv3 does what it does, I would like to hear about it on this forum.  BTW - the Hv3 MHC documentation does not mention this "feature".

Attached Image(s)

#1

1 Reply Related Threads

    LostInSpace
    Super Member
    • Total Posts : 229
    • Reward points : 0
    • Joined: 2016/03/11 22:47:59
    • Location: 0
    • Status: offline
    Re: "New Project" Option in H3 vs. H2.06 2019/05/22 20:51:08 (permalink)
    0
    >>>>This means that all new projects share the same src directory.
     
    Yes, that does not seem like a good idea, especially when my projects have 15 or more driver files in them.
     
    If I found this, I would open a support ticket, in my experience someone gets back to me very quickly and usually is is something... Well.... If I'm honest..... Something that I have done that is not very smart. Sometimes they tell me - yeah, it is to be fixed in the next release, and at the very least now they know about it.
     
    #2
    Jump to:
    © 2019 APG vNext Commercial Version 4.5