[ScintillaNET] Re: Build tools
- From: gserack@xxxxxxxxxxxxxxx
- To: scintillanet@xxxxxxxxxxxxx
- Date: Thu, 03 Jun 2004 17:37:01 -0600
>> 1. VS.NET doesn't run On Linux. I'm trying to build my code for multiple
>platforms.
>
>If that's the case, then msbuild is out as well
No, MSbuild is a .NET executable. It'll run on mono. Even if it didn't, that's
why I'd probably fall back to (n)Ant.
>> 2. VS.NET doesn't have support for prebuild/postbuild tasks.
>
>As someone mentioned, you can run arbitrary script as prebuild/postbuild
>task
>
Yik. The support for aribtrary script is there, but no features. I dont' want
to run a batch file. If that was the case, I'd just use a batch file anyway.
Nant, Ant, MSBuild all have a set of tasks they can perform, from version
control, packaging, deployment, etc...
I want those features, I don't want to build batch files to do all that.
>> 4. I need it to run outside the development environment.
>
>You can. Read http://www.codeproject.com/dotnet/builditemincontextmenu.asp
>for more info.
>
It's not really outside the development environment when you use devenv, you
just don't see it. Loading a massive development evironment to do what a much
smaller tool can do is somewhat irritating, and really doesn't solve anything.
I can already call the compiler from a batch program.
>In general, I think two issues are mixed up here:
>* building the code
>* doing other stuff with it (like running unit tests etc.)
>
No, I just want both. I *have* this with Ant, I just want a .NET type tool to
do the same thing, that understands assemblies and whatnot.
And, given that the very component I'm building (ScintillaNET) has Generated
bindings that need to be completed before actual compilation can take place
anyway, It is not just simply the "Other stuff"--It's a critical peice of the
component compilation.
Microsoft has already indicated that the next version of visual studio will
have msbuild built in, as well as the next version of the desktop OS (Longhorn)
will ship with the tool. It is inevitable that it is going to be the defacto
standard.
>On Windows, if your VS.NET project is up-to-date, you get building from
>command line via devenv.exe for free. I don't see a reason to redo that in
>any other way.
'Cause it doesn't do anything else but compile.
>You still have to figure out how to build on non-Windows and do it by hand
>but, unless it gives you building on windows for free, no need to use that
>in place of devenv.exe.
>As to "doing other stuff" - clearly VS.NET is not the tool for it. But
>building via devenv.exe can be a part of the process, regardless of the
>tool used for doing the overall build.
Yeah! That's what I'm talking about!
Other related posts:
- » [ScintillaNET] Re: Build tools
