• AVR Freaks

Hot!MPLABX 5.25 project include paths issue

Author
vladi552
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2019/08/22 06:10:17
  • Location: 0
  • Status: offline
2019/08/24 05:46:35 (permalink)
0

MPLABX 5.25 project include paths issue

I'm using Win10-64. AtmelStudio7 installed with it's build-in AVR toolchain.
Once new С standalone Microchip project has been created in MPLABX 5.25 the standard C types uint8_t, uint16_t ... displayed as unresolved (indicated with small icon). However, the project compilation is not affected.
The used AVR toolchain have two stdint.h header path inside:
1. Atmel\Studio\7.0\toolchain\avr8\avr8-gnu-toolchain\avr\include
2. Atmel\Studio\7.0\toolchain\avr8\avr8-gnu-toolchain\lib\gcc\avr\5.4.0\include
MPLABX 5.25 use pt.2 path and it's looking like not valid. Right path is as in pt.1.
I added it in proj properties under the AVR GCC global option and this fix a problem.
I'm not sure if this hotfix valid? System includes must be handle by MPLABX, I think. Is't it?
#1

7 Replies Related Threads

    ric
    Super Member
    • Total Posts : 24581
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: offline
    Re: MPLABX 5.25 project include paths issue 2019/08/26 21:48:34 (permalink)
    0
    MPLABX does this all the time with the PIC compilers (i.e. can't resolve valid symbols), so I'm not surprised it makes the same mistake with the AVR toolchain...
     

    I also post at: PicForum
    Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
    NEW USERS: Posting images, links and code - workaround for restrictions.
    To get a useful answer, always state which PIC you are using!
    #2
    cabletie
    Starting Member
    • Total Posts : 36
    • Reward points : 0
    • Joined: 2011/07/02 06:21:46
    • Location: Zulu -5
    • Status: offline
    Re: MPLABX 5.25 project include paths issue 2019/08/28 06:20:57 (permalink)
    0
    ric
    MPLABX does this all the time with the PIC compilers (i.e. can't resolve valid symbols), so I'm not surprised it makes the same mistake with the AVR toolchain...



      I have noticed this also but with MPLABX V5.20 and XC 8 V2.0 with IDC4 and PIC16F18877.  I get around it
    by performing an "insignificant edit" (i.e. add a space then delete it), exit from the file XC8.h without saving changes and the IDE error/warning goes away.    oh.... the warning is "unresolved include in XC8.h" and when opened the error flag is on the xc8debug.h include directive; the pic.h include also gets a warning.  Both disappear after the unsaved edit.   Evidently X5.25 did not fix this......
      another issue I noticed is the Add Watch window text font size is so small I can barely read it.  The IDE did
    this also but I changed the windows settings to get it readable but it did not do anything for the Add Watch window.  It would seem to me the editor settings would be inherited throughout the IDE.GUI ...  just sayin'  
    #3
    Jim Nickerson
    User 452
    • Total Posts : 6361
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: offline
    Re: MPLABX 5.25 project include paths issue 2019/08/28 06:45:21 (permalink)
    +1 (1)
    I have found right clicking on the project, selecting code Assistance and Reparse Project results in the same as your insignificant edit in most cases.
    Attachments are not available: Download requirements not met

    Attachment(s)

    Attachments are not available: Download requirements not met
    #4
    nice
    Super Member
    • Total Posts : 1090
    • Reward points : 0
    • Joined: 2004/09/18 11:42:25
    • Location: Germany
    • Status: offline
    Re: MPLABX 5.25 project include paths issue 2019/08/28 16:12:07 (permalink)
    0
    Usually "Reparse Project" has worked for me too. With 5.25 all bets are off. If opening a dsPIC33CK project of mine with 5.15 there are no unresolved references. If opening the very same project with 5.25 it shows unresolved references, which won’t go away if reparsing the project. IMHO MPLAB X’s parser is FUBAR. As it doesn’t work correctly for Microchip devices, I’m not too surprised at all that it doesn’t  work as intended for Atmel devices as well.

    With respect to the the reported issue, this thread might be relevant.
    #5
    cabletie
    Starting Member
    • Total Posts : 36
    • Reward points : 0
    • Joined: 2011/07/02 06:21:46
    • Location: Zulu -5
    • Status: offline
    Re: MPLABX 5.25 project include paths issue 2019/08/28 21:21:24 (permalink)
    0
    Tried the "reparse project" but sadly  it  did  not  work......
     
    Ctrl+Left Click the offending include
    type something
    delete it
    exit/close file
    discard changes
    *blip*  error/warning gone....
     
      I  thought new releases and revision were supposed to
    bring improvements, not introduce new bugs.....or
    am I missing something?  
     
     
     
    #6
    Jim Nickerson
    User 452
    • Total Posts : 6361
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: offline
    Re: MPLABX 5.25 project include paths issue 2019/08/29 06:28:47 (permalink)
    0
    I find sometimes adding the specific path to the includes to Project Properties, XC8 Compiler, Preprocessing and messages, Include Directories helps the compiler to locate the includes.
    In my case adding "C:\Program Files (x86)\Microchip\xc8\v2.05\include\plib" helped
    #7
    cabletie
    Starting Member
    • Total Posts : 36
    • Reward points : 0
    • Joined: 2011/07/02 06:21:46
    • Location: Zulu -5
    • Status: offline
    Re: MPLABX 5.25 project include paths issue 2019/08/29 09:27:15 (permalink)
    0
    Thank you Sir,  yes, I stand corrected.   I did the reparse but I did not restart the computer.
    So I had to, again, do an edit.  When I finished for the night I shutdown the computer.
    This morning upon startup I noticed some extra background IDE processing and think I
    caught a glimpse at a message which stated something about parsing.... ??  I was yet
    nursing a hot cup of coffee (still foggy).   However, when I opened the project no
    errors appeared as yesterday.   So in my case, it appears  the computer needed a
    reboot for the reparse to be effective. 
      Not that it has anything to do with the above mentioned errors but this projects
    firmware reached stability this morning....  :-))
    Thank you,  I appreciate the assistance.
    #8
    Jump to:
    © 2019 APG vNext Commercial Version 4.5