Well, I suppose it all depends on how similar the D project files are to the 
C++ ones. I did try to abstract out common functions between the C++ and C# 
support. The more data points I have to work with, the easier it will be to 
identify the areas that need more abstraction (and what it should look like).

On Mar 4, 2012, at 4:04 AM, Gour wrote:

> Hello!
> 
>> Out of curiosity, do you have any plans to support Visual Studio (i.e.
>> Visual D - http://www.dsource.org/projects/visuald)?
> 
> I have contacted Andrew who is working on D support for premake in
> regard and he replied:
> 
> "As for Visual Studio, I'd only do it if/when I needed it, and I
> (currently) only develop on Linux, so I don't have the burning need. I
> would like to add support for Code::Blocks if I ever get the chance. VS
> probably wouldn't be all that hard except for all the various versions
> etc. and the fact that I would struggle to test it."
> 
> which made me think how hard/easy is to add new langauge support to
> premake, iow. how much is language support decoupled from the format
> (project files, Makefiles...) support?
> 
> Iow, I wonder if one wants to add support for new language, one has to
> write down from scratch all the suppor for different formats as well or
> it's possible to take advantage of the current infrastructure as well?
> 
> Does 4.4 change the situation?
> 
> 
> Sincerely,
> Gour


------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Premake-users mailing list
Premake-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/premake-users

Reply via email to