Home » Eclipse Projects » Eclipse Platform » CVS Modules
| CVS Modules [message #312829] |
Wed, 21 February 2007 11:10  |
Eclipse User |
|
|
|
Originally posted by: mike.replacewithmylastname.com
I apologize in advance for this dumb question. I'm trying to build
Eclipse for Windows from the CVS sources, but I'm not sure which modules
to get. Can anyone let me know which modules to get (and whether to
import it as a project). I've done my best to RTFM and STFW and somehow
can't find this, so pointers are welcome.
Thanks,
Mike
|
|
| | |
| Re: CVS Modules [message #312843 is a reply to message #312841] |
Wed, 21 February 2007 15:57  |
| Eclipse User |
|
|
|
Originally posted by: jacek.pospychala.pl.ibm.com
Mike,
if you're not oriented in these modules use, then it might be difficult
to understand any problems you'll have to face when configuring whole
build environment.
I assume that you are aware of Eclipse CVS repositories:
http://wiki.eclipse.org/index.php/CVS_Howto#CVS_Repository_P aths
The only one you'll be interested in is /cvsroot/eclipse
In the meantime I've also found an excellent FAQ for you:
http://wiki.eclipse.org/index.php/Platform-releng-faq
but some information there is outdated, so again deeper knowledge will
be required. You may also ask questions on any problems you'll find,
here on newsgroups.
Mike Spertus napisał(a):
> Jacek Pospychala wrote:
>> Mike,
>> i haven't built Eclipse from sources, but I think, you should have a
>> look at org.eclipse.releng* projects in eclipse CVS (/cvsroot/eclipse)
>>
> I'm afraid I'm not even that far. I'm still figuring out what to check
> out of CVS. The select modules screen shows a couple of hundred modules.
> Which one should I check out to build Eclipse?
>
> Thanks,
>
> Mike
>
>> Mike Spertus napisał(a):
>>> I apologize in advance for this dumb question. I'm trying to build
>>> Eclipse for Windows from the CVS sources, but I'm not sure which
>>> modules to get. Can anyone let me know which modules to get (and
>>> whether to import it as a project). I've done my best to RTFM and
>>> STFW and somehow can't find this, so pointers are welcome.
>>>
>>> Thanks,
>>>
>>> Mike
|
|
|
| Re: CVS Modules [message #312848 is a reply to message #312829] |
Wed, 21 February 2007 20:59 |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"Mike Spertus" <mike@replacewithmylastname.com> wrote in message
news:erhqtc$5ke$1@utils.eclipse.org...
>I apologize in advance for this dumb question. I'm trying to build Eclipse
>for Windows from the CVS sources, but I'm not sure which modules to get.
>Can anyone let me know which modules to get (and whether to import it as a
>project). I've done my best to RTFM and STFW and somehow can't find this,
>so pointers are welcome.
Eclipse is not really just one thing, so there's no one answer to your
question. Eclipse is a modular architecture, with many plug-ins that all
fit together. It is released in several combinations - for instance,
Equinox; the Eclipse Rich Client Platform; the Eclipse SDK; the Eclipse Web
Tooling Platform; and so on. Each of these builds on others.
So the answer to which modules you need to get depends on which version of
Eclipse you're trying to build.
But one way of looking at this is: why do you need to build it at all? Are
you:
1. on an unusual platform?
2. just trying to make some modifications to particular functionality?
3. trying to extend Eclipse with additional functionality?
I'm guessing it's not #1, because you said "for Windows."
If it's #2, then all you need to do is download an already-built version of
the appropriate component(s), and then edit and build the particular
plug-ins containing the functionality you want to modify. In fact Eclipse
makes it easy: just start up Eclipse, create a new workspace, switch to the
Plug-in Development perspective, click on the Plug-ins tab, select the
plug-in(s) you want to modify, right-click and select "Import As Source".
Presto, you've got a development workspace with the full source code of
those plug-ins, ready to edit.
And if it's #3, it's even easier than that; you shouldn't have to edit any
existing plug-ins at all, all you need to do is write new ones.
I'd strongly recommend reading the book "Eclipse: Building Commercial
Quality Plug-ins" (ISBN 032142672X), if the answer is #2 or #3.
|
|
|
| Re: CVS Modules [message #312922 is a reply to message #312848] |
Sun, 25 February 2007 12:32 |
| Eclipse User |
|
|
|
Originally posted by: mike.replacewithmylastname.com
Walter,
Thanks! This is exactly what I was looking for. I was actually doing
your option #2, and you're instructions are fine. However, it turns out
that Eclipse 3.3 M5 has the changes I was looking for anyway, so I don't
need to do any work at all! I still am curious, though, about which
modules I would need to get to build the Eclipse SDK.
Thanks,
Mike
Walter Harley wrote:
> "Mike Spertus" <mike@replacewithmylastname.com> wrote in message
> news:erhqtc$5ke$1@utils.eclipse.org...
>> I apologize in advance for this dumb question. I'm trying to build Eclipse
>> for Windows from the CVS sources, but I'm not sure which modules to get.
>> Can anyone let me know which modules to get (and whether to import it as a
>> project). I've done my best to RTFM and STFW and somehow can't find this,
>> so pointers are welcome.
>
> Eclipse is not really just one thing, so there's no one answer to your
> question. Eclipse is a modular architecture, with many plug-ins that all
> fit together. It is released in several combinations - for instance,
> Equinox; the Eclipse Rich Client Platform; the Eclipse SDK; the Eclipse Web
> Tooling Platform; and so on. Each of these builds on others.
>
> So the answer to which modules you need to get depends on which version of
> Eclipse you're trying to build.
>
> But one way of looking at this is: why do you need to build it at all? Are
> you:
> 1. on an unusual platform?
> 2. just trying to make some modifications to particular functionality?
> 3. trying to extend Eclipse with additional functionality?
>
> I'm guessing it's not #1, because you said "for Windows."
>
> If it's #2, then all you need to do is download an already-built version of
> the appropriate component(s), and then edit and build the particular
> plug-ins containing the functionality you want to modify. In fact Eclipse
> makes it easy: just start up Eclipse, create a new workspace, switch to the
> Plug-in Development perspective, click on the Plug-ins tab, select the
> plug-in(s) you want to modify, right-click and select "Import As Source".
> Presto, you've got a development workspace with the full source code of
> those plug-ins, ready to edit.
>
> And if it's #3, it's even easier than that; you shouldn't have to edit any
> existing plug-ins at all, all you need to do is write new ones.
>
> I'd strongly recommend reading the book "Eclipse: Building Commercial
> Quality Plug-ins" (ISBN 032142672X), if the answer is #2 or #3.
>
>
|
|
|
Goto Forum:
Current Time: Sun Jul 27 13:48:03 EDT 2025
Powered by FUDForum. Page generated in 0.56757 seconds |
Home