[Mono-dev] Sharing build specs between MS VS .net 2005 and mono on Linux

[Leszek Ciesielski]

xbuild (mono's msbuild equivalent) is being extended to support vs2005
files, but the works are progressing slowly. (MSBuild is used
internally by VS and SD to build projects).

As for now, company I'm working for is using NAnt together with custom
script that generates VS2005 projects from the NAnt *.build files.
This is a bit hackish, and NAnt has it's shortcomings (eg. is a bit
bugged), but it's the best solution we had tested (our project started
on mono+linux, now it is also developed on mono+windows/ms.net+windows
by several developers). cmake looks promissing, but as you said, it
currently lacks certain features.

Optimally, xbuild would support new msbuild format files, and
switching between mono and ms.net would be a complete no brainer :-)

On 9/15/06, Mads Bondo Dydensborg <mbd at dbc.dk> wrote:
> Hi there
>
> My company is developing a (non-GUI) product that eventually will need to be
> able to run under both Mono/Linux and MSCLI/Windows.
>
> Currently the development takes place on Windows, using MS VS .net 2005.
> However, we are adding new developers (including me), which are developing in
> a Linux based environment. This means, that we would like to have a build
> environment that is supported both under VSNET05 and Linux/Mono.
>
> Now, I understand that MonoDevelop and prj2make has been able to work with
> VSNET 2003 project files, but will not work with 2005 project files. Are
> there any work taking place to support the newer format?
>
> Alternatively, what soloutions could you recommend in supporting both
> environments from some sort of common build specification at the same time?
>
> I looked at cmake, which have the ability to generate project files for
> VSNET05 and makefiles for Linux from a general specification file, but using
> cmake would require extending it with support for C#.
>
> I also looked briefly at nAnt, which looks good, but the initial comment from
> the Windows developers has been that they feel it lacks integration with
> Visual Studio .net 2005.
>
> Comments on these solutions, general advise, etc, very much welcomed. I
> imagine we are not the only company that has faced this kind of problem?
>
> Regards & thanks in advance,
>
> Mads
>
> --
> Med venlig hilsen/Regards
>
> Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg
> Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 44 86 77 34
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>


-- 
MS-DOS user since 5.0
Windows user since 3.11
Linux user since kernel 2.4
Novell Netware user since 2.2
WARCRAFT user since 1.0