Green Hills Compiler Support SPC5 Studio

[NMazz.2]

I am attempting to get the GHS compilier to build with SPC58NG dev kit and have switched the Build settings to below

 I have updated the project to include the path and commented out the error statement

ifeq ($(GHS_PATH),)

export PATH := C:\ghs\comp_202114\$(PATH_SEPARATOR)${PATH}

 # $(error Please specify a valid path into GHS_PATH for ccppc (GHS) compiler)

endif

and it will compile but then include some strange error that doesn't really help. Is there any setting I need to fix it looks to be something in the linking process.

[Tesla DeLorean]

>>compile but then include some strange error that doesn't really help

Says the linker failed because it can't find a symbol/function to bind with.

Either you're missing a source, or object file, or you have some #ifdef level exclusion of code you actually need, but isn't supplied for the GHS tools.

Perhaps start by figuring out what symbol it is choking on, a partial .MAP or linker output? Increase verbosity level if appropriate.

[NMazz.2]

Yeah okay it was missing a callback that didnt bother gcc.

On another note every time I regenerate something, the makefile gets regenerated and I have to rewrite the fix in the makefile.

I have added ghs to my path variables on my machine and also in the project. Any work arounds for this?

ifeq ($(GHS_PATH),)

 $(error Please specify a valid path into GHS_PATH for ccppc (GHS) compiler)

endif

[Tesla DeLorean · Accepted solution]

TBH this looks circular, adding to the PATH for executables / tools

export PATH := C:\ghs\comp_202114\$(PATH_SEPARATOR)${PATH}

Surely you want to be exporting GHS_PATH, not PATH, as presumable used elsewhere in the scripting or INCLUDE / LIB paths, etc. Or that GHS_PATH exists from the outset in your installed environment.

[Erwan YVIN]

Yes , it is in Windows Preferences , you should add the GHS_PATH in your environment ;)