Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Re: Re: questions about building and modifying CDT plugins
Yes, I noticed that importing a .psf will checkout projects from HEAD. I was just wondering if there existed any .psf files that had the right paths for each project to checkout from a branch instead of HEAD. This would be so much nicer than having to either (a) individually check out each project from the right location, or (b) use the .psf to auto-check out HEAD, then individually update each project to branch.

Sorry for all my CVS questions - I'm a SVN user and not at all familiar with CVS. But they do pertain to the CDT CVS structure, so I suppose they're relevant.

T

On Thu, Mar 11, 2010 at 2:17 PM, John Cortell <rat042@xxxxxxxxxxxxx> wrote:
They're there, just buried. Look at the contents of the psf file. It's just a text file. It gives you the full cvs path to the projects.

My recommendation to work with 6.0 is to check everything out using the psf file. Then go through and do an update to the particular branch/tag you want (using Team > Switch to Another Branch or Version). I've never tried this, but I think it should work. Where it wouldn't is if a project that existed in 6.0 was removed and is thus not checked out by the psf. But I don't think that's the case. Anyway, it's worth a shot.

John



At 04:04 PM 3/11/2010, Tim Black wrote:
Thanks, John. I've been most interested in getting/working with 6.0.x to use with eclipse 3.5. This is the only reason I was getting cdt-platform branches and versions from CVS. Are there psf files for branches or versions?

If not, it looks to me like the only way to check out a CDT snapshot is to browse through Branches or Versions in CVS and check out individual projects following a checklist. But I don't even see any individual projects, e.g. org.eclipse.cdt.make.core, just the cdt-platform ones. And these don't build as mentioned in my previous posts. Most likely bc I'm checking them out at the wrong level like John mentioned. Bc I have been checking them out at the only level provided to me, which is, e.g. /cvsroot/tools/Versions/cdt-platform/cdt-platform CDT_6_0_2 or /cvsroot/tools/Branches/cdt_6_0/cdt-platform cdt_6_0.

So I'm not at all convinced that I'm getting the correct thing from CVS. I am using the CVS Repository Perspective in eclipse. Originally I didn't see anything under Branches or Versions. Then I did a "Refresh Branches" and eventually I was able to see some things under Branches and Versions, but all I see that looks applicable is Branches/cdt_6_0/cdt-platform and Versions/cdt-platform/ as I mentioned above. I expected to see the same contents there as I would see under HEAD/org.eclipse.cdt/all, but it's different - they're all packaged up into these cdt-platform projects which don't build when I check them out, and I can't browse beneath them to check out individual projects.

IS there some other configuration step I missed in CVS Perspective in Eclipse? Or is this a CVS permissions problem (I am anonymous)?

As for the errors I'm getting building HEAD, I'll wait a few hours and retry.

Tim


On Thu, Mar 11, 2010 at 12:52 PM, John Cortell <rat042@xxxxxxxxxxxxx> wrote:
Chances are you checked out the projects at the wrong level (some directory above where you should have checked them from).

When you checkout from cvs, you need to checkout specifically the project directories, not a directory that contains them. The preferred way to check out CDT is using the PSF. It is error-proof (assuming no CVS errors, of course) :-)

John


At 02:46 PM 3/11/2010, Tim Black wrote:
Understood.

Before even trying to work with HEAD, I was having trouble getting the 6.0.x CDT sources working with 3.5 eclipse sdk. I have tried Branches/cdt_6_0/cdt-platform cdt_6_0 and Versions/cdt-platform/cdt-
platform CDT_6_0_x. The resulting projects don't build. Not that they create build errors, they just don't build. I have Build Automatically checked and they don't create any output in the bin/ directory. Also, in File - Export - Deployable plug-ins and fragments, nothing is listed in the "Available Plug-ins and Fragments" like it was when I had only org.eclipse.cdt.make.core as a source project imported into my workspace. I get same behavior if I do File - Export - Deployable Features. Any ideas what's wrong here?

