Jonathan Chayce Dickinson wrote:
>> [...]
> Interesting, and disappointing. I have grown rather fond of Nant. Back
> in the day (Okay, last week) when I decided to write a meta-builder (a
> la qmake) I thought I might do it using Yaml. SharpOS is going to need
> it's one build language one day: why don't I just make a full-blown
> builder that uses Yaml: It's a long term idea and probably won't be
> around till ms 0.0.4 or so, but Yaml is SOOO much nicer to edit than
> XML. And I could (try) make a converter for it, which may not be
> necessary in itself (we could just tack it onto the end of the MSBuild
> process).
Can I re-iterate the 'wow' factor this would have. Screw it, I am going
to go ahead and write it: you can decide if you like it or not. The mono
devs can use it as they have always been using Nant, and us windows devs
can just run it with something like:
yabble -export msbuild
So if xfury goes and adds something us windevs can just close VS, run
the tool, and we are in sync again.
Imagine writing build code like this:
csc:
- input
- yabble-recurse:
- *.cs
- yabble-path: [yabble-up, common.cs]
- output:
- yabble-path: [yabble-top, build, sharpos.kernel.exe]
- include:
- yabble-path: [yabble-top, build, sharpos.korlib.dll]
- yabble-if:
- or
- build
- or
- test
- dist
Now that is MEAN. And that yabble-recurse would automagically fix the
*/* issue that Johann brought up in the first place.
Okay, seriously. It's 1AM bed time!!!
--
Jonathan Dickinson
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
