Community
Participate
Working Groups
When users are debugging their code which uses a product on the XDCPATH, and they step into one of those APIs, they currently still have to browse to find the source as CCS/Eclipse manages its source search path independent of the XDCPATH. A nice ease-of-use feature would be to add the XDCPATH to the locations where sources are browsed from.
A related customer use case that could be satisfied by this enhancement would be that Eclipse's auto-complete, used when editing sources, would search for definitions/headers via the XDCPATH.
Tracked via SDSCM00038455
code completion, F1 help, and indexer support are all working in xdctools 3.25.05.