I learned from Curt Arnold that there have been problems building NAnt on the gump machine.

On unix, NAnt uses pkg-config to get information on the installed mono package.

We did this in order to support multiple versions of Mono on a given machine. Looking back, it might have been enough to get the path from the mono shell script located in the PATH environment variable and leave it up to users to modify the PATH accordingly when they want to target a different version of Mono.

For people not familiar with Mono: a single version of Mono contains a single runtime but class libraries for multiple versions of .NET (in Mono these are referred to as profiles). Even if you do not modify the PATH environment variable, NAnt will still support targeting multiple versions .NET.

When we decided to use pkg-config to retrieve info on the mono package, the actual packaging of Mono was not yet clear and we assumed that they'd ship a separate package for each .NET version (including both a runtime and the class libraries).

So far for the background information.

Curt sent me the build log of one of the NAnt build failure:

<snip>
The current runtime framework 'mono-2.0' is not correctly configured
in the NAnt configuration file.
Framework directory '/usr/lib/pkgconfig/../../lib/mono/1.0' does  not exist.
</snip>

Would it possible to send me the output of the following commands on the gump machine:

$ pkg-config --modversion mono
$ pkg-config --variable=prefix mono
$ pkg-config --variable=libdir mono
$ which mono

Can you also verify whether the following files/directories exist:

$prefix/bin/mono
$prefix/lib/mono/1.0     <= this probably won't exist

Our framework support is configured using NAnt projects in the NAnt configuration file (NAnt.exe.config), and by reviewing it I noticed that we do not use the value of the libdir variable, but instead assume that its $prefix/lib. This is ofcourse not correct.

I'll stay on this until it's working.

Gert

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to