[ptp-user] Remote C builds using RDT at PTP 2.1.1 level

[Dave Wootton <dwootton@xxxxxxxxxx>]

Chris
I finally got back to experimenting
with RDT after installing PTP 2.1.1. I can now set environment variables
in the project properties and can get my remote make to see those environment
variables

I have some additional questions and
problems
1) I don't see any way to change the
make target for a make comand. I can change the command name, but it seems
that the implied make target is 'all'. If I specify the build command as
'gmake xxx', then a 'gmake xxx all' gets run, which means that it eventually
fails since there is no 'all' target in my makefiles.
2) When I look at the environment variables
for a remote project, I see PWD and CWD predefined, but the pathnames have
'\' instead of '/', probably since I am running on a windows system connecting
to a back end AIX system. Since the assumed platform for remote targets
is 'UNIX', shouldn't the pathname unconditionally contain '/'?
3) The include directories pre-filled
in remote paths include some directories on my local system (f:/program
files/mingw/.... I'm not sure what's finding these since I don't see any
environment variable specifying these directories. Shouold the remote build
project ignore local include directories?
4) When I create a remote project, the
F:/Program Files/MinGW directories show up in the includes folder and I
can see files if I expend the nodes for those directories. If I add remote
directories to the remote paths list, those show up in the includes folder
but have no '+' to expand them even though there are files in them.
5) When indexing runs, I get a bunch
of messages for undefined variables. For instance, 'FILE' shows up as an
undefined variable even though it's defined in /usr/include/stdio.h. Does
the fact taht FILE id defined as a typedef inside an 'ifdef' cause a problem?
How does the indexer know anything about pre-processor variables? 
6) Even if I don't have paths to all
directories defined in remote files and paths, when I right click on index
in the project view and click 'Search for Unrsolved Includes', none of
the missing includes show up in the search
7) For remote projects, shouldn't standard
system directories (at least /usr/include and /usr/include/sys) be the
default for remote paths?
Dave