scottellington at comcast.net
Thu Mar 23 16:46:31 EST 2006
Let me go ahead and summarize what my ideas are for this Addin and then
mention a few issues I already foresee:
This addin will take the configuration details for a given solution and
it's child solutions and projects, and create a complete AutoTools setup
for it. This will allow developers to follow Mono's deployment
( http://www.mono-project.com/Guidelines:Application_Deployment )
without having to get their hands dirty in the pain that is autotools.
Lluis and others have other goals for AutoTools integration. It would
be better for them to describe those.
Here are couple of issue that have already sprung to mind (Note: my
Autotools knowledge is not limitless, so please correct me if I am
mistaken in any way):
1) autotools works in a hierarchical manner. That is, everything is
under one directory, often organized into subdirectories. Yet MD can
link to projects/solutions in different directories and so forth. I
don't know exactly how to reconcile this.
2) MD stores reference to things like gtk# as GAC references. Yet we
would probably want to be testing for the gtk-sharp-2.0 pkg-config
module. How do we go about this? Do we need another reference type?
This brings up another possible feature for the autotools addin:
creating pkg-config (pc) files for libraries.
There are probably many more issues, these are just the first I see.
On Tue, 2006-03-21 at 11:13 -0500, Scott Ellington wrote:
> I think I'm going to put together a basic addin for AutoTools
> integration. I put my name up on the TODO list on the website. More
> details to follow.
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
More information about the Monodevelop-list