[MonoDevelop] error compiling Boo binding from trunk

[Michael Hutchinson]

On Tue, Dec 8, 2009 at 7:56 PM, Andy Selvig <ajselvig at gmail.com> wrote:
> Hi-
>
> I'm getting an error when trying to compile the Boo binding from
> trunk. It seems strange to me. Any thoughts?
>
> Boo Compiler version 0.8.2.2960 (CLR v2.0.50727.1433)
>
> ** (/usr/lib/boo/booc.exe:16835): WARNING **: The following assembly
> referenced from
> /home/andy/Mono/MonoDevelop-svn/extras/BooBinding/build/BooShell.dll
> could not be loaded:
>     Assembly:   MonoDevelop.Core    (assemblyref_index=7)
>     Version:    2.1.0.0
>     Public Key: (none)
> The assembly was not found in the Global Assembly Cache, a path listed
> in the MONO_PATH environment variable, or in the location of the
> executing assembly
> (/home/andy/Mono/MonoDevelop-svn/extras/BooBinding/build/).
>
>
> ** (/usr/lib/boo/booc.exe:16835): WARNING **: Could not load file or
> assembly 'MonoDevelop.Core, Version=2.1.0.0, Culture=neutral,
> PublicKeyToken=null' or one of its dependencies.
> BCE0106: Failed to access the types defined in assembly 'BooShell,
> Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' -
> (/home/andy/Mono/MonoDevelop-svn/extras/BooBinding/build/BooShell.dll):The
> classes in the module cannot be loaded.
> Could not load file or assembly 'MonoDevelop.Core, Version=2.1.0.0,
> Culture=neutral, PublicKeyToken=null' or one of its dependencies.

AFAICT there's a build dependency order issue in the boo binding
makefiles, which means that when MD assembly versions change, the
build breaks. You can work around it by running "make clean" in the
boo binding.

-- 
Michael Hutchinson
http://mjhutchinson.com