Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ptp-user] Remote Build Location

Thanks Markus, make -C is a great work around.  I'll see if I can't find the bug today.

Greg

On Mon, Aug 24, 2015 at 7:54 AM, Kubot, Markus AVL/DE <markus.kubot@xxxxxxx> wrote:

Hi all,

it’s funny, that is exactly my problem for several weeks now if you have a look to the subject in the previous mailing list “Synchronized Project eclipse LUNA”

 

THIS IS A BUG because in INDIGO all worked well synchronizing and the start of make in any remote directory.

Try  make –C….

 

Best regards

 

Markus

 

Von: ptp-user-bounces@xxxxxxxxxxx [mailto:ptp-user-bounces@xxxxxxxxxxx] Im Auftrag von Greg W
Gesendet: Freitag, 21. August 2015 21:59
An: PTP User list
Betreff: Re: [ptp-user] Remote Build Location

 

This is a simple Hello World Makefile synchronized project created through the new project wizard.  Or are you just suggesting I create a simple Hello World makefile project on the remote machine just to verify make, gcc, etc are setup correctly on the remote machine?

Here's some more information that may or may not be helpful:

The files are synchronizing correctly, they show up on the remote machine in the remote path specified in the new project wizard.  If I open a terminal to the remote machine in eclipse and navigate to my remote sync'd folder I can run make to compile the hello world example and it compiles and runs just fine.

I was thinking I'd have a look at some of the source for the project.  Are the instructions found here: https://wiki.eclipse.org/PTP/environment_setup_80 still correct?

Thanks!

Greg

 

 

On Fri, Aug 21, 2015 at 2:31 PM, John Eblen <jeblen@xxxxxxx> wrote:

One idea would be to create a simple "Hello World" Makefile project, using the same

remote machine, and see if the problem persists. This would narrow down the possible

causes. (The Linux GCC toolchain is very common, so that is probably not the problem.)

 

 

Thanks

John

 

On Fri, Aug 21, 2015 at 2:33 PM, Greg W <grwoodw@xxxxxxxxx> wrote:

Hi John,

I selected Linux GCC as the toolchain.  If it is a bug, how can I help find and fix it?

Thanks,

Greg

 

On Fri, Aug 21, 2015 at 1:17 PM, John Eblen <jeblen@xxxxxxx> wrote:

Hi Greg

 

I don't see anything you are doing wrong. This seems to be a bug. The "OLDPWD"

value is quite interesting. It suggests that somewhere in the command construction

an extra "cd" command is being added. What toolchain did you select when you

created the project?

 

 

Thanks

John

 

On Fri, Aug 21, 2015 at 12:25 PM, Greg W <grwoodw@xxxxxxxxx> wrote:

John,

Thanks for your response.  I must not understand something correctly.  I have read the discussion from April and selected "Replace native environment with specified one" in C/C++ Build -> Environment and I have tried several combinations for the values of the default variables CWD and PWD with no apparent impact on the result.

To try to understand what is going on behind the scenes In C/C++ Build -> Builder Settings I have deselected "Use default build command" and left "build command:" blank.  Build directory is the default: "${workspace_loc:/HelloWorld-Sync}". Then in the behavior tab I selected "Build (Incremental build)" and entered "env" in the text box.  When I hit the build button I expect to get the remote system's environment variables and I do.  What I find peculiar is the OLDPWD and PWD environment variables:

OLDPWD=/home/greg/ptp/workspace/HelloWorld-Sync
PWD=/home/greg

It seems that on the remote system the directory is getting changed from my sync'd directory to my home directory.  Am I doing something wrong?  what am I missing?

Thanks for your time!

Greg



 

On Fri, Aug 21, 2015 at 10:33 AM, John Eblen <jeblen@xxxxxxx> wrote:

Hi Greg

 

PTP should run make in the same directory where files are sync'ed. (CDT is unaware

of the remote system, so changing the path in the CDT dialogs won't help.)

 

For WIndows, the exported environment variables can sometimes cause problems. The

below discussion on the mailing list from April may help:

 

 

---------- Forwarded message ----------
From: John Eblen <jeblen@xxxxxxx>
Date: Fri, Apr 24, 2015 at 10:59 AM
Subject: Re: [ptp-user] remote build of synchronized fortran project - ptp under windows
To: PTP User list <
ptp-user@xxxxxxxxxxx>

If I understand it correctly, the "native" environment means the environment variables already

set on the local machine outside of Eclipse. The "specified" environment means the variables that

are set inside Eclipse. The specified environment is always appended.

 

Thus if Windows environment variables are set in C/C++ preferences, they will always be included.

It doesn't matter where the build occurs. (PTP synchronized projects simply forward the build

command created by CDT, the plug-in that manages C/C++ projects.)

 

Remote environment variables are a combination of what is set in CDT and what is already

configured on the remote system. PTP's "environment management system," though, provides

a way to load modules on the remote system.

 

 

John

 

On Fri, Aug 21, 2015 at 10:24 AM, Greg W <grwoodw@xxxxxxxxx> wrote:

please forgive me if this question has already been asked.  I haven't been able to find a solution.  I have Eclipse for Parallel Application Developers (Mars) installed on a Windows 7 machine and all the updates from https://download.eclipse.org/tools/ptp/updates/mars.  When I create a synchronized C/C++ Makefile project and try to build the project I get the following error:

 

Make all

make: *** No rule to make target 'all'. Stop.

 

I'm pretty confident this is an issue with eclipse trying to build in the wrong path.  When I remove the default build command and enter 'pwd' in Build (Incremental build) on the behavior tab it displays my home folder on the remote machine instead of the project path.  When I try to manually specify the build directory eclipse appends my home directory path and c: to the manually entered path.  When I click the 'file system' button to specify the build path it opens a file browser for my local windows file system.  Shouldn't it open a file browser for the remote file system?

 

Any help anyone can provide would be greatly appreciated!

 

Thank you,

Greg

 

_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-user

 

 

On Fri, Aug 21, 2015 at 10:24 AM, Greg W <grwoodw@xxxxxxxxx> wrote:

please forgive me if this question has already been asked.  I haven't been able to find a solution.  I have Eclipse for Parallel Application Developers (Mars) installed on a Windows 7 machine and all the updates from https://download.eclipse.org/tools/ptp/updates/mars.  When I create a synchronized C/C++ Makefile project and try to build the project I get the following error:

 

Make all

make: *** No rule to make target 'all'. Stop.

 

I'm pretty confident this is an issue with eclipse trying to build in the wrong path.  When I remove the default build command and enter 'pwd' in Build (Incremental build) on the behavior tab it displays my home folder on the remote machine instead of the project path.  When I try to manually specify the build directory eclipse appends my home directory path and c: to the manually entered path.  When I click the 'file system' button to specify the build path it opens a file browser for my local windows file system.  Shouldn't it open a file browser for the remote file system?

 

Any help anyone can provide would be greatly appreciated!

 

Thank you,

Greg

 

_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-user

 


_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-user

 


_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-user

 


_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-user

 


_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-user

 


_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-user

 


_______________________________________________
ptp-user mailing list
ptp-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ptp-user


Back to the top