Re: [ptp-user] A command and a question about Synchronized Projects in I

[Greg Watson <g.watson@xxxxxxxxxxxx>]

Corey,

Thanks for your feedback!

I'll say a couple of things, then I'll let Roland and/or John (who have done most of the work) respond.

The original idea was not to replace Team support in Eclipse, but to provide a separate mechanism for supporting remote projects. So I had always envisioned checking out the project from CVS (or GIT or SVN) into my workspace, then converting to a synchronized project. This way, commits to the main repo would still be managed by the user through the Team interfaces, and the commits to the synchronized version would be purely for the purpose of keeping it in sync. However, that doesn't mean your suggestion to batch commits wouldn't be a useful option.

Regarding remote include files. I implemented a mechanism for supporting remote includes in CDT that is in the latest builds. However, we haven't managed to get this to work automatically with synchronized project yet, as it requires some integration with the remote scanner discovery (the thing that discovers what includes/defines are set on the remote system). I'm not sure if this will make it into 5.0 or not yet. However, in the mean time you can play with manually configuring remote includes. All you need to do is to open the project properties, go to C/C++ General Settings > Paths and Symbols. Then choose the build configuration you want to use. Click on GNU C and remove the existing paths. Then add new paths to the remote include directories using UNC notation (e.g. //<connection>/usr/include where <connection> is the name of the connection you specified for Remote Tools).

Hope this helps,
Greg

On May 17, 2011, at 6:57 PM, Corey Ashford wrote:

> 
> Hi Folks,
> 
> I am evaluating the different remote project capabilities in PTP, and
> I'm currently looking at the "Synchronized Project" type.
> 
> I've played around with it a bit, and so far it looks pretty cool!  I
> like how transparent it is in using Git (the only synchronization option
> available, it appears) to synchronize the source and target directories.
> 
> There is no online help that I could find, so I had to take some guesses
> as to how to set it up, but after doing that, it sort of "just worked"
> and seems to be very fast and transparent.  I even threw an existing Git
> project at it, and it worked without a hitch.
> 
> One concern I have about the way it uses Git: it seems to play fast and
> loose with making commits, especially to existing Git trees.  My
> intuition is that some people will find it objectionable.  If I was
> working on a source tree that was maintained using Git, I think I would
> be annoyed too, that I would have to collapse perhaps tens of commits
> into one real one.
> 
> I had set up something similar, that synchronizes the host and target
> source using a shared git tree.  The synchronization step was postponed
> till a build was attempted, and instead of making an actual commit, a
> list of of modified+staged files is created and then rsync'd to the
> target.  At some point you want to commit your changes in a series of
> one or more patches, and when you do that, you do a "git reset --hard"
> on the target side, and then pull after the commit(s) are pushed from
> the local side.  This followed a "master repo" set-up, but I think you
> could adapt it for a peer-to-peer setup.
> 
> I'm not suggesting that you switch to a similar system, but eliminating
> the large number of commits that are done to the tree would be a desired
> feature.
> 
> -----
> 
> My question: Is there any capability to deal with remotely-located
> include files (for example /usr/include/string.h) ?  I couldn't find any
> way to add remotely-located paths.
> 
> Thanks for your consideration,
> 
> - Corey
> _______________________________________________
> ptp-user mailing list
> ptp-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-user