| Re: [ptp-user] Remote C builds using RDT at PTP 2.1.1 level |
Hi Dave,
> 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.
You'll have to change the build target and the clean target in the builder settings. It's on the "Behavior" tab in the builder settings.
> 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 '/'?
Yeah... like you say this is because the variables are coming from the local system. On my AIX system these don't cause any havoc though. If they cause problems for you, you'll have to tell it to replace the environment (which has some issues but for right now is the only solution).
> 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?
These directories come from the toolchain you select when creating the project. Just delete them if they are not appropriate.
> 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.
That is expected right now because the CModelBuilder is not yet hosted remotely. The model is actually being built from a local parse. We are working on the remote model builder right now so we should have one for PTP 2.2.
> 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?
Currently you have to define them all manually in the Remote Paths and Symbols properties. We have a remote scanner discovery profile but unfortunately there is a bad CDT bug that keeps custom scanner discovery collectors from being used (you can select one but the original toolchain one always gets used instead).
The good news is that if someone on your team defines them once they can export the settings (File->Export->C/C++->Project Settings) for everyone else to import.
> 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
I think that searches your project contents for the includes, so if they are system includes it's not going to find them.
> 7) For remote projects, shouldn't standard system directories (at
> least /usr/include and /usr/include/sys) be the default for remote paths?
Again, these depend on the toolchain. For the XLC toolchain, this is the default, but unfortunately that scanner discovery/marker repopulation deadlock you saw before seems to happen more frequently with the XLC toolchain (I've seen it also with cygwin though so it's not a problem with the XLC toolchain itself).
I'm thinking that for 2.1.2 maybe I'll add in a Remote XLC toolchain to hopefully get around some of these problems. We're not really supposed to add features in the point release but the change would be pretty minor and would go a long way towards making things more usable for you.
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
Dave Wootton <dwootton@xxxxxxxxxx>
Sent by: ptp-user-bounces@xxxxxxxxxxx 03/07/2009 07:15 PM
|
|
