Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ptp-dev] Convert to Synchronized project using remote xlC compiler toolchain

>Please double check this, and If it still doesn't work let me know where you changed the directory.
Yes it still doesn't work. here is what I did:

I the convert to Sync Project wizard I specified
Remote Provider RT, Connection name, Location:  /myhomedir_on_remote_system/shallowForJohn


Build Configs > Set Active > Remote

Then I edit project properties
and C/C++ Build .... Build location    is still the project location in my local workspace

I forced a sync first




...Beth

Beth Tibbitts
Eclipse Parallel Tools Platform  http://eclipse.org/ptp
IBM STG - High Performance Computing Tools
Mailing Address:  IBM Corp., 745 West New Circle Road, Lexington, KY 40511

Inactive hide details for John Eblen ---09/21/2011 04:43:39 PM---Yes, 1 and 3 are necessary, but 2 should not be. If the correcJohn Eblen ---09/21/2011 04:43:39 PM---Yes, 1 and 3 are necessary, but 2 should not be. If the correct remote location is given in the wiza


    From:

John Eblen <jeblen@xxxxxxx>

    To:

Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>

    Date:

09/21/2011 04:43 PM

    Subject:

Re: [ptp-dev] Convert to Synchronized project using remote xlC compiler toolchain

    Sent by:

ptp-dev-bounces@xxxxxxxxxxx



Yes, 1 and 3 are necessary, but 2 should not be. If the correct remote location is given in the wizard, the build directory should not have to be changed. Please double check this, and If it still doesn't work let me know where you changed the directory.

As for local navigation, I think the "Remote Includes Path" section of the help page addresses this.


Thanks
John

On Wed, Sep 21, 2011 at 4:04 PM, Beth Tibbitts <tibbitts@xxxxxxxxxx> wrote:
    Well with some help from Chris, I think I have this working. At least building cleanly.
    I check the initial project out from CVS, thus in a local project -- Makefile project, and what works best is setting the toolchain to Remote XLC (because i want to eventually build it there)
    Then convert to sync project, and change build config to remote

    But what the "convert to sync project" doesn't seem to be doing is to change the build directory to the location of the remote project on the local machine
    (this was also true when i didn't specify a toolchain).  It still points to the local of the project on the local machine.

    I also need to change the project properties to the location of the xlC compiler on the remote machine. (then close and re-open project, and scanner discovery now finds the remote includes it needs)

    So when the following are set correctly
    1. toolchain (specified on initial local project creation even tho it doesn't match local machine)
    2. build directory (had to do this manually, shouldn't the wizard do that?)
    3. xlC path, did this in project properties manually too, I don't have xlC on my local machine.
    I can build correctly

    What should local navigation (hyperlinking to include files, for example) be doing for a sync project?
    I must admit I do not know all the details/differences of sync vs. pure remote projects.



    ...Beth

    Beth Tibbitts
    Eclipse Parallel Tools Platform      http://eclipse.org/ptp
    IBM STG - High Performance Computing Tools
    Mailing Address:  IBM Corp., 745 West New Circle Road, Lexington, KY 40511

    Inactive hide details for Chris Recoskie ---09/21/2011 02:15:33 PM---The problem could be that perhaps you are copying the scanChris Recoskie ---09/21/2011 02:15:33 PM---The problem could be that perhaps you are copying the scanner discovery profile/profileID from the l

    From:

Chris Recoskie <recoskie@xxxxxxxxxx>
    To:

Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
    Date:

09/21/2011 02:15 PM
    Subject:

Re: [ptp-dev] Convert to Synchronized project using remote xlC compiler toolchain
    Sent by:

ptp-dev-bounces@xxxxxxxxxxx



    The problem could be that perhaps you are copying the scanner discovery profile/profileID from the local config. The remote config should have a remote discovery profile.

    The compiler path in the XLC page is a resource property on the project, if I recall.

    ===========================
    Chris Recoskie
    Team Lead, IBM CDT and RDT
    IBM Toronto

    Inactive hide details for John Eblen ---09/21/2011 12:58:25 PM---The conversion wizard copies the settings of the active configJohn Eblen ---09/21/2011 12:58:25 PM---The conversion wizard copies the settings of the active configuration when creating the Remote confi

    From:
    John Eblen <    jeblen@xxxxxxx>

    To:
    Parallel Tools Platform general developers <    ptp-dev@xxxxxxxxxxx>

    Date:
    09/21/2011 12:58 PM

    Subject:
    Re: [ptp-dev] Convert to Synchronized project using remote xlC compiler toolchain

    Sent by:
    ptp-dev-bounces@xxxxxxxxxxx



    The conversion wizard copies the settings of the active configuration when creating the Remote configuration. Inside C/C++ Build you can then change the settings for Remote. Oddly, though, the XL C/C++ compiler page does not allow you to select a configuration. So I don't know which configurations are altered when this is changed.

    On Wed, Sep 21, 2011 at 11:39 AM, Beth Tibbitts <    tibbitts@xxxxxxxxxx> wrote: 
      I'm having trouble converting a local C/C++ project to a sync project that needs the xlC toolchain on the remote system.
      I made the original local project specify the xlC/C++ toolchain (not remote).  The remote machine is Linux.
          I did not modify the default locations of xlc or the version
      It's an MPI program, not that it matters.  "Shallow" our typical PTP tutorial exercise.
      when i convert it, get the makefile to get called and no build errors,

      I have the remote project building
      but am getting some errors like "Cannot run program '/xlc' and 'xlC' "  
      and what looks like some other problems.
      Any ideas?
      I do not get this problem when i specify e.g. Mac GCC toolchain on the local project, then the remote system in Linux and GCC.
      l

      I still get the above even If I change project properties, C/C++ Build, XlC/C++ compiler, compiler root path to be correct.
      (xlC is in my path and can be found by command line on the remote sys)
      This part of project properties looked like it dealt with local only, but does the sync project take it to use it?

      It does appear to have built ok, i have .o's and executable.

      Any idea what's going on?


      ...Beth

      Beth Tibbitts
      Eclipse Parallel Tools Platform        http://eclipse.org/ptp
      IBM STG - High Performance Computing Tools
      Mailing Address:  IBM Corp., 745 West New Circle Road, Lexington, KY 40511

      _______________________________________________
      ptp-dev mailing list
      ptp-dev@xxxxxxxxxxx
      https://dev.eclipse.org/mailman/listinfo/ptp-dev
    _______________________________________________
    ptp-dev mailing list
    ptp-dev@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/ptp-dev

    _______________________________________________
    ptp-dev mailing list
    ptp-dev@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/ptp-dev



    _______________________________________________
    ptp-dev mailing list
    ptp-dev@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev


JPEG image

JPEG image

GIF image

GIF image

JPEG image

Back to the top