[
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
|
If frequent API changes between plugins is a real problem (which is not the case for build plugins btw) one could check out from CVS tag from which the build was done. That would take care of broken HEAD snapshots as well. But of course you won't be able to update from the HEAD then.
Andrew
On Thu, Mar 11, 2010 at 3:29 PM, John Cortell
<rat042@xxxxxxxxxxxxx> wrote:
We should post a disclaimer that this approach usually has a short shelf
life. We change internal APIs all the time, so using an integration
snapshot against the latest HEAD version of a plugin
may succeed
in the short term (but can just as easily not succeed), but you will
likely find yourself with build errors if you do a CVS update down the
road. For that reason, it really is best to just get all the plugins from
CVS if you're going to be working with the sources for a while.
John
At 02:23 PM 3/11/2010, Andrew Gvozdev wrote:
Did you install CDT itself? In
most cases it is enough to check out just the plugin you are interested
in. So it would be this way:
1. Install 3.6M5 Eclipse SDK
2. Install latest CDT 7.0 build from
http://download.eclipse.org/tools/cdt/builds/7.0.0/index.html
3. Check out the plugin you are interested in
(org.eclipse.cdt.make.core?). For a good measure also check out
org.eclipse.cdt.core (in case any dependency was introduced since last
build).
4. It should compile automatically. Do "Debug as Eclipse
Application" to test it.
Andrew
On Thu, Mar 11, 2010 at 2:57 PM, Tim Black
<timblaktu@xxxxxxxxx>
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