Author Topic: MacOS: MPLAB X 6.10 Unresolved include pic16f887.h  (Read 554 times)

0 Members and 1 Guest are viewing this topic.

Offline newtekuserTopic starter

  • Frequent Contributor
  • **
  • Posts: 359
  • Country: us
MacOS: MPLAB X 6.10 Unresolved include pic16f887.h
« on: July 04, 2023, 07:49:48 pm »
I am getting an unresolved include in xc.h file, it is unable to locate the pic16887.h file but the file exists in the pic include folder and the project can be built just fine.

Adding the path "/Applications/microchip/xc8/v2.41/pic/include/" to for the compiler settings in the project properties menu doesn't fix this.

This is not an issue on Windows 11. Does anyone know how to fix this on MacOS?
« Last Edit: July 04, 2023, 07:54:00 pm by newtekuser »
 

Online RoGeorge

  • Super Contributor
  • ***
  • Posts: 6269
  • Country: ro
Re: MacOS: MPLAB X 6.10 Unresolved include pic16f887.h
« Reply #1 on: July 05, 2023, 06:36:25 am »
You wrote "pic16887.h", but the picture is about "pic16f887.h".  When something works in Windows but not in other OSs, I look for capitalization of the characters in the filename+path.  Windows doesn't care (they are considered the same name), while in the other OSs "A" and "a" are different.

Offline newtekuserTopic starter

  • Frequent Contributor
  • **
  • Posts: 359
  • Country: us
Re: MacOS: MPLAB X 6.10 Unresolved include pic16f887.h
« Reply #2 on: July 06, 2023, 12:57:38 am »
Looks like I was looking in the wrong place, the pic16f887.h header file is in /Applications/microchip/xc8/v2.41/pic/include/proc. Once I added the path to the compiler the issue went away and the editor is happy now.
« Last Edit: July 06, 2023, 01:06:07 am by newtekuser »
 

Offline tooki

  • Super Contributor
  • ***
  • Posts: 11632
  • Country: ch
Re: MacOS: MPLAB X 6.10 Unresolved include pic16f887.h
« Reply #3 on: July 07, 2023, 06:12:46 am »
You wrote "pic16887.h", but the picture is about "pic16f887.h".  When something works in Windows but not in other OSs, I look for capitalization of the characters in the filename+path.  Windows doesn't care (they are considered the same name), while in the other OSs "A" and "a" are different.
That is not the case on macOS. (By default, that is.)

On macOS, it’s actually on a per-disk basis, depending on whether the disk is formatted with a case-sensitive filesystem or not. Case-sensitive is not recommended for most purposes because too much software breaks.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf