The changes from 3408b8e5f1 cause
regressions in distros which do not use lib as folder for
arch-specific libraries, like Fedora x86_64.
Instead, reloc_libdir should be used (as in data/mono.pc.in).
This change is released under the MIT/X11 license.
Since libgdiplus is not installed together with Mono, it should not be
assumed to be in the same prefix.
The new policy for the --with-libgdiplus configure option is the
following:
- --with-libgdiplus=/absolute/path/to/libgdiplus.{so,dylib}
both during build/check and after installation Mono will try to use
the specified libgdiplus library; the rationale is that when an
absolute path is given, it can be assumed to be the full path to
the library that is already installed (possibly in a non-default
path).
- default, --with-libgdiplus=no, --with-libgdiplus=installed
both during build/check and after installation Mono will try to use
a system-wide libgdiplus library, that is assumed to reside in the
paths that are automatically searched by the dynamic linker; the
library is supposed to be already installed in the default path and
to be useable both during the build and afterwards.
- --with-libgdiplus=sibling, --with-libgdiplus=yes
during build/check Mono will try to use the libgdiplus library that
is assumed to be in the sibling folder (../libgdiplus), but after
the installation it will try to use a system-wide libgdiplus
library, that should be in the paths that are automatically
searched by the dynamic linker; the assumption is that the library
is not yet installed, but it will go to the default prefix after
installing it.
- --with-libgdiplus=../some/relative/path/to/libgdiplus.{so,dylib,la}
during build/check Mono will try to use the specified libgdiplus
library, but after the installation it will try to use a
system-wide libgdiplus library, that should be in the paths that
are automatically searched by the dynamic linker; the assumption is
that the library is not yet installed, but it will go to the
default prefix after installing it.
The libMonoPosixHelper is installed together with Mono, hence its path
in the configuration should be relative to the Mono prefix.
It was previously assumed to reside in a system path, so the the
dynamic linker would find it anyway.
This patch is based on the one included in bug #18555 (by Gaëtan
Lehmann <[email protected]>), but it also updates
runtime/Makefile.am to keep runtime/etc/mono/config consistent.
Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=18555
When libgdiplus is configured as sibling, it is available in the
libgdiplus_loc path. This path was added to runtime/mono/config, but
it was later overridden by the prefix-based path.
Using the same approach as for libMonoPosixHelper fixed the lookup of
the library (performed, for example, when testing
MonoTests.System.Drawing without installing libgdiplus).
This change is released under the MIT license.
When the xbuild_12 profile is verified, the corlib from the net_4_5
profile should be in the MONO_PATH, otherwise the verification will
fail with:
The assembly mscorlib.dll was not found or could not be loaded.
It should have been installed in the `.../mono/4.5/mscorlib.dll' directory.
Without that referencing browser 'Default' (parentID="Default")
in a .browser file make the app throw exceptions here
mcs/class/System.Web/System.Web.Configuration_2.0/nBrowser/Build.cs#L206
Signed-off-by: Etienne CHAMPETIER <[email protected]>
- fix compile/runtime issues caused by upstream changes
- add NaCl glibc support
- various changes to support running tests in NaCl glibc
from 'make check'
Neither moonlight itself or moonlight applications can be built
with an mcs.exe older than 2.12. As such, to allow users of the moonlight
SDK to build moonlight applications without having a system mono from
git we need to build the compiler ourselves. This will be bundled in the
SDK. We also use it to build all our managed libs as part of the regular
moonlight build.
Also made gmcs force -sdk=2 since -sdk=4 is now the default. _tmpinst/mcs is needed because
the CSharp CodeDOM provider invokes it and without the script in place it will launch the
first mcs available in the path.
This is needed as the 4.0 profile calls 'al' (which is defaults to 4.0) and not
'al2' and if Mono older than 2.8 is installed on the machine, 'al' coming from it
will fail to work with the current Mono and thus some tests will fail.
The commit should fix the 300+ failing tests on the build bots.
will configure mono to only build moonlight-specific stuff and
nothing else. --with-moonlight=yes now just adds the moon profile to
the build
* Makefile.am: Add moonlight-specific rules that only build what
moon needs. These are called directly from moon, to do fast
moon+mono+mcs builds
* runtime/Makefile.am: Change the build rules to have a moonlight-only
build configuration, as well as a normal build that optionally includes
it
svn path=/trunk/mono/; revision=155093
* Makefile.am:
* mono/Makefile.am: Only build some subdirs when configured for
moonlight.
* configure.in: If configured --with-moonlight=yes, define MOONLIGHT and
use that variable instead of INSTALL_2_1.
* runtime/Makefile.am: If configured for moonlight, only build
net_2_1_raw.
svn path=/trunk/mono/; revision=152880
* configure.in
* runtime/Makefile.am
* data/Makefile.am: create a and populate a configuration folder
for the net_4_0 profile.
svn path=/trunk/mono/; revision=138645
* configure.in: add a --with-monotouch option.
* runtime/Makefile.am: use it to trigger the mcs monotouch build.
svn path=/trunk/mono/; revision=138308