Re: [ptp-dev] Synchronized Project Build Output Location

[Wyatt Spear <wspear@xxxxxxxxxxxxxx>]

That's great, thanks!  That will get me the path.  I will need to do a little string juggling to make sure the right executable is found and launched but I can work with this for now.  It will always throw an exception of the project is not of the synchronized variety?  I'm not seeing any other way to check if I need to use this method or not.

The bug is posted.  For me, helper methods to get the IFileSource for built binaries would be ideal, but I'd settle for making the API externally available.

Regards,

Wyatt

On Fri, Sep 9, 2011 at 5:32 PM, Roland Schulz <roland@xxxxxxx> wrote:

On Fri, Sep 9, 2011 at 6:03 PM, Wyatt Spear <wspear@xxxxxxxxxxxxxx> wrote:

What component would this be under, bug-wise?

RDT.sync

 

Also is there anything I can try in the meantime as a stop-gap measure?  I have access to the ILaunchConfiguration, ICProject and IManagedBuildInfo objects which are enough to let me launch the synchronized build so the remote resources/paths must be buried in there somewhere.  I would be willing to deal with some spaghetti code to get the remote paths out until a formal API is introduced.  If I can get this working I might be able to slide it in under the next 5-branch release.

This should do it: 

IConfiguration configuration = ManagedBuildManager.getBuildInfo(project).getDefaultConfiguration(); 

BuildConfigurationManager.getInstance().getBuildScenarioForBuildConfiguration(configuration).getLocation();

You can also look at org.eclipse.ptp.rdt.sync.core.remotemake.SyncCommandLauncher.execute(IPath, String[], String[], IPath, IProgressMonitor) to see how we do it.

Of course this depends on the internal BuildConfigurationManager. But I suppose you can use it if you don't mind the API warnings.

Roland

 

Thanks,

Wyatt

On Fri, Sep 9, 2011 at 2:52 PM, John Eblen <jeblen@xxxxxxx> wrote:

Okay, I see. For synchronization projects, unfortunately, the paths are stored internally. Feel free to file a bug on this, and I'll look into making this data more accessible.


Thanks
John

On Fri, Sep 9, 2011 at 4:50 PM, Wyatt Spear <wspear@xxxxxxxxxxxxxx> wrote:

Basically I'm using:  CProject.getResource().getLocationURI().getPath(); which returns the local project path.  I need an equivalent call to get the remote resource/path.

=Wyatt

On Fri, Sep 9, 2011 at 12:56 PM, John Eblen <jeblen@xxxxxxx> wrote:

Hi Wyatt

How are you accessing this information? What class and method are you using? I'm somewhat confused because the sync builder itself is just an extension point (defined in org.eclipse.ptp.rdt.sync.core/plugin.xml). Also, the executable path depends on the build configuration. Some configurations may build locally.


John

On Fri, Sep 9, 2011 at 3:17 PM, Wyatt Spear <wspear@xxxxxxxxxxxxxx> wrote:

Greetings,

So, I thought I had it all together as far as remote ETFW but synchronized projects aren't quite there yet.  The problem is the synchronized project builder returns an executable path on the local file-system.  Is there any way to get the actual path or store for the remotely built executable out of the synchronized builder?

Thanks,

Wyatt

_______________________________________________
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

--
ORNL/UT Center for Molecular Biophysics cmb.ornl.gov
865-241-1537, ORNL PO BOX 2008 MS6309

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