Bug 397631 - Connection-qualified include paths used in managed build
Summary: Connection-qualified include paths used in managed build
Status: NEW
Alias: None
Product: PTP
Classification: Tools
Component: RDT.sync (show other bugs)
Version: 7.0.2   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-07 17:14 EST by Dave Hudak CLA
Modified: 2014-08-11 15:05 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Hudak CLA 2013-01-07 17:14:09 EST
When I create a managed build synchronized project, I provide include paths in the project properties that are qualified with the connection name (e.g., //oakley/nfs/14/samsi/devel/openslide-3.3.2/include/openslide).  This allows the indexer to find the remote system header files and resolve the program's symbols.  

However, when I try to build the project, the connection-qualifier is passed to the remote system:

12:08:12 **** Build of configuration Debug_remote for project sid-sync-5 ****
make all 
Building file: ../opencvtest.cpp
Invoking: GCC C++ Compiler
g++ -I//oakley/nfs/14/samsi/devel/openslide-3.3.2/include/openslide -I//oakley/nfs/14/samsi/devel/opencv-2.4.2/include -I//oakley/nfs/14/samsi/devel/opencv-2.4.2/include/opencv -I//oakley/nfs/14/samsi/devel/opencv-2.4.2/include/opencv2/core -I//oakley/nfs/14/samsi/devel/opencv-2.4.2/include/opencv2/flann -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"opencvtest.d" -MT"opencvtest.d" -o "opencvtest.o" "../opencvtest.cpp"

This prevents the project from building.  If I go back to the project properties and remove the connection name, the build works but the indexer does not.
Comment 1 Beth Tibbitts CLA 2013-01-08 09:00:30 EST
See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=390233
for other sync project problems
Comment 2 Greg Watson CLA 2013-04-26 16:29:19 EDT
I believe this is a managed project, which is why we didn't notice this problem before.
Comment 3 Greg Watson CLA 2014-05-29 17:11:13 EDT
Changed version to 7.0.2
Comment 4 Steven R. Brandt CLA 2014-08-11 15:05:23 EDT
Workaround: if you click "is a workspace path" then the path isn't passed to the remote machine.

You can add each path twice, once with the //oakley (check "is a workspace path"), and once without (uncheck "is a workspace path").