It looks to me like the "cdt-platform" projects in CVS are like metaprojects in SNV - they pull together project components under one umbrella. Is this the preferred item to checkout from CVS when their goal is to rebuild all of CDT?

Tim

On Thu, Mar 11, 2010 at 12:32 PM, John Cortell <rat042@xxxxxxxxxxxxx> wrote:
That was committed within the last  few hours, so perhaps this is another snag with the CVS mirroring. This happened a few weeks ago for someone else. Basically, non-committers work from a mirror CVS repository that is updated several times a day. If the synch operation happens in the middle of someone making a commit of numerous files, the mirror site can have a broken snapshot.
John

At 02:27 PM 3/11/2010, Tim Black wrote:
You beat me to it! ;-)
Hey, so any ideas on the IResumeWithoutSignalHandler error? I can't find its definition anywhere in any of the projects checked out via the project set...
Tim
On Thu, Mar 11, 2010 at 12:24 PM, John Cortell <rat042@xxxxxxxxxxxxx> wrote:
Yep.
I've already updated the wiki :-)
John
At 02:24 PM 3/11/2010, Tim Black wrote:
OK, thanks. It sounds like you're saying that using the .psf file is the accepted best practice for getting a complete set of CDT code from CVS. Unless I hear any argument, I will update the wiki page to that effect.
Any idea, though, why I'd be getting errors building org.eclipse.cdt.dsf.gdb.ui. (all related to resolving IResumeWithoutSignalHandler) Again I'm using CVS HEAD (via the psf file) and 3.6M5 Eclipse SDK?
Tim
On Thu, Mar 11, 2010 at 12:08 PM, John Cortell <rat042@xxxxxxxxxxxxx> wrote:
I meant..."on that wiki page."
At 02:06 PM 3/11/2010, John Cortell wrote:
Tim,
Disregard the list of projects on that directory. It shouldn't be there. What you want to do is use the project set file (psf) to download CDT from CVS. That file automates the process and ensures you get everything you need. The link to the psf was provided in the thread below.
John
At 01:57 PM 3/11/2010, Tim Black wrote:
Thanks for the feedback, Dave.
I just did a fresh install of 3.6M5 Eclipse SDK, then from CVS HEAD checked out all the necessary CDT projects listed at http://wiki.eclipse.org/Getting_started_with_CDT_development, and I get lots of "cannot be resolved to type" errors in org.eclipse.cdt.managedbuilder.gnu.ui. (can't resolve BuildEnvVar, BuildException, BuildEnvironmentVariable, ...)
Assuming this error isn't a transient due to some non-atomic commit, I'm guessing the wiki list is just out of date and I don't really have all the necessary projects. The project set appears to be a superset of the wiki list. I started over and this time imported the project set, and now I get almost no errors. Progress! But I am getting 5 errors in org.eclipse.cdt.dsf.gdb.ui. (all related to resolving IResumeWithoutSignalHandler) This is much better, but does anyone know why I'm getting this error using CVS HEAD and 3.6M5 Eclipse SDK? Dave, did you get this error?
Tim
On Thu, Mar 11, 2010 at 7:56 AM, Dave Korn < dave.korn.cygwin@xxxxxxxxxxxxxx> wrote:
On 11/03/2010 14:25, Dave Korn wrote:
> predefined CDT project set from http://www.eclipse.org/cdt/psf/cdt-main.psf
> and everything "just worked" first time for me.
 Sorry, I forgot one little thing: I had to(*) manually edit the .psf file to
replace ":extssh:dev.eclipse.org:" with ": pserver:anonymous@xxxxxxxxxxxxxxx:",
because it's designed for devs who have write access to the repository.  Apart
from that it was all plain sailing.
   cheers,
     DaveK
--
(*) - There's probably a way to change this in the UI, but I don't know well
enough, which is why I say I "had to".
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


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


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


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

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


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

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


Back to the top