XBuild status report #8

[Marek Sieradzki]

Done during this week:

- Most of tasks have been tested. Appropriate errors/warnings reporting
will be done when I test all errors that I can produce under MSBuild.
- Most important task Csc is working now.
- Importing is working. Need to fix relative directory paths in imported
projects.
- Transforms in tasks' parameters are working.
- Added test build files in assembly directories. They can be used to
build xbuild using it. (Need xbuild/msbuild first)

Problems:

- Time.
- Ugly code for parsing in Expression and *Reference. I should use jay
or something similar for it. There isn't any documentation for it? I
should look into mcs (or similar) and yacc docs?

Tasks for few days left:

- Reformatting some code.
- Finish metadata references in inputs/outputs and tasks' parameters.

--
Marek Sieradzki <marek.s...@gmail.com>

[miguel de icaza]

Marek,

     How can I build xbuild? 

     How can I test the code?

     Am now reviewing all the projects

Miguel.

[Marek Sieradzki]

You can load MonoDevelop solution and build it. Then it will make .dll
files and .exe file in xbuild/bin/Debug which you can use to run
'xbuild' in main module directory. This should build it once again using
xbuild this time.

Next thing are various task. You add what you want to <Target> element
like <Message> etc. Should I write .csproj tests for each task?
Generally tasks should be documented on MSDN. Samples for them should be
working. If you are writing separate test you should <Import> file that
contains all UsingTask definitions. Conditions aren't working.
Transforms should work.


> Miguel.
--
Marek Sieradzki <marek.s...@gmail.com>

[Marek Sieradzki]

Dnia 01-09-2005, czw o godzinie 14:19 -0400, miguel de icaza napisał(a):

> Marek,
>
> How can I build xbuild?

There is MonoDevelop solution. In xbuild/bin/Debug there should be final
program. You must replace paths like "/media/xbuild" with path that
leads to it on your computer. Next you can build Microsoft.Build.csproj
file using xbuild. It won't be properly opened in VS2005 because it's
not VS2005 format. However it should build under msbuild.

>
> How can I test the code?

In Microsoft.Build.Tasks there are tasks classes. Every one of them
should have documentation in MSDN. Example from MSDN should work.
(GenerateResource have additional abilities because it was based on
monoresgen)

>
> Am now reviewing all the projects

Additional information: Conditions aren't working. Transforms are
working.

[miguel de icaza]

Hey,

There is MonoDevelop solution. In xbuild/bin/Debug there should be final
program. You must replace paths like "/media/xbuild" with path that
leads to it on your computer. Next you can build Microsoft.Build.csproj
file using xbuild. It won't be properly opened in VS2005 because it's
not VS2005 format. However it should build under msbuild.

For the sake of integrating this in the future into Mono proper, could you provide a Makefile that creates XBuild?

In Microsoft.Build.Tasks there are tasks classes. Every one of them
should have documentation in MSDN. Example from MSDN should work.
(GenerateResource have additional abilities because it was based on
monoresgen)

Do you have some .xbuild or .build files we can try also?
 

Additional information: Conditions aren't working. Transforms are
working.

Excellent!
 

[Marek Sieradzki]

Dnia 01-09-2005, czw o godzinie 15:42 -0400, miguel de icaza napisał(a):
> Hey,
>
> There is MonoDevelop solution. In xbuild/bin/Debug there
> should be final
> program. You must replace paths like "/media/xbuild" with path
> that
> leads to it on your computer. Next you can build
> Microsoft.Build.csproj
> file using xbuild. It won't be properly opened in VS2005
> because it's
> not VS2005 format. However it should build under msbuild.
>
>
> For the sake of integrating this in the future into Mono proper, could
> you provide a Makefile that creates XBuild?

I don't have experience in making makefile especially with those which
use autotools. I can try.

>
>
> In Microsoft.Build.Tasks there are tasks classes. Every one of
> them
> should have documentation in MSDN. Example from MSDN should
> work.
> (GenerateResource have additional abilities because it was
> based on
> monoresgen)
>
>
> Do you have some .xbuild or .build files we can try also?
>

I had some but I always tested using one file. I removed previous
entries and used next task. I'll make some files for tasks today but now
I'm going to school. :)

>
> Additional information: Conditions aren't working. Transforms
> are
> working.
>
>
> Excellent!

--
Marek Sieradzki <marek.s...@gmail.com>

[Marek Sieradzki]

Dnia 01-09-2005, czw o godzinie 15:42 -0400, miguel de icaza napisał(a):
> Hey,
>
> There is MonoDevelop solution. In xbuild/bin/Debug there
> should be final
> program. You must replace paths like "/media/xbuild" with path
> that
> leads to it on your computer. Next you can build
> Microsoft.Build.csproj
> file using xbuild. It won't be properly opened in VS2005
> because it's
> not VS2005 format. However it should build under msbuild.
>
>
> For the sake of integrating this in the future into Mono proper, could
> you provide a Makefile that creates XBuild?

I have made some Makefiles. I copied one of my assemblies into mcs/class
and tried to run make but it said something about .makefrag file. (It
didn't exist).

MSBuild is distributed with Microsoft.*.targets and
Microsoft.Common.tasks files. It should be probably distributed with
Microsoft.Build.Engine.

XBuild (command line tool) should be distributed with .rsp file and
schema files. What should be added to makefile if I want to do that?
Where these files will be copied when running make-install?

Microsoft.Build.Tasks contains Csc and AL tasks that are using constant
path actually to /usr/local/bin. It is used to generate filenames of mcs
and al. How to change these files to use paths like prefix from
autotools? (by the way it should use
Microsoft.Build.Utilities.ToolLocationHelper)

>
>
> In Microsoft.Build.Tasks there are tasks classes. Every one of
> them
> should have documentation in MSDN. Example from MSDN should
> work.
> (GenerateResource have additional abilities because it was
> based on
> monoresgen)
>
>
> Do you have some .xbuild or .build files we can try also?

There are some files in tests directory.

--
Marek Sieradzki <marek.s...@gmail.com>