[asterisk-dev] Setting up a development environment for Asterisk

Tilghman Lesher tilghman at meg.abyt.es
Tue Jan 11 16:16:12 CST 2011

On Tuesday 11 January 2011 15:08:58 Nick Khamis wrote:
> >>I'm not sure breaking Makefile would be the best approach.
> I will manually go through each module, and modify the makefiles to
> reflect the
> new directory structure.
> >>I don't think we'll have an issue adding the workspace under
> contrib/eclipse directory.
> That would be real good Paul. That way I can check in as I complete a
> module.
> I will have to do this manually to make sure nothing is getting
> disconnected code, makefiles and so on.

I do have a slight concern with this being your first contribution to the
Asterisk project.  What I'm specifically afraid of is that this will become
your only contribution, you disappear, and you leave behind a set of files
to maintain, which, inevitably, will fall out of date with a change to the
core build process, leaving behind bitrot.  I'd like to believe you'll
stick around after creating this, but given past history with several
external contributors, I am, to say the least, skeptical.

I'd encourage you to learn the existing system, first, before embarking
on a quest to convert Asterisk to using Eclipse, so you understand the
benefits of the system we have already, before you try to convince us
we need to maintain your Eclipse project code.


More information about the asterisk-dev mailing list