mirror of
https://github.com/BepInEx/mono.git
synced 2026-11-17 19:10:23 -10:00
Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
9f09256d3c | ||
|
|
4e4824afab |
No files matched your search
@@ -1,182 +1,3 @@
|
||||
2003-09-08 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Added check for valgrind headers.
|
||||
|
||||
2003-09-03 Zoltan Varga <[email protected]>
|
||||
|
||||
* Makefile.am: Use $(MAKE) in even more places. Patch by Bernie Solomon
|
||||
([email protected]).
|
||||
|
||||
2003-08-27 Zoltan Varga <[email protected]>
|
||||
|
||||
* Makefile.am: Use $(MAKE) instead of make. Patch by Bernie Solomon
|
||||
([email protected]).
|
||||
|
||||
2003-08-25 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono.pc.in: Added gthread-2.0.
|
||||
|
||||
2003-08-22 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Added gthread-2.0 to GLIB_CFLAGS and GLIB_LIBS, so we
|
||||
can call g_thread_init ().
|
||||
|
||||
2003-08-21 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/threadpool.cs mono/tests/threadpool1.cs: Make increments
|
||||
of static variables atomic. Fixes bug #47683.
|
||||
|
||||
2003-08-21 Johannes Roith <[email protected]>
|
||||
|
||||
* mono/Makefile.am: small update. make sure, glib makes it in the build, add optional target for dependencies
|
||||
|
||||
2003-08-18 Johannes Roith <[email protected]>
|
||||
|
||||
* mono/Makefile.am: add windows build option
|
||||
* mono/monowiz.win32.nsi: add windows build script
|
||||
* mono/mono-win32-light.bmp: add bitmap
|
||||
|
||||
2003-08-16 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/checked.cs: Added mul.ovf tests.
|
||||
|
||||
2003-08-15 Duncan Mak <[email protected]>
|
||||
|
||||
* doc/mysql: Change references to ByteFX.Data.MySQLClient to the
|
||||
correct ByteFX.Data.MySqlClient (note the change in
|
||||
capitalization). Thanks to Tom Wagner <[email protected]> for
|
||||
spotting the error.
|
||||
|
||||
2003-08-15 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/bug-47295.cs: Regression test for bug #47295.
|
||||
|
||||
2003-08-11 Duncan Mak <[email protected]>
|
||||
|
||||
* runtime/Makefile.am (assemblies_DATA): Add Mono.Cairo.dll.
|
||||
|
||||
Sun Aug 3 21:12:13 BST 2003 Malte Hildingson <[email protected]>
|
||||
|
||||
* configure.in: added FPU test for ARM.
|
||||
|
||||
Thu Jul 31 16:19:07 CEST 2003 Paolo Molaro <[email protected]>
|
||||
|
||||
* configure.in, etc.: portability fixes and support for
|
||||
buidling outside the srcdir from Laurent Morichetti <[email protected]>.
|
||||
|
||||
2003-07-22 Duncan Mak <[email protected]>
|
||||
|
||||
* runtime/Makefile.am: Remove sqlsharp as we no longer distribute it.
|
||||
|
||||
2003-07-22 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am: Add missing test. Make tests interruptable
|
||||
by Ctrl-C. Add testinterp target to run the tests with the interpreter.
|
||||
Do not try to build vararg.cs under mcs.
|
||||
|
||||
* configure.in: Fix detection of GC_gcj_malloc.
|
||||
|
||||
2003-07-14 Jerome Laban <[email protected]>
|
||||
|
||||
* acconfig.h:
|
||||
* configure.in: Check for gethostbyname2_r availability.
|
||||
* data/machine.config: Added section system.net/settings. Added
|
||||
option for IPv6 availability.
|
||||
|
||||
2003-07-13 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/cattr-object.cs: Make it run under both mono and MS.NET.
|
||||
|
||||
* mono/tests/struct.cs: Add test for unboxing trampolines.
|
||||
|
||||
* mono/tests/bug-27420.cs: new regression test.
|
||||
|
||||
* mono/tests/Makefile.am: skip vararg test since it does not compile
|
||||
under mono. Add testinterp target. Add new tests.
|
||||
|
||||
2003-07-10 Martin Willemoes Hansen
|
||||
|
||||
* doc/web/team.xml : Modified my tasks a bit.
|
||||
|
||||
2003-07-01 Paolo Molaro <[email protected]>
|
||||
|
||||
* acconfig.h, configure.in: added bundle support.
|
||||
|
||||
2003-06-10 Dick Porter <[email protected]>
|
||||
|
||||
* acconfig.h:
|
||||
* configure.in: Check for struct ip_mreq if struct ip_mreqn isn't
|
||||
available.
|
||||
|
||||
2003-06-10 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Define HAVE_GC_GCJ_MALLOC for included libgc.
|
||||
|
||||
2003-06-10 Martin Baulig <[email protected]>
|
||||
|
||||
* configure.in: Fall back to boehm if we don't have a libgc
|
||||
subdirectory.
|
||||
|
||||
2003-06-10 Martin Baulig <[email protected]>
|
||||
|
||||
* configure.in: Make the libgc stuff actually work; we now create
|
||||
a shared libmonogc.so when using the included libgc.
|
||||
|
||||
2003-06-09 Martin Baulig <[email protected]>
|
||||
|
||||
* configure.in: Only check for gc if --with-gc=boehm.
|
||||
|
||||
2003-06-08 Martin Baulig <[email protected]>
|
||||
|
||||
* configure.in: Tell libgc's configure about our threads library.
|
||||
|
||||
2003-06-08 Martin Baulig <[email protected]>
|
||||
|
||||
* libgc/: Integrate the libgc module here.
|
||||
|
||||
[Note: A simple `cvs update' won't work this time; you either need
|
||||
to re-checkout the `mono' module or manually move the `libgc'
|
||||
module here.]
|
||||
|
||||
* configure.in (--with-gc): Added `included' option to use the
|
||||
included libgc. This is now also the default.
|
||||
(LIBGC_CFLAGS, LIBGC_LIBS): Put the libgc stuff here and AC_SUBST it.
|
||||
(INCLUDED_LIBGC): New automake conditional.
|
||||
(USE_INCLUDED_LIBGC): #define this if appropriate.
|
||||
|
||||
* autogen.sh: Run libgc/autogen.sh.
|
||||
|
||||
* Makefile.am (SUBDIRS): Added libgc.
|
||||
|
||||
2003-06-05 Duncan Mak <[email protected]>
|
||||
|
||||
* mono.spec.in (Requires): Add libxml2 and libxslt dependency on
|
||||
the package.
|
||||
|
||||
2003-05-19 Dick Porter <[email protected]>
|
||||
|
||||
* configure.in: Netbsd build fix by [email protected].
|
||||
|
||||
2003-05-10 Martin Willemoes Hansen <[email protected]>
|
||||
|
||||
* scripts/Makefile.am: Added monoresgen secutil sqlsharp
|
||||
shell wrapper scripts.
|
||||
|
||||
2003-05-08 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am:
|
||||
- Compile with mcs.
|
||||
- Disable some warnings.
|
||||
- Added executables to clean target.
|
||||
- Make testjit the default target.
|
||||
- Print list of failed tests at the end of a test run.
|
||||
- Abort tests when Ctrl-C is pressed.
|
||||
|
||||
* mono/tests/test-driver: Return with a special exit code when
|
||||
SIGINT is detected.
|
||||
|
||||
* mono/tests/checked.cs: Make it compile.
|
||||
|
||||
2003-05-02 Miguel de Icaza <[email protected]>
|
||||
|
||||
* runtime/Makefile.am ($(monobins_DATA)): Use explicit file names
|
||||
|
||||
+1
-54
@@ -1,62 +1,9 @@
|
||||
AUTOMAKE_OPTIONS = foreign
|
||||
|
||||
SUBDIRS = @libgc_dir@ mono doc docs runtime scripts man data samples
|
||||
|
||||
dnl EXTRA_SUBDIRS = libgc
|
||||
SUBDIRS = mono doc docs runtime scripts man data
|
||||
|
||||
EXTRA_DIST= mono.pc.in mono.spec.in
|
||||
|
||||
pkgconfigdir = $(libdir)/pkgconfig
|
||||
pkgconfig_DATA= mono.pc
|
||||
DISTCLEANFILES= mono.pc
|
||||
|
||||
#
|
||||
# The following target is used to compile and install
|
||||
# mono and mcs without running into the out-of-sync
|
||||
# problems by doing the compilation in the right order.
|
||||
#
|
||||
|
||||
fullbuild: remove-binaries mcs-tree-safe-build xinstall-runtime mcs-rest install
|
||||
|
||||
mcs-tree-safe-build:
|
||||
(cd ../mcs/jay; $(MAKE))
|
||||
(cd ../mcs/mcs; $(MAKE) MCS=mcs)
|
||||
(cd ../mcs/class/corlib; $(MAKE) MCS=mcs)
|
||||
cp ../mcs/class/lib/corlib.dll runtime
|
||||
cp ../mcs/mcs/mcs.exe runtime
|
||||
|
||||
xinstall-runtime:
|
||||
if echo $(SUBDIRS) | grep "libgc " > /dev/null; then (cd libgc; $(MAKE) && $(MAKE) install); fi
|
||||
(cd mono; $(MAKE) && $(MAKE) install)
|
||||
|
||||
mcs-rest:
|
||||
(cd ../mcs/class; $(MAKE))
|
||||
|
||||
remove-binaries:
|
||||
rm ../mcs/class/lib/corlib.dll ../mcs/mcs/mcs.exe runtime/*dll runtime/*.exe >& /dev/null; echo
|
||||
|
||||
|
||||
win32getdeps:
|
||||
wget http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip
|
||||
wget http://www.go-mono.com/archive/glib-2.0.4-20020703.zip
|
||||
wget http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip
|
||||
wget http://www.go-mono.com/archive/libiconv-1.7.zip
|
||||
wget http://www.go-mono.com/archive/libiconv-dev-1.7.zip
|
||||
wget http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip
|
||||
wget http://www.jroith.de/nsis4cygwin.zip
|
||||
unzip -n -d / pkgconfig-0.11-20020310.zip
|
||||
unzip -n -d / glib-2.0.4-20020703.zip
|
||||
unzip -n -d / glib-dev-2.0.4-20020703.zip
|
||||
unzip -n -d / libiconv-1.7.zip
|
||||
unzip -n -d / libiconv-dev-1.7.zip
|
||||
unzip -n -d / libintl-0.10.40-20020101.zip
|
||||
unzip -n -d / nsis4cygwin.zip
|
||||
|
||||
win32setup:
|
||||
cp /usr/lib/libglib-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/iconv.dll @prefix@/lib
|
||||
cp /usr/lib/libgmodule-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/libgobject-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/libgthread-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/libintl-1.dll @prefix@/lib
|
||||
makensis /DMILESTONE=@VERSION@ /DSOURCE_INSTALL_DIR=`cygpath -a -w @prefix@`\\* monowiz.win32.nsi
|
||||
@@ -1,28 +1,14 @@
|
||||
|
||||
This is Mono.
|
||||
|
||||
1. Installation
|
||||
2. Using Mono
|
||||
3. Directory Roadmap
|
||||
Installation:
|
||||
|
||||
1. Compilation and Installation
|
||||
===============================
|
||||
Read doc/download for installation instructions,
|
||||
or read the HTML version:
|
||||
|
||||
If you obtained this package as an officially released tarball,
|
||||
this is very simple, use configure and make:
|
||||
http://www.go-mono.com/download.html
|
||||
|
||||
./configure --prefix=/usr/local
|
||||
make
|
||||
make install
|
||||
|
||||
If you obtained this as a snapshot, you will need an existing
|
||||
Mono installation. To upgrade your installation do:
|
||||
|
||||
./autogen --prefix=/usr/local
|
||||
make fullbuild
|
||||
|
||||
2. Using Mono
|
||||
=============
|
||||
* Using Mono
|
||||
|
||||
Once you have installed the software, you can run a few programs:
|
||||
|
||||
@@ -43,8 +29,7 @@ This is Mono.
|
||||
See the man pages for mono(1), mint(1), monodis(1) and mcs(2)
|
||||
for further details.
|
||||
|
||||
3. Directory Roadmap
|
||||
====================
|
||||
* A directory roadmap:
|
||||
|
||||
doc/
|
||||
Contains documentation and the web site contents.
|
||||
|
||||
@@ -3,10 +3,8 @@
|
||||
#undef HAVE_MSG_NOSIGNAL
|
||||
#undef HAVE_SOL_IP
|
||||
#undef HAVE_SOL_TCP
|
||||
#undef HAVE_SOL_IPV6
|
||||
#undef HAVE_IP_PKTINFO
|
||||
#undef HAVE_STRUCT_IP_MREQN
|
||||
#undef HAVE_STRUCT_IP_MREQ
|
||||
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
|
||||
#undef USE_MONO_MUTEX
|
||||
#undef HAVE_LARGE_FILE_SUPPORT
|
||||
@@ -15,15 +13,9 @@
|
||||
#undef NAME_DEV_RANDOM
|
||||
#undef HAVE_CRYPT_RNG
|
||||
#undef HAVE_BOEHM_GC
|
||||
#undef USE_INCLUDED_LIBGC
|
||||
#undef DISABLE_SHARED_HANDLES
|
||||
#undef HAVE_TIMEZONE
|
||||
#undef HAVE_TM_GMTOFF
|
||||
#undef MONO_SIZEOF_SUNPATH
|
||||
#undef MONO_ZERO_ARRAY_LENGTH
|
||||
#undef NEED_LINK_UNLINK
|
||||
#undef PTHREAD_POINTER_ID
|
||||
#undef HAVE_GC_H
|
||||
#undef HAVE_GC_GCJ_MALLOC
|
||||
#undef WITH_BUNDLE
|
||||
#undef HAVE_GETHOSTBYNAME2_R
|
||||
@@ -117,12 +117,6 @@ automake --add-missing --gnu $am_opt ||
|
||||
echo "Running autoconf ..."
|
||||
autoconf || { echo "**Error**: autoconf failed."; exit 1; }
|
||||
|
||||
if test -d $srcdir/libgc; then
|
||||
echo Running libgc/autogen.sh ...
|
||||
(cd $srcdir/libgc ; NOCONFIGURE=1 ./autogen.sh "$@")
|
||||
echo Done running libgc/autogen.sh ...
|
||||
fi
|
||||
|
||||
|
||||
conf_flags="--enable-maintainer-mode --enable-compile-warnings" #--enable-iso-c
|
||||
|
||||
|
||||
+51
@@ -0,0 +1,51 @@
|
||||
/* config.h.in. Generated automatically from configure.in by autoheader 2.13. */
|
||||
|
||||
/* Define if you have the ANSI C header files. */
|
||||
#undef STDC_HEADERS
|
||||
|
||||
#undef HAVE_INET_PTON
|
||||
#undef HAVE_INET_ATON
|
||||
#undef HAVE_SOL_IP
|
||||
#undef HAVE_SOL_TCP
|
||||
#undef HAVE_IP_PKTINFO
|
||||
#undef HAVE_STRUCT_IP_MREQN
|
||||
#undef HAVE_PTHREAD
|
||||
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
|
||||
#undef USE_MONO_MUTEX
|
||||
#undef HAVE_LARGE_FILE_SUPPORT
|
||||
#undef PLATFORM_WIN32
|
||||
#undef HAVE_NEW_ICONV
|
||||
#undef NAME_DEV_RANDOM
|
||||
#undef HAVE_CRYPT_RNG
|
||||
#undef HAVE_BOEHM_GC
|
||||
|
||||
/* The number of bytes in a void *. */
|
||||
#undef SIZEOF_VOID_P
|
||||
|
||||
/* Define if you have the inet_aton function. */
|
||||
#undef HAVE_INET_ATON
|
||||
|
||||
/* Define if you have the inet_pton function. */
|
||||
#undef HAVE_INET_PTON
|
||||
|
||||
/* Define if you have the <dlfcn.h> header file. */
|
||||
#undef HAVE_DLFCN_H
|
||||
|
||||
/* Define if you have the <netdb.h> header file. */
|
||||
#undef HAVE_NETDB_H
|
||||
|
||||
/* Define if you have the <sys/filio.h> header file. */
|
||||
#undef HAVE_SYS_FILIO_H
|
||||
|
||||
/* Define if you have the <sys/sockio.h> header file. */
|
||||
#undef HAVE_SYS_SOCKIO_H
|
||||
|
||||
/* Define if you have the <utime.h> header file. */
|
||||
#undef HAVE_UTIME_H
|
||||
|
||||
/* Name of package */
|
||||
#undef PACKAGE
|
||||
|
||||
/* Version number of package */
|
||||
#undef VERSION
|
||||
|
||||
+41
-260
@@ -1,23 +1,9 @@
|
||||
AC_INIT(README)
|
||||
AC_CANONICAL_SYSTEM
|
||||
AM_CONFIG_HEADER(config.h)
|
||||
AM_INIT_AUTOMAKE(mono,0.27)
|
||||
AM_INIT_AUTOMAKE(mono,0.24)
|
||||
AM_MAINTAINER_MODE
|
||||
|
||||
dnl
|
||||
dnl libgc checks
|
||||
dnl
|
||||
|
||||
gc_headers=no
|
||||
gc=included
|
||||
use_included_gc=no
|
||||
|
||||
if test -d $srcdir/libgc ; then
|
||||
gc_default=included
|
||||
else
|
||||
gc_default=boehm
|
||||
fi
|
||||
|
||||
#
|
||||
# These are the flags that need to be stored in the mono.pc file for
|
||||
# compiling code that will embed Mono
|
||||
@@ -29,31 +15,16 @@ AC_SUBST(libmono_ldflags)
|
||||
|
||||
# Thread configuration inspired by sleepycat's db
|
||||
AC_MSG_CHECKING([host platform characteristics])
|
||||
libgc_threads=no
|
||||
case "$host" in
|
||||
*-*-mingw*|*-*-cygwin*)
|
||||
platform_win32=yes
|
||||
AC_DEFINE(PLATFORM_WIN32)
|
||||
CC="gcc -mno-cygwin"
|
||||
HOST_CC="gcc"
|
||||
# latest libgc already defines GC_WIN32_THREADS
|
||||
# CPPFLAGS="$CPPFLAGS -DGC_WIN32_THREADS -DWIN32_THREADS"
|
||||
CPPFLAGS="$CPPFLAGS -DWIN32_THREADS"
|
||||
CPPFLAGS="$CPPFLAGS -DGC_WIN32_THREADS -DWIN32_THREADS"
|
||||
libdl=
|
||||
libgc_threads=win32
|
||||
gc_default=boehm
|
||||
;;
|
||||
*-*-*netbsd*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -D_REENTRANT"
|
||||
libmono_cflags="-D_REENTRANT"
|
||||
LDFLAGS="$LDFLAGS -pthread"
|
||||
libmono_ldflags="-pthread"
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
libdl=
|
||||
libgc_threads=pthreads
|
||||
;;
|
||||
*-*-*freebsd*|*-*-*openbsd*)
|
||||
*-*-*bsd*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -D_THREAD_SAFE"
|
||||
libmono_cflags="-D_THREAD_SAFE"
|
||||
@@ -62,7 +33,6 @@ case "$host" in
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
AC_DEFINE(PTHREAD_POINTER_ID)
|
||||
libdl=
|
||||
libgc_threads=pthreads
|
||||
;;
|
||||
*-*-linux*)
|
||||
platform_win32=no
|
||||
@@ -70,22 +40,12 @@ case "$host" in
|
||||
libmono_cflags="-DMONO_USE_EXC_TABLES -fexceptions -D_REENTRANT"
|
||||
libmono_ldflags="-lpthread"
|
||||
libdl="-ldl"
|
||||
libgc_threads=pthreads
|
||||
;;
|
||||
*-*-hpux*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -DGC_HPUX_THREADS -D_HPUX_SOURCE -D_XOPEN_SOURCE_EXTENDED -D_REENTRANT"
|
||||
libmono_cflags="-D_REENTRANT"
|
||||
libmono_ldflags="-lpthread"
|
||||
libgc_threads=pthreads
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
;;
|
||||
*-*-solaris*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -DGC_SOLARIS_THREADS -DGC_SOLARIS_PTHREADS -D_REENTRANT"
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
libmono_cflags="-D_REENTRANT"
|
||||
libgc_threads=pthreads
|
||||
;;
|
||||
*-*-darwin*)
|
||||
platform_win32=no
|
||||
@@ -96,8 +56,6 @@ case "$host" in
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
AC_DEFINE(PTHREAD_POINTER_ID)
|
||||
libdl=
|
||||
libgc_threads=no
|
||||
gc_default=none
|
||||
;;
|
||||
*)
|
||||
AC_MSG_WARN([*** Please add $host to configure.in checks!])
|
||||
@@ -112,12 +70,6 @@ AC_CHECK_TOOL(CC, gcc, gcc)
|
||||
AC_PROG_CC
|
||||
AM_PROG_CC_STDC
|
||||
AC_PROG_INSTALL
|
||||
dnl We should use AM_PROG_AS, but it's not available on automake/aclocal 1.4
|
||||
: ${CCAS='$(CC)'}
|
||||
# Set ASFLAGS if not already set.
|
||||
: ${CCASFLAGS='$(CFLAGS)'}
|
||||
AC_SUBST(CCAS)
|
||||
AC_SUBST(CCASFLAGS)
|
||||
|
||||
AC_CHECK_PROG(BISON, bison,yes,no)
|
||||
if test "x$BISON" = "xno";
|
||||
@@ -145,9 +97,6 @@ AM_PROG_LIBTOOL
|
||||
|
||||
AC_CHECK_HEADERS(sys/filio.h sys/sockio.h netdb.h utime.h semaphore.h sys/un.h)
|
||||
|
||||
# for mono/mini/tramp-x86.c
|
||||
AC_CHECK_HEADERS(valgrind/memcheck.h)
|
||||
|
||||
# for mono/metadata/debug-symfile.c
|
||||
AC_CHECK_HEADERS(elf.h)
|
||||
|
||||
@@ -157,11 +106,7 @@ AC_CHECK_HEADERS(wchar.h)
|
||||
# not 64 bit clean in cross-compile
|
||||
AC_CHECK_SIZEOF(void *, 4)
|
||||
|
||||
WARN=''
|
||||
if test x"$GCC" = xyes; then
|
||||
WARN='-Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings'
|
||||
fi
|
||||
CFLAGS="-g $WARN"
|
||||
CFLAGS='-g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings'
|
||||
|
||||
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
|
||||
if test "x$PKG_CONFIG" = "xno"; then
|
||||
@@ -170,8 +115,8 @@ fi
|
||||
|
||||
dnl for use on the build system
|
||||
dnl pkg-config is stupid
|
||||
BUILD_GLIB_CFLAGS=`$PKG_CONFIG --cflags glib-2.0 gthread-2.0`
|
||||
BUILD_GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0 gthread-2.0`
|
||||
BUILD_GLIB_CFLAGS=`$PKG_CONFIG --cflags glib-2.0`
|
||||
BUILD_GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0`
|
||||
AC_SUBST(BUILD_GLIB_CFLAGS)
|
||||
AC_SUBST(BUILD_GLIB_LIBS)
|
||||
|
||||
@@ -193,8 +138,8 @@ GLIB_REQUIRED_VERSION=1.3.11
|
||||
|
||||
PKG_CHECK_MODULES(BASE_DEPENDENCIES, glib-2.0 >= $GLIB_REQUIRED_VERSION)
|
||||
|
||||
GLIB_CFLAGS=`$PKG_CONFIG --cflags glib-2.0 gthread-2.0`
|
||||
GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0 gthread-2.0`
|
||||
GLIB_CFLAGS=`$PKG_CONFIG --cflags glib-2.0`
|
||||
GLIB_LIBS=`$PKG_CONFIG --libs glib-2.0`
|
||||
GMODULE_CFLAGS=`$PKG_CONFIG --cflags gmodule-2.0`
|
||||
GMODULE_LIBS=`$PKG_CONFIG --libs gmodule-2.0`
|
||||
|
||||
@@ -203,26 +148,16 @@ AC_SUBST(GLIB_LIBS)
|
||||
AC_SUBST(GMODULE_CFLAGS)
|
||||
AC_SUBST(GMODULE_LIBS)
|
||||
|
||||
AC_ARG_WITH(gc, [ --with-gc=boehm,included,none],[gc=$with_gc],[gc=$gc_default])
|
||||
gc_headers=no
|
||||
AC_CHECK_HEADERS(gc.h gc/gc.h, gc_headers=yes)
|
||||
AC_CHECK_LIB(gc, GC_malloc, found_boehm="yes",,$libdl)
|
||||
gc=auto
|
||||
AC_ARG_WITH(gc, [ --with-gc=boehm,none],[gc=$with_gc])
|
||||
|
||||
# assembly bundle support, see metadata/make-bundle.pl for more info
|
||||
AC_ARG_WITH(bundle, [ --with-bundle=bundle_template],[
|
||||
BUNDLE_FILE=$with_bundle
|
||||
AC_SUBST(BUNDLE_FILE)
|
||||
AC_DEFINE(WITH_BUNDLE)
|
||||
],[with_bundle=no])
|
||||
AM_CONDITIONAL(WITH_BUNDLE, test x$with_bundle != xno)
|
||||
|
||||
LIBGC_CFLAGS=
|
||||
LIBGC_LIBS=
|
||||
libgc_dir=
|
||||
case "x$gc" in
|
||||
xboehm|xbohem|xyes)
|
||||
AC_CHECK_HEADERS(gc.h gc/gc.h, gc_headers=yes)
|
||||
AC_CHECK_LIB(gc, GC_malloc, found_boehm="yes",,$libdl)
|
||||
|
||||
if test "x$found_boehm" != "xyes"; then
|
||||
AC_MSG_ERROR("GC requested but libgc not found! Install libgc or run configure with --with-gc=none.")
|
||||
AC_MSG_ERROR("GC requested but libgc not found!")
|
||||
fi
|
||||
if test "x$gc_headers" != "xyes"; then
|
||||
AC_MSG_ERROR("GC requested but header files not found! You may need to install them by hand.")
|
||||
@@ -230,56 +165,30 @@ case "x$gc" in
|
||||
|
||||
AC_DEFINE(HAVE_BOEHM_GC)
|
||||
AC_SUBST(HAVE_BOEHM_GC)
|
||||
LIBGC_LIBS="-lgc $libdl"
|
||||
|
||||
# AC_CHECK_FUNCS does not work for some reason...
|
||||
AC_CHECK_LIB(gc, GC_gcj_malloc, found_gcj_malloc="yes",,$libdl)
|
||||
if test "x$found_gcj_malloc" = "xyes"; then
|
||||
AC_DEFINE(HAVE_GC_GCJ_MALLOC)
|
||||
fi
|
||||
LIBS="$LIBS -lgc $libdl"
|
||||
;;
|
||||
|
||||
xincluded)
|
||||
AC_CONFIG_SUBDIRS(libgc)
|
||||
|
||||
found_boehm=yes
|
||||
gc_headers=yes
|
||||
use_included_gc=yes
|
||||
libgc_dir=libgc
|
||||
|
||||
LIBGC_CFLAGS='-I$(top_srcdir)/libgc/include'
|
||||
LIBGC_LIBS='$(top_builddir)/libgc/libmonogc.la'
|
||||
|
||||
AC_DEFINE(HAVE_BOEHM_GC)
|
||||
AC_SUBST(HAVE_BOEHM_GC)
|
||||
|
||||
AC_DEFINE(HAVE_GC_H)
|
||||
AC_DEFINE(USE_INCLUDED_LIBGC)
|
||||
|
||||
# The included libgc contains GCJ support
|
||||
AC_DEFINE(HAVE_GC_GCJ_MALLOC)
|
||||
;;
|
||||
|
||||
xnone)
|
||||
AC_MSG_WARN("Compiling mono without GC.")
|
||||
;;
|
||||
*)
|
||||
AC_MSG_ERROR([Invalid argument to --with-gc.])
|
||||
# If libgc was found, use it. Otherwise just warn.
|
||||
if test "x$found_boehm" != "xyes"; then
|
||||
AC_MSG_WARN("Compiling mono without GC.")
|
||||
else
|
||||
if test "x$gc_headers" != "xyes"; then
|
||||
AC_MSG_ERROR("Found libgc but not its header files! You may need to install them by hand.")
|
||||
fi
|
||||
AC_DEFINE(HAVE_BOEHM_GC)
|
||||
AC_SUBST(HAVE_BOEHM_GC)
|
||||
LIBS="$LIBS -lgc $libdl"
|
||||
gc="boehm"
|
||||
fi
|
||||
;;
|
||||
esac
|
||||
|
||||
we_are_embedded_in_mono=yes
|
||||
export we_are_embedded_in_mono
|
||||
export libgc_threads
|
||||
|
||||
AM_CONDITIONAL(INCLUDED_LIBGC, test x$use_included_gc = xyes)
|
||||
AC_SUBST(LIBGC_CFLAGS)
|
||||
AC_SUBST(LIBGC_LIBS)
|
||||
AC_SUBST(libgc_dir)
|
||||
|
||||
dnl
|
||||
dnl End of libgc checks
|
||||
dnl
|
||||
if test "x$gc" = xboehm; then
|
||||
AC_CHECK_FUNCS(GC_gcj_malloc)
|
||||
fi
|
||||
|
||||
if test x$platform_win32 = xno; then
|
||||
dnl ******************************************************************
|
||||
@@ -364,21 +273,6 @@ if test x$platform_win32 = xno; then
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for SOL_IPV6 ***
|
||||
dnl *****************************
|
||||
AC_MSG_CHECKING(for SOL_IPV6)
|
||||
AC_TRY_COMPILE([#include <netdb.h>], [
|
||||
int level = SOL_IPV6;
|
||||
], [
|
||||
# Yes, we have it...
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_SOL_IPV6)
|
||||
], [
|
||||
# We'll have to use getprotobyname
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for SOL_TCP ***
|
||||
dnl *****************************
|
||||
@@ -420,32 +314,8 @@ if test x$platform_win32 = xno; then
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_STRUCT_IP_MREQN)
|
||||
], [
|
||||
# We'll just have to try and use struct ip_mreq
|
||||
# We'll just have to use struct ip_mreq
|
||||
AC_MSG_RESULT(no)
|
||||
AC_MSG_CHECKING(for struct ip_mreq)
|
||||
AC_TRY_COMPILE([#include <netinet/in.h>], [
|
||||
struct ip_mreq mreq;
|
||||
mreq.imr_interface.s_addr = 0;
|
||||
], [
|
||||
# Yes, we have it...
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_STRUCT_IP_MREQ)
|
||||
], [
|
||||
# No multicast support
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
])
|
||||
|
||||
dnl **********************************
|
||||
dnl *** Check for gethostbyname2_r ***
|
||||
dnl **********************************
|
||||
AC_MSG_CHECKING(for gethostbyname2_r)
|
||||
AC_TRY_LINK([#include <netdb.h>], [
|
||||
gethostbyname2_r(NULL,0,NULL,NULL,0,NULL,NULL);
|
||||
], [
|
||||
# Yes, we have it...
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_GETHOSTBYNAME2_R)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
@@ -479,23 +349,6 @@ if test x$platform_win32 = xno; then
|
||||
AC_MSG_RESULT($cv_mono_sizeof_sunpath)
|
||||
AC_DEFINE_UNQUOTED(MONO_SIZEOF_SUNPATH, $cv_mono_sizeof_sunpath)
|
||||
|
||||
dnl *************************************
|
||||
dnl *** Checks for zero length arrays ***
|
||||
dnl *************************************
|
||||
AC_MSG_CHECKING(whether $CC supports zero length arrays)
|
||||
AC_TRY_COMPILE([
|
||||
struct s {
|
||||
int length;
|
||||
char data [0];
|
||||
};
|
||||
], [], [
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE_UNQUOTED(MONO_ZERO_ARRAY_LENGTH, 0)
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
AC_DEFINE_UNQUOTED(MONO_ZERO_ARRAY_LENGTH, 1)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for libxnet ***
|
||||
dnl *****************************
|
||||
@@ -565,12 +418,6 @@ if test x$platform_win32 = xno; then
|
||||
AC_ERROR(unable to find a way to determine timezone)
|
||||
fi
|
||||
fi
|
||||
|
||||
dnl ****************************************************************
|
||||
dnl *** Checks for working poll() (macosx defines it but doesn't ***
|
||||
dnl *** have it in the library (duh)) ***
|
||||
dnl ****************************************************************
|
||||
AC_CHECK_FUNCS(poll)
|
||||
else
|
||||
AC_CHECK_LIB(ws2_32, main, LIBS="$LIBS -lws2_32", AC_ERROR(bad mingw install?))
|
||||
AC_CHECK_LIB(psapi, main, LIBS="$LIBS -lpsapi", AC_ERROR(bad mingw install?))
|
||||
@@ -652,78 +499,17 @@ fi
|
||||
TARGET="unknown"
|
||||
ACCESS_UNALIGNED="yes"
|
||||
|
||||
JIT_SUPPORTED=no
|
||||
LIBC="libc.so.6"
|
||||
|
||||
case "$host" in
|
||||
# mips-sgi-irix5.* | mips-sgi-irix6.*)
|
||||
# TARGET=MIPS;
|
||||
# ACCESS_UNALIGNED="no"
|
||||
# ;;
|
||||
i*86-*-*)
|
||||
TARGET=X86;
|
||||
arch_target=x86;
|
||||
JIT_SUPPORTED=yes
|
||||
;;
|
||||
sparc*-*-*)
|
||||
TARGET=SPARC;
|
||||
arch_target=sparc;
|
||||
ACCESS_UNALIGNED="no"
|
||||
;;
|
||||
# alpha*-*-linux* | alpha*-*-osf*)
|
||||
# TARGET=ALPHA;
|
||||
# ACCESS_UNALIGNED="no"
|
||||
# ;;
|
||||
# ia64-*-linux* | ia64-*-hpux*)
|
||||
# TARGET=IA64;
|
||||
# arch_target=ia64;
|
||||
# JIT_SUPPORTED=no;
|
||||
# ACCESS_UNALIGNED="no";
|
||||
# case "$host_os" in
|
||||
# linux*) LIBC="libc.so.6.1";;
|
||||
# hpux*) LIBC="libc.so.1";;
|
||||
# esac
|
||||
# ;;
|
||||
# m68k-*-linux*)
|
||||
# TARGET=M68K
|
||||
# ;;
|
||||
macppc-*-openbsd* | powerpc-*-linux* | powerpc-*-openbsd* | \
|
||||
powerpc-*-sysv* | powerpc-*-darwin*)
|
||||
TARGET=POWERPC;
|
||||
arch_target=ppc;
|
||||
JIT_SUPPORTED=yes
|
||||
;;
|
||||
arm-*-linux-* | armv4l-*-linux-*)
|
||||
TARGET=ARM;
|
||||
arch_target=arm;
|
||||
ACCESS_UNALIGNED="no"
|
||||
;;
|
||||
s390-*-linux*)
|
||||
TARGET=S390;
|
||||
arch_target=s390;
|
||||
ACCESS_UNALIGNED="no"
|
||||
;;
|
||||
#mips-sgi-irix5.* | mips-sgi-irix6.*) TARGET=MIPS; ACCESS_UNALIGNED="no";;
|
||||
i*86-*-*) TARGET=X86; arch_target=x86;;
|
||||
sparc*-*-*) TARGET=SPARC; arch_target=sparc; ACCESS_UNALIGNED="no";;
|
||||
#alpha*-*-linux* | alpha*-*-osf*) TARGET=ALPHA; ACCESS_UNALIGNED="no";;
|
||||
#m68k-*-linux*) TARGET=M68K;;
|
||||
macppc-*-openbsd* | powerpc-*-linux* | powerpc-*-openbsd* | powerpc-*-sysv* | powerpc-*-darwin*) TARGET=POWERPC; arch_target=ppc;;
|
||||
arm-*-linux-* | armv4l-*-linux-*) TARGET=ARM; arch_target=arm; ACCESS_UNALIGNED="no";;
|
||||
s390-*-linux*) TARGET=S390; arch_target=s390; ACCESS_UNALIGNED="no";;
|
||||
esac
|
||||
|
||||
if test ${TARGET} = ARM; then
|
||||
dnl ******************************************
|
||||
dnl *** Check to see what FPU is available ***
|
||||
dnl ******************************************
|
||||
AC_MSG_CHECKING(which FPU to use)
|
||||
|
||||
AC_TRY_COMPILE([], [
|
||||
__asm__ ("ldfd f0, [r0]");
|
||||
], fpu=FPA, [
|
||||
AC_TRY_COMPILE([], [
|
||||
__asm__ ("fldd d0, [r0]");
|
||||
], fpu=VFP, fpu=NONE)
|
||||
])
|
||||
|
||||
AC_MSG_RESULT($fpu)
|
||||
CPPFLAGS="$CPPFLAGS -DARM_FPU_$fpu"
|
||||
unset fpu
|
||||
fi
|
||||
|
||||
if test ${TARGET} = unknown; then
|
||||
CPPFLAGS="$CPPFLAGS -DNO_PORT"
|
||||
AC_MSG_WARN("mono has not been ported to $host: some things may not work.")
|
||||
@@ -738,14 +524,12 @@ AM_CONDITIONAL(MIPS_SGI, test ${TARGET}${ac_cv_prog_gcc} = MIPSno)
|
||||
AM_CONDITIONAL(SPARC, test x$TARGET = xSPARC)
|
||||
AM_CONDITIONAL(X86, test x$TARGET = xX86)
|
||||
AM_CONDITIONAL(ALPHA, test x$TARGET = xALPHA)
|
||||
AM_CONDITIONAL(IA64, test x$TARGET = xIA64)
|
||||
AM_CONDITIONAL(M68K, test x$TARGET = xM68K)
|
||||
AM_CONDITIONAL(POWERPC, test x$TARGET = xPOWERPC)
|
||||
AM_CONDITIONAL(ARM, test x$TARGET = xARM)
|
||||
AM_CONDITIONAL(S390, test x$TARGET = xS390)
|
||||
|
||||
AM_CONDITIONAL(JIT_SUPPORTED, test x$JIT_SUPPORTED = xyes)
|
||||
|
||||
LIBC="libc.so.6"
|
||||
AC_SUBST(LIBC)
|
||||
|
||||
AC_SUBST(arch_target)
|
||||
@@ -773,22 +557,19 @@ mono/arch/arm/Makefile
|
||||
mono/arch/alpha/Makefile
|
||||
mono/interpreter/Makefile
|
||||
mono/tests/Makefile
|
||||
mono/tests/tests-config
|
||||
mono/benchmark/Makefile
|
||||
mono/monoburg/Makefile
|
||||
mono/monograph/Makefile
|
||||
mono/jit/Makefile
|
||||
mono/io-layer/Makefile
|
||||
mono/handles/Makefile
|
||||
mono/mini/Makefile
|
||||
mono/profiler/Makefile
|
||||
runtime/Makefile
|
||||
scripts/Makefile
|
||||
man/Makefile
|
||||
doc/Makefile
|
||||
docs/Makefile
|
||||
data/Makefile
|
||||
samples/Makefile
|
||||
data/config
|
||||
mono.spec
|
||||
])
|
||||
|
||||
|
||||
@@ -1,4 +0,0 @@
|
||||
Makefile.in
|
||||
Makefile
|
||||
config
|
||||
.cvsignore
|
||||
@@ -4,3 +4,8 @@ EXTRA_DIST = config.in machine.config
|
||||
|
||||
mono_DATA = config machine.config
|
||||
|
||||
DISTCLEANFILES = config
|
||||
|
||||
config: config.in Makefile
|
||||
sed -e 's^\@LIBC\@^libc.so.6^g' < $(srcdir)/config.in > config.tmp \
|
||||
&& mv config.tmp config
|
||||
@@ -6,7 +6,6 @@
|
||||
<dllmap dll="odbc32.dll" target="libodbc.so" />
|
||||
<dllmap dll="libglib-2.0-0.dll" target="libglib-2.0.so" />
|
||||
<dllmap dll="libgobject-2.0-0.dll" target="libgobject-2.0.so" />
|
||||
<dllmap dll="libgthread-2.0-0.dll" target="libgthread-2.0.so" />
|
||||
<dllmap dll="libpango-1.0-0.dll" target="libpango-1.0.so" />
|
||||
<dllmap dll="libatk-1.0-0.dll" target="libatk-1.0.so" />
|
||||
<dllmap dll="libgdk-win32-2.0-0.dll" target="libgdk-x11-2.0.so" />
|
||||
@@ -15,5 +14,4 @@
|
||||
<dllmap dll="libgtk-win32-2.0-0.dll" target="libgtk-x11-2.0.so" />
|
||||
<dllmap dll="libglade-2.0-0.dll" target="libglade-2.0.so" />
|
||||
<dllmap dll="oci" target="clntsh" />
|
||||
<dllmap dll="gtkhtml-3.0" target="libgtkhtml-3.0.so.2" />
|
||||
</configuration>
|
||||
+1
-53
@@ -21,61 +21,21 @@
|
||||
type="System.Web.Configuration.GlobalizationConfigurationHandler, System.Web" />
|
||||
<section name="sessionState"
|
||||
type="System.Web.SessionState.SessionStateSectionHandler, System.Web" />
|
||||
<section name="webServices"
|
||||
type="System.Web.Services.Configuration.WebServicesConfigurationSectionHandler, System.Web.Services" />
|
||||
</sectionGroup>
|
||||
<sectionGroup name="system.net">
|
||||
<section name="settings"
|
||||
type="System.Net.Configuration.NetConfigurationHandler, System" />
|
||||
<section name="connectionManagement"
|
||||
type="System.Net.Configuration.ConnectionManagementHandler, System" />
|
||||
<section name="authenticationModules"
|
||||
type="System.Net.Configuration.NetAuthenticationModuleHandler, System" />
|
||||
<section name="defaultProxy"
|
||||
type="System.Net.Configuration.DefaultProxyHandler, System" />
|
||||
<section name="webRequestModules"
|
||||
type="System.Net.Configuration.WebRequestModuleHandler, System" />
|
||||
</sectionGroup>
|
||||
<section name="system.drawing" type="System.Configuration.NameValueSectionHandler" />
|
||||
</configSections>
|
||||
<system.net>
|
||||
<connectionManagement>
|
||||
<add address="*" maxconnection="2" />
|
||||
</connectionManagement>
|
||||
<authenticationModules>
|
||||
<add type="System.Net.BasicClient" />
|
||||
</authenticationModules>
|
||||
<defaultProxy>
|
||||
<proxy />
|
||||
<!-- bypassonlocal and proxyaddress are ok -->
|
||||
<!-- usessystemdefault is not supported -->
|
||||
</defaultProxy>
|
||||
<webRequestModules>
|
||||
<add prefix="http" type="System.Net.HttpRequestCreator, System" />
|
||||
<add prefix="https" type="System.Net.HttpRequestCreator, System" />
|
||||
<add prefix="file" type="System.Net.FileWebRequestCreator, System" />
|
||||
</webRequestModules>
|
||||
<settings>
|
||||
<ipv6 enabled="false"/>
|
||||
</settings>
|
||||
</system.net>
|
||||
<system.web>
|
||||
<httpHandlers>
|
||||
<add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web" />
|
||||
<add verb="*" path="*.asmx" validate="false"
|
||||
type="System.Web.Services.Protocols.WebServiceHandlerFactory, System.Web.Services" />
|
||||
<add verb="*" path="*.ashx" type="System.Web.UI.SimpleHandlerFactory, System.Web" />
|
||||
<add verb="*" path="*.asax" type="System.Web.HttpForbiddenHandler, System.Web" />
|
||||
<add verb="*" path="*.ascx" type="System.Web.HttpForbiddenHandler, System.Web" />
|
||||
<add verb="*" path="*.config" type="System.Web.HttpForbiddenHandler, System.Web" />
|
||||
<add verb="*" path="*.cs" type="System.Web.HttpForbiddenHandler, System.Web" />
|
||||
<add verb="GET,HEAD" path="*" type="System.Web.StaticFileHandler, System.Web" />
|
||||
<add verb="*" path="*" type="System.Web.HttpMethodNotAllowedHandler, System.Web" />
|
||||
</httpHandlers>
|
||||
<httpModules>
|
||||
<add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule, System.Web" />
|
||||
<add name="UrlAuthorization" type="System.Web.Security.UrlAuthorizationModule, System.Web" />
|
||||
<add name="Session" type="System.Web.SessionState.SessionStateModule, System.Web" />
|
||||
<add name="SessionStateModule" type="System.Web.SessionState.SessionStateModule, System.Web" />
|
||||
</httpModules>
|
||||
<authentication mode="Forms">
|
||||
<forms name=".MONOAUTH" loginUrl="login.aspx" protection="All" timeout="30" path="/">
|
||||
@@ -93,15 +53,6 @@
|
||||
uiculture="en-US" />
|
||||
-->
|
||||
<sessionState mode="InProc" />
|
||||
<webServices>
|
||||
<protocols>
|
||||
<add name="HttpSoap"/>
|
||||
<add name="HttpPost"/>
|
||||
<add name="HttpGet"/>
|
||||
<add name="Documentation"/>
|
||||
</protocols>
|
||||
<wsdlHelpGenerator href="DefaultWsdlHelpGenerator.aspx" />
|
||||
</webServices>
|
||||
</system.web>
|
||||
|
||||
<appSettings>
|
||||
@@ -112,8 +63,5 @@
|
||||
<system.diagnostics>
|
||||
<trace autoflush="false" indentsize="4" />
|
||||
</system.diagnostics>
|
||||
<system.drawing>
|
||||
</system.drawing>
|
||||
</configuration>
|
||||
|
||||
|
||||
+1
-1
@@ -5,7 +5,7 @@ WEB_FILES= \
|
||||
oledb papers \
|
||||
passport plans porting postgresql ppc projects rationale \
|
||||
resources roadmap runtime sqlclient sqlite sybase tdsclient \
|
||||
tds-providers status testing thanks tools \
|
||||
tds-providers team status testing thanks tools \
|
||||
porting anoncvs monodoc-xml winforms
|
||||
|
||||
OTHERS= pending resources-pending todo mono-build.sh mono-build-w32.sh
|
||||
|
||||
+57
-41
@@ -7,8 +7,9 @@
|
||||
* Web Services (the SOAP-based rpc system).
|
||||
</ul>
|
||||
|
||||
Both are functional at this point, and applications like
|
||||
"IBuySpy" run with Mono.
|
||||
There is work underway for both systems. The Web Forms
|
||||
support is more advanced at this point, and various ".aspx"
|
||||
programs can be run using the Mono runtime, including IBuySpy.
|
||||
|
||||
ASP.NET works either embedded into
|
||||
our XSP server test server or the mod_mono Apache module.
|
||||
@@ -16,57 +17,35 @@
|
||||
We are now working bug fixing and adding missing features
|
||||
after making the whole pipeline compatible with MS.
|
||||
|
||||
Tim started work on the Web Services. Lluis is in charge of
|
||||
it now and web services are now supported. He also added a web
|
||||
service sample to the XSP server set of tests.
|
||||
Tim started work on the Web Services. Although we have a
|
||||
SoapFormatter as part of the remoting infrastructure already
|
||||
(contributed by Jesus), most people will be using the ASP.NET
|
||||
Web Services support. Work for the supporting class libraries
|
||||
just started recently.
|
||||
|
||||
** Hosting
|
||||
The major missing element is a complete XmlSerializer.
|
||||
|
||||
ASP.NET provides a hosting interface. Today we ship support
|
||||
for two different hosting mechanisms:
|
||||
<ul>
|
||||
* <a href="#xsp">XSP</a>: A light-weight C# web server.
|
||||
** HttpRuntime
|
||||
|
||||
* <a href="#mod_mono">mod_mono</a>: An apache module
|
||||
that can host the Mono runtime and the ASP.NET runtime
|
||||
</ul>
|
||||
Patrik has authored most of the HttpRuntime support (both on
|
||||
the System.Web and on the foundation).
|
||||
|
||||
<a name="xsp">
|
||||
** XSP
|
||||
|
||||
XSP is a simple web server written in C# that can be used to
|
||||
run your ASP.NET applications. The code is available from our
|
||||
<a href="download.html">download page</a> or from the <a
|
||||
href="anoncvs.html">Anonymous CVS</a> repository (module name:
|
||||
xsp)/.
|
||||
|
||||
This is where initial development of the .aspx/.ascx/.asax
|
||||
compiler to C# took place. That compiler is now integrated in
|
||||
System.Web classes mostly under System.Web.Compilation
|
||||
namespace. We added a new web server that works with mono and
|
||||
MS runtime and is being used to debug our classes. It resides
|
||||
in xsp/server.
|
||||
This is where initial development of the .aspx/.ascx/.asax compiler
|
||||
to C# took place. That compiler is now integrated in System.Web classes
|
||||
mostly under System.Web.Compilation namespace.
|
||||
|
||||
A couple of classes of this new server can be reused/extended
|
||||
to make an apache module/cgi using mono (MonoWorkerRequest and
|
||||
MonoApplicationHost). This server also uses a couple of
|
||||
plugins distributed with Mono to support gzip HTTP transfers.
|
||||
We added a new web server that works with mono and MS runtime and is
|
||||
being used to debug our classes. It resides in xsp/server. A couple of
|
||||
classes of this new server can be reused/extended to make an apache
|
||||
module/cgi using mono (MonoWorkerRequest and MonoApplicationHost).
|
||||
|
||||
There is also a set of .aspx pages to test the server along with
|
||||
a few user controls under xsp/test.
|
||||
|
||||
You can check it out from CVS and run 'make install' to test it.
|
||||
|
||||
<a name="mod_mono">
|
||||
* mod_mono
|
||||
|
||||
This Apache module available at <a
|
||||
href="http://www.apacheworld.org/modmono/">ApacheWorld.org</a>
|
||||
hosts the Mono runtime and the Mono's ASP.NET runtime, and
|
||||
allows apache to server asp.net web pages.
|
||||
|
||||
Work is underway to improve it.
|
||||
|
||||
** Controls
|
||||
|
||||
A lot of work has been put in the various classes that
|
||||
@@ -75,7 +54,9 @@
|
||||
able to test them in real life: Gaurav and Leen worked very
|
||||
hard on this namespace.
|
||||
|
||||
We can now render all HtmlControls and all WebControls.
|
||||
We can now render all HtmlControls and almost all WebControls.
|
||||
DataGrid and DataList controls are being finished by Gaurav.
|
||||
Xml control needs some work on System.Xml related to XSL.
|
||||
|
||||
Help in making the controls better is appreciated.
|
||||
|
||||
@@ -84,6 +65,41 @@
|
||||
We want to encourage developers to create open source controls
|
||||
that can be used both on Mono's ASP.NET and Microsoft's ASP.NET.
|
||||
|
||||
* Web Forms: The pieces (historical)
|
||||
|
||||
There are a couple of components to the puzzle:
|
||||
|
||||
<ul>
|
||||
* .aspx page parser (converts .aspx to C# code).
|
||||
|
||||
* System.Web.HttpRuntime support.
|
||||
|
||||
* Web controls (System.Web.UI.HtmlControls and
|
||||
System.Web.UI.WebControls).
|
||||
|
||||
* Underlying infrastructure for the controls (System.Web.UI).
|
||||
|
||||
* HttpRuntime.ProcessRequest is the core of the ASP.NET
|
||||
implementation.
|
||||
</ul>
|
||||
|
||||
|
||||
Gonzalo has been working on an ASP.NET parser that takes .aspx
|
||||
files and generated the code required to run them (the code lives in
|
||||
module `xsp' along with a little web server for testing).
|
||||
|
||||
Most of the runtime support was written by Patrik Torstensson
|
||||
(now at Intel). This was interesting, because in order to implement
|
||||
some of its features, Patrik had to go into the runtime/JIT engine and
|
||||
he spent a few weeks doing work there.
|
||||
|
||||
The classes for running ASP.NET are being actively written.
|
||||
Gaurav, Leen and Patrik worked in the core of the classes
|
||||
required to run ASP.NET web application as well as a small
|
||||
embeddable web server.
|
||||
|
||||
Duncan got our System.Web assembly to compile.
|
||||
|
||||
** How to Help
|
||||
|
||||
Testing and fixing HtmlControls, WebControls and validators is an
|
||||
|
||||
@@ -8,12 +8,6 @@
|
||||
|
||||
A Programmer's Introduction to C# - Second Edition: Eric Gunnerson
|
||||
|
||||
* .NET Framework
|
||||
|
||||
Avery good techincal book about .NET is Don Box's <a
|
||||
href="http://service.bfast.com/bfast/click?bfmid=2181&sourceid=39391960&isbn=0201734117">Essential
|
||||
.NET</a>
|
||||
|
||||
* Remoting
|
||||
|
||||
<a href="http://www.dotnetremoting.cc/book/AdvancedDotNetRemoting.asp">
|
||||
|
||||
@@ -1,69 +0,0 @@
|
||||
* Bug reporting
|
||||
|
||||
To report bugs you need to create a <a
|
||||
href="http://bugzilla.ximian.com/createaccount.cgi">Bugzilla
|
||||
Account</a>.
|
||||
|
||||
Here are some convenient shortcuts to browse or add bug reports.
|
||||
|
||||
<ul>
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&newqueryname=&form_name=query&order=bugs.priority%2C%20bugs.bug_id">[Query]</> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FClass%20Libraries">[Add]</a> Class Libraries
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FAssembler&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FAssembler">[Add]</a> IL Assembler.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FMCS&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FMCS">[Add]</a> C# Compiler.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FRuntime">[Add]</a> Runtime
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FDoctools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FDoctools">[Add]</a> Documentation system.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=gtk%23&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=gtk%23">[Add]</a> Gtk#
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FDebugger&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FDebugger">[Add]</a> Debugger.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&product=Mono%2FMCS&product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=%27Importance%27&form_name=query">[Query]</a> All core components.
|
||||
</ul>
|
||||
|
||||
<a name="goodbugreport"/>
|
||||
** How to make good bug reports
|
||||
|
||||
<ol>
|
||||
* Submit a test case, the smaller it is, the better
|
||||
|
||||
* Use <a href="http://bugzilla.ximian.com">
|
||||
http://bugzilla.ximian.com</a> to report the bug.
|
||||
|
||||
<p>In <b>addition</b> to bugzilla, posting to the list is
|
||||
fine if the bug merits larger exposure or design
|
||||
discussions to solve; posting to the list twice or more
|
||||
is just a way to annoy people and make them waste time,
|
||||
specially when you start a new thread about it.
|
||||
|
||||
* If the test involves libraries or assemblies that are
|
||||
not part of mono, add info about where to download all
|
||||
the dependencies, and how to compile/install them.
|
||||
|
||||
* If compiling the test case requires more than:
|
||||
<pre> mcs test.cs </pre>
|
||||
provide the <b>full command line</b> you used to compile
|
||||
the test.
|
||||
|
||||
* If running the test requires more than:
|
||||
<pre> mono test.exe </pre>
|
||||
provide the <b>full command line</b> needed to replicate
|
||||
the bug.
|
||||
|
||||
* Provide info about the version of the software you're
|
||||
using (both mono and the operating system or relevant
|
||||
libraries).
|
||||
|
||||
* Provide the output you expect the test case to produce.
|
||||
|
||||
* Provide the actual output <b>you</b> get from the test case.
|
||||
</ol>
|
||||
|
||||
A good bug report complies with at least 6 items from the list.
|
||||
If your bug report complies with 3 or less items, it is very
|
||||
poor and it means it will take much more time to fix (when it's
|
||||
not ignored).
|
||||
|
||||
@@ -1,45 +1,25 @@
|
||||
* CVS Access
|
||||
|
||||
Here we describe how one obtains commit access to the CVS repository
|
||||
and the responsibilities that come with that access privilege.
|
||||
If you are an active Mono developer, you can get a CVS account
|
||||
that hosts the Mono source code. This web page contains
|
||||
details about how to use the CVS server as well as the
|
||||
policies to use it.
|
||||
|
||||
** What is CVS?
|
||||
If you are not a developer, but want to track the development, please
|
||||
see the <a href="anoncvs.html">AnonCVS</a> instructions.
|
||||
|
||||
Briefly, CVS is a system tool used to store and maintain files and
|
||||
a history of their changes over time. The Mono source code and related
|
||||
files are kept on a CVS server at Ximian.
|
||||
|
||||
** What Access?
|
||||
|
||||
We mean "commit" access. This is the privilege to make permanent
|
||||
changes to the Mono source code and related files. You need an account
|
||||
created by the CVS server administrator in order to commit changes to
|
||||
the files on that server.
|
||||
|
||||
** How Does One Obtain Access?
|
||||
|
||||
Any active Mono developer can get a CVS account. Normally one is
|
||||
considered an 'active' developer after sending several patches to the
|
||||
mailing lists and/or bugzilla for review.
|
||||
|
||||
If you are not a developer, but want to access the latest sources,
|
||||
please see the <a href="anoncvs.html">AnonCVS</a> instructions.
|
||||
|
||||
If you feel you are ready for a CVS account send an e-mail to
|
||||
<a href="mailto:[email protected]">miguel</a> with your public OpenSSH
|
||||
key for this purpose. Please specify if the key was generated with SSH
|
||||
version 1 or version 2. Detailed instructions are below.
|
||||
Send an e-mail to miguel with your public OpenSSH key for this
|
||||
purpose. Please specify if the key was generated with SSH version 1
|
||||
or version 2.
|
||||
|
||||
* Policies
|
||||
|
||||
It is necessary that everyone with CVS commit access respect and
|
||||
adhere to the following rules. If you ask for and are granted CVS
|
||||
access, you are agreeing to follow these policies.
|
||||
|
||||
Here are some policies about the use of the Mono CVS server.
|
||||
|
||||
** Code License
|
||||
|
||||
If you are about to commit code to a module, the code that is
|
||||
being committed should be released under the same license as
|
||||
being commited should be released under the same license as
|
||||
the code that the module has.
|
||||
|
||||
Check the license if you are unsure, but it is basically:
|
||||
@@ -48,105 +28,25 @@
|
||||
If in doubt, check with the maintainers of the module, or send
|
||||
mail to [email protected].
|
||||
|
||||
** Changing code
|
||||
** Commiting code.
|
||||
|
||||
Even if you have CVS commit access, that doesn't mean you can change
|
||||
code at will in any directory or module. Directories and Namespaces
|
||||
have a sort of unofficial ownership. If you are not the owner of a
|
||||
piece of code and you want to make changes/fixes to it, there are two
|
||||
cases.
|
||||
1) The change is a typo fix or a one-liner build or trivial fix. In
|
||||
this case almost anyone can commit (always remembering to add the
|
||||
proper changelog entry to explain the change). We say "almost anyone",
|
||||
because changes to certain directories almost always should be reviewed
|
||||
first. Such as changes to core stuff: corlib/System, System.Collections,
|
||||
mini/, metadata/, System.IO.
|
||||
If you are the maintainer for a piece of code, feel free to
|
||||
commit code, and delegate the work to others.
|
||||
|
||||
2) The change is larger. In this case the patch *must* be sent to
|
||||
mono-devel-list for review by the owner of the code and by the other
|
||||
hackers. Always submit such patches to the list or bugzilla, although
|
||||
you may put the owner of the code in the CC header. Hackers come and go.
|
||||
Mailing a patch to only a personal address is a good way to get the
|
||||
patch forgotten and missed. Plus, getting the patches reviewed as well
|
||||
as reviewing them, is a good thing, so try to get used to it.
|
||||
Use ChangeLog entries so we can keep textual descriptions of
|
||||
your work, and use the contents of your ChangeLog file as the
|
||||
CVS commit message (ie, paste the contents of this into the
|
||||
editor buffer).
|
||||
|
||||
Note: If the patch is an addition of code and doesn't change any of the
|
||||
existing code, the rules are slightly relaxed: there is more freedom
|
||||
in committing such changes, if they don't interfere with the existing
|
||||
codebase.
|
||||
If you are making changes to someone else's code, please make
|
||||
sure you get in touch with the maintainer of that code before
|
||||
applying patches. You want to avoid commiting conflicting
|
||||
work to someone else's code.
|
||||
|
||||
** Owning Code
|
||||
|
||||
Now, how do you get to be the owner of a chunk of code? The answer is
|
||||
simple. You wrote the code, so you're the unofficial owner. There is
|
||||
also another way. After sending a few patches for the code, the
|
||||
owner (or the core developers of mono, if the owner somehow disappeared)
|
||||
trusts you and tells you you're free to commit without getting his
|
||||
review first.
|
||||
|
||||
|
||||
Here is a (partial) list of namespaces/directories with their owners:
|
||||
<ul>
|
||||
<li>Debugger module and debug code in mono: martin
|
||||
<li>mcs compiler: miguel, martin, ravi
|
||||
<li>Reflection/Reflection.Emit: lupus, zoltan
|
||||
<li>IO-layer: dick
|
||||
<li>mini: lupus, dietmar
|
||||
<li>test suite: nickd (though anyone should feel free to add test cases)
|
||||
<li>System.IO: dick, ville
|
||||
<li>security stuff: spouliot
|
||||
<li>ilasm: jackson
|
||||
<li>System.Web and related: gonzalo
|
||||
<li>System.Xml: eno, piers
|
||||
<li>Remoting: dietmar, lluis
|
||||
<li>interop/marshal: dietmar
|
||||
<li>threads: dick
|
||||
</ul>
|
||||
|
||||
If you are the owner of a piece of code, feel free to commit code, and
|
||||
delegate the work to others.
|
||||
|
||||
But, if you're not the owner of the code, committing a rewrite without
|
||||
getting a review first is not good cvsitizenship (especially when the
|
||||
rewrite claimed to fix bugs, but not a single regression test has been
|
||||
added to the suite).
|
||||
|
||||
** Commit Rules
|
||||
|
||||
Once you know you can commit a patch (because of the rules above) there
|
||||
are a few other small rules to follow:
|
||||
<ul>
|
||||
<li>Always add a changelog entry with a meaningful explanation
|
||||
<li>If you fix a bug, add a regression test for it in the regression
|
||||
suite
|
||||
<li>Don't commit unrelated changes together with a fix: do fine-grained
|
||||
commits
|
||||
<li>Always check what you're committing: make sure you're only committing
|
||||
what you need and make sure you don't change line endings and
|
||||
whitespace. Do a 'cvs diff -u' of the files you're going to commit and
|
||||
check the changes.
|
||||
<li>Don't do reformatting commits, unless you're the original author of
|
||||
the code
|
||||
<li>When fixing bugs, don't follow the documentation blindly, it may
|
||||
well be wrong. Test the behavior on the MS runtime or ask on the list
|
||||
for discussion if unsure. Don't be afraid of having your changes
|
||||
reviewed.
|
||||
<li>Never remove copyright notices from the code
|
||||
<li>Never remove licensing info from code
|
||||
<li>Never commit code you didn't write yourself or code that doesn't
|
||||
have a suitable license
|
||||
<li>Follow the style conventions
|
||||
<li>Keep an eye on performance considerations, especially for code in
|
||||
core classes, ask on the list for guidance
|
||||
<li>Do a regression test run and a bootstrapping build if making changes
|
||||
to core functionality before committing. Do not commit code that would
|
||||
break the compile, because that wastes everybody's time. Two things
|
||||
Please do not commit code that would break the compile to the
|
||||
CVS, because that normally wastes everybody's time. Two things
|
||||
are important in this step: trying to build your sources and making
|
||||
sure that you add all the new files before you do a commit.
|
||||
</ul>
|
||||
|
||||
Also, remember to pat yourself on the back after the commit, smile and
|
||||
think we're a step closer to a better free software world.
|
||||
|
||||
|
||||
* Using CVS.
|
||||
@@ -161,16 +61,14 @@
|
||||
ssh-keygen -t rsa
|
||||
</pre>
|
||||
|
||||
And mail <a href="mailto:[email protected]">miguel</a> the
|
||||
id_rsa.pub file.
|
||||
And mail me the id_rsa.pub file.
|
||||
|
||||
If you are using SSH version 1, run:
|
||||
<pre>
|
||||
ssh-keygen
|
||||
</pre>
|
||||
|
||||
And mail <a href="mailto:[email protected]">miguel</a> your
|
||||
identity.pub file.
|
||||
And mail me your identity.pub file.
|
||||
|
||||
If you are using SSH from SSH Communications Security (they offer
|
||||
a free SSH client for personal use), you have to use OpenSSH to
|
||||
@@ -183,8 +81,7 @@
|
||||
|
||||
where the file id_XXX.pub is your public key file,
|
||||
normally located under ~/.ssh/ or ~/.ssh2/.
|
||||
Send to <a href="mailto:[email protected]">miguel</a> the
|
||||
my_public_key.pub file.
|
||||
Send to miguel the my_public_key.pub file.
|
||||
|
||||
The *exact* format for this file must be:
|
||||
|
||||
@@ -226,7 +123,7 @@
|
||||
** Making patches
|
||||
|
||||
Usually you will want to make a patch to contribute, and let
|
||||
other people review it before committing it. To obtain such a
|
||||
other people review it before commiting it. To obtain such a
|
||||
"patch", you type:
|
||||
|
||||
<pre>
|
||||
@@ -235,25 +132,7 @@
|
||||
mail [email protected] < file.diff
|
||||
</pre>
|
||||
|
||||
** Committing your work
|
||||
|
||||
Once you get approval to commit to the CVS, or if you are
|
||||
committing code that you are the maintainer of, you will want
|
||||
to commit your code to CVS.
|
||||
|
||||
To do this, you have to "add" any new files that you created:
|
||||
|
||||
<pre>
|
||||
cvs add new-file.cs
|
||||
</pre>
|
||||
|
||||
And then commit your changes to the repository:
|
||||
|
||||
<pre>
|
||||
cvs commit file-1.cs file-2.cs
|
||||
</pre>
|
||||
|
||||
* Keeping track of changes.
|
||||
** Keeping track of changes.
|
||||
|
||||
We provide two e-mail based mechanisms to keep track of
|
||||
changes to the code base:
|
||||
@@ -272,6 +151,28 @@
|
||||
|
||||
We hope to offer LXR and Bonsai in the future as well.
|
||||
|
||||
** Commiting your work
|
||||
|
||||
Once you get approval to commit to the CVS, or if you are
|
||||
commiting code that you are the maintainer of, you will want
|
||||
to commit your code to CVS.
|
||||
|
||||
To do this, you have to "add" any new files that you created:
|
||||
|
||||
<pre>
|
||||
cvs add new-file.cs
|
||||
</pre>
|
||||
|
||||
And then commit your changes to the repository:
|
||||
|
||||
<pre>
|
||||
cvs commit file-1.cs file-2.cs
|
||||
</pre>
|
||||
|
||||
* The Mailing Lists
|
||||
|
||||
To keep track of the various development and changes to the
|
||||
CVS tree, you can subscribe to the [email protected].
|
||||
To subscribe, send an email message to
|
||||
[email protected] and in the body of the
|
||||
message put `subscribe'.
|
||||
@@ -284,3 +185,10 @@
|
||||
the <a
|
||||
href="mailto:[email protected]">[email protected]</a>
|
||||
to receive the patches as they are checked into CVS.
|
||||
|
||||
** Recommendations
|
||||
|
||||
To build the sources, most of the type trying the `make' command
|
||||
is enough. In some cases (the class libraries) we use nant, so
|
||||
you need to run nant manually.
|
||||
|
||||
+4
-9
@@ -17,7 +17,6 @@
|
||||
|
||||
<ul>
|
||||
<li><a href="#monodoc">monodoc - A graphical documentation viewer.</a></li>
|
||||
|
||||
<li>xmllint: a tool used to validate a proper XML document.
|
||||
</ul>
|
||||
|
||||
@@ -28,15 +27,11 @@
|
||||
|
||||
*** <a name="monodoc">MonoDoc</a>
|
||||
|
||||
The MonoDoc system offers both a GUI client as well as a <a
|
||||
href="http://www.go-mono.com:8080">Web-based interface</a> to
|
||||
the documentation.
|
||||
A graphical documentation viewer written in Gtk#. In the
|
||||
future we will have an ASP.NET front-end to present the
|
||||
documentation on the web as well.
|
||||
|
||||
The GUI edition uses <a
|
||||
href="http://gtk-sharp.sf.net">Gtk#</a> and the Web edition
|
||||
uses Mono's ASP.NET implementation.
|
||||
|
||||
<img src="images/Screenshot-Monodoc.png">
|
||||
** Status and Roadmap
|
||||
|
||||
** Get Involved
|
||||
|
||||
|
||||
+1
-49
@@ -16,8 +16,7 @@
|
||||
the source code for Mono, you can start tracking down the
|
||||
problem. Depending on how much time you have to devote to the
|
||||
problem you could: <a href="http://bugzilla.ximian.com">File a
|
||||
bug report</a> (read <a href="#goodbugreport">this</a>); track
|
||||
down the problem and provide a better
|
||||
bug report</a>; track down the problem and provide a better
|
||||
<a href="http://bugzilla.ximian.com">bug report</a>; fix the
|
||||
bug and provide a patch (you can <a
|
||||
href="mailto:[email protected]">post it</a> to the <a
|
||||
@@ -128,53 +127,6 @@
|
||||
|
||||
You can review the list of current bugs by going <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&product=Mono%2FMCS&product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=%27Importance%27&form_name=query">here</a>
|
||||
|
||||
Check our <a href="bugs.html">Bugs</a> that contains links to
|
||||
easily add a bug report, or to query the existing bugs.
|
||||
|
||||
<a name="goodbugreport"/>
|
||||
** How to make good bug reports
|
||||
|
||||
A mail from Paolo to mono-devel-list contained this check list:
|
||||
<ol>
|
||||
* Submit a test case, the smaller it is, the better
|
||||
|
||||
* Use <a href="http://bugzilla.ximian.com">
|
||||
http://bugzilla.ximian.com</a> to report the bug.
|
||||
|
||||
<p>In <b>addition</b> to bugzilla, posting to the list is
|
||||
fine if the bug merits larger exposure or design
|
||||
discussions to solve; posting to the list twice or more
|
||||
is just a way to annoy people and make them waste time,
|
||||
specially when you start a new thread about it.
|
||||
|
||||
* If the test involves libraries or assemblies that are
|
||||
not part of mono, add info about where to download all
|
||||
the dependencies, and how to compile/install them.
|
||||
|
||||
* If compiling the test case requires more than:
|
||||
<pre> mcs test.cs </pre>
|
||||
provide the <b>full command line</b> you used to compile
|
||||
the test.
|
||||
|
||||
* If running the test requires more than:
|
||||
<pre> mono test.exe </pre>
|
||||
provide the <b>full command line</b> needed to replicate
|
||||
the bug.
|
||||
|
||||
* Provide info about the version of the software you're
|
||||
using (both mono and the operating system or relevant
|
||||
libraries).
|
||||
|
||||
* Provide the output you expect the test case to produce.
|
||||
|
||||
* Provide the actual output <b>you</b> get from the test case.
|
||||
</ol>
|
||||
|
||||
A good bug report complies with at least 6 items from the list.
|
||||
If your bug report complies with 3 or less items, it is very
|
||||
poor and it means it will take much more time to fix (when it's
|
||||
not ignored).
|
||||
|
||||
** Small tasks
|
||||
|
||||
A few smaller tasks are here, dropped in no particular order:
|
||||
|
||||
+69
-89
@@ -14,16 +14,21 @@
|
||||
* Every classes are present.
|
||||
|
||||
* Most classes have their unit tests. Some tests like <code>
|
||||
SymmetricAlgorithmTest</code> are generated by external
|
||||
tools.
|
||||
|
||||
* MACTripleDES is compatible with the implementation shipped in
|
||||
framework 1.0. Version 1.1 gives different results when the
|
||||
MACed data is a multiple of BlockSize (8 bytes).
|
||||
SymmetricAlgorithmTest</code> are generated by an external
|
||||
tool.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* The current implementation of <code>CryptoStream</code> is
|
||||
very limited and contain known bugs (<a
|
||||
href="http://bugzilla.ximian.com/show_bug.cgi?id=40689">
|
||||
40689</a>). The class need to be re-designed.
|
||||
|
||||
* Support for adding/modifying OID using the
|
||||
<code>machine.config</code> configuration file (algorithms
|
||||
are done).
|
||||
|
||||
* RNGCryptoServiceProvider is currently only working on Linux.
|
||||
The current implementation reside in Mono's runtime and use
|
||||
the <code>/dev/[u]random</code> device (which do not exists
|
||||
@@ -39,6 +44,13 @@
|
||||
algorithm can be different for every CSP (Crypto Service
|
||||
Provider). However for compatibility we should provide an
|
||||
implementation compatible with the MS CSP (most likely used).
|
||||
|
||||
* Analyse the current coverage of the unit tests on the
|
||||
cryptographic classes and complete the unit tests.
|
||||
|
||||
* Optimizations (performance) on most class are possible. Some
|
||||
have been done using the Community Edition of BoundChecker
|
||||
(a free VisualStudio addon) - recommanded!
|
||||
</ul>
|
||||
|
||||
**** Notes
|
||||
@@ -46,12 +58,7 @@
|
||||
* All cryptographic algorithms are entirely managed, including
|
||||
classes named <code>*CryptoServiceProvider</code>, with the
|
||||
exception of <code>RNGCryptoServiceProvider</code> (which
|
||||
implementation resides in the runtime).
|
||||
|
||||
* There is a bug in the <code>PKCS1MaskGenerationMethod</code>
|
||||
class (in both framework 1.0 and 1.1). This means our
|
||||
implementation isn't compatible with MS (but is compatible with
|
||||
PKCS#1 v.2.1). However we get OAEP padding for every platform!
|
||||
resides in the runtime).
|
||||
|
||||
* Look at assembly Mono.Security.Win32 if you require more
|
||||
compatiblity with the Microsoft implementation (like accessing
|
||||
@@ -72,9 +79,9 @@
|
||||
|
||||
* Unit tests are generated from a set of existing certificates
|
||||
(about a dozen) each having different properties. Another
|
||||
set of certificates (more than 700) are used for a more
|
||||
set of certificates (more than 300) are used for a more
|
||||
complete test (but isn't part of the standard test suite for
|
||||
size and time consideration, i.e. a 7.5Mb C# source file).
|
||||
size and time consideration, i.e. a 3.5Mb C# source file).
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
@@ -83,6 +90,10 @@
|
||||
certificates from PE files but cannot validate the signature
|
||||
nor the certificate chain (and we're still missing some trust
|
||||
anchors). See Tools section for more information.
|
||||
|
||||
* Integration with CryptoAPI (on Windows) isn't possible as
|
||||
long as the <code>X509Certificate(IntPtr)</code> constructor
|
||||
isn't completed.
|
||||
</ul>
|
||||
|
||||
**** Notes
|
||||
@@ -119,27 +130,29 @@
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* All classes are present but some Transforms are only stubbed.
|
||||
|
||||
* We now have a fully managed C14N implementation.
|
||||
* All classes are present but some (most Transforms) are only
|
||||
stubbed.
|
||||
|
||||
* Most classes have their unit tests.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* Complete all Transform derived classes.
|
||||
* All the transforms needs to be done. But this requires far
|
||||
more XML knowledge than crypto. Note: Most tests runs because
|
||||
the feeded XML is pre-c14n (by hand in the code) before
|
||||
signing (not because the transforms works). In the short
|
||||
term <code>libxml2</code> could be used to provide C14N, but
|
||||
in the long term a fully managed class would be much better.
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
** Assembly: Mono.Security
|
||||
|
||||
<b>Rational: </b>
|
||||
<b>Rational</b>
|
||||
This assembly provides the missing pieces to .NET security. On Windows
|
||||
CryptoAPI is often used to provide much needed functionalities (like
|
||||
some cryptographic algorithms, code signing, X.509 certificates). Mono,
|
||||
for platform independance, implements these functionalities in 100%
|
||||
managed code.
|
||||
some cryptographic algorithms, code signing, X.509 certificates).
|
||||
|
||||
*** Namespace: Mono.Security
|
||||
<ul>
|
||||
@@ -148,8 +161,7 @@
|
||||
*** Namespace: Mono.Security.Authenticode
|
||||
<ul>
|
||||
* Code signing and verification.
|
||||
* Support for SPC (Software Publisher Certificate) files and
|
||||
PVK (Private Key) files.
|
||||
* Support for SPC files and PVK files.
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.Cryptography
|
||||
<ul>
|
||||
@@ -158,20 +170,20 @@
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.X509
|
||||
<ul>
|
||||
* X.509 structures (certificate, CRL...) building and decoding.
|
||||
* X.509 certificate building and decoding.
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.X509.Extensions
|
||||
<ul>
|
||||
* X.509 extensions (from public X.509 to private PKIX, Netsapce,
|
||||
Microsoft, Entrust...).
|
||||
* X.509 extensions (from X.509, PKIX, Netsapce, Microsoft,
|
||||
Entrust...).
|
||||
</ul>
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* Some part of the work has not yet been commited (still cleaning up).
|
||||
* Some part of the work has not yet been commited (cleaning up).
|
||||
|
||||
* A big part of this assembly is also included inside Mono's
|
||||
corlib. The classes are duplicated in this assembly so the
|
||||
corlib. The class are duplicated in this assembly so the
|
||||
functionalities can be used without a dependency on Mono's
|
||||
corlib (which depends on Mono's runtime).
|
||||
|
||||
@@ -181,19 +193,18 @@
|
||||
<hr>
|
||||
** Assembly: Mono.Security.Win32
|
||||
|
||||
<b>Rational: </b>
|
||||
<b>Rational</b>
|
||||
This assembly goal is to provide maximum compatibility with CryptoAPI
|
||||
to application running with Mono's runtime on the Windows operating
|
||||
system.
|
||||
|
||||
<b>This assembly should NEVER be used directly by any application</b>
|
||||
(e.g. referecing the assembly from a project).
|
||||
<b>This assembly should NEVER be used directly by any application</b>.
|
||||
The classes should only be used by modifying the <code>machine.config
|
||||
</code> configuration file (and then only if this increased
|
||||
compatibility is required by an application).
|
||||
|
||||
See the file <code><a href="http://cvs.hispalinux.es/cgi-bin/cvsweb/~checkout~/mcs/class/Mono.Security.Win32/README?rev=1.1&content-type=text/plain&cvsroot=mono">/mcs/class/Mono.Security.Win32/README</a></code>
|
||||
for complete instructions.
|
||||
See the file <code>/mcs/class/Mono.Security.Win32/README</code> for
|
||||
complete instructions.
|
||||
|
||||
*** Namespace: Mono.Security.Cryptography
|
||||
|
||||
@@ -205,10 +216,10 @@
|
||||
|
||||
* Wrapper classes for unmanaged versions of hash algorithms:
|
||||
MD2, MD4, MD5 and SHA1 are supported. <b>note</b>: some
|
||||
algorithms shouldn't be used in new design (MD4 is broken,
|
||||
MD2 and MD5 aren't considered safe for some usage). They are
|
||||
included to preserve interoperability with older applications
|
||||
(e.g. some old, but still valid, X.509 certificates use MD2).
|
||||
algorithms shouldn't be used in new design (MD4 is broken and
|
||||
MD2 isn't considered safe). They are included to preserve
|
||||
interoperability with older applications (e.g. some old, but
|
||||
still valid, X.509 certificates use MD2).
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
@@ -224,13 +235,9 @@
|
||||
|
||||
**** Ideas
|
||||
<ul>
|
||||
* Similar assemblies (e.g. <code>Mono.Security.XXX</code>)
|
||||
could be created for <a href="http://www.openssl.org">OpenSSL</a>,
|
||||
<a href="http://www.mozilla.org/projects/security/pki/nss/">NSS</a>,
|
||||
<a href="http://www.eskimo.com/~weidai/cryptlib.html">crypto++</a>,
|
||||
<a href="http://www.cryptlib.orion.co.nz/">cryptlib</a> ... for
|
||||
improved performance and/or HSM (Hardware Security Module) support
|
||||
under Linux and/or Windows.
|
||||
* Similar assembly could be created for <a href="http://www.openssl.org">
|
||||
OpenSSL</a>, NSS, crypto++, cryptlib ... for improved
|
||||
performance and/or HSM support under Linux.
|
||||
</ul>
|
||||
<hr>
|
||||
** Assembly: Microsoft.Web.Services
|
||||
@@ -247,7 +254,7 @@
|
||||
<a href="http://www.oasis-open.org/committees/wss/">OASIS</a> or
|
||||
other committees.
|
||||
|
||||
<b>[*] There are some licensing issues to consider before starting to
|
||||
<b>[*] There are some licensing issues to consider before stating to
|
||||
implement WS-Security. All contributors must sign an agreement with
|
||||
Microsoft before commiting anything related to WS-Security into CVS.
|
||||
</b>
|
||||
@@ -266,7 +273,7 @@
|
||||
<ul>
|
||||
* Nothing (yet) commited in CVS. However the classes in this
|
||||
namespace are outside WS-Security scope. So development, for
|
||||
those classes, could be done without signing this agreement.
|
||||
those, could be done without signing any agreements.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
@@ -276,12 +283,6 @@
|
||||
keypairs. This could also be used to store the SPC roots.
|
||||
</ul>
|
||||
|
||||
*** Notes
|
||||
<ul>
|
||||
* Microsoft has <a href="http://microsoft.com/downloads/details.aspx?FamilyId=21FB9B9A-C5F6-4C95-87B7-FC7AB49B3EDD&displaylang=en">released</a>
|
||||
a technical preview of WSE 2.
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
** Tools
|
||||
|
||||
@@ -292,7 +293,7 @@
|
||||
|
||||
**** Status
|
||||
|
||||
The following tools are complete (mostly complete):
|
||||
The following tools are complete:
|
||||
<ul>
|
||||
* <code>secutil</code> is a tool to extract certificates and
|
||||
strongnames from assemblies in a format that can be easily
|
||||
@@ -303,30 +304,15 @@
|
||||
(SPC) file - which is a long name for a simple PKCS#7 file.
|
||||
|
||||
* <code>makecert</code> to create X.509 test certificates that
|
||||
can be used (once transformed in SPC) to sign assemblies. It's
|
||||
now possible to generate SSL certificates for web servers.
|
||||
can be used (once transformed in SPC) to sign assemblies.
|
||||
</ul>
|
||||
|
||||
Somewhat usable, somewhat incomplete:
|
||||
**** TODO
|
||||
The following tools are still missing or incomplete:
|
||||
<ul>
|
||||
* <code>certview</code> is a certificate viewer for
|
||||
<code>System.Windows.Forms</code> (right now only working on
|
||||
Windows), while <code>gcertview</code> is the same viewer
|
||||
implemented for GTK# (working on both Windows and Linux).
|
||||
|
||||
* <code>sn</code> is a clone of the <code>sn</code> to manage
|
||||
strongnames. Current version is limited to creating new keypairs
|
||||
and converting values.
|
||||
|
||||
* <code>monosn</code> is a clone of the <code>sn</code> to manage
|
||||
strongnames. This tools is part of the runtime (not the class
|
||||
library) and as such is written in C and won't run without Mono.
|
||||
</ul>
|
||||
|
||||
|
||||
**** TODO
|
||||
The following tools are still missing or largely incomplete:
|
||||
<ul>
|
||||
|
||||
* <code>signcode</code> and <code>chktrust</code> (in progress)
|
||||
for signing and validating Authenticode(tm) signatures on
|
||||
@@ -345,34 +331,28 @@
|
||||
<ul>
|
||||
* SSL/TLS for secure communication (a prototype is under way).
|
||||
Some work is already visible in Mono.Security assembly (e.g.
|
||||
RC4, RSAManaged ...).
|
||||
RC4).
|
||||
</ul>
|
||||
|
||||
|
||||
<hr>
|
||||
** How to Help
|
||||
|
||||
<ul>
|
||||
* Complete any of the TODO (and feel good about it ;-).
|
||||
Complete any of the TODO (and feel good about it ;-).
|
||||
|
||||
* Analyse the current coverage of the unit tests on the
|
||||
cryptographic classes and complete the unit tests. <b><code>
|
||||
monocov</code> does a great job at this! Now we just need to
|
||||
complete the missing unit tests.</b>
|
||||
Add missing unit tests to classes or methods.
|
||||
|
||||
* Optimization can also be done on most algorithms as crypto
|
||||
is never fast enough. Some have been done using the
|
||||
Community Edition of BoundChecker (a free VisualStudio
|
||||
addon) - recommanded! Just be sure to test every optimization
|
||||
(using the unit tests) carefully - it's so fast to break an
|
||||
algorithm ;-).
|
||||
Write some documentation on the cryptographic classes for the
|
||||
<a href="http://go-mono.com/tutorial/html/en/index.html">Mono
|
||||
Handbook</a> as I'm not a very good writer (at least in English).
|
||||
|
||||
* Write some documentation on the cryptographic classes for
|
||||
<b>monodoc</b> as I'm not a very good writer (at least in English).
|
||||
</ul>
|
||||
Optimization can also be done on algorithms as crypto is never fast
|
||||
enough. Just be sure to test every optimization (using the unit test)
|
||||
carefully - it's so fast to break an algorithm ;-).
|
||||
|
||||
Contact Sebastien Pouliot (<a href="mailto:[email protected]">home</a>
|
||||
, <a href="mailto:[email protected]">work</a>) if you need additional
|
||||
informations about the status of the cryptographic classes.
|
||||
|
||||
<hr>
|
||||
Last reviewed: August 9, 2003 (post mono 0.25)
|
||||
Last reviewed: April 7, 2003 (post mono 0.23)
|
||||
+2
-6
@@ -25,11 +25,7 @@
|
||||
libraries as well as the class libraries produced by
|
||||
the project).
|
||||
|
||||
* Tutorials on Mono and the specifics of running it
|
||||
(The <a href="http://www.monohispano.org">Mono
|
||||
Hispano</a> team has produced lots of <a
|
||||
href="http://www.monohispano.org/tutoriales.php">tutorials
|
||||
in spanish</a>
|
||||
* Tutorials on Mono and the specifics of running it.
|
||||
|
||||
* A guide to Mono as compared to the Microsoft.NET
|
||||
Framework SDK
|
||||
@@ -203,7 +199,7 @@
|
||||
</pre>
|
||||
|
||||
Use this to create lists. Lists contains <item>
|
||||
elements which have to contain <term> containers.
|
||||
elements
|
||||
|
||||
<pre>
|
||||
<list type="table"> </lits>
|
||||
|
||||
+4
-400
@@ -12,406 +12,6 @@
|
||||
href="http://www.go-mono.org/mono-beginning.html">Resources/Beginning
|
||||
section</a>, the <a
|
||||
href="http://www.go-mono.org/faq.html">FAQ</a>.
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
<td>
|
||||
<b>Release 0.26</b><br>
|
||||
<a href="archive/mono-0.26.html">Release notes</a><br>
|
||||
Aug 14, 2003
|
||||
</td>
|
||||
<td>
|
||||
<table cellspacing="1" cellpadding="3">
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source Code</b>
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/mcs-0.26.tar.gz">Mono Class Libraries and C# Compiler.</a>
|
||||
<li><a href="archive/mono-0.26.tar.gz">Mono Runtime</a>
|
||||
<li><a href="archive/xsp-0.5.tar.gz">XSP web server (0.5)</a>
|
||||
<li><a href="archive/mod_mono-0.4.tar.gz">Apache Mono module (mod_mono)</a>
|
||||
<li><a href="archive/monodoc-0.6.tar.gz">MonoDoc 0.6</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source RPMs</b><br>
|
||||
(No RPMS for XSP).
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.26-1.ximian.6.1.src.rpm">mono-0.26-1.src.rpm (RH9)</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.26-1.ximian.5.1.src.rpm">mono-0.26-1.src.rpm (RH8)</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 9.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.26-1.ximian.6.1.i386.rpm">mono-0.26-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-devel-0.26-1.ximian.6.1.i386.rpm">mono-devel-0.26-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-debuginfo-0.26-1.ximian.6.1.i386.rpm">mono-debuginfo-0.26-1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/libpixregion-0.1.0-1.ximian.6.1.i386.rpm">libpixregion-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libpixregion-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">libpixregion-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libic-0.1.0-1.ximian.6.1.i386.rpm">libic-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libic-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">libic-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xc-0.1.0-1.ximian.6.1.i386.rpm">xc-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xc-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">xc-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xr-0.1.0-1.ximian.6.1.i386.rpm">xr-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xr-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">xr-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/monodoc-0.6-1.ximian.6.1.i386.rpm">monodoc-0.6-1.ximian.6.1.i386.rpm</a> (To be used only with CVS gtk-sharp)
|
||||
<li><a href="archive/redhat-90-i386/monodoc-debuginfo-0.5-1.ximian.6.1.i386.rpm">monodoc-debuginfo-0.5-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-wine-20030318-1.ximian.6.3.i386.rpm">mono-wine-20030318-1.ximian.6.3.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-wine-debuginfo-20030318-1.ximian.6.2.i386.rpm">mono-wine-debuginfo-20030318-1.ximian.6.3.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 8.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-80-i386/mono-0.26-2.ximian.5.1.i386.rpm">mono-0.26-2.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-devel-0.26-2.ximian.5.1.i386.rpm">mono-devel-0.26-2.ximian.5.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-80-i386/monodoc-0.5-1.ximian.5.1.i386.rpm">monodoc-0.5-1.ximian.5.1.i386.rpm</a> (To be used only with CVS gtk-sharp)
|
||||
<li><a href="archive/redhat-80-i386/mono-wine-20030318-1.ximian.5.3.i386.rpm">mono-wine-20030318-1.ximian.5.3.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/debian-36.gif"><b>Debian</b>
|
||||
<ul>
|
||||
<li><a href="h#ttp://www.debianplanet.com/mono/">Debian Packages here.</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/mandrake-36.gif"><b>Mandrake 9.1/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/mandrake-91-i586/mono-0.26-1.ximian.6.1.i586.rpm">mono-0.26-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/mono-devel-0.26-1.ximian.6.1.i586.rpm">mono-devel-0.26-1.ximian.6.1.i586.rpm</a>
|
||||
<!-- <li><a href="archive/mandrake-91-i586/monodoc-0.5-1.ximian.6.1.i586.rpm">monodoc-0.5-1.ximian.6.1.i586.rpm</a> -->
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/suse-36.gif"><b>SuSE 8.2</b>
|
||||
<ul>
|
||||
<li><a href="archive/suse-82-i586/mono-0.26-2.ximian.7.1.i586.rpm">mono-0.26-2.ximian.7.1.i586.rpm</a>
|
||||
<li><a href="archive/suse-82-i586/mono-devel-0.26-2.ximian.7.1.i586.rpm">mono-devel-0.26-2.ximian.7.1.i586.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/windows-36.gif"><b>Windows installer</b>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.26-win32-2.exe">mono-0.26-win32-2.exe</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
<td>
|
||||
<b>Release 0.25</b><br>
|
||||
<a href="archive/mono-0.25.html">Release notes</a><br>
|
||||
Jun 26, 2003
|
||||
</td>
|
||||
<td>
|
||||
<table cellspacing="1" cellpadding="3">
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source Code</b>
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/mcs-0.25.tar.gz">Mono Class Libraries and C# Compiler.</a>
|
||||
<li><a href="archive/mono-0.25.tar.gz">Mono Runtime</a>
|
||||
<li><a href="archive/xsp-0.4.tar.gz">XSP web server (0.4)</a>
|
||||
<li><a href="archive/monodoc-0.5.tar.gz">MonoDoc 0.5</a>
|
||||
<li><a href="archive/gtk-sharp-0.10.tar.gz">Gtk# 0.10</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source RPMs</b><br>
|
||||
(No RPMS for XSP).
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.25-1.ximian.5.src.rpm">mono-0.25-1.src.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 9.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.25-1.ximian.6.1.i386.rpm">mono-0.25-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-devel-0.25-1.ximian.6.1.i386.rpm">mono-devel-0.25-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-debuginfo-0.25-1.ximian.6.1.i386.rpm">mono-debuginfo-0.25-1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/libpixregion-0.1.0-1.ximian.6.1.i386.rpm">libpixregion-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libpixregion-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">libpixregion-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libic-0.1.0-1.ximian.6.1.i386.rpm">libic-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libic-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">libic-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xc-0.1.0-1.ximian.6.1.i386.rpm">xc-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xc-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">xc-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xr-0.1.0-1.ximian.6.1.i386.rpm">xr-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xr-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">xr-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-0.10-1.ximian.6.1.i386.rpm">gtk-sharp-0.10-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-gapi-0.10-1.ximian.6.1.i386.rpm">gtk-sharp-gapi-0.10-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-debuginfo-0.10-1.ximian.6.1.i386.rpm">gtk-sharp-debuginfo-0.10-1.ximian.6.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/monodoc-0.5-1.ximian.6.1.i386.rpm">monodoc-0.5-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/monodoc-debuginfo-0.5-1.ximian.6.1.i386.rpm">monodoc-debuginfo-0.5-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/mono-wine-20030318-1.ximian.6.2.i386.rpm">mono-wine-20030318-1.ximian.6.2.i386.rpm</a>
|
||||
<li><a href="archive/mono-wine-debuginfo-20030318-1.ximian.6.2.i386.rpm">mono-wine-debuginfo-20030318-1.ximian.6.2.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 8.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-80-i386/mono-0.25-1.ximian.5.1.i386.rpm">mono-0.25-1.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-devel-0.25-1.ximian.5.1.i386.rpm">mono-devel-0.25-1.ximian.5.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-80-i386/gtk-sharp-0.10-1.ximian.5.1.i386.rpm">gtk-sharp-0.10-1.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/gtk-sharp-gapi-0.10-1.ximian.5.1.i386.rpm">gtk-sharp-gapi-0.10-1.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/monodoc-0.5-1.ximian.5.1.i386.rpm">monodoc-0.5-1.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/mono-wine-20030318-1.ximian.5.2.i386.rpm">mono-wine-20030318-1.ximian.5.2.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/debian-36.gif"><b>Debian</b>
|
||||
<ul>
|
||||
<li><a href="http://www.debianplanet.com/mono/">Debian Packages here.</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/windows-36.gif"><b>Windows Setup Wizard (XP, 2000, NT)</b>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.25-win32-1.exe">Setup program.</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 7.3/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-73-i386/mono-0.25-1.ximian.4.1.i386.rpm">mono-0.25-1.ximian.4.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/mono-devel-0.25-1.ximian.4.1.i386.rpm">mono-devel-0.25-1.ximian.4.1.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/mandrake-36.gif"><b>Mandrake 9.1/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/mandrake-91-i586/mono-0.25-1.ximian.6.1.i586.rpm">mono-0.25-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/mono-devel-0.25-1.ximian.6.1.i586.rpm">mono-devel-0.25-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/gtk-sharp-0.10-1.ximian.6.1.i586.rpm">gtk-sharp-0.10-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/gtk-sharp-gapi-0.10-1.ximian.6.1.i586.rpm">gtk-sharp-gapi-0.10-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/monodoc-0.5-1.ximian.6.1.i586.rpm">monodoc-0.5-1.ximian.6.1.i586.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<!--
|
||||
We don't have SuSE packages right now
|
||||
-->
|
||||
<!-- <tr> -->
|
||||
<!-- <td bgcolor="#999999"> -->
|
||||
<!-- <img src="images/suse-36.gif"><b>SuSE 8.2/x86</b> -->
|
||||
<!-- <ul> -->
|
||||
<!-- <li><a href="archive/suse-80-i386/mono-0.25-1.i386.rpm">mono-0.25-1.i386.rpm</a> -->
|
||||
<!-- <li><a href="archive/suse-80-i386/mono-devel-0.25-1.i386.rpm">mono-devel-0.25-1.i386.rpm</a> -->
|
||||
<!-- </ul> -->
|
||||
<!-- </td> -->
|
||||
<!-- </tr> -->
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<tr bgcolor="#CCCCC">
|
||||
<td>
|
||||
<b>Regression Tests</b><br>
|
||||
</td>
|
||||
<td>
|
||||
You can get binaries for the Mono Regression Test
|
||||
Suite <a href="archive/mono-tests.tar.gz">here</a>
|
||||
</td>
|
||||
</tr>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
* Older Releases:
|
||||
|
||||
We provide binaries for older releases until we have packages for the new release.
|
||||
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
<td>
|
||||
<b>Release 0.24</b><br>
|
||||
<a href="archive/mono-0.24.html">Release notes</a><br>
|
||||
May 6, 2003
|
||||
</td>
|
||||
<td>
|
||||
<table cellspacing="1" cellpadding="3">
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source Code</b>
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/mcs-0.24.tar.gz">Mono Class Libraries and C# Compiler.</a>
|
||||
<li><a href="archive/mono-0.24.tar.gz">Mono Runtime</a>
|
||||
<li><a href="archive/gc6.1.tar.gz">Boehm GC 6.1</a>
|
||||
<li><a href="archive/xsp-0.4.tar.gz">XSP web server (0.4)</a>
|
||||
<li><a href="archive/monodoc-0.4.tar.gz">MonoDoc 0.4</a>
|
||||
<li><a href="archive/gtk-sharp-0.9.tar.gz">Gtk# 0.9</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source RPMs</b><br>
|
||||
(No RPMS for XSP).
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/libgc-6.1-1.src.rpm">libgc-6.1-1.src.rpm</a>
|
||||
<li><a href="archive/mono-0.24-1.src.rpm">mono-0.24-1.src.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 9.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.24-1.i386.rpm">mono-0.24-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-devel-0.24-1.i386.rpm">mono-devel-0.24-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-debuginfo-0.24-1.i386.rpm">mono-debuginfo-0.24-1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-0.9-1.i386.rpm">gtk-sharp-0.9-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-debuginfo-0.9-1.i386.rpm">gtk-sharp-debuginfo-0.9-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/monodoc-0.4-1.i386.rpm">monodoc-0.4-1.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 8.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-80-i386/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-0.24-2.i386.rpm">mono-0.24-2.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-devel-0.24-2.i386.rpm">mono-devel-0.24-2.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-80-i386/gtk-sharp-0.9-1.i386.rpm">gtk-sharp-0.9-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/monodoc-0.4-1.i386.rpm">monodoc-0.4-1.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/debian-36.gif"><b>Debian</b>
|
||||
<ul>
|
||||
<li><a href="http://www.debianplanet.com/mono/">Debian Packages here.</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/windows-36.gif"><b>Windows Setup Wizard (XP, 2000, NT)</b>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.24-win32-1.exe">Setup program.</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 7.3/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-73-i386/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/mono-0.24-1.i386.rpm">mono-0.24-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/mono-devel-0.24-1.i386.rpm">mono-devel-0.24-1.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/mandrake-36.gif"><b>Mandrake 8.2/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/mandrake-82-i386/libgc-6.1-1.i586.rpm">libgc-6.1-1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-82-i386/libgc-devel-6.1-1.i586.rpm">libgc-devel-6.1-1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-82-i386/mono-0.24-1.i586.rpm">mono-0.24-1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-82-i386/mono-devel-0.24-1.i586.rpm">mono-devel-0.24-1.i586.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/suse-36.gif"><b>SuSE 8.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/suse-80-i386/libgc-6.1-1.i386.rpm">libgc-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/suse-80-i386/libgc-devel-6.1-1.i386.rpm">libgc-devel-6.1-1.i386.rpm</a>
|
||||
<li><a href="archive/suse-80-i386/mono-0.24-1.i386.rpm">mono-0.24-1.i386.rpm</a>
|
||||
<li><a href="archive/suse-80-i386/mono-devel-0.24-1.i386.rpm">mono-devel-0.24-1.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<b>Linux s/390</b>
|
||||
<ul>
|
||||
<li><a href="archive/s390/libgc-6.1-1.s390.rpm">libgc-6.1-1.s390.rpm</a>
|
||||
<li><a href="archive/s390/libgc-devel-6.1-1.s390.rpm">libgc-devel-6.1-1.s390.rpm</a>
|
||||
<li><a href="archive/s390/mono-0.24-1.s390.rpm">mono-0.24-1.s390.rpm</a>
|
||||
<li><a href="archive/s390/mono-devel-0.24-1.s390.rpm">mono-devel-0.24-1.s390.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<tr bgcolor="#CCCCC">
|
||||
<td>
|
||||
<b>Regression Tests</b><br>
|
||||
</td>
|
||||
<td>
|
||||
You can get binaries for the Mono Regression Test
|
||||
Suite <a href="archive/mono-tests.tar.gz">here</a>
|
||||
</td>
|
||||
</tr>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
@@ -548,6 +148,10 @@
|
||||
|
||||
|
||||
|
||||
* Older Releases:
|
||||
|
||||
We provide binaries for older releases until we have packages for the new release.
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
|
||||
+1
-12
@@ -68,20 +68,9 @@
|
||||
not interfere with code in other domains. This is useful if
|
||||
you want to host different applications in your program.
|
||||
|
||||
Now, it is necessary to transfer control to Mono, and setup
|
||||
the threading infrastructure, you do this like this:
|
||||
Then you can load an assembly containing code into the domain:
|
||||
|
||||
<pre>
|
||||
void *user_data = NULL;
|
||||
|
||||
mono_runtime_exec_managed_code (domain, main_thread_handler, user_data);
|
||||
</pre>
|
||||
|
||||
Where your main_thread_handler can load your assembly and execute it:
|
||||
|
||||
<pre>
|
||||
static void main_thread_handler (gpointer user_data)
|
||||
{
|
||||
MonoAssembly *assembly;
|
||||
|
||||
assembly = mono_domain_assembly_open (domain, "file.dll");
|
||||
|
||||
@@ -4,7 +4,6 @@
|
||||
<a href="#gui">Building GUI applications with Mono</a><br>
|
||||
<a href="#msft">Mono and Microsoft</a><br>
|
||||
<a href="#platforms">Mono platforms</a><br>
|
||||
<a href="#compatibility">Compatibility</a></br>
|
||||
<a href="#pnpproject">Mono and the Portable.NET Project</a><br>
|
||||
<a href="#webservices">Web Services</a><br>
|
||||
<a href="#asp">Mono and ASP.NET</a><br>
|
||||
@@ -39,48 +38,6 @@ A: The Mono Project is an open development initiative sponsored by
|
||||
implement various technologies developed by Microsoft that have now
|
||||
been submitted to the ECMA for standardization.
|
||||
|
||||
The Mono project has also sparked a lot of interest in developing
|
||||
C#-based components, libraries and frameworks. Today Mono is not
|
||||
limited to implement the .NET Framework, but also contains other
|
||||
components. Some of the components of the Mono platform were
|
||||
developed by the Mono team, and some others we have incorporated
|
||||
from other open source efforts, the most important ones:
|
||||
|
||||
<ul>
|
||||
<li><a
|
||||
href="http://remoting-corba.sourceforge.net/">Remoting.CORBA</a>: A
|
||||
CORBA implementation for Mono.
|
||||
|
||||
<li>Ginzu: An implementation on top of Remoting for the <a
|
||||
href="http://www.zeroc.com">ICE</a> stack
|
||||
|
||||
<li><a href="http://gtk-sharp.sf.net">Gtk#</a>: Bindings for
|
||||
the popular Gtk+ GUI toolkit for Unix and Windows systems.
|
||||
Other bindings are available: Diacanvas-Sharp and MrProject.
|
||||
|
||||
<li><a
|
||||
href="http://www.icsharpcode.net/OpenSource/SharpZipLib/Default.aspx">#ZipLib</a>:
|
||||
A library to manipulate various kinds of compressed files and
|
||||
archives (Zip and tar).
|
||||
|
||||
<li>GlGen (available from the Mono CVS): Bindings for OpenGL.
|
||||
|
||||
<li>Mono.LDAP: LDAP access for .NET apps.
|
||||
|
||||
<li>Mono.Data: We ship support for Postgress, MySql, Sybase,
|
||||
DB2, SqlLite, Tds (SQL server protocol) and Oracle databases.
|
||||
|
||||
<li>Mono.Cairo: Bindings for the <a
|
||||
href="http://www.cairographics.org">Cairo</a> rendering
|
||||
engine (Our System.Drawing is implemented on top of this).
|
||||
|
||||
<li>Mono.Posix: Bindings for building POSIX applications using
|
||||
C#.
|
||||
|
||||
<li>Mono.Http: Support for creating custom, embedded HTTP
|
||||
servers and common HTTP handlers for your applications.
|
||||
</ul>
|
||||
|
||||
Q: What is the difference between Mono and the .NET Initiative?
|
||||
|
||||
A: The ".NET Initiative" is a somewhat nebulous company-wide effort by
|
||||
@@ -101,9 +58,7 @@ A: Mono contains a number of components useful for building new
|
||||
compiler, and a garbage collecting runtime.
|
||||
|
||||
* A class library that can work with any language
|
||||
which works on the CLR. Both .NET compatible class
|
||||
libraries as well as Mono-provided class libraries
|
||||
are included.
|
||||
which works on the CLR.
|
||||
|
||||
* A compiler for the C# language. In the future we
|
||||
might work on other compilers that target the Common
|
||||
@@ -174,17 +129,6 @@ A: Different parts of Mono will achieve usability at different stages,
|
||||
Other higher level class libraries (ASP.NET, ADO.NET, WinForms) will
|
||||
be released when they become stable.
|
||||
|
||||
Q: When will Mono 1.0 ship?
|
||||
|
||||
A: We are planning on releasing Mono 1.0 (Mono Core) which will ship all the
|
||||
components of Mono that are known to be stable in Q4 2003/Q1 2004.
|
||||
|
||||
This release will lack System.Windows.Forms and
|
||||
Enterprise.Services, as they will not be production ready on this timeframe.
|
||||
|
||||
Mono 1.2 should come in Q2 2004 and include the missing components
|
||||
libraries that will make Mono feature-compatible with .NET 1.0
|
||||
|
||||
Q: What major components will you include in Mono?
|
||||
|
||||
A: Hopefully everything that Microsoft ships on their Framework
|
||||
@@ -343,18 +287,13 @@ A: There are several reasons for this.
|
||||
|
||||
Next is compatibility. It is not possible to implement
|
||||
System.Windows.Forms on top of Gtk+/Qt and have 100% compatibility,
|
||||
because System.Windows.Forms exposes some Win32-isms, such as the
|
||||
because System.Windows.Forms exposes <i>lots</i> of Win32-isms, such as the
|
||||
Win32 message loop. In order to maintain compatibility, Wine must be used,
|
||||
and this is being done; see the
|
||||
<a href="/winforms.html">System.Windows.Forms effort page</a>.
|
||||
|
||||
Q: Wine applications do not look like native applications, what are
|
||||
you going to do about this?
|
||||
|
||||
A: We have already a few patches into our version of Windows.Forms
|
||||
that makes Wine use the colors and font settings from your desktop,
|
||||
improving the integration a lot. In the future, we will continue
|
||||
to improve this interoperability scenario.
|
||||
|
||||
Additionally, Wine apps don't currently fit in -- visually -- with
|
||||
Gtk+ or Qt apps.
|
||||
|
||||
Q: Will I be able to run my smart clients on systems powered by Mono?
|
||||
|
||||
@@ -395,12 +334,6 @@ A: We do not know, volunteers are working on this, but there is no set
|
||||
date yet. The current approach is using the Wine Library to implement
|
||||
it.
|
||||
|
||||
Q: Do you have a comparission chart about the various toolkit
|
||||
offerings?
|
||||
|
||||
A: A document explaining this is available at: <a
|
||||
href="http://primates.ximian.com/~miguel/toolkits.html">http://primates.ximian.com/~miguel/toolkits.html</a>.
|
||||
|
||||
<a name="msft"></a>
|
||||
** Mono and Microsoft
|
||||
|
||||
@@ -456,6 +389,13 @@ A: No. MS Passport is unrelated to running .NET compatible applications
|
||||
produced with the Mono tools. The only thing you will need is a
|
||||
just-in-time compiler (JIT).
|
||||
|
||||
Q: What is a 100% .NET application?
|
||||
|
||||
A: A `100% .NET application' is one that only uses the APIs defined
|
||||
under the System namespace and does not use PInvoke. These
|
||||
applications would in theory run unmodified on Windows, Linux,
|
||||
HP-UX, Solaris, MacOS X and others.
|
||||
|
||||
Q: If Microsoft will release a port of their .NET platform under the
|
||||
`Shared Source' license, why should I bother with anything else?
|
||||
|
||||
@@ -493,6 +433,12 @@ A: No, it will not. Microsoft Office is a Windows application. To
|
||||
learn more about running Windows applications on Intel Unix systems
|
||||
refer to <a href="http://www.winehq.com">the Wine Project</a>.
|
||||
|
||||
Q: Will I be able to compile a Microsoft VB.NET application and execute
|
||||
the resultant MSIL file under MONO on Linux without converting to C#
|
||||
and recompiling?
|
||||
|
||||
A: Once we have a complete VisualBasic runtime, yes.
|
||||
|
||||
Q: Can mono run the WebMatrix?
|
||||
|
||||
A: No. That requires System.Windows.Forms support which is not
|
||||
@@ -543,136 +489,6 @@ A: Mono requires Unicode versions of Win32 APIs to run,
|
||||
Win32 libs. This is achieved by inserting -lunimono before
|
||||
-lkerner32/user32 in the linker's specs file.
|
||||
|
||||
Q: Why support Windows, when you can run the real thing?
|
||||
|
||||
A: There are various reasons:
|
||||
|
||||
<ul>
|
||||
<li> About half the contributors to Mono are Windows developers.
|
||||
They have many different for contributing to the effort, and
|
||||
we find it very important to let those developers run the runtime on Windows without forcing
|
||||
them to use a new operating system.
|
||||
|
||||
<li> Supporting Windows helps us identify the portable portions
|
||||
of Mono from the non-portable versions of it, helping Mono
|
||||
become more portable in the future.
|
||||
|
||||
<li> Mono does not heavily modify the windows registry, update system DLLs,
|
||||
install DLLs to the Windows/System32 path. Another words, I knew Mono would
|
||||
not cause any legacy enterprise applications to stop working - and it
|
||||
hasn't. However, our CIO er is againt it because of the changes that would
|
||||
be made to Windows 2000, such as, affecting security.
|
||||
</ul>
|
||||
|
||||
<a name="compatibility"></a>
|
||||
** Compatibility
|
||||
|
||||
Q: Can Mono run applications developed with the Microsoft.NET framework?
|
||||
|
||||
A: Yes, Mono can run applications developed with the Microsoft .NET Framework
|
||||
on Unix. There are a few caveats to keep in mind: Mono has not
|
||||
been completed yet, so a few API calls might be missing; And in
|
||||
some cases the Mono behavior *might* be incorrect.
|
||||
|
||||
Q: Will missing API entry points be implemented?
|
||||
|
||||
A: Yes, the goal of Mono is to implement precisely the .NET Framework
|
||||
API (as well as compile-time selectable subsets, for those
|
||||
interested in a lighter version of Mono).
|
||||
|
||||
Q: If the behavior of an API call is different, will you fix it?
|
||||
|
||||
A: Yes, we will. But we will need your assistance for this. If you find a bug
|
||||
in the Mono implementation, please fill a bug report in <a
|
||||
href="http://bugzilla.ximian.com">http://bugzilla.ximian.com</a>.
|
||||
Do not assume we know about the problem, we might not, and using the bug tracking
|
||||
system helps us organize the development process.
|
||||
|
||||
Q: Can I develop my applications on Windows, and deploy on a supported
|
||||
Mono platform (like Linux)?
|
||||
|
||||
A: Yes, you can.
|
||||
|
||||
As of today, Mono is not 100% finished, so it is sometimes useful
|
||||
to compile the code with Mono, to find out if your application
|
||||
depends on unimplemented functionality.
|
||||
|
||||
Q: Will applications run out the box with Mono?
|
||||
|
||||
A: Sometimes they will. But sometimes a .NET application might invoke
|
||||
Win32 API calls, or assume certain patterns that are not correct
|
||||
for cross-platform applications.
|
||||
|
||||
Q: What is a 100% .NET application?
|
||||
|
||||
A: A `100% .NET application' is one that only uses the APIs defined
|
||||
under the System namespace and does not use P/Invoke. These
|
||||
applications would in theory run unmodified on Windows, Linux,
|
||||
HP-UX, Solaris, MacOS X and others.
|
||||
|
||||
Note that this requirement also holds for all assemblies used by the
|
||||
application. If one of them is Windows-specific, then the entire program
|
||||
is not a 100% .NET application.
|
||||
|
||||
Furthermore, a 100% .NET application must not contain non-standard data
|
||||
streams in the assembly. For example, Visual Studio .NET will insert a
|
||||
<tt>#-</tt> stream into assemblies built under the "Debug" target.
|
||||
This stream contains debugging information for use by Visual Studio .NET;
|
||||
however, this stream can not be interpreted by Mono (unless you're willing
|
||||
to donate support).
|
||||
|
||||
Thus, it is recommended that all Visual Studio .NET-compiled code be
|
||||
compiled under the Release target before it is executed under Mono.
|
||||
|
||||
Q: Can I execute my Visual Studio .NET program (Visual Basic .NET, Visual C#,
|
||||
Managed Extensions for C++, etc.) under Mono?
|
||||
|
||||
A: Yes, with some reservations.
|
||||
|
||||
The .NET program must either be a 100% .NET application, or (somehow) have
|
||||
all dependent assemblies available on all desired platforms. (How to do so
|
||||
is outside the bounds of this FAQ.)
|
||||
|
||||
For example, since Mono's System.Windows.Forms implementation will use
|
||||
Wine, System.Windows.Forms is only as portable as Wine is. It's possible
|
||||
that Mono may run on a platform, but Wine will not, in which case a
|
||||
System.Windows.Forms app will not run on that platform. This is similarly
|
||||
true for all assemblies that are not 100% managed code.
|
||||
|
||||
Mono must also have an implementation for the .NET assemblies used. For
|
||||
example the System.EnterpriseServices namespace is part of .NET, but it
|
||||
has not been implemented in Mono. Thus, any applications using this
|
||||
namespace will not run under Mono.
|
||||
|
||||
With regards to languages, C# applications tend to be most portable.
|
||||
|
||||
Visual Basic .NET applications are portable, but Mono's
|
||||
Microsoft.VisualBasic.dll implementation is incomplete. It is recommended
|
||||
to either avoid using this assembly in your own code, only use the
|
||||
portions that Mono has implemented, or to help implement the missing
|
||||
features. Additionally, you can set 'Option Strict On', which
|
||||
eliminates the implicit calls to the unimplemented
|
||||
Microsoft.VisualBasic.CompilerServices.ObjectType class.
|
||||
(Thanks to Jörg Rosenkranz.)
|
||||
|
||||
Managed Extensions for C++ is least likely to operate under Mono. Mono
|
||||
does not support mixed mode assemblies (that is, assemblies containing both
|
||||
managed and unmanaged code, which Managed C++ can produce). You need a
|
||||
fully-managed assembly to run under Mono, and getting the Visual C++ .NET
|
||||
compiler to generate such an executable can be difficult. You need to use
|
||||
only the .NET-framework assemblies, not the C libraries (you can't use
|
||||
<b>printf</b>(3) for example.), and you need to use
|
||||
the linker options <tt>/nodefaultlib /entry:main mscoree.lib</tt> in
|
||||
addition to the <tt>/clr</tt> compiler flag. You can still use certain
|
||||
compiler intrinsic functions (such as <b>memcpy</b>(3)) and the STL.
|
||||
You should also see <a
|
||||
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vcmex/html/vcgrfconvertingmanagedextensionsforcprojectsfrommixed-modetopureil.asp"
|
||||
>Converting Managed Extensions for C++ Projects from Mixed Mode to Pure
|
||||
Intermediate Language</a> at MSDN.
|
||||
Finally, you can use PEVERIFY.EXE from the .NET SDK to determine if the
|
||||
assembly is fully managed.
|
||||
|
||||
Thanks to Serge Chaban for the linker flags to use.
|
||||
|
||||
<a name="pnpproject"></a>
|
||||
** Mono and Portable.NET
|
||||
@@ -685,22 +501,8 @@ A: Most of Mono is being written using C#, with only
|
||||
|
||||
It is easier to describe what is unique about Mono:
|
||||
<ul>
|
||||
<li> An advanced native-code compilation engine: Both
|
||||
just-in-time compilation (JIT) and pre-compilation of CIL
|
||||
bytecodes into native code are supported.
|
||||
|
||||
<li> A foundation for code optimization: The new code generator in
|
||||
Mono builds on the experience of our first JIT engine, and enables
|
||||
us to implement various advanced compiler optimization
|
||||
tricks. With an SSA-framework, plenty of new optimizations are possible.
|
||||
|
||||
The current list of optimizations are: Peephole postpass,
|
||||
Branch optimizations, Inline method calls, Constant folding, Constant
|
||||
propagation, Copy propagation, Dead code elimination, Linear scan
|
||||
global reg allocation, Conditional moves, Emit per-domain code,
|
||||
Instruction scheduling, Intrinsic method implementations, Tail
|
||||
recursion and tail calls, Loop related optimizations, Fast x86 FP
|
||||
compares, Leaf procedures optimizations
|
||||
<li> A Just-in-Time compiler engine. This is important for
|
||||
making your applications fast.
|
||||
|
||||
<li> A self-hosting C# compiler written in C#, which is clean, easy
|
||||
to maintain.
|
||||
@@ -714,43 +516,38 @@ A: Most of Mono is being written using C#, with only
|
||||
systems, while the interpreter works on SPARC, StrongARM,
|
||||
s390 and PowerPC systems.
|
||||
|
||||
Our new compilation engine is being ported to the PowerPC.
|
||||
|
||||
<li> Supports Linux, BSD, Windows and Solaris at this point.
|
||||
<li> Supports Linux, Windows and Solaris at this point.
|
||||
|
||||
<li> The JIT engine is written using a portable instruction
|
||||
selector which not only generates good code but
|
||||
selector which not only generates good code (we are told
|
||||
that we are faster than Rotor, but it is hard to tell) but
|
||||
is also the foundation to re-target the JIT engine to other
|
||||
systems.
|
||||
|
||||
<li> Full support for remoting in the runtime.
|
||||
The system employed is described in various compiler
|
||||
books and it is very similar to what is described in the
|
||||
book that covers LCC, the ANSI C retargetable C compiler.
|
||||
|
||||
<li> The JIT engine supports in-lining, constant folding and propagation,
|
||||
|
||||
<li> Full support for remoting in the runtime, but the class
|
||||
libraries are still behind.
|
||||
|
||||
<li> The C# compiler, the JIT engine and the class libraries are
|
||||
mature enough that the whole system has been self-hosting
|
||||
since April 2002. This means that we develop Mono
|
||||
completely with itself at this point.
|
||||
mature enough that the whole system is self-hosting. This means that
|
||||
we develop Mono completely with itself at this point.
|
||||
|
||||
By forcing ourselves to use our own code to develop our
|
||||
tools, we bug fix problems rapidly, and the system is
|
||||
overall more robust and tested than if we did not.
|
||||
<li> We are not yet done, and there is a lot of work left to be
|
||||
done
|
||||
|
||||
<li> We have a great community of developers, without which Mono
|
||||
would not be possible.
|
||||
|
||||
<li> We are working on an ahead of time compilation mode to
|
||||
pre-compile code for the target architecture (this is part
|
||||
of our new code generation effort).
|
||||
</ul>
|
||||
|
||||
In general, Mono is more mature and complete since it has been used
|
||||
to develop itself, which is a big motivator for stability and
|
||||
correctness, while Portable.NET remains pretty much an untested
|
||||
platform.
|
||||
|
||||
Q: I hear Mono keeps changing the P/Invoke API, why?
|
||||
|
||||
A: We are just fixing our implementation to be compatible with the
|
||||
Microsoft implementation. In other words, the Mono P/Invoke API is
|
||||
more complete when compared to the Portable.NET version, hence
|
||||
various pieces of software that depend on this extended
|
||||
functionality fail to work properly with Portable.NET.
|
||||
|
||||
<a name="webservices"></a>
|
||||
** Web Services
|
||||
|
||||
@@ -860,9 +657,6 @@ A: With any luck, Free Software enthusiasts will contribute tools to
|
||||
initially using the Microsoft implementation of the CLI and then
|
||||
executed later with Mono.
|
||||
|
||||
We are recommending people to use and contribute to existing
|
||||
projects like SharpDevelop, Anjuta and Eclipse.
|
||||
|
||||
Q: What kind of rules make the Common Intermediate Language useful for
|
||||
JITers?
|
||||
|
||||
@@ -890,14 +684,32 @@ A: In Mono, xsp is just the name of the C# code generator for ASP.NET
|
||||
Pages" technology so as they are very different things, they don't
|
||||
conflict.
|
||||
|
||||
Q: What about using something like Jabber instead of the System.Messaging
|
||||
namespace?.
|
||||
|
||||
A: In short, MSMQ is not something like Jabber, but asynchronous messaging
|
||||
through queues. Useful queues do more than serialize messages, they are
|
||||
also platform bridges.
|
||||
|
||||
Q: Are you supporting XMLDocument and relatives?.
|
||||
|
||||
A: Currently, we aren't implementing them yet. It would require updates to
|
||||
most of the XmlNode derivatives so it's not a trivial task. We are
|
||||
currently focusing on getting XPath support working.
|
||||
|
||||
Q: Is there any plan to develop an aspx server for Mono?.
|
||||
|
||||
A: The XSP reference server is available and you can also use mod_mono
|
||||
with Apache.
|
||||
A: The web server turned out to be very simple compared to the rest of the
|
||||
work. Gonzalo has got the page generator mostly done (a module called
|
||||
xsp, who has nothing to do with the XSP term used in the Apache Project).
|
||||
Patrik has done a lot of the work to get the ProcessRequest to work.
|
||||
You can try to help in the final touches to the System.Web classes and
|
||||
writing regression tests for the widgets we have.
|
||||
|
||||
Q: Is there any way I can develop the class libraries using Linux yet?
|
||||
|
||||
A: Yes. Mono has been self hosting since May 2002.
|
||||
A: Yes. Some class libraries can be developed on Linux. Search for
|
||||
Paolo's post (he lists which classes can be compiled fine now).
|
||||
|
||||
Q: Is there any way I can install a known working copy of mono in /usr,
|
||||
and an experimental copy somewhere else, and have both copies use
|
||||
@@ -917,27 +729,37 @@ Q: Would it be too terrible to have another corlib signed as mscorlib?
|
||||
A: We rename corlib to mscorlib also when saving the PE files, in fact,
|
||||
the runtime can execute program created by mono just fine.
|
||||
|
||||
Q: Is there a relatively straightforward way to repeat the steps taken
|
||||
by Paolo to get Mono completely self-hosted on Linux?
|
||||
|
||||
A: To build the compiler and class libraries in Linux, run:
|
||||
<ul><li>make -f makefile.gnu. To install them, run: </li>
|
||||
<li>make -f makefile.gnu install prefix=/opt/mono</li>
|
||||
</ul>
|
||||
|
||||
If you want to produce and distribute a monocharge tarball, run:
|
||||
make -f makefile.gnu dist
|
||||
Of course you have to run these in the top level mcs directory.
|
||||
|
||||
Q: Is it possible to build a C# file to some sort of intermediate format which
|
||||
can linked into a final module, like the traditional .c -> .o -> .so path?
|
||||
|
||||
A: You can use:
|
||||
A: You could do: mcs /target:module file1.cs, mcs /target:module file2.cs,
|
||||
mcs /target:exe file1.dll file2.dll /out:mybin.exe
|
||||
|
||||
mcs /target:library file1.cs, mcs /target:library file2.cs,
|
||||
mcs /target:exe file1.dll file2.dll /out:mybin.exe
|
||||
Q: Is there any plans for implementing remoting in the near future?, When will
|
||||
work in System.Runtime.Remoting.dll start?
|
||||
|
||||
Q: Is there any plans for implementing remoting in the near future?
|
||||
A: The remoting infrastructure is in place. Some of the channels and
|
||||
formatters are not.
|
||||
|
||||
A: The remoting infrastructure is in place. We have implementations
|
||||
of the TcpChannel, HttpChannel and the Soap and Binary Formatters.
|
||||
They are compatible with .NET.
|
||||
|
||||
However, some classes from the library may have a different binary
|
||||
representation, because they may have a different internal data
|
||||
structure, so for example you won't be able to exchange a Hastable
|
||||
object between Mono and MS.NET. It should not be a problem if you
|
||||
are using primitive types, arrays or your own classes. In any case,
|
||||
could you post a test case?
|
||||
Q: I'm wondering if there are any plans to start using nant to build the
|
||||
class lib + test lib. i think that every project need/should use an
|
||||
automated build process and nant + a couple of tools enables this. is
|
||||
the problem that the compiler can't run nant yet?
|
||||
|
||||
A: Maybe well be doing some sort of automated build process + testing when
|
||||
the summer finish.
|
||||
|
||||
Q: My C code uses the __stdcall which is not availble on Linux, how can I
|
||||
make the code portable Windows/Unix across platforms?
|
||||
@@ -949,42 +771,6 @@ A: Replace the __stdcall attribute with the STDCALL macro, and include this
|
||||
#define STDCALL __attribute__((stdcall))
|
||||
#endif
|
||||
|
||||
Q: I want to be able to execute Mono binaries, without having to use the "mono"
|
||||
command. How can I do this?
|
||||
|
||||
A: From Carlos Perelló:
|
||||
|
||||
<i>I think that the best solution is the binfmt feature with the
|
||||
wrapper that exists with Debian packages at:
|
||||
|
||||
<a href="http://www.debianplanet.org/mono/dists/unstable/main/source/admin/">http://www.debianplanet.org/mono/dists/unstable/main/source/admin/</a>
|
||||
|
||||
If you want use it with Big endian machines, you should apply a patch
|
||||
(<a href="http://carlos.pemas.net/debian/mono/binfmt-detector-cli.c.diff">http://carlos.pemas.net/debian/mono/binfmt-detector-cli.c.diff</a>)
|
||||
|
||||
It works really good and lets you use wine also, it reads the .exe file
|
||||
headers and check if it's a .net executable.
|
||||
|
||||
This way you just execute: ./my-cool-mono-application.exe and it works
|
||||
without the need of any wrapper.</i>
|
||||
|
||||
Q: I see funny characters when I run programs, what is the problem?
|
||||
|
||||
A: (From Peter Williams and Gonzalo Paniagua):
|
||||
|
||||
This is Red Hat 9 (probably) using UTF8 on its console; the bytes are
|
||||
the UTF8 endianness markers. You can do:
|
||||
|
||||
LC_ALL=C mono myexe.exe
|
||||
|
||||
And they wont show up.
|
||||
|
||||
Alternatively, you can do:
|
||||
|
||||
$ echo -e "\033%G"
|
||||
|
||||
to enable UTF-8 on the console.
|
||||
|
||||
<a name="asp">
|
||||
** Mono and ASP.NET
|
||||
|
||||
@@ -1021,7 +807,7 @@ A: Modules developed for Apache 2 are not compatible with Apache 1.3
|
||||
|
||||
Q: Can I run Apache 1 and Apache 2 on the same machine?
|
||||
|
||||
You can always keep a copy of Apache 2 running in parallel with your Apache
|
||||
You can always keep a copy of Apache 2 running in paralell with your Apache
|
||||
1.3 (either different port or using a reverse proxy).
|
||||
|
||||
You can also bind the two servers to different IP addresses on the
|
||||
@@ -1283,7 +1069,7 @@ A: There should not be any need to recode.
|
||||
Q: What do I need to watch out for when programming in VB.NET so that I'm
|
||||
sure to be able to run those apps on Linux?
|
||||
|
||||
A: Not making any P/Invoke or DLL calls should and not using anything in
|
||||
A: Not making any PInvoke or DLL calls should and not using anything in
|
||||
the Microsoft.* namespaces should suffice. Also do not use any
|
||||
Methods/Classes marked as "This type/method supports the .NET Framework
|
||||
infrastructure and is not intended to be used directly from your code."
|
||||
@@ -1438,9 +1224,9 @@ A: First some background information.
|
||||
for the open source Mono platform, nor integration with today's
|
||||
Mono's rich support of Linux.
|
||||
|
||||
The Mono strategy for dealing with these technologies is as
|
||||
The Mono strategy for dealing with these tehcnologies is as
|
||||
follows: (1) work around the patent by using a different
|
||||
implementation technique that retains the API, but changes the
|
||||
implementation techinque that retains the API, but changes the
|
||||
mechanism; if that is not possible, we would (2) remove the pieces
|
||||
of code that were covered by those patents, and also (3) find prior
|
||||
art that would render the patent useless.
|
||||
@@ -1457,17 +1243,6 @@ A: First some background information.
|
||||
components, and things that we have developed (like Gtk#) or Apache
|
||||
integration.
|
||||
|
||||
Q: Is Mono only an implementation of the .NET Framework?
|
||||
|
||||
A: Mono implements both the .NET Framework, as well as plenty of class
|
||||
libraries that are either Unix specific, <a
|
||||
href="http://www.gnome.org">Gnome</a> specific, or that are not
|
||||
part of the .NET Framework but people find useful.
|
||||
|
||||
The following map shows the relationship between the components:
|
||||
|
||||
<img src="http://primates.ximian.com/~miguel/tmp/map.png">
|
||||
|
||||
<a name="etc"></a>
|
||||
** Miscellaneous Questions
|
||||
|
||||
@@ -1564,6 +1339,3 @@ A: It's possible to run VC++ generated apps under Mono, but we do not
|
||||
or if you think that you found a bug, etc. Please visit the
|
||||
<a href="http://geneura.ugr.es/~jaime/deploy/mono-common-problems.html">Mono Common Problems</a> document and try there.
|
||||
|
||||
** Credits
|
||||
|
||||
The FAQ contains material contributed by Miguel de Icaza, Jaime Anguiano, Lluis Sánchez.
|
||||
@@ -12,8 +12,10 @@
|
||||
Common Language Infrastructure (also referred as the CLR) and a
|
||||
set of <a href="class-library.html">class libraries</a>. The
|
||||
runtime can be <a href="embedded-api.html">embedded</a> into your
|
||||
application. It implements of both <a href="ado-net.html">ADO.NET</a>
|
||||
and <a href="asp-net.html">ASP.NET</a>.
|
||||
application.
|
||||
|
||||
Mono has implementations of both <a href="ado-net">ADO.NET</a>
|
||||
and <a href="asp-net">ASP.NET</a> as part of its distribution.
|
||||
|
||||
You can read our <a href="rationale.html">rationale</a> for
|
||||
this project. If you have questions about the project, please
|
||||
@@ -32,9 +34,16 @@
|
||||
href="http://www.gotmono.com/cgi-bin/yabb/YaBB.pl">forum</a> at <a
|
||||
href="http://www.gotmono.com">GotMono</a>.
|
||||
|
||||
Wikis: <a href="http://www.nullenvoid.com/gtksharp/wiki">Gtk# Wiki</a>
|
||||
and <a href="http://www.nullenvoid.com/mono/wiki">Mono
|
||||
Wiki</a>
|
||||
You can contact the team at: <a
|
||||
href="mailto:mono-list@ximian.com">mono[email protected]</a>
|
||||
|
||||
In order to follow the process of the project and to learn more
|
||||
about the team members we have created the <a
|
||||
href="http://monoevo.sf.net/mwn/index.html">Mono Weekly News letter</a>.
|
||||
Which archives can be found <a
|
||||
href="http://monoevo.sf.net/mwn/archives.html">here</a>.
|
||||
We have a <a href="http://www.nullenvoid.com/gtksharp/wiki">Gtk# Wiki</a>
|
||||
and a <a href="http://www.nullenvoid.com/mono/wiki">Mono Wiki</a>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
@@ -74,7 +83,7 @@
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b><a href="asp-net.html">ASP.NET</a></b></td>
|
||||
<td>Webforms and WebServices working<br></td>
|
||||
<td>Webforms working<br></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
@@ -98,392 +107,10 @@
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td colspan="3">
|
||||
<b><center>In the news</center></b>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/netmagazine.png">
|
||||
</td>
|
||||
<td>
|
||||
<a href="http://www.fawcette.com/dotnetmag/2003_TE/magazine/columns/trends/default.asp">May 31st, 2003</a>: CLI integration.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/infoworld.png">
|
||||
</td>
|
||||
<td>
|
||||
<a href="http://www.infoworld.com/article/03/05/22/HNmono_1.html">May 22nd, 2003</a>: Mono 1.0 plans.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/infoworld.png">
|
||||
</td>
|
||||
<td>
|
||||
<a href="http://www.infoworld.com/article/03/03/14/11stratdev_1.html">Mar 14th, 2003</a>: Whither Mono?
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/b2.png">
|
||||
</td>
|
||||
<td>
|
||||
<a href="http://www.infoworld.com/article/03/05/22/HNmono_1.html">Dec, 2002</a>: The Penguin takes flight.
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@item Sep 1st, 2003: Ice for Mono; XmlSerializer generators; Monodoc progress.
|
||||
|
||||
<b>Ice:</b> Vladimir has checked into CVS (Module ginzu) an
|
||||
implementation of <a href="http://www.zeroc.com">ZeroC's</a>
|
||||
<a href="http://www.zeroc.com/ice.html">ICE</a> protocol. It
|
||||
is implemented using Remoting. If you were looking for an
|
||||
efficient binary protocol to use with Remoting, this is it.
|
||||
|
||||
ICE is simpler to use than CORBA, and was created by people
|
||||
who were deeply involved in CORBA and wanted to fix its
|
||||
problems (you can see a <a
|
||||
href="http://www.zeroc.com/iceVsCorba.html">list of
|
||||
differences</a>).
|
||||
|
||||
<b>XmlSerializer</b>: Lluis has checked in a new technology
|
||||
for use in our XmlSerializer: the XmlSerializer code
|
||||
generator. Currently our XmlSerializer generates a
|
||||
description of instructions for serializing data, these
|
||||
instructions are later interpreted while using it: Reflection
|
||||
is used to pull all the data. The code generator is the first
|
||||
step into turning the Serializer from an intepreter into a
|
||||
compiler and improving the performance of it.
|
||||
|
||||
Currently was used internally to implement the WSDL
|
||||
serializer, in the future it will just be part of the standard
|
||||
serialization process.
|
||||
|
||||
<b>MonoDoc:</b> New providers! Thanks to <a
|
||||
href="http://www.jaggersoft.com/">Jon Jagger</a> for providing
|
||||
us with his master XML files for the C# specification we now
|
||||
have integrated the C# spec into Monodoc. Another provider is
|
||||
the Error provider: now we include all the C# compiler errors
|
||||
in the help system.
|
||||
|
||||
Alp has contributed various user interface improvement, and
|
||||
updated our list widget for key navigation; Ben made the
|
||||
matches window more useful and Joshua has helped us clean up
|
||||
the ECMA provider even more.
|
||||
|
||||
@item Aug 14th, 2003: Mono 0.26 has been released
|
||||
|
||||
A new version of Mono is available, the new features include:
|
||||
<a href="http://www.cairographics.org/">Cairo support</a>, <a
|
||||
href="http://remoting-corba.sf.net">Remoting.Corba</a>
|
||||
support, as well as a managed XSLT implementation.
|
||||
|
||||
Existing features have been improved vastly: better
|
||||
Windows.Forms, runtime, faster compiler, web services, better
|
||||
compliance to the spec and more.
|
||||
|
||||
Check out the <a
|
||||
href="http://www.go-mono.com/archive/mono-0.26.html">Release
|
||||
notes</a> for details.
|
||||
|
||||
@item Aug 9th, 2003: Python for .NET Preview 2 available; Mono Documentation site up.
|
||||
|
||||
Brian Lloyd has <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-August/015313.html">announced</a>
|
||||
the availability of his Python binding to .NET. This works
|
||||
with .NET and Mono. For more information about it, see
|
||||
Brian's site at <a href="
|
||||
http://zope.org/Members/Brian/PythonNet/">http://zope.org/Members/Brian/PythonNet/</a>
|
||||
|
||||
We have uploaded the current Mono Documentation (core
|
||||
libraries and Gtk#) to <a
|
||||
href="http://mono.ximian.com:8080"/>http://mono.ximian.com:8080</a>.
|
||||
The site is running the ASP.NET edition of <a
|
||||
href="archive/monodoc-0.6.tar.gz">MonoDoc 0.6</a> on XSP.
|
||||
|
||||
@item Aug 6th, 2003: Winforms samples
|
||||
|
||||
Timothy Parez is coordinating the effort to create sample
|
||||
programs that exercise the various Windows.Forms controls. We
|
||||
are using this as graphical regression test suite for the Mono
|
||||
implementation.
|
||||
|
||||
The screenshots of the various widgets, together with the
|
||||
source code is available on the <a
|
||||
href="http://www.nullenvoid.com/mono/wiki/index.php/WineSamples">WineSamples</a>
|
||||
page on the <a
|
||||
href="http://www.nullenvoid.com/mono/wiki/">Mono Wiki</a>.
|
||||
|
||||
A new cvs module called `winforms' has been created that
|
||||
contains the source code for the samples. To run the samples,
|
||||
you can install the WineLib packages available from our <a
|
||||
href="download.html">download page</a>.
|
||||
|
||||
@item Aug 5th, 2003: New Apache Module architecture: 1.3 and 2.x supported
|
||||
|
||||
Gonzalo rearchitected our Apache module for hosting Mono and
|
||||
ASP.NET. The previous incarnation hosted a Mono runtime on
|
||||
each Apache process, which lead to a slow setup for webforms.
|
||||
The new setup uses a shared mono process for all the incoming
|
||||
requests. Daniel later improved up the new architecture and
|
||||
added dual support, so now in addition to Apache 2.x, we
|
||||
support Apache 1.3 with the same codebase.
|
||||
|
||||
The new code is available on CVS, on module `mod_mono', and
|
||||
now requires an XSP installation to be available.
|
||||
|
||||
@item Aug 4th, 2003: Ximian acquired by Novell.
|
||||
|
||||
Today <a href="http://www.novell.com">Novell</a> acquired <a
|
||||
href="http://www.ximian.com">Ximian</a>. The press release is
|
||||
available <a
|
||||
href="http://www.ximian.com./about_us/press_center/press_releases/index.html?pr=novell">here</a>.
|
||||
|
||||
Mono and Gnome form an integral part of the Novell strategy.
|
||||
|
||||
@item Jul 30th, 2003: Remoting.CORBA, Managed XSLT.
|
||||
|
||||
Today Lluis announced that Mono CVS contains all the fixes to
|
||||
run <a
|
||||
href="http://remoting-corba.sourceforge.net/">Remoting.CORBA</a>:
|
||||
both client and server channels work; We are interested in people
|
||||
testing it with other ORBs.
|
||||
|
||||
Ben checked-in today his managed implementation of Xslt that
|
||||
we mentioned on Jul 19th; This uncovered various limitations
|
||||
on the XPath implementation, which Piers has swifly removed.
|
||||
Monodoc, NUnit and our Corcompare work with it. Since this is
|
||||
implementation is not completed yet, we still support the
|
||||
libxslt-based version by default. For more details on how to
|
||||
try the new XSLT implementation, see <a
|
||||
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001681.html">Ben's
|
||||
post</a>
|
||||
|
||||
@item Jul 27th, 2003: Wine packages and Daily Snapshots
|
||||
|
||||
MonoWine packages (used to run System.Windows.Forms) software
|
||||
are now available from our (<a
|
||||
href="download.html">download</a> page). You can track the
|
||||
progress on our <a
|
||||
href="http://www.nullenvoid.com/mono/wiki/index.php/WineSamples">Wiki
|
||||
page.</a>
|
||||
|
||||
We're now building daily snapshots of Mono. They come in
|
||||
three distinct flavors:
|
||||
|
||||
<ul>
|
||||
* mono snapshot tarballs - These are 'release-style' tarballs and
|
||||
contain everything necessary to setup a new
|
||||
installation from scratch. This includes the Mono
|
||||
runtime and all the assemblies we distribute.
|
||||
|
||||
* monocharge tarballs - These tarballs contain only
|
||||
the assemblies built on that day.
|
||||
|
||||
* monolite tarballs - These tarballs contain a copy of
|
||||
'corlib.dll', 'mcs.exe', 'System.dll', 'System.Xml.dll' and
|
||||
'Mono.CSharp.Debugger.dll'. They can be used to
|
||||
re-bootstrap an out-of-sync installation.
|
||||
</ul>
|
||||
|
||||
The daily builds are availble here: <a href="http://go-mono.com/daily">http://go-mono.com/daily</a>
|
||||
|
||||
If you find that the builds are broken, please notify Duncan.
|
||||
|
||||
@item Jul 19th, 2003: Recent developments
|
||||
|
||||
Since Mono has matured, we have limited the news on the site
|
||||
to major accomplishments that are finished, but this week, it
|
||||
is worth devoting some time to talk about some of the
|
||||
work-in-progress projects that are progressing.
|
||||
|
||||
Jackson has added support to the IL assembler for generics as
|
||||
well as to the PEAPI library, and it has assembled its first
|
||||
generic program. Support for handling images with generics
|
||||
has been on our file format reader for a while, but the JIT
|
||||
engine is still incomplete.
|
||||
|
||||
On the XSLT world, Atsushi and Ben continue to make big
|
||||
improvements. Ben recently got the prototype managed XSLT
|
||||
implementation to run its first stylesheet. Although
|
||||
currently Mono uses libxslt to implement the System.Xml.Xsl
|
||||
namespace, to have a fully .NET compliant implementation we
|
||||
will need a managed version, and this is the beginning of it.
|
||||
|
||||
Lluis recently posted an update on the <a
|
||||
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001550.html">state
|
||||
of WSDL</a> in Mono. Now that the web services runtime is
|
||||
ready, the WSDL compiler becomes more important as a
|
||||
development tool.
|
||||
|
||||
Atsushi continues his work on the DTD validating reader in
|
||||
System.Xml, as well as improving our XML Schema support.
|
||||
|
||||
@item Jul 14th, 2003: New build system; IPV6 support.
|
||||
|
||||
Peter Williams has contributed a new build system that
|
||||
addresses many of the annoyance we had with our previous build
|
||||
system. He has worked on this for a few weeks, and Gonzalo
|
||||
helped test it and get it into CVS. We no longer have the
|
||||
historical dual build system: make for Unix and nant for
|
||||
Windows.
|
||||
|
||||
This system also offers the opportunity to compile our class
|
||||
libraries with different profiles (.NET 1.0, .NET 1.1 and the
|
||||
various ECMA subsets).
|
||||
|
||||
Peter explains the new build system <a
|
||||
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001506.html">here</a>
|
||||
|
||||
Jerome's IPV6 code has been checked into CVS; With Peter's new
|
||||
build system, we will be able to expose it (as part of the
|
||||
NET_1_1 build).
|
||||
|
||||
@item Jul 9th, 2003: ASP.NET web services, coverage tools.
|
||||
|
||||
Web Services keep advancing: now we also support server-side
|
||||
authoring of Web Services as well as web service clients
|
||||
(which shipped in Mono 0.25). This works using our ASP.NET
|
||||
runtime, so it works with either XSP or the Apache module. The
|
||||
new Web Services work from Lluis added the missing bits:
|
||||
<ul>
|
||||
<li> .asmx files.
|
||||
<li> Method calls with complex parameters (whatever XmlSerializer can currently serialize, which is a quite a lot).
|
||||
<li> ref and out parameters.
|
||||
<li> Soap headers (In, Out and InOut).
|
||||
<li> Soap extensions, both global (configured in web.config) and particular to methods (configured using attributes).
|
||||
</ul>
|
||||
|
||||
For more details, see Lluis <a href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001449.html">post</a>
|
||||
|
||||
GUI-wise: Work on <a href="http://xr.xwin.org">Xr</a> to
|
||||
implement System.Drawing continues. This will provide a full
|
||||
GDI+ implementation for Mono, and this will be hooked up into
|
||||
Gtk# and System.Windows.Forms.
|
||||
|
||||
MonoDoc keeps moving along, with a new web-based version
|
||||
coming up next, and we are also exploring a collaborative
|
||||
extension to allow people to contribute documentation through
|
||||
their web browsers.
|
||||
|
||||
Zoltan's Coverage analysis tool has been checked into CVS.
|
||||
With this tool it is now possible to find which class library
|
||||
code paths are missing regression tests. The module is
|
||||
`monocov'. Details are <a
|
||||
href="http://www.nexus.hu/vargaz/">here</a>. A fresh Gtk#
|
||||
version is available now.
|
||||
|
||||
Jean's remoting-based Soap implenentation is also maturing.
|
||||
|
||||
@item Jun 26th: Mono 0.25 has been released.
|
||||
|
||||
We have released Mono 0.25. A list of the new features is
|
||||
available <a href="archive/mono-0.25.html">here</a>.
|
||||
|
||||
Packages for Windows, and various Linux distributions are
|
||||
available on our <a href="download.html">download</a> page.
|
||||
|
||||
@item Jun 17th, 2003: Web Services client; Profiling hooks
|
||||
|
||||
Lluis and Gonzalo have checked into CVS the support for web
|
||||
services in the Mono runtime. This allows Mono to work as a
|
||||
web services client. We still require a WSDL compiler to
|
||||
compile the initial stub, but Erik has the beginning of a WSDL
|
||||
compiler ready and Atsushi has continued work on his
|
||||
experimental Xml Schema to C# class generator.
|
||||
|
||||
As part of this, the Mono Http runtime has been rewritten to
|
||||
increase reliability, scalability and conformance to the
|
||||
specs. Also our io-layer has been extended to not have
|
||||
arbitrary limits. This was done as part of our collaboration
|
||||
with SourceGear.
|
||||
|
||||
Paolo has commited the new pluggable profiling API to the Mono
|
||||
runtime: now the profiler is built as a module, and a new code
|
||||
coverage analysis has been checked in (and Zoltan already
|
||||
added improvements to it).
|
||||
|
||||
Mark's Mozilla bindings continue to improve, and we will shortly
|
||||
migrate the Mono documentation browser to use Mozilla, to take
|
||||
advantage of the tutorial's use of CSS.
|
||||
|
||||
Jackson's work on the IL assembler and Ben on running
|
||||
regression tests have provided us with a very needed tool in
|
||||
the Mono toolkit. One of the last missing pieces on the SDK.
|
||||
|
||||
On the crypto world, we got Sebastien's certificate viewer
|
||||
checked into CVS and the crypto code keeps advancing by leaps
|
||||
and bounds.
|
||||
|
||||
Alexandre and Aleksey Work continues on Windows.Forms on top
|
||||
of Wine and Gtk# (the former for full compatibility, the later
|
||||
for ease-of-authoring).
|
||||
|
||||
Cesar checked in the beginning of the semantic analysis code
|
||||
for his JScript compiler, and will be working on it full time.
|
||||
|
||||
@item Jun 11th, 2003: SourceGear and Ximian announce partnership
|
||||
|
||||
Ximian, Inc., the leading provider of desktop and server
|
||||
solutions enabling enterprise Linux adoption, today announced
|
||||
that SourceGear Corporation will use Mono\x{2122} Project
|
||||
technology to offer cross-platform versions of its
|
||||
products. In addition, the companies have entered into a
|
||||
development partnership under which Ximian will provide
|
||||
custom Mono development to enable delivery of SourceGear
|
||||
products later this year. As a result, SourceGear will offer
|
||||
both UNIX and Linux clients for its SourceGear Vault source
|
||||
code management tool, enabling broader use of its solutions in
|
||||
mixed-platform development organizations.
|
||||
|
||||
<a href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=sourcegear">Read more...</a>
|
||||
|
||||
Some technical details are available <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-June/014334.html">here</a>.
|
||||
|
||||
@item May 20th, 2003: OpenLink releases WineLib patches.
|
||||
|
||||
OpenLink <a
|
||||
href="http://lists.ximian.com/archives/public/mono-winforms-list/2003-May/000284.html">announced</a>
|
||||
the release of Vladimir's work to turn Wine into a library
|
||||
that can be used dynamically from Mono. This work simplifies
|
||||
the work on System.Windows.Forms as it is no longer necessary
|
||||
have a special version of the GC, nor have a stub program.
|
||||
The patches are available <a
|
||||
href="http://www.openlinksw.com/mono/">here</a>.
|
||||
|
||||
Mono packages for the Linux/s390 are available now in the <a
|
||||
href="download.html">download page</a>.
|
||||
|
||||
@item May 10th, 2003: Eclipse runs on Mono
|
||||
|
||||
Today Zoltan Varga announced that he got the <a
|
||||
href="http://www.eclipse.org">Eclipse IDE</a> running on top
|
||||
of Mono+<a href="http://www.ikvm.net">IKVM</a>.
|
||||
|
||||
A screenshot of Eclipse running with Mono can be found <a
|
||||
href="images/ikvm-screenshot.png">here</a>
|
||||
|
||||
@item May 6th, 2003: Mono 0.24 ships
|
||||
|
||||
We have released Mono 0.24 which includes our new code
|
||||
generation engine. A list of the new features is available <a
|
||||
href="archive/mono-0.24.html">here</a>.
|
||||
|
||||
Packages for Windows, and various Linux distributions are
|
||||
available on our <a href="download.html">download</a> page.
|
||||
We are shipping Gtk# and MonoDoc packages for the first time.
|
||||
|
||||
@item Apr 21st, 2003: Virtuoso 3.0 ships.
|
||||
|
||||
<a href="http://www.openlinksw.com">OpenLink's</a> released
|
||||
@@ -1329,6 +956,4 @@
|
||||
|
||||
<h2>Older News</h2>
|
||||
|
||||
Click <a href="oldnews.html">here</a> to see the olds news.
|
||||
|
||||
|
||||
Click <a href="oldnews.html">here</a> to see the olds news.
|
||||
+16
-20
@@ -9,7 +9,6 @@
|
||||
* <a href="#Oberon">Oberon</a>
|
||||
* <a href="#Forth">Forth</a>
|
||||
* <a href="#mbas">Mono Basic</a> (Mono's VB.NET compiler)
|
||||
* <a href="#dotlist">dotLisp</a>
|
||||
</ul>
|
||||
|
||||
Languages which are known to run, but we have not done a
|
||||
@@ -85,9 +84,9 @@
|
||||
** Component Pascal
|
||||
|
||||
The Component Pascal compiler: <a
|
||||
href="http://www.citi.qut.edu.au/research/plas/projects/cp_files/cpnet.html">Home
|
||||
href="http://www2.fit.qut.edu.au/CompSci/PLAS/ComponentPascal">Home
|
||||
Page</a>, you can <a
|
||||
href="http://www.citi.qut.edu.au/research/plas/projects/cp_files/cpdownload.html">
|
||||
href="http://www2.fit.qut.edu.au/CompSci/PLAS/ComponentPascal/gpcp1.1.4-netRTM.zip">
|
||||
download it</a>
|
||||
|
||||
<a name="Forth">
|
||||
@@ -111,22 +110,10 @@
|
||||
<a href="mailto:[email protected]">Brian Lloyd</a> is
|
||||
working on linking the Python runtime with the .NET runtime.
|
||||
More information on the PS.NET project can be found <a
|
||||
href="http://www.zope.org/Members/Brian/PythonNet">here</a>.
|
||||
href="http://www.zope.org/Members/Brian/PythonNet/index_html">here</a>.
|
||||
An FAQ document is available <a
|
||||
href="http://www.zope.org/Members/Brian/PythonNet/FAQ.html">here</a>.
|
||||
|
||||
<a name="dotlisp">
|
||||
** dotLisp
|
||||
|
||||
DotLisp is available from: <a
|
||||
href="http://sourceforge.net/projects/dotlisp/">http://sourceforge.net/projects/dotlisp/</a>
|
||||
|
||||
<a name="JavaScript">
|
||||
* Java Script
|
||||
|
||||
Cesar is working on Mono's implementation of JScript, the code
|
||||
is available on CVS on module `mcs'.
|
||||
|
||||
* Missing languages
|
||||
|
||||
Here is a list of a few languages that we would like to see
|
||||
@@ -135,6 +122,19 @@
|
||||
implementing or adapting a compiler for any of these
|
||||
languages:
|
||||
|
||||
<a name="JavaScript">
|
||||
* Java Script
|
||||
|
||||
The Mozilla project has an implementation of JavaScript
|
||||
written in Java called <a
|
||||
href="http://www.mozilla.org/rhino/">Rhino</a>.
|
||||
|
||||
You could port this code from Java to C#.
|
||||
|
||||
Note that since JavaScript allows for evaluation at runtime,
|
||||
the compiler has to be built as a class that can be invoked at
|
||||
runtime.
|
||||
|
||||
<a name="c">
|
||||
* C
|
||||
|
||||
@@ -152,10 +152,6 @@
|
||||
<a name="Java">
|
||||
* Java
|
||||
|
||||
Java bytecode can run directly on Mono using the <a
|
||||
href="http://www.ikvm.net">IKVM</a> java virtual machine for
|
||||
.NET.
|
||||
|
||||
We have a <a href="java.html">separate page</a> for Java.
|
||||
|
||||
|
||||
-194
@@ -1,194 +0,0 @@
|
||||
* Mono hacking TODO list
|
||||
|
||||
From time to time people that want to contribute to Mono ask
|
||||
on the mailing list what they can help with. The generic
|
||||
answer is always:
|
||||
<ul>
|
||||
* Write documentation.
|
||||
* Write regression tests.
|
||||
* Complete the implementations of the class libraries.
|
||||
* Help fix the bugs filed in our bugzilla database.
|
||||
</ul>
|
||||
|
||||
The proposed tasks are very important for the Mono project and
|
||||
are suitable for people that can dedicate even just an hour
|
||||
per week to contribute. But some people may need something
|
||||
more focused to work on, such as students that want to do a
|
||||
thesis on their contribution to Mono. For such people (and
|
||||
also for professors who want ideas for thesis regarding JIT or
|
||||
VM technologies), here is a list of tasks that need attention.
|
||||
|
||||
The estimated time to complete any of the tasks is between 1
|
||||
week to several months to accomodate for different hacking
|
||||
possibilities.
|
||||
|
||||
Note on the time estimates: they are very rough estimates, a
|
||||
smart and dedicated hacker can complete the tasks in half of
|
||||
the minimum time, a part-time hacker that also has a social
|
||||
life can take more than double the max time, but there's
|
||||
nothing to worry as long as progress is being done.
|
||||
|
||||
If some people (or group of people) want to take on a task,
|
||||
they should write to the mono-devel mailing list and in the
|
||||
relative bugzilla bug report. Discussions about how to
|
||||
implement a feature or additional information on the task
|
||||
should be mailed to the list or in the bugzilla report as well
|
||||
so that people can keep informed on the progress or have the
|
||||
information needed to start contributing.
|
||||
|
||||
Mono is an excellent platform for research on JITs, virtual
|
||||
machines and specifically the CLR because it provides an
|
||||
advanced free software implementation that can be used as a
|
||||
basis for more optimizations, new approaches to problems and
|
||||
new features.
|
||||
|
||||
There are different areas of interest where high-level
|
||||
contributions can be made:
|
||||
|
||||
<ul>
|
||||
* <b>JIT compiler</b>: tasks can be: adding more optimizations, reducing
|
||||
compile time, porting to different architectures.
|
||||
|
||||
* <b>AOT compiler</b>: optimizing the compiler output and the AOT loader,
|
||||
better support for multiple application domains.
|
||||
|
||||
* <b>VM runtime</b>: optimizing the runtime data structures, experimenting with
|
||||
different garbage collectors, integration with different component models.
|
||||
|
||||
* <b>Class library</b>: many opportunities in the implementation of regular
|
||||
expressions, Xml related technologies (XPath, XLST, etc).
|
||||
|
||||
* <b>Compilers</b>: writing compilers, interpreters and runtimes for langauges
|
||||
so that they run on the CLR (using Reflection.Emit support, for example).
|
||||
</ul>
|
||||
|
||||
Happy hacking!
|
||||
|
||||
<table border=1 cellspacing="0" cellpadding="0">
|
||||
<tr>
|
||||
<th>Area<th>Description<th>Difficulty<th>Time estimate<th>Bugzilla ID
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Runtime (mono/metadata)
|
||||
<td>Optimize method vtable. Currently all the methods in a class
|
||||
are added to the method vtable, including static and non-virtual methods.
|
||||
This makes vtables bigger and the instructions to access them are longer,
|
||||
increasing also code size. Some code in metadata/icall.c and maybe also some
|
||||
remoting code may depend on the current layout: such code should be fixed as well.
|
||||
<td>Medium
|
||||
<td>1-2 weeks
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>System assembly (mcs/class/System/)
|
||||
<td>Implement the IL-based regular expression engine. Instead of
|
||||
intepreting the regular expression pattern, a method is created at runtime using
|
||||
Reflection.Emit. This makes for faster pattern matching because there is no
|
||||
intepreter overhead and the matching code is jitted to fast native code.
|
||||
Bonus points if the compiled regular expression is compatible with the ones generated
|
||||
by the MS runtime.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>2-4 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Implement common subexpression elimination.
|
||||
Global and local common subexpression elimination needs to be implemented
|
||||
to achieve better performance. The local case is easier and may take just one month.
|
||||
It should be implemented in the context of the SSA framework (mini/ssa.c).
|
||||
<td>Hard (thesis subject)
|
||||
<td>2-4 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Optimize AOT compiler output.
|
||||
Currently the code generated by the AOT compiler may be significantly slower than
|
||||
jitted code. This is mostly because the AOT code supports multiple application domains
|
||||
and some values that are constant at JIT-time are not constant at AOT-time. It may be
|
||||
needed to write a simple dynamic linker and/or binary object writer. Bonus poinst if
|
||||
it supports ELF, PE/COFF and mach-O binary formats. A possible idea for improvements
|
||||
is also the use of appdomain ID-indexed tables to get at the appdomain specific data.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>3-6 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Implement generics support.
|
||||
We need to add support for the additional instructions and change existing ones to
|
||||
support the generics requirements.
|
||||
<td>Medium-hard
|
||||
<td>2-3 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Port the JIT to additional architectures.
|
||||
Currently ports are in the works for ppc, arm, sparc, s390. None of the ports
|
||||
are as feature-complete as the x86 one, yet, so help is needed in getting them
|
||||
up to speed. Ports to more architectures are welcome as well.
|
||||
<td>Medium-hard
|
||||
<td>3-6 months per arch
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Runtime and JIT (mono/metadata and mono/mini/)
|
||||
<td>Add support for COM and/or XPCOM and/or ORBit.
|
||||
We need a way to seamlessy use existing component technologies inside the mono runtime.
|
||||
The COM support needs to match the MS runtime behaviour and is targeted at windows systems.
|
||||
XPCOM and ORBit support are important on Unix platforms. Bonus points for developing
|
||||
the runtime support so that different component systems can be used at the same time.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>3-4 months for each
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Runtime and JIT (mono/metadata and mono/mini/)
|
||||
<td>Implement support for Code Access Security.
|
||||
Support needs to be added to the JIT and the runtime to ensure
|
||||
code that executes privileged operations is permitted to do so.
|
||||
The task includes loading the security information from metadata,
|
||||
collecting evidence, inserting calls to the permission objects,
|
||||
stack walking to collect security info.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>4-5 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Runtime and JIT (mono/metadata and mono/mini/)
|
||||
<td>Implement support for a generational GC.
|
||||
We're currently using a conservative non-moving GC.
|
||||
Support for a generational and moving GC requires changes to the JIT
|
||||
(to record locations in frames as well as registers that may contain
|
||||
pointers to GC-allocated memory) and to the runtime code (when
|
||||
objects are manipulated directly we should make sure they are pinned
|
||||
and reachable by the GC also in the C unmanaged code). Code from an existing
|
||||
precise GC such as the ORP one could be reused or a new GC may be developed
|
||||
(increasing the estimated development time).
|
||||
<td>Hard (thesis subject)
|
||||
<td>6-8 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Compilers for dynamic languages
|
||||
<td>Write a IL compiler and runtime support for dynamic languages like
|
||||
Python, Perl, Ruby, PHP.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>6-12 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
@@ -43,7 +43,7 @@
|
||||
in the Microsoft .NET Environment</a> is an article
|
||||
by Mr. Venu who is a MySQL AB developer.</li>
|
||||
|
||||
<p>Testing for Mono's Mono.Data.MySql and ByteFX's ByteFX.Data.MySqlClient is below.
|
||||
<p>Testing for Mono's Mono.Data.MySql and ByteFX's ByteFX.Data.MySQLClient is below.
|
||||
|
||||
** Current Status
|
||||
|
||||
@@ -51,7 +51,7 @@
|
||||
|
||||
<ul>
|
||||
|
||||
<li>ByteFX.Data.MySqlClient
|
||||
<li>ByteFX.Data.MySQLClient
|
||||
<ul>
|
||||
<li>Build and Runs on Microsoft .NET and Mono</li>
|
||||
<li>Works with SQL# (command-line and GTK# GUI versions)</li>
|
||||
@@ -109,7 +109,7 @@
|
||||
The current plan for the MySQL data providers:
|
||||
|
||||
<ul>
|
||||
<li>ByteFX.Data.MySqlClient
|
||||
<li>ByteFX.Data.MySQLClient
|
||||
<ul>
|
||||
<li>Testing and fixes</li>
|
||||
<li>Implement missing features</li>
|
||||
@@ -163,7 +163,7 @@
|
||||
<pre>
|
||||
using System;
|
||||
using System.Data;
|
||||
using ByteFX.Data.MySqlClient;
|
||||
using ByteFX.Data.MySQLClient;
|
||||
|
||||
public class Test
|
||||
{
|
||||
@@ -175,7 +175,7 @@
|
||||
"User ID=myuserid;" +
|
||||
"Password=mypassword;";
|
||||
IDbConnection dbcon;
|
||||
dbcon = new MySqlConnection(connectionString);
|
||||
dbcon = new MySQLConnection(connectionString);
|
||||
dbcon.Open();
|
||||
IDbCommand dbcmd = dbcon.CreateCommand();
|
||||
// requires a table to be created named employee
|
||||
|
||||
@@ -0,0 +1,246 @@
|
||||
System.Object
|
||||
System.Exception
|
||||
System.ValueType
|
||||
System.Delegate
|
||||
System.MulticastDelegate
|
||||
System.Enum
|
||||
System.Activator
|
||||
System.ArgIterator
|
||||
System.__ComObject
|
||||
System.TypedReference
|
||||
System.Security.AllowPartiallyTrustedCallersAttribute
|
||||
System.Runtime.Serialization.Formatter
|
||||
System.Runtime.Serialization.FormatterConverter
|
||||
System.Runtime.Serialization.FormatterServices
|
||||
System.Runtime.Serialization.ObjectIDGenerator
|
||||
System.Runtime.Serialization.ObjectManager
|
||||
System.Reflection.ModuleResolveEventHandler
|
||||
System.Reflection.Pointer
|
||||
System.Globalization.CompareInfo
|
||||
System.Globalization.HebrewCalendar
|
||||
System.Globalization.HijriCalendar
|
||||
System.Globalization.JapaneseCalendar
|
||||
System.Globalization.KoreanCalendar
|
||||
System.Globalization.SortKey
|
||||
System.Globalization.StringInfo
|
||||
System.Globalization.TaiwanCalendar
|
||||
System.Globalization.TextElementEnumerator
|
||||
System.Globalization.TextInfo
|
||||
System.Globalization.ThaiBuddhistCalendar
|
||||
System.IO.IsolatedStorage.IsolatedStorageFile
|
||||
System.Reflection.Emit.MethodRental
|
||||
System.Runtime.CompilerServices.AccessedThroughPropertyAttribute
|
||||
System.Runtime.CompilerServices.CallConvCdecl
|
||||
System.Runtime.CompilerServices.CallConvStdcall
|
||||
System.Runtime.CompilerServices.CallConvThiscall
|
||||
System.Runtime.CompilerServices.CallConvFastcall
|
||||
System.Runtime.CompilerServices.CustomConstantAttribute
|
||||
System.Runtime.CompilerServices.DateTimeConstantAttribute
|
||||
System.Runtime.CompilerServices.DiscardableAttribute
|
||||
System.Runtime.CompilerServices.DecimalConstantAttribute
|
||||
System.Runtime.CompilerServices.CompilationRelaxationsAttribute
|
||||
System.Runtime.CompilerServices.CompilerGlobalScopeAttribute
|
||||
System.Runtime.CompilerServices.IDispatchConstantAttribute
|
||||
System.Runtime.CompilerServices.IsVolatile
|
||||
System.Runtime.CompilerServices.IUnknownConstantAttribute
|
||||
System.Runtime.CompilerServices.RequiredAttributeAttribute
|
||||
System.Runtime.InteropServices.ArrayWithOffset
|
||||
System.Runtime.InteropServices.DispIdAttribute
|
||||
System.Runtime.InteropServices.ClassInterfaceType
|
||||
System.Runtime.InteropServices.ClassInterfaceAttribute
|
||||
System.Runtime.InteropServices.ComVisibleAttribute
|
||||
System.Runtime.InteropServices.LCIDConversionAttribute
|
||||
System.Runtime.InteropServices.ComRegisterFunctionAttribute
|
||||
System.Runtime.InteropServices.ComUnregisterFunctionAttribute
|
||||
System.Runtime.InteropServices.ProgIdAttribute
|
||||
System.Runtime.InteropServices.ImportedFromTypeLibAttribute
|
||||
System.Runtime.InteropServices.IDispatchImplType
|
||||
System.Runtime.InteropServices.IDispatchImplAttribute
|
||||
System.Runtime.InteropServices.ComSourceInterfacesAttribute
|
||||
System.Runtime.InteropServices.ComConversionLossAttribute
|
||||
System.Runtime.InteropServices.TypeLibTypeFlags
|
||||
System.Runtime.InteropServices.TypeLibFuncFlags
|
||||
System.Runtime.InteropServices.TypeLibVarFlags
|
||||
System.Runtime.InteropServices.TypeLibTypeAttribute
|
||||
System.Runtime.InteropServices.TypeLibFuncAttribute
|
||||
System.Runtime.InteropServices.TypeLibVarAttribute
|
||||
System.Runtime.InteropServices.ComImportAttribute
|
||||
System.Runtime.InteropServices.PreserveSigAttribute
|
||||
System.Runtime.InteropServices.ComAliasNameAttribute
|
||||
System.Runtime.InteropServices.AutomationProxyAttribute
|
||||
System.Runtime.InteropServices.PrimaryInteropAssemblyAttribute
|
||||
System.Runtime.InteropServices.CoClassAttribute
|
||||
System.Runtime.InteropServices.ComEventInterfaceAttribute
|
||||
System.Runtime.InteropServices.COMException
|
||||
System.Runtime.InteropServices.ComMemberType
|
||||
System.Runtime.InteropServices.CurrencyWrapper
|
||||
System.Runtime.InteropServices.DispatchWrapper
|
||||
System.Runtime.InteropServices.ErrorWrapper
|
||||
System.Runtime.InteropServices.ExtensibleClassFactory
|
||||
System.Runtime.InteropServices.HandleRef
|
||||
System.Runtime.InteropServices.InvalidComObjectException
|
||||
System.Runtime.InteropServices.InvalidOleVariantTypeException
|
||||
System.Runtime.InteropServices.TypeLibImporterFlags
|
||||
System.Runtime.InteropServices.ExporterEventKind
|
||||
System.Runtime.InteropServices.ITypeLibExporterNotifySink
|
||||
System.Runtime.InteropServices.ITypeLibConverter
|
||||
System.Runtime.InteropServices.MarshalDirectiveException
|
||||
System.Runtime.InteropServices.ObjectCreationDelegate
|
||||
System.Runtime.InteropServices.RuntimeEnvironment
|
||||
System.Runtime.InteropServices.RegistrationServices
|
||||
System.Runtime.InteropServices.SafeArrayRankMismatchException
|
||||
System.Runtime.InteropServices.SafeArrayTypeMismatchException
|
||||
System.Runtime.InteropServices.SEHException
|
||||
System.Runtime.InteropServices.TypeLibConverter
|
||||
System.Runtime.InteropServices.BIND_OPTS
|
||||
System.Runtime.InteropServices.UCOMIBindCtx
|
||||
System.Runtime.InteropServices.UCOMIConnectionPointContainer
|
||||
System.Runtime.InteropServices.UCOMIConnectionPoint
|
||||
System.Runtime.InteropServices.UCOMIEnumMoniker
|
||||
System.Runtime.InteropServices.CONNECTDATA
|
||||
System.Runtime.InteropServices.UCOMIEnumConnections
|
||||
System.Runtime.InteropServices.UCOMIEnumConnectionPoints
|
||||
System.Runtime.InteropServices.UCOMIEnumString
|
||||
System.Runtime.InteropServices.UCOMIEnumVARIANT
|
||||
System.Runtime.InteropServices.FILETIME
|
||||
System.Runtime.InteropServices.UCOMIMoniker
|
||||
System.Runtime.InteropServices.UCOMIPersistFile
|
||||
System.Runtime.InteropServices.UCOMIRunningObjectTable
|
||||
System.Runtime.InteropServices.STATSTG
|
||||
System.Runtime.InteropServices.UCOMIStream
|
||||
System.Runtime.InteropServices.DESCKIND
|
||||
System.Runtime.InteropServices.BINDPTR
|
||||
System.Runtime.InteropServices.UCOMITypeComp
|
||||
System.Runtime.InteropServices.TYPEKIND
|
||||
System.Runtime.InteropServices.TYPEFLAGS
|
||||
System.Runtime.InteropServices.IMPLTYPEFLAGS
|
||||
System.Runtime.InteropServices.TYPEATTR
|
||||
System.Runtime.InteropServices.FUNCDESC
|
||||
System.Runtime.InteropServices.IDLFLAG
|
||||
System.Runtime.InteropServices.IDLDESC
|
||||
System.Runtime.InteropServices.PARAMFLAG
|
||||
System.Runtime.InteropServices.PARAMDESC
|
||||
System.Runtime.InteropServices.TYPEDESC
|
||||
System.Runtime.InteropServices.ELEMDESC
|
||||
System.Runtime.InteropServices.VARDESC
|
||||
System.Runtime.InteropServices.DISPPARAMS
|
||||
System.Runtime.InteropServices.EXCEPINFO
|
||||
System.Runtime.InteropServices.FUNCKIND
|
||||
System.Runtime.InteropServices.INVOKEKIND
|
||||
System.Runtime.InteropServices.CALLCONV
|
||||
System.Runtime.InteropServices.FUNCFLAGS
|
||||
System.Runtime.InteropServices.VARFLAGS
|
||||
System.Runtime.InteropServices.UCOMITypeInfo
|
||||
System.Runtime.InteropServices.SYSKIND
|
||||
System.Runtime.InteropServices.LIBFLAGS
|
||||
System.Runtime.InteropServices.TYPELIBATTR
|
||||
System.Runtime.InteropServices.UCOMITypeLib
|
||||
System.Runtime.InteropServices.UnknownWrapper
|
||||
System.Runtime.Remoting.IObjectHandle
|
||||
System.Runtime.Remoting.IRemotingTypeInfo
|
||||
System.Runtime.Remoting.IChannelInfo
|
||||
System.Runtime.Remoting.IEnvoyInfo
|
||||
System.Runtime.Remoting.RemotingConfiguration
|
||||
System.Runtime.Remoting.TypeEntry
|
||||
System.Runtime.Remoting.ActivatedClientTypeEntry
|
||||
System.Runtime.Remoting.ActivatedServiceTypeEntry
|
||||
System.Runtime.Remoting.WellKnownClientTypeEntry
|
||||
System.Runtime.Remoting.WellKnownServiceTypeEntry
|
||||
System.Runtime.Remoting.RemotingException
|
||||
System.Runtime.Remoting.ServerException
|
||||
System.Runtime.Remoting.RemotingTimeoutException
|
||||
System.Runtime.Remoting.RemotingServices
|
||||
System.Runtime.Remoting.InternalRemotingServices
|
||||
System.Runtime.Remoting.SoapServices
|
||||
System.Runtime.Remoting.Activation.UrlAttribute
|
||||
System.Runtime.Remoting.Messaging.IMessageSink
|
||||
System.Runtime.Remoting.Messaging.AsyncResult
|
||||
System.Runtime.Remoting.Messaging.CallContext
|
||||
System.Runtime.Remoting.Messaging.ILogicalThreadAffinative
|
||||
System.Runtime.Remoting.Messaging.InternalMessageWrapper
|
||||
System.Runtime.Remoting.Messaging.IMethodCallMessage
|
||||
System.Runtime.Remoting.Messaging.MethodCallMessageWrapper
|
||||
System.Runtime.Remoting.Messaging.HeaderHandler
|
||||
System.Runtime.Remoting.Messaging.IMessageCtrl
|
||||
System.Runtime.Remoting.Messaging.IRemotingFormatter
|
||||
System.Runtime.Remoting.Messaging.ReturnMessage
|
||||
System.Runtime.Remoting.Messaging.MethodCall
|
||||
System.Runtime.Remoting.Messaging.ConstructionCall
|
||||
System.Runtime.Remoting.Messaging.MethodResponse
|
||||
System.Runtime.Remoting.Messaging.ConstructionResponse
|
||||
System.Runtime.Remoting.Messaging.MethodReturnMessageWrapper
|
||||
System.Runtime.Remoting.Messaging.OneWayAttribute
|
||||
System.Runtime.Remoting.Messaging.MessageSurrogateFilter
|
||||
System.Runtime.Remoting.Messaging.RemotingSurrogateSelector
|
||||
System.Runtime.Remoting.Contexts.CrossContextDelegate
|
||||
System.Runtime.Remoting.Contexts.ContextProperty
|
||||
System.Runtime.Remoting.Contexts.IContextPropertyActivator
|
||||
System.Runtime.Remoting.Contexts.IContributeClientContextSink
|
||||
System.Runtime.Remoting.Contexts.IContributeDynamicSink
|
||||
System.Runtime.Remoting.Contexts.IContributeEnvoySink
|
||||
System.Runtime.Remoting.Contexts.IContributeObjectSink
|
||||
System.Runtime.Remoting.Contexts.IContributeServerContextSink
|
||||
System.Runtime.Serialization.Formatters.InternalRM
|
||||
System.Runtime.Serialization.Formatters.InternalST
|
||||
System.Runtime.Serialization.Formatters.SoapMessage
|
||||
System.Runtime.Serialization.Formatters.SoapFault
|
||||
System.Runtime.Serialization.Formatters.ServerFault
|
||||
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
|
||||
System.Security.Cryptography.CryptoConfig
|
||||
System.Security.Cryptography.KeyedHashAlgorithm
|
||||
System.Security.Cryptography.HMACSHA1
|
||||
System.Security.Cryptography.MACTripleDES
|
||||
System.Security.Cryptography.MaskGenerationMethod
|
||||
System.Security.Cryptography.PasswordDeriveBytes
|
||||
System.Security.Cryptography.PKCS1MaskGenerationMethod
|
||||
System.Security.Cryptography.RC2
|
||||
System.Security.Cryptography.RC2CryptoServiceProvider
|
||||
System.Security.Cryptography.RSACryptoServiceProvider
|
||||
System.Security.Cryptography.RSAOAEPKeyExchangeDeformatter
|
||||
System.Security.Cryptography.RSAOAEPKeyExchangeFormatter
|
||||
System.Security.Cryptography.RSAPKCS1KeyExchangeDeformatter
|
||||
System.Security.Cryptography.RSAPKCS1KeyExchangeFormatter
|
||||
System.Security.Cryptography.RSAPKCS1SignatureDeformatter
|
||||
System.Security.Cryptography.RSAPKCS1SignatureFormatter
|
||||
System.Security.Cryptography.SHA1Managed
|
||||
System.Security.Cryptography.TripleDES
|
||||
System.Security.Cryptography.TripleDESCryptoServiceProvider
|
||||
System.Security.Permissions.EnvironmentPermission
|
||||
System.Security.Permissions.FileDialogPermission
|
||||
System.Security.Permissions.IsolatedStorageFilePermission
|
||||
System.Security.Permissions.PrincipalPermissionAttribute
|
||||
System.Security.Permissions.SecurityPermissionAttribute
|
||||
System.Security.Permissions.PublisherIdentityPermissionAttribute
|
||||
System.Security.Permissions.PublisherIdentityPermission
|
||||
System.Security.Permissions.ReflectionPermission
|
||||
System.Security.Permissions.RegistryPermission
|
||||
System.Security.Permissions.PrincipalPermission
|
||||
System.Security.Permissions.SiteIdentityPermission
|
||||
System.Security.Permissions.StrongNameIdentityPermission
|
||||
System.Security.Permissions.StrongNamePublicKeyBlob
|
||||
System.Security.Permissions.UIPermission
|
||||
System.Security.Permissions.UrlIdentityPermission
|
||||
System.Security.Permissions.ZoneIdentityPermission
|
||||
System.Security.Policy.ApplicationDirectory
|
||||
System.Security.Policy.ApplicationDirectoryMembershipCondition
|
||||
System.Security.Policy.FirstMatchCodeGroup
|
||||
System.Security.Policy.Hash
|
||||
System.Security.Policy.HashMembershipCondition
|
||||
System.Security.Policy.NetCodeGroup
|
||||
System.Security.Policy.PermissionRequestEvidence
|
||||
System.Security.Policy.Publisher
|
||||
System.Security.Policy.PublisherMembershipCondition
|
||||
System.Security.Policy.Site
|
||||
System.Security.Policy.SiteMembershipCondition
|
||||
System.Security.Policy.StrongName
|
||||
System.Security.Policy.StrongNameMembershipCondition
|
||||
System.Security.Policy.UnionCodeGroup
|
||||
System.Security.Policy.Url
|
||||
System.Security.Policy.UrlMembershipCondition
|
||||
System.Security.Policy.Zone
|
||||
System.Security.Policy.ZoneMembershipCondition
|
||||
System.Security.Principal.WindowsIdentity
|
||||
System.Security.Principal.WindowsImpersonationContext
|
||||
System.Security.Principal.WindowsPrincipal
|
||||
System.Threading.CompressedStack
|
||||
|
||||
@@ -1,15 +0,0 @@
|
||||
#!/bin/sh
|
||||
|
||||
MANAGED_CALLS=`gdb -silent $1 -pid $2 << EOF | awk '/.* in \?\? \(\)/ {printf("call print_method_from_ip(%s)\n", $2);}'
|
||||
set height 0
|
||||
thread apply all bt
|
||||
quit
|
||||
EOF`
|
||||
|
||||
gdb -silent $1 -pid $2 << EOF
|
||||
set height 0
|
||||
thread apply all bt
|
||||
$MANAGED_CALLS
|
||||
quit
|
||||
EOF
|
||||
|
||||
+7
-33
@@ -18,7 +18,7 @@
|
||||
standard GNOME interfaces for easily creating reusable,
|
||||
language independent components, controls and compound
|
||||
documents. This technology is known as <a
|
||||
href="http://developer.ximian.com/articles/whitepapers/bonobo">Bonobo</a>.
|
||||
href="http://developer.ximian.com/tech/bonobo.html">Bonobo</a>.
|
||||
Interfaces to Bonobo exist for C, Perl, Python, and
|
||||
Java.
|
||||
|
||||
@@ -134,51 +134,25 @@
|
||||
|
||||
** What makes up Mono?
|
||||
|
||||
There are various pieces that make up Mono today:
|
||||
There are various pieces that will make up Mono:
|
||||
|
||||
<ul>
|
||||
* A C# compiler.
|
||||
|
||||
* The Virtual Execution System: that has the
|
||||
* The Virtual Execution System: that will have the
|
||||
Just-in-Time compiler, garbage collector, loader,
|
||||
threading engine.
|
||||
|
||||
A byte code interpreter is provided for quickly
|
||||
A byte code interpreter will be provided for quickly
|
||||
porting Mono to new systems and debugging the JIT
|
||||
purposes, but it is not intended to be the ideal
|
||||
execution environment.
|
||||
|
||||
* An implemenation of the .NET class libraries:
|
||||
Remoting, Reflection, Reflection.Emit, Xml, Xpath,
|
||||
Xslt, Xml Serialization, Web Services support.
|
||||
* An implemenation of the .NET class library.
|
||||
|
||||
* Cross platform class libraries for data access:
|
||||
Postgress, MySQL, DB2, TDS, Sybase, Oracle, ODBC and
|
||||
Gnome's GDA.
|
||||
* Visual development tools.
|
||||
|
||||
* Unix class libraries: Mono.Posix
|
||||
|
||||
* Gnome-specific class libraries: The Gtk# family.
|
||||
|
||||
* A code pre-compiler to generate native code ahead of
|
||||
time.
|
||||
|
||||
* Gtk# a toolkit to develop GNOME applications on Unix
|
||||
and Windows.
|
||||
|
||||
* An implementation of the Remoting infrastructure in
|
||||
.NET
|
||||
</ul>
|
||||
|
||||
Other work-in-progress components:
|
||||
|
||||
<ul>
|
||||
* A VB.NET compiler and JScript compilers are in the works.
|
||||
|
||||
* Web services on the server side.
|
||||
|
||||
* We are planning to include Remoting.CORBA as part of
|
||||
Mono standard distribution.
|
||||
* A CIL GCC frontend.
|
||||
</ul>
|
||||
|
||||
** Why use GNOME components?
|
||||
|
||||
+4
-4
@@ -11,8 +11,8 @@
|
||||
|
||||
The <a href="http://msdn.microsoft.com/net">Microsoft.NET site.</a>
|
||||
|
||||
The Microsoft .NET Framework can be downloaded <a
|
||||
href="http://msdn.microsoft.com/library/default.asp?url=/downloads/list/netdevframework.asp">here</a>
|
||||
The Microsoft .NET Framework 1.0 can be downloaded <a
|
||||
href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true">here</a>
|
||||
|
||||
New methods that are not documented in 1.0, are documented <a
|
||||
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/framewrkaddend.asp">here</a>
|
||||
@@ -87,8 +87,8 @@
|
||||
You can get the documentation for the ECMA specs from:
|
||||
|
||||
<ul>
|
||||
* <a href="http://www.ecma-international.org/publications/standards/ECMA-334.HTM">C# Language Specification</a>
|
||||
* <a href="http://www.ecma-international.org/publications/standards/ECMA-335.HTM">Common Language Infrastructure</a>
|
||||
* <a href="http://www.ecma.ch/ecma1/STAND/ecma-334.htm">C# Language Specification</a>
|
||||
* <a href="http://www.ecma.ch/ecma1/STAND/ecma-335.htm">Common Language Infrastructure</a>
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
+19
-59
@@ -9,14 +9,15 @@
|
||||
We currently have two runtimes:
|
||||
|
||||
<ul>
|
||||
* <b>mono:</b> Our Just-in-Time and Ahead-of-Time code
|
||||
generator for maximum performance.
|
||||
* <b>mono:</b> The Just In Time compiler implemented
|
||||
using a BURS instruction selector. We only support
|
||||
x86 machines in the JIT engine at this point.
|
||||
|
||||
* <b>mint:</b> The Mono interpreter. This is an
|
||||
easy-to-port runtime engine.
|
||||
</ul>
|
||||
|
||||
We are using the Boehm conservative garbage collector.
|
||||
We are using the Bohem conservative garbage collector.
|
||||
|
||||
The Mono runtime can be used as a stand-alone process, or it
|
||||
can be <a href="embedded-api">embedded into applications</a> (see
|
||||
@@ -30,52 +31,12 @@
|
||||
href="http://primates.ximian.com/~lupus/slides/jit/">slides
|
||||
here</a>
|
||||
|
||||
** Current JIT Engine: technical details (<b>updated, June 28th, 2003</b>)
|
||||
** Current JIT Engine: technical details (<b>updated, July 8th, 2002</b>)
|
||||
|
||||
We have re-written our JIT compiler. We wanted to support a
|
||||
number of features that were missing:
|
||||
|
||||
<ul>
|
||||
* Ahead-of-time compilation.
|
||||
|
||||
The idea is to allow developers to pre-compile their code
|
||||
to native code to reduce startup time, and the working
|
||||
set that is used at runtime in the just-in-time compiler.
|
||||
|
||||
Although in Mono this has not been a visible problem, we
|
||||
wanted to pro-actively address this problem.
|
||||
|
||||
When an assembly (a Mono/.NET executable) is installed in
|
||||
the system, it would then be possible to pre-compile the
|
||||
code, and have the JIT compiler tune the generated code
|
||||
to the particular CPU on which the software is
|
||||
installed.
|
||||
|
||||
This is done in the Microsoft.NET world with a tool
|
||||
called ngen.exe
|
||||
|
||||
* Have a good platform for doing code optimizations.
|
||||
|
||||
The design called for a good architecture that would
|
||||
enable various levels of optimizations: some
|
||||
optimizations are better performed on high-level
|
||||
intermediate representations, some on medium-level and
|
||||
some at low-level representations.
|
||||
|
||||
Also it should be possible to conditionally turn these on
|
||||
or off. Some optimizations are too expensive to be used
|
||||
in just-in-time compilation scenarios, but these
|
||||
expensive optimizations can be turned on for
|
||||
ahead-of-time compilations or when using profile-guided
|
||||
optimizations on a subset of the executed methods.
|
||||
|
||||
* Reduce the effort required to port the Mono code
|
||||
generator to new architectures.
|
||||
|
||||
For Mono to gain wide adoption in the Unix world, it is
|
||||
necessary that the JIT engine works in most of today's
|
||||
commercial hardware platforms.
|
||||
</ul>
|
||||
The JIT engine uses a code-generator generator approach for
|
||||
compilation. Given the properties of CIL byte codes, we can
|
||||
take full advantage of a real instruction selector for our
|
||||
code generator.
|
||||
|
||||
The JIT engine implements a number of optimizations:
|
||||
|
||||
@@ -86,7 +47,7 @@
|
||||
|
||||
* Inlining.
|
||||
|
||||
* Constant folding, copy propagation, dead code elimination.
|
||||
* Constant folding.
|
||||
|
||||
Although compilers typically do
|
||||
constant folding, the combination of inlining with
|
||||
@@ -95,9 +56,6 @@
|
||||
* Linear scan register allocation. In the past,
|
||||
register allocation was our achilles heel, but now
|
||||
we have left this problem behind.
|
||||
|
||||
* SSA-based framework. Various optimizations are
|
||||
implemented on top of this framework
|
||||
</ul>
|
||||
|
||||
There are a couple of books that deal with this technique: "A
|
||||
@@ -106,13 +64,7 @@
|
||||
technical description of <a
|
||||
href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/iburg.pdf&pub=ACM">lbrug</a>.
|
||||
|
||||
The new JIT engines uses three intermediate representations:
|
||||
the source is the CIL which is transformed into a forest of
|
||||
trees; This is fed into a BURS instruction selector that
|
||||
generates the final low-level intermediate representation.
|
||||
|
||||
The instruction selector is documented in the following
|
||||
papers:
|
||||
A few papers that describe the instruction selector:
|
||||
|
||||
<ul>
|
||||
* <a href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/interface.pdf&pub=wiley">A code generation interface for ANSI C</a>
|
||||
@@ -122,6 +74,14 @@
|
||||
|
||||
</ul>
|
||||
|
||||
** New JIT engine.
|
||||
|
||||
We are working on a new JIT engine. The new JIT engine
|
||||
focuses on portability and in two intermediate representations
|
||||
that simplify the development of optimizations. This together
|
||||
with the Ahead-of-Time compilation will allow developers to
|
||||
deploy applications that match the speed of natively compiled code.
|
||||
|
||||
** Garbage Collection
|
||||
|
||||
We are using the Boehm conservative GC. We might consider
|
||||
|
||||
+4
-45
@@ -51,14 +51,6 @@
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
** Eclipse running with Mono
|
||||
|
||||
Zoltan Varga made the Java VM for .NET <a
|
||||
href="http://www.ikvm.net">IKVM</a> run <a
|
||||
href="http://www.eclipse.org">Eclipse</a>, the IBM Open Source IDE.
|
||||
|
||||
<a href="images/ikvm-screenshot.png"><img src="images/ikvm-screenshot-thumb.png"></a>
|
||||
|
||||
** Mono Basic
|
||||
|
||||
The Mono Basic compiler ships with the Mono distribution.
|
||||
@@ -135,27 +127,14 @@
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
** Type Reflector
|
||||
** SkyNET
|
||||
|
||||
Type Reflector is a tool included in Mono to inspect your assemblies.
|
||||
SkyNET is written in C# and uses GTK# for displaying a star chart.
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/type-reflector.png">
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
** Object Browser
|
||||
|
||||
Radek Doulik's Object Browser (in Mono CVS) is a useful tool
|
||||
to inspect existing assemblies and their source code:
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/Screenshot-ObjectBrowserDemo.png">
|
||||
<img src="http://go-mono.com/images/skynet.png">
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
@@ -164,14 +143,6 @@
|
||||
|
||||
Windows.Forms running with Wine on Linux:
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
<a href="http://go-mono.com/images/monomdi.jpg"><img src="http://go-mono.com/images/monomdi-thumb.jpg"></a>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
@@ -179,7 +150,7 @@
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
|
||||
** Mono running on the iPaq
|
||||
|
||||
<table border=1>
|
||||
@@ -215,15 +186,3 @@
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
** SkyNET
|
||||
|
||||
SkyNET is written in C# and uses GTK# for displaying a star chart.
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="http://go-mono.com/images/skynet.png">
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
+49
-10
@@ -24,7 +24,7 @@
|
||||
<b>mcs/class/doc/TemplateTest.cs</b>
|
||||
|
||||
Save a copy of this file in the appropriate test subdirecty
|
||||
(see below), and replace all the {text} markers with
|
||||
(see below), and replace all the [text] markers with
|
||||
appropriate code. Comments in the template are there to guide
|
||||
you. You should also look at existing tests to see how other
|
||||
people have written them.
|
||||
@@ -41,22 +41,29 @@
|
||||
the appropriate sub-directory under Test for the class you are
|
||||
testing.
|
||||
|
||||
Once your test class is complete, you need to add it to the
|
||||
AllTests.cs file in the same directory as your new test. Add a
|
||||
call to "suite.AddTest()" passing the name of your new test
|
||||
class's suite property as the parameter. You will see
|
||||
examples in the AllTests.cs file, so just copy and paste
|
||||
inside there.
|
||||
|
||||
Once all of that is done, you can do a 'make test' from the top mcs
|
||||
directory. Your test class will be automagically included in the
|
||||
build and the tests will be run along with all the others.
|
||||
|
||||
* Tips on writing Unit tests.
|
||||
|
||||
You should look at the <a href="http://nunit.org">NUnit documentation</a>,
|
||||
as it is a fantastic product, and includes fantastic documentation,
|
||||
but here are some tips for those of you who are already reading
|
||||
You should look at the NUnit documentation, as it is a
|
||||
fantastic product, and includes fantastic documentation, but
|
||||
here are some tips for those of you who are already reading
|
||||
this web page.
|
||||
|
||||
|
||||
** Provide an unique error message for Assert()
|
||||
|
||||
Include an unique message for each Assert() so that when the assert
|
||||
fails, it is trivial to locate it in the source. Otherwise, it may be
|
||||
fails, it is trivial to locate the failing one. Otherwise, it may be
|
||||
difficult to determine which part of the test is failing. A good way
|
||||
to ensure unique messages is to use something like #A01, #A02 etc.
|
||||
|
||||
@@ -97,10 +104,43 @@
|
||||
AssertEquals ("A01", myTicks[0], t1.Ticks);
|
||||
</pre>
|
||||
|
||||
** Constructors
|
||||
|
||||
When writing your testcase, please make sure to provide a constructor
|
||||
which takes no arguments:
|
||||
|
||||
<pre>
|
||||
public class DateTimeTest : TestCase
|
||||
{
|
||||
|
||||
public DateTimeTest() : base ("[MonoTests.System.DateTimeTest]") {}
|
||||
public DateTimeTest (string name): base(name) {}
|
||||
|
||||
public static ITest Suite
|
||||
{
|
||||
get {
|
||||
TestSuite suite = new TestSuite ();
|
||||
return suite;
|
||||
}
|
||||
}
|
||||
}
|
||||
</pre>
|
||||
|
||||
** Namespace
|
||||
|
||||
Please keep the namespace within each test directory consistent - all
|
||||
tests which are referenced in the same AllTests.cs must be in the same
|
||||
namespace. Of course you can use subnamespaces as you like -
|
||||
especially for subdirectories of your testsuite.
|
||||
|
||||
For instance, if your AllTests.cs is in namespace "MonoTests" and you
|
||||
have a subdirectory called "System", you can put all the tests in that
|
||||
dir into namespace "MonoTests.System".
|
||||
|
||||
** Test your test with the Microsoft runtime
|
||||
|
||||
If possible, try to run your testsuite with the Microsoft runtime on
|
||||
.NET on Windows and make sure all tests in it pass. This is especially
|
||||
Windows and make sure all tests in it pass. This is especially
|
||||
important if you're writing a totally new testcase - without this
|
||||
check you can never be sure that your testcase contains no bugs ....
|
||||
|
||||
@@ -111,10 +151,9 @@
|
||||
result when run with the Microsoft runtime - either because there is a
|
||||
bug in their runtime or something is misleading or wrong in their
|
||||
documentation. In this case, please put a detailed description of the
|
||||
problem to mcs/class/doc/API-notes and do also report it to the
|
||||
<a href="mailing-lists">mailing list</a> - we'll forward this to the
|
||||
Microsoft people from time to time to help them fix their documentation
|
||||
and runtime.
|
||||
problem to mcs/class/doc/API-notes and do also report it to the list -
|
||||
we'll forward this to the Microsoft people from time to time to help
|
||||
them fix their documentation and runtime.
|
||||
|
||||
** Unit tests.
|
||||
|
||||
|
||||
@@ -5,7 +5,6 @@
|
||||
1,Team,team.html,team.src
|
||||
1,Other sites,other.html,other.src
|
||||
1,Old News,oldnews.html,oldnews.src
|
||||
1,Bug Reporting,bugs.html,bugs.src
|
||||
0,Mono,rationale.html,rationale.src
|
||||
1,Runtime,runtime.html,runtime.src
|
||||
2,Embedding,embedded-api.html,embedded-api.src
|
||||
@@ -23,7 +22,6 @@
|
||||
1,Documentation,documentation.html,documentation.src
|
||||
1,Class Docs,classlib-doc.html,classlib-doc.src
|
||||
1,Test Suite,testing.html,testing.src
|
||||
1,Mono TODO,mono-todo.html,mono-todo.src
|
||||
1,Tools,tools.html,tools.src
|
||||
1,Porting,porting.html,porting.src
|
||||
2,PowerPC,ppc.html,ppc.src
|
||||
|
||||
+29
-23
@@ -1,16 +1,12 @@
|
||||
ifeq ($(findstring CYGWIN,$(shell uname)),)
|
||||
CSC=mcs
|
||||
RUN_MONO=mono
|
||||
else
|
||||
CSC=csc /nologo
|
||||
endif
|
||||
ROOT=C:/WINNT
|
||||
CSCRIPT = $(ROOT)/system32/cscript.exe
|
||||
CSC=csc
|
||||
|
||||
CORCOMPARE=../../../mcs/tools/corcompare
|
||||
|
||||
OBJECTS= \
|
||||
deploy/ado-net.html \
|
||||
deploy/bugs.html \
|
||||
deploy/provider-factory.html \
|
||||
deploy/provider-factory.html \
|
||||
deploy/mysql.html \
|
||||
deploy/odbc.html \
|
||||
deploy/oledb.html \
|
||||
@@ -47,7 +43,6 @@ OBJECTS= \
|
||||
deploy/mbas.html \
|
||||
deploy/mono-beginning.html \
|
||||
deploy/mono-contribution-howto.html \
|
||||
deploy/mono-todo.html \
|
||||
deploy/monodoc-xml.html \
|
||||
deploy/other.html \
|
||||
deploy/papers.html \
|
||||
@@ -65,6 +60,20 @@ OBJECTS= \
|
||||
deploy/testing.html \
|
||||
deploy/tools.html \
|
||||
deploy/winforms.html \
|
||||
deploy/class-status.html \
|
||||
deploy/class-status-corlib.html \
|
||||
deploy/class-status-System.html \
|
||||
deploy/class-status-System.Xml.html \
|
||||
deploy/class-status-System.Drawing.html \
|
||||
deploy/class-status-System.Data.html \
|
||||
deploy/class-status-System.Web.html \
|
||||
deploy/class-status-System.Web.Services.html \
|
||||
deploy/class-status-Microsoft.VisualBasic.html \
|
||||
deploy/class-status-System.EnterpriseServices.html \
|
||||
deploy/class-status-System.Runtime.Serialization.Formatters.Soap.html \
|
||||
deploy/class-status-System.Security.html \
|
||||
deploy/class-status-System.Windows.Forms.html \
|
||||
deploy/class-status-Cscompmgd.html \
|
||||
deploy/class-library.html \
|
||||
deploy/classlib-doc.html
|
||||
|
||||
@@ -78,7 +87,7 @@ NON_HTML_SOURCES= \
|
||||
../mono-build.sh \
|
||||
../mono-build-w32.sh
|
||||
|
||||
all: $(OBJECT) deploy/index.rss ../team
|
||||
all: $(OBJECTS) deploy/index.rss ../team
|
||||
perl process.pl commands template.html.in deploy
|
||||
-mkdir deploy/team
|
||||
cp team/*png deploy/team
|
||||
@@ -97,13 +106,13 @@ mono-beginning.xml: ../mono-beginning.xml
|
||||
cp ../mono-beginning.xml .
|
||||
|
||||
deploy/index.rss: mono-rss.exe ../index
|
||||
$(RUN_MONO) ./mono-rss.exe ../index deploy/index.rss
|
||||
./mono-rss.exe ../index deploy/index.rss
|
||||
|
||||
mono-rss.exe: mono-rss.cs rss.cs
|
||||
$(CSC) mono-rss.cs rss.cs
|
||||
|
||||
../team: render-team-page.exe team.xml
|
||||
$(RUN_MONO) ./render-team-page.exe team.xml "../team"
|
||||
./render-team-page.exe team.xml "../team"
|
||||
|
||||
render-team-page.exe: render-team-page.cs
|
||||
$(CSC) render-team-page.cs
|
||||
@@ -113,9 +122,8 @@ clean:
|
||||
|
||||
push:
|
||||
cp -f $(NON_HTML_SOURCES) deploy
|
||||
#echo scp -P 2200 -r deploy/* www@www.go-mono.com:/web/cvsmodules/mono
|
||||
#(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . www@www.go-mono.com:/web/cvsmodules/mono )
|
||||
(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . [email protected]:/web/cvsmodules/mono )
|
||||
echo scp -P 2200 -r deploy/* www@www.ximian.com:/web/cvsmodules/mono
|
||||
(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh -p 2200' . www@www.ximian.com:/web/cvsmodules/mono )
|
||||
|
||||
push2:
|
||||
scp -r deploy/* primates:public_html/xxx
|
||||
@@ -124,12 +132,10 @@ $(OBJECTS): $(patsubst deploy/%.html,src/%.src, $(OBJECTS))
|
||||
|
||||
#.PRECIOUS: $(patsubst deploy/%.html,src/%.src, $(OBJECTS))
|
||||
|
||||
transform.exe: transform.cs
|
||||
$(CSC) transform.cs
|
||||
|
||||
|
||||
.PRECIOUS: src/%.src
|
||||
src/%.src: ../% commands template.html.in makefile
|
||||
src/%.src: ../% commands makefile template.html.in
|
||||
perl htmlify $< > $@
|
||||
|
||||
.PRECIOUS: ../class-status-%
|
||||
@@ -138,20 +144,20 @@ src/%.src: ../% commands template.html.in makefile
|
||||
|
||||
|
||||
.PRECIOUS: src/%.html.in
|
||||
src/%.html.in: src/%.xml transform.exe $(CORCOMPARE)/cormissing.xsl
|
||||
$(RUN_MONO) ./transform.exe $< $(CORCOMPARE)/cormissing.xsl > $@
|
||||
src/%.html.in: src/%.xml $(CORCOMPARE)/transform.js $(CORCOMPARE)/cormissing.xsl
|
||||
$(CSCRIPT) /nologo $(CORCOMPARE)/transform.js $< $(CORCOMPARE)/cormissing.xsl > $@
|
||||
|
||||
|
||||
|
||||
.PRECIOUS: src/%.xml
|
||||
src/%.xml: ../../../mcs/class/lib/%.dll $(CORCOMPARE)/CorCompare.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/CorCompare.exe -x $@ $<
|
||||
$(CORCOMPARE)/CorCompare.exe -x $@ $<
|
||||
|
||||
src/corlib.xml: ../../../mcs/class/lib/corlib_cmp.dll $(CORCOMPARE)/CorCompare.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/CorCompare.exe -f corlib -ms mscorlib -x $@ $<
|
||||
$(CORCOMPARE)/CorCompare.exe -f corlib -ms mscorlib -x $@ $<
|
||||
|
||||
src/System.Security.xml: ../../../mcs/class/lib/System.Security_cmp.dll $(CORCOMPARE)/CorCompare.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/CorCompare.exe -f System.Security -ms System.Security -x $@ $<
|
||||
$(CORCOMPARE)/CorCompare.exe -f System.Security -ms System.Security -x $@ $<
|
||||
|
||||
../class-status: ../class-status.in
|
||||
cp -f $< $@
|
||||
|
||||
+2
-11
@@ -6,21 +6,18 @@
|
||||
using System;
|
||||
using System.IO;
|
||||
using System.Xml;
|
||||
using System.Text;
|
||||
using RSS;
|
||||
|
||||
class X {
|
||||
static RSS.RSS rss;
|
||||
static Channel c;
|
||||
static int item_count;
|
||||
static int line;
|
||||
|
||||
|
||||
static void PopulateRSS (StreamReader input)
|
||||
{
|
||||
string s;
|
||||
|
||||
while ((s = input.ReadLine ()) != null){
|
||||
line++;
|
||||
if (s.StartsWith ("@item "))
|
||||
break;
|
||||
}
|
||||
@@ -55,7 +52,6 @@ class X {
|
||||
} else {
|
||||
description += "\n" + (s == "\n" ? "<p>" : s);
|
||||
}
|
||||
line++;
|
||||
} while ((s = input.ReadLine ()) != null);
|
||||
|
||||
if (i != null){
|
||||
@@ -80,12 +76,7 @@ class X {
|
||||
|
||||
using (FileStream fs = new FileStream (input, FileMode.Open)){
|
||||
using (StreamReader input_stream = new StreamReader (fs)){
|
||||
try {
|
||||
PopulateRSS (input_stream);
|
||||
} catch {
|
||||
Console.WriteLine ("{0} failure while loading: {1}", line, input);
|
||||
throw;
|
||||
}
|
||||
PopulateRSS (input_stream);
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
+11
-97
@@ -12,34 +12,6 @@
|
||||
|
||||
<contributors xmlns="http://go-mono.org/team.xsd">
|
||||
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>Joel</first-name>
|
||||
|
||||
<last-name>Basson</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Cape Town, South Africa</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>External Contributor</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>System.Windows.Forms Gtk</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
@@ -312,7 +284,7 @@
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<location>Honolulu, Hawai`i</location>
|
||||
<location>Kansas City</location>
|
||||
|
||||
<tasks>
|
||||
|
||||
@@ -454,9 +426,9 @@
|
||||
|
||||
<task>NUnit1 -> NUnit2 conversion</task>
|
||||
|
||||
<task>Mono Handbook, Documentation</task>
|
||||
<task>Stubbing</task>
|
||||
|
||||
<task>DiaCanvas#</task>
|
||||
<task>Mono Handbook work</task>
|
||||
|
||||
<task>Various fixes</task>
|
||||
|
||||
@@ -858,13 +830,13 @@
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>jonpryor.png</image>
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Richmond, Virginia</location>
|
||||
<location>Blacksburg, Virginia</location>
|
||||
|
||||
<organization>Cadmus Professional Communications</organization>
|
||||
<organization>Virginia Tech</organization>
|
||||
|
||||
<description>Mono Hacker</description>
|
||||
<description>Graduate Student</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
@@ -915,13 +887,13 @@
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>justdandy43@hotmail.com</e-mail>
|
||||
<e-mail>[email protected].com</e-mail>
|
||||
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Richmond, Virginia, USA</location>
|
||||
<location>Columbia, South Carolina, USA</location>
|
||||
|
||||
<organization>an insurance company</organization>
|
||||
<organization>Unemployed</organization>
|
||||
|
||||
<description>Mono hacker</description>
|
||||
|
||||
@@ -983,7 +955,7 @@
|
||||
|
||||
<image>none.png</image>
|
||||
|
||||
<location>São Paulo</location>
|
||||
<location>São Paulo</location>
|
||||
|
||||
<organization>WEBforAll.</organization>
|
||||
|
||||
@@ -1410,62 +1382,4 @@
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>John</first-name>
|
||||
|
||||
<last-name>Luke</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Daytona, FL</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>Contributor.</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>Documentation.</task>
|
||||
|
||||
<task>Monodoc.</task>
|
||||
|
||||
<task>Gtk#</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>Peter</first-name>
|
||||
|
||||
<last-name>Williams</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>peterw.png</image>
|
||||
|
||||
<location>Cambridge, MA</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>Makefile Magician</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>MCS build system </task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
</contributors>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 4.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.8 KiB |
@@ -15,7 +15,6 @@
|
||||
.navi0 { font-size: 14px; font-weight: bold; background: #444444; }
|
||||
.navi1 { font-size: 14px; font-weight: bold; left-margin: 10pt}
|
||||
.navi2 { font-size: 10px; font-weight: bold; left-margin: 20pt}
|
||||
.topmenu { font-size: 14px; font-weight: bold; }
|
||||
.footnote { font-size: 12px; color: #aaaaaa; }
|
||||
|
||||
a.navi0 { color: #ffffff; text-decoration: none}
|
||||
@@ -30,10 +29,6 @@
|
||||
a.navi2:visited { color: #cccccc; }
|
||||
a.navi2:hover { color: #ee9900; text-decoration: underline; }
|
||||
|
||||
a.topmenu { color: #ffffff; text-decoration: none; margin-left: 7px;}
|
||||
a.topmenu:visited { color: #cccccc; }
|
||||
a.topmenu:hover { color: #ee9900; text-decoration: underline; }
|
||||
|
||||
// -->
|
||||
</style>
|
||||
#CSS#
|
||||
@@ -43,27 +38,11 @@
|
||||
|
||||
<table cellpadding="0" cellspacing="0" border="0" width="100%">
|
||||
<tr>
|
||||
<td><img src="images/pixel.gif" alt=""></td><!-- left border
|
||||
-->
|
||||
<td colspan="4">
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<a href="http://www.go-mono.com"><img
|
||||
src="images/mono-new.gif" alt="mono-logo" border="0"></a>
|
||||
</td>
|
||||
<td>
|
||||
<a class="topmenu" href="download.html">Downloads</a> |
|
||||
<a class="topmenu" href="http://go-mono.com/daily">Daily snapshots</a> |
|
||||
<a class="topmenu" href="screenshots.html">Screenshots</a> |
|
||||
<a class="topmenu" href="http://www.go-mono.com:8080">Documentation</a> |
|
||||
<a class="topmenu" href="bugs.html">Bugs</a>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
<td><img src="images/pixel.gif" alt=""></td><!-- right border
|
||||
-->
|
||||
<td><img src="images/pixel.gif" alt=""></td><!-- left border -->
|
||||
<td colspan="4">
|
||||
<a href="http://www.go-mono.com"><img src="images/mono-new.gif"
|
||||
alt="mono-logo" border="0"></a></td>
|
||||
<td><img src="images/pixel.gif" alt=""></td><!-- right border -->
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/pixel.gif" width="1" height="1" alt=""></td>
|
||||
|
||||
@@ -1,20 +0,0 @@
|
||||
using System;
|
||||
using System.Xml;
|
||||
using System.Xml.Xsl;
|
||||
|
||||
namespace Transform
|
||||
{
|
||||
class Transform
|
||||
{
|
||||
public static void Main (string [] rgstrArgs)
|
||||
{
|
||||
XmlDocument xml = new XmlDocument ();
|
||||
xml.Load (rgstrArgs [0]);
|
||||
|
||||
XslTransform xsl = new XslTransform ();
|
||||
xsl.Load (rgstrArgs [1]);
|
||||
|
||||
xsl.Transform (xml, null, Console.Out);
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -27,14 +27,6 @@
|
||||
|
||||
* Win32/Wine edition.
|
||||
|
||||
To get the Windows.Forms support working, you need a Mono
|
||||
installation from CVS, and you need to install Wine plus the
|
||||
<a href="http://www.openlinksw.com">OpenLink patch</a>, and
|
||||
define the environment variable "SWF" (export SWF=1 from your
|
||||
shell). For more information, see the <a
|
||||
href="http://www.nullenvoid.com/mono/wiki/index.php/MonoWinePackages">Mono
|
||||
Wine Packages</a> page in the Mono Wiki.
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
|
||||
+1
-2
@@ -1,4 +1,3 @@
|
||||
EXTRA_DIST = gc-issues jit-thoughts object-layout unmanaged-calls \
|
||||
exceptions jit-trampolines stack-alignment embedded-api \
|
||||
assembly-bundle
|
||||
exceptions jit-trampolines stack-alignment embedded-api
|
||||
|
||||
@@ -1,42 +0,0 @@
|
||||
|
||||
HOWTO bundle assemblies inside the mono runtime.
|
||||
|
||||
Bundling assemblies inside the mono runtime may be useful for a number
|
||||
of reasons:
|
||||
* creating a standalone complete runtime that can be more easily
|
||||
distributed
|
||||
* having an application run against a known set of assemblies
|
||||
that has been tested
|
||||
|
||||
Of course, there are drawbacks, too: if there has been fixes to the assemblies,
|
||||
replacing them means recompiling the runtime as well and if there are other mono apps,
|
||||
unless they use the same mono binary, there will be less opportunities for
|
||||
the operating system to optimize memory usage. So use this feature only
|
||||
when really needed.
|
||||
|
||||
To bundle a set of assemblies, you need to create a file that lists the assembly
|
||||
names and the relative files. Empty lines and lines starting with # are ignored:
|
||||
|
||||
== cut cut ==
|
||||
# Sample bundle template
|
||||
mscorlib: /path/to/mscorlib/assembly.dll
|
||||
myapp: /path/to/myapp.exe
|
||||
== cut cut ==
|
||||
|
||||
Next you need to build the mono runtime using a special configure option:
|
||||
|
||||
./configure --with-bundle=/path/to/bundle/template
|
||||
|
||||
The path to the template should be an absolute path.
|
||||
|
||||
The script metadata/make-bundle.pl will take the specifie assemblies and embed
|
||||
them inside the runtime where the loading routines can find them before
|
||||
searching for them on disk.
|
||||
|
||||
There are still two issues to solve:
|
||||
* config files: sometimes they are needed but they are not yet bundled
|
||||
inside the library ()
|
||||
* building with the included libgc makes it not possible to build a mono
|
||||
binary statically linked to libmono: this needs to be fixed to make bundles
|
||||
really useful
|
||||
|
||||
+11
-12
@@ -56,20 +56,19 @@ leave: is simply translated into a branch to the target. If the leave
|
||||
instruction is inside a finally block (but not inside another handler)
|
||||
we call the finally handler before we branch to the target.
|
||||
|
||||
finally/endfinally, filter/endfilter: is translated into subroutine ending with
|
||||
a "return" statement. The subroutine does not save EBP, because we need access
|
||||
to the local variables of the enclosing method. Its is possible that
|
||||
instructions inside those handlers modify the stack pointer, thus we save the
|
||||
stack pointer at the start of the handler, and restore it at the end. We have
|
||||
to use a "call" instruction to execute such finally handlers. This makes it
|
||||
also possible to execute them inside the stack unwinding code. The exception
|
||||
object for filters is passed in a local variable (cfg->exvar).
|
||||
finally/endfinally: is translated into subroutine ending with a "return"
|
||||
statement. The subroutine does not save EBP/ESP, because we need access to the
|
||||
local variables of the enclosing method. We have to use a "call"
|
||||
instruction to execute such finally handlers. This makes it possible to
|
||||
execute them inside the stack unwinding code.
|
||||
|
||||
throw: we first save all regs into a sigcontext struct and then call the stack
|
||||
unwinding code.
|
||||
throw: we first save all regs into a sigcontext struct (we pass the
|
||||
exception object in register ECX), and then call the stack unwinding
|
||||
code.
|
||||
|
||||
catch handler: receives the exception object in ECX. They store that
|
||||
object into a local variable, so that rethrow can access the object.
|
||||
|
||||
catch handler: catch hanlders are always called from the stack unwinding
|
||||
code. The exception object is passed in a local variable (cfg->exvar).
|
||||
|
||||
gcc support for Exceptions
|
||||
==========================
|
||||
|
||||
@@ -1,349 +0,0 @@
|
||||
Mono JIT porting guide.
|
||||
Paolo Molaro ([email protected])
|
||||
|
||||
* Introduction
|
||||
|
||||
This documents describes the process of porting the mono JIT
|
||||
to a new CPU architecture. The new mono JIT has been designed
|
||||
to make porting easier though at the same time enable the port
|
||||
to take full advantage from the new architecture features and
|
||||
instructions. Knowledge of the mini architecture (described in the
|
||||
mini-doc.txt file) is a requirement for understanding this guide,
|
||||
as well as an earlier document about porting the mono interpreter
|
||||
(available on the web site).
|
||||
|
||||
There are six main areas that a port needs to implement to
|
||||
have a fully-functional JIT for a given architecture:
|
||||
|
||||
1) instruction selection
|
||||
2) native code emission
|
||||
3) call conventions and register allocation
|
||||
4) method trampolines
|
||||
5) exception handling
|
||||
6) minor helper methods
|
||||
|
||||
To take advantage of some not-so-common processor features (for example
|
||||
conditional execution of instructions as may be found on ARM or ia64), it may
|
||||
be needed to develop an high-level optimization, but doing so is not a
|
||||
requirement for getting the JIT to work.
|
||||
|
||||
We'll see in more details each of the steps required, note, though,
|
||||
that a new port may just as well start from a cut&paste of an existing
|
||||
port to a similar architecture (for example from x86 to amd64, or from
|
||||
powerpc to sparc).
|
||||
The architecture specific code is split from the rest of the JIT,
|
||||
for example the x86 specific code and data is all included in the
|
||||
following files in the distribution:
|
||||
|
||||
mini-x86.h mini-x86.c
|
||||
inssel-x86.brg
|
||||
cpu-pentium.md
|
||||
tramp-x86.c
|
||||
exceptions-x86.c
|
||||
|
||||
I suggest a similar split for other architectures as well.
|
||||
|
||||
Note that this document is still incomplete: some sections are only
|
||||
sketched and some are missing, but the important info to get a port
|
||||
going is already described.
|
||||
|
||||
|
||||
* Architecture-specific instructions and instruction selection.
|
||||
|
||||
The JIT already provides a set of instructions that can be easily
|
||||
mapped to a great variety of different processor instructions.
|
||||
Sometimes it may be necessary or advisable to add a new instruction
|
||||
that represent more closely an instruction in the architecture.
|
||||
Note that a mini instruction can be used to represent also a short
|
||||
sequence of CPU low-level instructions, but note that each
|
||||
instruction represents the minimum amount of code the instruction
|
||||
scheduler will handle (i.e., the scheduler won't schedule the instructions
|
||||
that compose the low-level sequence as individual instructions, but just
|
||||
the whole sequence, as an indivisible block).
|
||||
New instructions are created by adding a line in the mini-ops.h file,
|
||||
assigning an opcode and a name. To specify the input and output for
|
||||
the instruction, there are two different places, depending on the context
|
||||
in which the instruction gets used.
|
||||
If the instruction is used in the tree representation, the input and output
|
||||
types are defined by the BURG rules in the *.brg files (the usual
|
||||
non-terminals are 'reg' to represent a normal register, 'lreg' to
|
||||
represent a register or two that hold a 64 bit value, freg for a
|
||||
floating point register).
|
||||
If an instruction is used as a low-level CPU instruction, the info
|
||||
is specified in a machine description file. The description file is
|
||||
processed by the genmdesc program to provide a data structure that
|
||||
can be easily used from C code to query the needed info about the
|
||||
instruction.
|
||||
As an example, let's consider the add instruction for both x86 and ppc:
|
||||
|
||||
x86 version:
|
||||
add: dest:i src1:i src2:i len:2 clob:1
|
||||
ppc version:
|
||||
add: dest:i src1:i src2:i len:4
|
||||
|
||||
Note that the instruction takes two input integer registers on both CPU,
|
||||
but on x86 the first source register is clobbered (clob:1) and the length
|
||||
in bytes of the instruction differs.
|
||||
Note that integer adds and floating point adds use different opcodes, unlike
|
||||
the IL language (64 bit add is done with two instructions on 32 bit architectures,
|
||||
using a add that sets the carry and an add with carry).
|
||||
A specific CPU port may assign any meaning to the clob field for an instruction
|
||||
since the value will be processed in an arch-specific file anyway.
|
||||
See the top of the existing cpu-pentium.md file for more info on other fields:
|
||||
the info may or may not be applicable to a different CPU, in this latter case
|
||||
the info can be ignored.
|
||||
The code in mini.c together with the BURG rules in inssel.brg, inssel-float.brg
|
||||
and inssel-long32.brg provides general purpose mappings from the tree representation
|
||||
to a set of instructions that should be easily implemented in any architecture.
|
||||
To allow for additional arch-specific functionality, an arch-specific BURG file
|
||||
can be used: in this file arch-specific instructions can be selected that provide
|
||||
better performance than the general instructions or that provide functionality
|
||||
that is needed by the JIT but that cannot be expressed in a general enough way.
|
||||
As an example, x86 has the special instruction "push" to make it easier to
|
||||
implement the default call convention (passing arguments on the stack): almost
|
||||
all the other architectures don't have such an instruction (and don't need it anyway),
|
||||
so we added a special rule in the inssel-x86.brg file for it.
|
||||
|
||||
So, one of the first things needed in a port is to write a cpu-$(arch).md machine
|
||||
description file and fill it with the needed info. As a start, only a few
|
||||
instructions can be specified, like the ones required to do simple integer
|
||||
operations. The default rules of the instruction selector will emit the common
|
||||
instructions and so we're ready to go for the next step in porting the JIT.
|
||||
|
||||
|
||||
*) Native code emission
|
||||
|
||||
Since the first step in porting mono to a new CPU is to port the interpreter,
|
||||
there should be already a file that allows the emission of binary native code
|
||||
in a buffer for the architecture. This file should be placed in the
|
||||
mono/arch/$(arch)/
|
||||
directory.
|
||||
|
||||
The bulk of the code emission happens in the mini-$(arch).c file, in a function
|
||||
called mono_arch_output_basic_block (). This function takes a basic block, walks the
|
||||
list of instructions in the block and emits the binary code for each.
|
||||
Optionally a peephole optimization pass is done on the basic block, but this can be
|
||||
left for later, when the port actually works.
|
||||
This function is very simple, there is just a big switch on the instruction opcode
|
||||
and in the corresponding case the functions or macros to emit the binary native code
|
||||
are used. Note that in this function the lengths of the instructions are used to
|
||||
determine if the buffer for the code needs enlarging.
|
||||
|
||||
To complete the code emission for a method, a few other functions need
|
||||
implementing as well:
|
||||
|
||||
mono_arch_emit_prolog ()
|
||||
mono_arch_emit_epilog ()
|
||||
mono_arch_patch_code ()
|
||||
|
||||
mono_arch_emit_prolog () will emit the code to setup the stack frame for a method,
|
||||
optionally call the callbacks used in profiling and tracing, and move the
|
||||
arguments to their home location (in a caller-save register if the variable was
|
||||
allocated to one, or in a stack location if the argument was passed in a volatile
|
||||
register and wasn't allocated a non-volatile one). caller-save registers used by the
|
||||
function are saved in the prolog as well.
|
||||
|
||||
mono_arch_emit_epilog () will emit the code needed to return from the function,
|
||||
optionally calling the profiling or tracing callbacks. At this point the basic blocks
|
||||
or the code that was moved out of the normal flow for the function can be emitted
|
||||
as well (this is usually done to provide better info for the static branch predictor).
|
||||
In the epilog, caller-save registers are restored if they were used.
|
||||
Note that, to help exception handling and stack unwinding, when there is a transition
|
||||
from managed to unmanaged code, some special processing needs to be done (basically,
|
||||
saving all the registers and setting up the links in the Last Managed Frame
|
||||
structure).
|
||||
|
||||
When the epilog has been emitted, the upper level code arranges for the buffer of
|
||||
memory that contains the native code to be copied in an area of executable memory
|
||||
and at this point, instructions that use relative addressing need to be patched
|
||||
to have the right offsets: this work is done by mono_arch_patch_code ().
|
||||
|
||||
|
||||
* Call conventions and register allocation
|
||||
|
||||
To account for the differences in the call conventions, a few functions need to
|
||||
be implemented.
|
||||
|
||||
mono_arch_allocate_vars () assigns to both arguments and local variables
|
||||
the offset relative to the frame register where they are stored, dead
|
||||
variables are simply discarded. The total amount of stack needed is calculated.
|
||||
|
||||
mono_arch_call_opcode () is the function that more closely deals with the call
|
||||
convention on a given system. For each argument to a function call, an instruction
|
||||
is created that actually puts the argument where needed, be it the stack or a
|
||||
specific register. This function can also re-arrange th order of evaluation
|
||||
when multiple arguments are involved if needed (like, on x86 arguments are pushed
|
||||
on the stack in reverse order). The function needs to carefully take into accounts
|
||||
platform specific issues, like how structures are returned as well as the
|
||||
differences in size and/or alignment of managed and corresponding unmanaged
|
||||
structures.
|
||||
|
||||
The other chunk of code that needs to deal with the call convention and other
|
||||
specifics of a CPU, is the local register allocator, implemented in a function
|
||||
named mono_arch_local_regalloc (). The local allocator deals with a basic block
|
||||
at a time and basically just allocates registers for temporary
|
||||
values during expression evaluation, spilling and unspilling as necessary.
|
||||
The local allocator needs to take into account clobbering information, both
|
||||
during simple instructions and during function calls and it needs to deal
|
||||
with other architecture-specific weirdnesses, like instructions that take
|
||||
inputs only in specific registers or output only is some.
|
||||
Some effort will be put later in moving most of the local register allocator to
|
||||
a common file so that the code can be shared more for similar, risc-like CPUs.
|
||||
The register allocator does a first pass on the instructions in a block, collecting
|
||||
liveness information and in a backward pass on the same list performs the
|
||||
actual register allocation, inserting the instructions needed to spill values,
|
||||
if necessary.
|
||||
|
||||
When this part of code is implemented, some testing can be done with the generated
|
||||
code for the new architecture. Most helpful is the use of the --regression
|
||||
command line switch to run the regression tests (basic.cs, for example).
|
||||
Note that the JIT will try to initialize the runtime, but it may not be able yet to
|
||||
compile and execute complex code: commenting most of the code in the mini_init()
|
||||
function in mini.c is needed to let the JIT just compile the regression tests.
|
||||
Also, using multiple -v switches on the command line makes the JIT dump an
|
||||
increasing amount of information during compilation.
|
||||
|
||||
|
||||
* Method trampolines
|
||||
|
||||
To get better startup performance, the JIT actually compiles a method only when
|
||||
needed. To achieve this, when a call to a method is compiled, we actually emit a
|
||||
call to a magic trampoline. The magic trampoline is a function written in assembly
|
||||
that invokes the compiler to compile the given method and jumps to the newly compiled
|
||||
code, ensuring the arguments it received are passed correctly to the actual method.
|
||||
Before jumping to the new code, though, the magic trampoline takes care of patching
|
||||
the call site so that next time the call will go directly to the method instead of the
|
||||
trampoline. How does this all work?
|
||||
mono_arch_create_jit_trampoline () creates a small function that just
|
||||
preserves the arguments passed to it and adds an additional argument (the method
|
||||
to compile) before calling the generic trampoline. This small function is called
|
||||
the specific trampoline, because it is method-specific (the method to compile
|
||||
is hard-code in the instruction stream).
|
||||
The generic trampoline saves all the arguments that could get clobbered
|
||||
and calls a C function that will do two things:
|
||||
|
||||
*) actually call the JIT to compile the method
|
||||
*) identify the calling code so that it can be patched to call directly
|
||||
the actual method
|
||||
|
||||
If the 'this' argument to a method is a boxed valuetype that is passed to
|
||||
a method that expects just a pointer to the data, an additional unboxing
|
||||
trampoline will need to be inserted as well.
|
||||
|
||||
|
||||
* Exception handling
|
||||
|
||||
Exception handling is likely the most difficult part of the port, as it needs
|
||||
to deal with unwinding (both managed and unmanaged code) and calling
|
||||
catch and filter blocks. It also needs to deal with signals, because mono
|
||||
takes advantage of the MMU in the CPU and of the operation system to
|
||||
handle dereferences of the NULL pointer. Some of the function needed
|
||||
to implement the mechanisms are:
|
||||
|
||||
mono_arch_get_throw_exception () returns a function that takes an exception object
|
||||
and invokes an arch-specific function that will enter the exception processing.
|
||||
To do so, all the relevant registers need to be saved and passed on.
|
||||
|
||||
mono_arch_handle_exception () this function takes the exception thrown and
|
||||
a context that describes the state of the CPU at the time the exception was
|
||||
thrown. The function needs to implement the exception handling mechanism,
|
||||
so it makes a search for an handler for the exception and if none is found,
|
||||
it follows the unhandled exception path (that can print a trace and exit or
|
||||
just abort the current thread). The difficulty here is to unwind the stack
|
||||
correctly, by restoring the register state at each call site in the call chain,
|
||||
calling finally, filters and handler blocks while doing so.
|
||||
|
||||
As part of exception handling a couple of internal calls need to be implemented
|
||||
as well.
|
||||
ves_icall_get_frame_info () returns info about a specific frame.
|
||||
mono_jit_walk_stack () walks the stack and calls a callback with info for
|
||||
each frame found.
|
||||
ves_icall_get_trace () return an array of StackFrame objects.
|
||||
|
||||
** Code generation for filter/finally handlers
|
||||
|
||||
Filter and finally handlers are called from 2 different locations:
|
||||
|
||||
1.) from within the method containing the exception clauses
|
||||
2.) from the stack unwinding code
|
||||
|
||||
To make this possible we implement them like subroutines, ending with a
|
||||
"return" statement. The subroutine does not save the base pointer, because we
|
||||
need access to the local variables of the enclosing method. Its is possible
|
||||
that instructions inside those handlers modify the stack pointer, thus we save
|
||||
the stack pointer at the start of the handler, and restore it at the end. We
|
||||
have to use a "call" instruction to execute such finally handlers.
|
||||
|
||||
The MIR code for filter and finally handlers looks like:
|
||||
|
||||
OP_START_HANDLER
|
||||
...
|
||||
OP_END_FINALLY | OP_ENDFILTER(reg)
|
||||
|
||||
OP_START_HANDLER: should save the stack pointer somewhere
|
||||
OP_END_FINALLY: restores the stack pointers and returns.
|
||||
OP_ENDFILTER (reg): restores the stack pointers and returns the value in "reg".
|
||||
|
||||
** Calling finally/filter handlers
|
||||
|
||||
There is a special opcode to call those handler, its called OP_CALL_HANDLER. It
|
||||
simple emits a call instruction.
|
||||
|
||||
Its a bit more complex to call handler from outside (in the stack unwinding
|
||||
code), because we have to restore the whole context of the method first. After that
|
||||
we simply emit a call instruction to invoke the handler. Its usually
|
||||
possible to use the same code to call filter and finally handlers (see
|
||||
arch_get_call_filter).
|
||||
|
||||
** Calling catch handlers
|
||||
|
||||
Catch handlers are always called from the stack unwinding code. Unlike finally clauses
|
||||
or filters, catch handler never return. Instead we simply restore the whole
|
||||
context, and restart execution at the catch handler.
|
||||
|
||||
** Passing Exception objects to catch handlers and filters.
|
||||
|
||||
We use a local variable to store exception objects. The stack unwinding code
|
||||
must store the exception object into this variable before calling catch handler
|
||||
or filter.
|
||||
|
||||
* Minor helper methods
|
||||
|
||||
A few minor helper methods are referenced from the arch-independent code.
|
||||
Some of them are:
|
||||
|
||||
*) mono_arch_cpu_optimizations ()
|
||||
This function returns a mask of optimizations that should be enabled for the
|
||||
current CPU and a mask of optimizations that should be excluded, instead.
|
||||
|
||||
*) mono_arch_regname ()
|
||||
Returns the name for a numeric register.
|
||||
|
||||
*) mono_arch_get_allocatable_int_vars ()
|
||||
Returns a list of variables that can be allocated to the integer registers
|
||||
in the current architecture.
|
||||
|
||||
*) mono_arch_get_global_int_regs ()
|
||||
Returns a list of caller-save registers that can be used to allocate variables
|
||||
in the current method.
|
||||
|
||||
*) mono_arch_instrument_mem_needs ()
|
||||
*) mono_arch_instrument_prolog ()
|
||||
*) mono_arch_instrument_epilog ()
|
||||
Functions needed to implement the profiling interface.
|
||||
|
||||
|
||||
* Writing regression tests
|
||||
|
||||
Regression tests for the JIT should be written for any bug found in the JIT
|
||||
in one of the *.cs files in the mini directory. Eventually all the operations
|
||||
of the JIT should be tested (including the ones that get selected only when
|
||||
some specific optimization is enabled).
|
||||
|
||||
|
||||
* Platform specific optimizations
|
||||
|
||||
An example of a platform-specific optimization is the peephole optimization:
|
||||
we look at a small window of code at a time and we replace one or more
|
||||
instructions with others that perform better for the given architecture or CPU.
|
||||
|
||||
@@ -1,88 +0,0 @@
|
||||
.\"
|
||||
.\" makecert manual page.
|
||||
.\" Copyright 2003 Motus Technologies
|
||||
.\" Author:
|
||||
.\" Sebastien Pouliot ([email protected])
|
||||
.\"
|
||||
.TH Mono "MakeCert"
|
||||
.SH NAME
|
||||
MakeCert \- Create X.509 certificates for test purposes
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B MakeCert [options] certificate
|
||||
.SH DESCRIPTION
|
||||
Create an X.509 certificate using the provided informations. This
|
||||
is useful for testing Authenticode signatures, SSL and S/MIME
|
||||
technologies.
|
||||
.SH PARAMETERS
|
||||
.TP
|
||||
.I "-# num"
|
||||
Certificate serial number
|
||||
.TP
|
||||
.I "-n dn"
|
||||
Subject Distinguished Name
|
||||
.TP
|
||||
.I "-in dn"
|
||||
Issuert Distinguished Name
|
||||
.TP
|
||||
.I "-r"
|
||||
Create a self-signed (root) certificate
|
||||
.TP
|
||||
.I "-sv pkvfile"
|
||||
Private key file (.PVK) for the subject (created if missing)
|
||||
.TP
|
||||
.I "-iv pvkfile"
|
||||
Private key file (.PVK) for the issuer
|
||||
.TP
|
||||
.I "-ic certfile"
|
||||
Extract the issuer's name from the specified certificate
|
||||
.TP
|
||||
.I "-?"
|
||||
Help (display this help message)
|
||||
.TP
|
||||
.I "-!"
|
||||
Extended help (for advanced options)
|
||||
.TP
|
||||
.I "-a hash"
|
||||
Select hash algorithm. Only MD5 and SHA1 are supported.
|
||||
.TP
|
||||
.I "-b date"
|
||||
The date since when the certificate is valid (notBefore).
|
||||
.TP
|
||||
.I "-cy [authority|end]"
|
||||
Basic constraints. Select Authority or End-Entity certificate.
|
||||
.TP
|
||||
.I "-e date"
|
||||
The date until when the certificate is valid (notAfter).
|
||||
.TP
|
||||
.I "-eku oid[,oid]"
|
||||
Add some extended key usage OID to the certificate.
|
||||
.TP
|
||||
.I "-h number"
|
||||
Add a path length restriction to the certificate chain.
|
||||
.TP
|
||||
.I "-ic cert"
|
||||
Take the issuer's name from the specified certificate.
|
||||
.TP
|
||||
.I "-in name"
|
||||
Take the issuer's name from the specified parameter.
|
||||
.TP
|
||||
.I "-iv pvkfile"
|
||||
Sign the certificate using the private key inside the PVK file.
|
||||
.TP
|
||||
.I "-m number"
|
||||
Certificate validity period (in months).
|
||||
.TP
|
||||
.I "-sv pvkfile"
|
||||
Create a new PVK file if non-existant, otherwise use the PVK file as the subject public key.
|
||||
.SH AUTHOR
|
||||
Written by Sebastien Pouliot
|
||||
.SH COPYRIGHT
|
||||
Copyright (C) 2003 Motus Technologies.
|
||||
Released under BSD license.
|
||||
.SH MAILING LISTS
|
||||
Visit http://mail.ximian.com/mailman/mono-list for details.
|
||||
.SH WEB SITE
|
||||
Visit: http://www.go-mono.com for details
|
||||
.SH SEE ALSO
|
||||
.BR signcode(1)
|
||||
-13
@@ -1,13 +0,0 @@
|
||||
<?xml version="1.0"?>
|
||||
<manpages>
|
||||
<manpage name="Mono" page="mono.1" />
|
||||
<manpage name="Mint" page="mono.1" />
|
||||
<manpage name="Mcs" page="mcs.1" />
|
||||
<manpage name="Ilasm" page="ilasm.1" />
|
||||
<manpage name="Monodis" page="mono.1" />
|
||||
<manpage name="Cilc" page="cilc.1" />
|
||||
<manpage name="Sql#" page="sqlsharp.1" />
|
||||
<manpage name="SecUtil" page="secutil.1" />
|
||||
<manpage name="MonoStyle" page="monostyle.1" />
|
||||
|
||||
</manpages>
|
||||
@@ -1,4 +0,0 @@
|
||||
<?xml version="1.0"?>
|
||||
<monodoc>
|
||||
<source provider="man" basefile="tree" path="manpages"/>
|
||||
</monodoc>
|
||||
@@ -195,9 +195,7 @@ for details on how to use this file.
|
||||
.SH NOTES
|
||||
During compilation the MCS compiler defines the __MonoCS__ symbol,
|
||||
this can be used by pre-processor instructions to compile Mono C#
|
||||
compiler specific code. Please note that this symbol is only to test
|
||||
for the compiler, and is not useful to distinguish compilation or
|
||||
deployment platforms.
|
||||
compiler specific code.
|
||||
.SH AUTHORS
|
||||
The Mono C# Compiler was written by Miguel de Icaza, Ravi Pratap and
|
||||
Martin Baulig at Ximian.
|
||||
|
||||
+28
-33
@@ -10,7 +10,7 @@
|
||||
..
|
||||
.TH Mono "Mono 1.0"
|
||||
.SH NAME
|
||||
mono \- Mono's ECMA-CLI native code generator (Just-in-Time and Ahead-of-Time)
|
||||
mono \- Mono's code ECMA-CLI code generator (Just-in-Time and Ahead-of-Time)
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B mono [options] file [arguments...]
|
||||
@@ -85,11 +85,9 @@ The following optimizations are implemented:
|
||||
cmov Conditional moves
|
||||
shared Emit per-domain code
|
||||
sched Instruction scheduling
|
||||
intrins Intrinsic method implementations
|
||||
instrins Intrinsic method implementations
|
||||
tailc Tail recursion and tail calls
|
||||
loop Loop related optimizations
|
||||
leaf Leaf procedures optimizations
|
||||
profile Use profiling information
|
||||
.fi
|
||||
.Sp
|
||||
For example, to enable all the optimization but dead code
|
||||
@@ -97,28 +95,41 @@ elimination and inlining, you can use:
|
||||
.nf
|
||||
-O=all,-deadce,-inline
|
||||
.fi
|
||||
.SH DEVELOPMENT OPTIONS
|
||||
.TP
|
||||
.I "-V", "--version"
|
||||
Prints JIT version information.
|
||||
.I "--break method"
|
||||
Inserts a breakpoint before the method whose name is `method'
|
||||
(namespace.class:methodname). Use `Main' as method name to insert a
|
||||
breakpoint on the application's main method.
|
||||
.TP
|
||||
.I "--breakonex"
|
||||
Inserts a breakpoint on exceptions. This allows you to debug your
|
||||
application with a native debugger when an exception is thrown.
|
||||
.TP
|
||||
.I "--coverage"
|
||||
Performs coverage analysis on the underlying IL code.
|
||||
.TP
|
||||
.I "--trace"
|
||||
Shows method names as they are invoked.
|
||||
|
||||
|
||||
|
||||
.SH DEVELOPMENT OPTIONS
|
||||
The following options are used to help when developing a JITed application.
|
||||
The following options are used to debug a JITed application. They're
|
||||
only useful when running the JIT in a debugger:
|
||||
.TP
|
||||
.I "--debug"
|
||||
Turns on the debugging mode in the runtime. If an assembly was
|
||||
compiled with debugging information, it will produce line number
|
||||
information for stack traces.
|
||||
.TP
|
||||
.I "--profile[=profiler[:profiler_args]]"
|
||||
.I "--profile"
|
||||
Instructs the runtime to collect profiling information about execution
|
||||
times and memory allocation, and dump it at the end of the execution.
|
||||
If a profiler is not specified, the default profiler is used. profiler_args
|
||||
is a profiler-specific string of options for the profiler itself.
|
||||
.PP
|
||||
The default profiler accepts -time and -alloc to options to disable
|
||||
the time profiling or the memory allocation profilng.
|
||||
.SH JIT MAINTAINER OPTIONS
|
||||
|
||||
|
||||
|
||||
.SH MAINTAINER OPTIONS
|
||||
The maintainer options are only used by those developing the runtime
|
||||
itself, and not typically of interest to runtime users or developers.
|
||||
.TP
|
||||
@@ -156,20 +167,10 @@ compiled. This is used for testing the code generator performance.
|
||||
.TP
|
||||
.I "-v", "--verbose"
|
||||
Increases the verbosity level, each time it is listed, increases the
|
||||
verbosity level to include more information (including, for example,
|
||||
a disassembly of the native code produced, code selector info etc.).
|
||||
verbosity level to include more information.
|
||||
.TP
|
||||
.I "--break method"
|
||||
Inserts a breakpoint before the method whose name is `method'
|
||||
(namespace.class:methodname). Use `Main' as method name to insert a
|
||||
breakpoint on the application's main method.
|
||||
.TP
|
||||
.I "--breakonex"
|
||||
Inserts a breakpoint on exceptions. This allows you to debug your
|
||||
application with a native debugger when an exception is thrown.
|
||||
.TP
|
||||
.I "--trace"
|
||||
Shows method names as they are invoked.
|
||||
.I "-V", "--version"
|
||||
Prints JIT version information.
|
||||
|
||||
|
||||
.SH ENVIRONMENT VARIABLES
|
||||
@@ -196,12 +197,6 @@ If set, this variable overrides the default system configuration directory
|
||||
If set, this variable overrides the default runtime configuration file
|
||||
($PREFIX/etc/mono/config). The --config command line options overrides the
|
||||
environment variable.
|
||||
.TP
|
||||
.I "MONO_DEBUG"
|
||||
If set, enables some features of the runtime useful for debugging.
|
||||
|
||||
Currently it only makes the runtime display the stack traces for all the
|
||||
threads running and exit. It may not exit cleanly. Use at your own risk.
|
||||
.SH FILES
|
||||
On Unix assemblies are loaded from the installation lib directory. If you set
|
||||
`prefix' to /usr, the assemblies will be located in /usr/lib. On
|
||||
|
||||
-481
@@ -1,481 +0,0 @@
|
||||
GNU LIBRARY GENERAL PUBLIC LICENSE
|
||||
Version 2, June 1991
|
||||
|
||||
Copyright (C) 1991 Free Software Foundation, Inc.
|
||||
675 Mass Ave, Cambridge, MA 02139, USA
|
||||
Everyone is permitted to copy and distribute verbatim copies
|
||||
of this license document, but changing it is not allowed.
|
||||
|
||||
[This is the first released version of the library GPL. It is
|
||||
numbered 2 because it goes with version 2 of the ordinary GPL.]
|
||||
|
||||
Preamble
|
||||
|
||||
The licenses for most software are designed to take away your
|
||||
freedom to share and change it. By contrast, the GNU General Public
|
||||
Licenses are intended to guarantee your freedom to share and change
|
||||
free software--to make sure the software is free for all its users.
|
||||
|
||||
This license, the Library General Public License, applies to some
|
||||
specially designated Free Software Foundation software, and to any
|
||||
other libraries whose authors decide to use it. You can use it for
|
||||
your libraries, too.
|
||||
|
||||
When we speak of free software, we are referring to freedom, not
|
||||
price. Our General Public Licenses are designed to make sure that you
|
||||
have the freedom to distribute copies of free software (and charge for
|
||||
this service if you wish), that you receive source code or can get it
|
||||
if you want it, that you can change the software or use pieces of it
|
||||
in new free programs; and that you know you can do these things.
|
||||
|
||||
To protect your rights, we need to make restrictions that forbid
|
||||
anyone to deny you these rights or to ask you to surrender the rights.
|
||||
These restrictions translate to certain responsibilities for you if
|
||||
you distribute copies of the library, or if you modify it.
|
||||
|
||||
For example, if you distribute copies of the library, whether gratis
|
||||
or for a fee, you must give the recipients all the rights that we gave
|
||||
you. You must make sure that they, too, receive or can get the source
|
||||
code. If you link a program with the library, you must provide
|
||||
complete object files to the recipients so that they can relink them
|
||||
with the library, after making changes to the library and recompiling
|
||||
it. And you must show them these terms so they know their rights.
|
||||
|
||||
Our method of protecting your rights has two steps: (1) copyright
|
||||
the library, and (2) offer you this license which gives you legal
|
||||
permission to copy, distribute and/or modify the library.
|
||||
|
||||
Also, for each distributor's protection, we want to make certain
|
||||
that everyone understands that there is no warranty for this free
|
||||
library. If the library is modified by someone else and passed on, we
|
||||
want its recipients to know that what they have is not the original
|
||||
version, so that any problems introduced by others will not reflect on
|
||||
the original authors' reputations.
|
||||
|
||||
Finally, any free program is threatened constantly by software
|
||||
patents. We wish to avoid the danger that companies distributing free
|
||||
software will individually obtain patent licenses, thus in effect
|
||||
transforming the program into proprietary software. To prevent this,
|
||||
we have made it clear that any patent must be licensed for everyone's
|
||||
free use or not licensed at all.
|
||||
|
||||
Most GNU software, including some libraries, is covered by the ordinary
|
||||
GNU General Public License, which was designed for utility programs. This
|
||||
license, the GNU Library General Public License, applies to certain
|
||||
designated libraries. This license is quite different from the ordinary
|
||||
one; be sure to read it in full, and don't assume that anything in it is
|
||||
the same as in the ordinary license.
|
||||
|
||||
The reason we have a separate public license for some libraries is that
|
||||
they blur the distinction we usually make between modifying or adding to a
|
||||
program and simply using it. Linking a program with a library, without
|
||||
changing the library, is in some sense simply using the library, and is
|
||||
analogous to running a utility program or application program. However, in
|
||||
a textual and legal sense, the linked executable is a combined work, a
|
||||
derivative of the original library, and the ordinary General Public License
|
||||
treats it as such.
|
||||
|
||||
Because of this blurred distinction, using the ordinary General
|
||||
Public License for libraries did not effectively promote software
|
||||
sharing, because most developers did not use the libraries. We
|
||||
concluded that weaker conditions might promote sharing better.
|
||||
|
||||
However, unrestricted linking of non-free programs would deprive the
|
||||
users of those programs of all benefit from the free status of the
|
||||
libraries themselves. This Library General Public License is intended to
|
||||
permit developers of non-free programs to use free libraries, while
|
||||
preserving your freedom as a user of such programs to change the free
|
||||
libraries that are incorporated in them. (We have not seen how to achieve
|
||||
this as regards changes in header files, but we have achieved it as regards
|
||||
changes in the actual functions of the Library.) The hope is that this
|
||||
will lead to faster development of free libraries.
|
||||
|
||||
The precise terms and conditions for copying, distribution and
|
||||
modification follow. Pay close attention to the difference between a
|
||||
"work based on the library" and a "work that uses the library". The
|
||||
former contains code derived from the library, while the latter only
|
||||
works together with the library.
|
||||
|
||||
Note that it is possible for a library to be covered by the ordinary
|
||||
General Public License rather than by this special one.
|
||||
|
||||
GNU LIBRARY GENERAL PUBLIC LICENSE
|
||||
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
|
||||
|
||||
0. This License Agreement applies to any software library which
|
||||
contains a notice placed by the copyright holder or other authorized
|
||||
party saying it may be distributed under the terms of this Library
|
||||
General Public License (also called "this License"). Each licensee is
|
||||
addressed as "you".
|
||||
|
||||
A "library" means a collection of software functions and/or data
|
||||
prepared so as to be conveniently linked with application programs
|
||||
(which use some of those functions and data) to form executables.
|
||||
|
||||
The "Library", below, refers to any such software library or work
|
||||
which has been distributed under these terms. A "work based on the
|
||||
Library" means either the Library or any derivative work under
|
||||
copyright law: that is to say, a work containing the Library or a
|
||||
portion of it, either verbatim or with modifications and/or translated
|
||||
straightforwardly into another language. (Hereinafter, translation is
|
||||
included without limitation in the term "modification".)
|
||||
|
||||
"Source code" for a work means the preferred form of the work for
|
||||
making modifications to it. For a library, complete source code means
|
||||
all the source code for all modules it contains, plus any associated
|
||||
interface definition files, plus the scripts used to control compilation
|
||||
and installation of the library.
|
||||
|
||||
Activities other than copying, distribution and modification are not
|
||||
covered by this License; they are outside its scope. The act of
|
||||
running a program using the Library is not restricted, and output from
|
||||
such a program is covered only if its contents constitute a work based
|
||||
on the Library (independent of the use of the Library in a tool for
|
||||
writing it). Whether that is true depends on what the Library does
|
||||
and what the program that uses the Library does.
|
||||
|
||||
1. You may copy and distribute verbatim copies of the Library's
|
||||
complete source code as you receive it, in any medium, provided that
|
||||
you conspicuously and appropriately publish on each copy an
|
||||
appropriate copyright notice and disclaimer of warranty; keep intact
|
||||
all the notices that refer to this License and to the absence of any
|
||||
warranty; and distribute a copy of this License along with the
|
||||
Library.
|
||||
|
||||
You may charge a fee for the physical act of transferring a copy,
|
||||
and you may at your option offer warranty protection in exchange for a
|
||||
fee.
|
||||
|
||||
2. You may modify your copy or copies of the Library or any portion
|
||||
of it, thus forming a work based on the Library, and copy and
|
||||
distribute such modifications or work under the terms of Section 1
|
||||
above, provided that you also meet all of these conditions:
|
||||
|
||||
a) The modified work must itself be a software library.
|
||||
|
||||
b) You must cause the files modified to carry prominent notices
|
||||
stating that you changed the files and the date of any change.
|
||||
|
||||
c) You must cause the whole of the work to be licensed at no
|
||||
charge to all third parties under the terms of this License.
|
||||
|
||||
d) If a facility in the modified Library refers to a function or a
|
||||
table of data to be supplied by an application program that uses
|
||||
the facility, other than as an argument passed when the facility
|
||||
is invoked, then you must make a good faith effort to ensure that,
|
||||
in the event an application does not supply such function or
|
||||
table, the facility still operates, and performs whatever part of
|
||||
its purpose remains meaningful.
|
||||
|
||||
(For example, a function in a library to compute square roots has
|
||||
a purpose that is entirely well-defined independent of the
|
||||
application. Therefore, Subsection 2d requires that any
|
||||
application-supplied function or table used by this function must
|
||||
be optional: if the application does not supply it, the square
|
||||
root function must still compute square roots.)
|
||||
|
||||
These requirements apply to the modified work as a whole. If
|
||||
identifiable sections of that work are not derived from the Library,
|
||||
and can be reasonably considered independent and separate works in
|
||||
themselves, then this License, and its terms, do not apply to those
|
||||
sections when you distribute them as separate works. But when you
|
||||
distribute the same sections as part of a whole which is a work based
|
||||
on the Library, the distribution of the whole must be on the terms of
|
||||
this License, whose permissions for other licensees extend to the
|
||||
entire whole, and thus to each and every part regardless of who wrote
|
||||
it.
|
||||
|
||||
Thus, it is not the intent of this section to claim rights or contest
|
||||
your rights to work written entirely by you; rather, the intent is to
|
||||
exercise the right to control the distribution of derivative or
|
||||
collective works based on the Library.
|
||||
|
||||
In addition, mere aggregation of another work not based on the Library
|
||||
with the Library (or with a work based on the Library) on a volume of
|
||||
a storage or distribution medium does not bring the other work under
|
||||
the scope of this License.
|
||||
|
||||
3. You may opt to apply the terms of the ordinary GNU General Public
|
||||
License instead of this License to a given copy of the Library. To do
|
||||
this, you must alter all the notices that refer to this License, so
|
||||
that they refer to the ordinary GNU General Public License, version 2,
|
||||
instead of to this License. (If a newer version than version 2 of the
|
||||
ordinary GNU General Public License has appeared, then you can specify
|
||||
that version instead if you wish.) Do not make any other change in
|
||||
these notices.
|
||||
|
||||
Once this change is made in a given copy, it is irreversible for
|
||||
that copy, so the ordinary GNU General Public License applies to all
|
||||
subsequent copies and derivative works made from that copy.
|
||||
|
||||
This option is useful when you wish to copy part of the code of
|
||||
the Library into a program that is not a library.
|
||||
|
||||
4. You may copy and distribute the Library (or a portion or
|
||||
derivative of it, under Section 2) in object code or executable form
|
||||
under the terms of Sections 1 and 2 above provided that you accompany
|
||||
it with the complete corresponding machine-readable source code, which
|
||||
must be distributed under the terms of Sections 1 and 2 above on a
|
||||
medium customarily used for software interchange.
|
||||
|
||||
If distribution of object code is made by offering access to copy
|
||||
from a designated place, then offering equivalent access to copy the
|
||||
source code from the same place satisfies the requirement to
|
||||
distribute the source code, even though third parties are not
|
||||
compelled to copy the source along with the object code.
|
||||
|
||||
5. A program that contains no derivative of any portion of the
|
||||
Library, but is designed to work with the Library by being compiled or
|
||||
linked with it, is called a "work that uses the Library". Such a
|
||||
work, in isolation, is not a derivative work of the Library, and
|
||||
therefore falls outside the scope of this License.
|
||||
|
||||
However, linking a "work that uses the Library" with the Library
|
||||
creates an executable that is a derivative of the Library (because it
|
||||
contains portions of the Library), rather than a "work that uses the
|
||||
library". The executable is therefore covered by this License.
|
||||
Section 6 states terms for distribution of such executables.
|
||||
|
||||
When a "work that uses the Library" uses material from a header file
|
||||
that is part of the Library, the object code for the work may be a
|
||||
derivative work of the Library even though the source code is not.
|
||||
Whether this is true is especially significant if the work can be
|
||||
linked without the Library, or if the work is itself a library. The
|
||||
threshold for this to be true is not precisely defined by law.
|
||||
|
||||
If such an object file uses only numerical parameters, data
|
||||
structure layouts and accessors, and small macros and small inline
|
||||
functions (ten lines or less in length), then the use of the object
|
||||
file is unrestricted, regardless of whether it is legally a derivative
|
||||
work. (Executables containing this object code plus portions of the
|
||||
Library will still fall under Section 6.)
|
||||
|
||||
Otherwise, if the work is a derivative of the Library, you may
|
||||
distribute the object code for the work under the terms of Section 6.
|
||||
Any executables containing that work also fall under Section 6,
|
||||
whether or not they are linked directly with the Library itself.
|
||||
|
||||
6. As an exception to the Sections above, you may also compile or
|
||||
link a "work that uses the Library" with the Library to produce a
|
||||
work containing portions of the Library, and distribute that work
|
||||
under terms of your choice, provided that the terms permit
|
||||
modification of the work for the customer's own use and reverse
|
||||
engineering for debugging such modifications.
|
||||
|
||||
You must give prominent notice with each copy of the work that the
|
||||
Library is used in it and that the Library and its use are covered by
|
||||
this License. You must supply a copy of this License. If the work
|
||||
during execution displays copyright notices, you must include the
|
||||
copyright notice for the Library among them, as well as a reference
|
||||
directing the user to the copy of this License. Also, you must do one
|
||||
of these things:
|
||||
|
||||
a) Accompany the work with the complete corresponding
|
||||
machine-readable source code for the Library including whatever
|
||||
changes were used in the work (which must be distributed under
|
||||
Sections 1 and 2 above); and, if the work is an executable linked
|
||||
with the Library, with the complete machine-readable "work that
|
||||
uses the Library", as object code and/or source code, so that the
|
||||
user can modify the Library and then relink to produce a modified
|
||||
executable containing the modified Library. (It is understood
|
||||
that the user who changes the contents of definitions files in the
|
||||
Library will not necessarily be able to recompile the application
|
||||
to use the modified definitions.)
|
||||
|
||||
b) Accompany the work with a written offer, valid for at
|
||||
least three years, to give the same user the materials
|
||||
specified in Subsection 6a, above, for a charge no more
|
||||
than the cost of performing this distribution.
|
||||
|
||||
c) If distribution of the work is made by offering access to copy
|
||||
from a designated place, offer equivalent access to copy the above
|
||||
specified materials from the same place.
|
||||
|
||||
d) Verify that the user has already received a copy of these
|
||||
materials or that you have already sent this user a copy.
|
||||
|
||||
For an executable, the required form of the "work that uses the
|
||||
Library" must include any data and utility programs needed for
|
||||
reproducing the executable from it. However, as a special exception,
|
||||
the source code distributed need not include anything that is normally
|
||||
distributed (in either source or binary form) with the major
|
||||
components (compiler, kernel, and so on) of the operating system on
|
||||
which the executable runs, unless that component itself accompanies
|
||||
the executable.
|
||||
|
||||
It may happen that this requirement contradicts the license
|
||||
restrictions of other proprietary libraries that do not normally
|
||||
accompany the operating system. Such a contradiction means you cannot
|
||||
use both them and the Library together in an executable that you
|
||||
distribute.
|
||||
|
||||
7. You may place library facilities that are a work based on the
|
||||
Library side-by-side in a single library together with other library
|
||||
facilities not covered by this License, and distribute such a combined
|
||||
library, provided that the separate distribution of the work based on
|
||||
the Library and of the other library facilities is otherwise
|
||||
permitted, and provided that you do these two things:
|
||||
|
||||
a) Accompany the combined library with a copy of the same work
|
||||
based on the Library, uncombined with any other library
|
||||
facilities. This must be distributed under the terms of the
|
||||
Sections above.
|
||||
|
||||
b) Give prominent notice with the combined library of the fact
|
||||
that part of it is a work based on the Library, and explaining
|
||||
where to find the accompanying uncombined form of the same work.
|
||||
|
||||
8. You may not copy, modify, sublicense, link with, or distribute
|
||||
the Library except as expressly provided under this License. Any
|
||||
attempt otherwise to copy, modify, sublicense, link with, or
|
||||
distribute the Library is void, and will automatically terminate your
|
||||
rights under this License. However, parties who have received copies,
|
||||
or rights, from you under this License will not have their licenses
|
||||
terminated so long as such parties remain in full compliance.
|
||||
|
||||
9. You are not required to accept this License, since you have not
|
||||
signed it. However, nothing else grants you permission to modify or
|
||||
distribute the Library or its derivative works. These actions are
|
||||
prohibited by law if you do not accept this License. Therefore, by
|
||||
modifying or distributing the Library (or any work based on the
|
||||
Library), you indicate your acceptance of this License to do so, and
|
||||
all its terms and conditions for copying, distributing or modifying
|
||||
the Library or works based on it.
|
||||
|
||||
10. Each time you redistribute the Library (or any work based on the
|
||||
Library), the recipient automatically receives a license from the
|
||||
original licensor to copy, distribute, link with or modify the Library
|
||||
subject to these terms and conditions. You may not impose any further
|
||||
restrictions on the recipients' exercise of the rights granted herein.
|
||||
You are not responsible for enforcing compliance by third parties to
|
||||
this License.
|
||||
|
||||
11. If, as a consequence of a court judgment or allegation of patent
|
||||
infringement or for any other reason (not limited to patent issues),
|
||||
conditions are imposed on you (whether by court order, agreement or
|
||||
otherwise) that contradict the conditions of this License, they do not
|
||||
excuse you from the conditions of this License. If you cannot
|
||||
distribute so as to satisfy simultaneously your obligations under this
|
||||
License and any other pertinent obligations, then as a consequence you
|
||||
may not distribute the Library at all. For example, if a patent
|
||||
license would not permit royalty-free redistribution of the Library by
|
||||
all those who receive copies directly or indirectly through you, then
|
||||
the only way you could satisfy both it and this License would be to
|
||||
refrain entirely from distribution of the Library.
|
||||
|
||||
If any portion of this section is held invalid or unenforceable under any
|
||||
particular circumstance, the balance of the section is intended to apply,
|
||||
and the section as a whole is intended to apply in other circumstances.
|
||||
|
||||
It is not the purpose of this section to induce you to infringe any
|
||||
patents or other property right claims or to contest validity of any
|
||||
such claims; this section has the sole purpose of protecting the
|
||||
integrity of the free software distribution system which is
|
||||
implemented by public license practices. Many people have made
|
||||
generous contributions to the wide range of software distributed
|
||||
through that system in reliance on consistent application of that
|
||||
system; it is up to the author/donor to decide if he or she is willing
|
||||
to distribute software through any other system and a licensee cannot
|
||||
impose that choice.
|
||||
|
||||
This section is intended to make thoroughly clear what is believed to
|
||||
be a consequence of the rest of this License.
|
||||
|
||||
12. If the distribution and/or use of the Library is restricted in
|
||||
certain countries either by patents or by copyrighted interfaces, the
|
||||
original copyright holder who places the Library under this License may add
|
||||
an explicit geographical distribution limitation excluding those countries,
|
||||
so that distribution is permitted only in or among countries not thus
|
||||
excluded. In such case, this License incorporates the limitation as if
|
||||
written in the body of this License.
|
||||
|
||||
13. The Free Software Foundation may publish revised and/or new
|
||||
versions of the Library General Public License from time to time.
|
||||
Such new versions will be similar in spirit to the present version,
|
||||
but may differ in detail to address new problems or concerns.
|
||||
|
||||
Each version is given a distinguishing version number. If the Library
|
||||
specifies a version number of this License which applies to it and
|
||||
"any later version", you have the option of following the terms and
|
||||
conditions either of that version or of any later version published by
|
||||
the Free Software Foundation. If the Library does not specify a
|
||||
license version number, you may choose any version ever published by
|
||||
the Free Software Foundation.
|
||||
|
||||
14. If you wish to incorporate parts of the Library into other free
|
||||
programs whose distribution conditions are incompatible with these,
|
||||
write to the author to ask for permission. For software which is
|
||||
copyrighted by the Free Software Foundation, write to the Free
|
||||
Software Foundation; we sometimes make exceptions for this. Our
|
||||
decision will be guided by the two goals of preserving the free status
|
||||
of all derivatives of our free software and of promoting the sharing
|
||||
and reuse of software generally.
|
||||
|
||||
NO WARRANTY
|
||||
|
||||
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
|
||||
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
|
||||
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
|
||||
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
|
||||
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
|
||||
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
||||
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
|
||||
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
|
||||
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
|
||||
|
||||
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
|
||||
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
|
||||
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
|
||||
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
|
||||
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
|
||||
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
|
||||
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
|
||||
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
|
||||
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
|
||||
DAMAGES.
|
||||
|
||||
END OF TERMS AND CONDITIONS
|
||||
|
||||
Appendix: How to Apply These Terms to Your New Libraries
|
||||
|
||||
If you develop a new library, and you want it to be of the greatest
|
||||
possible use to the public, we recommend making it free software that
|
||||
everyone can redistribute and change. You can do so by permitting
|
||||
redistribution under these terms (or, alternatively, under the terms of the
|
||||
ordinary General Public License).
|
||||
|
||||
To apply these terms, attach the following notices to the library. It is
|
||||
safest to attach them to the start of each source file to most effectively
|
||||
convey the exclusion of warranty; and each file should have at least the
|
||||
"copyright" line and a pointer to where the full notice is found.
|
||||
|
||||
<one line to give the library's name and a brief idea of what it does.>
|
||||
Copyright (C) <year> <name of author>
|
||||
|
||||
This library is free software; you can redistribute it and/or
|
||||
modify it under the terms of the GNU Library General Public
|
||||
License as published by the Free Software Foundation; either
|
||||
version 2 of the License, or (at your option) any later version.
|
||||
|
||||
This library is distributed in the hope that it will be useful,
|
||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
||||
Library General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU Library General Public
|
||||
License along with this library; if not, write to the Free
|
||||
Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
|
||||
|
||||
Also add information on how to contact you by electronic and paper mail.
|
||||
|
||||
You should also get your employer (if you work as a programmer) or your
|
||||
school, if any, to sign a "copyright disclaimer" for the library, if
|
||||
necessary. Here is a sample; alter the names:
|
||||
|
||||
Yoyodyne, Inc., hereby disclaims all copyright interest in the
|
||||
library `Frob' (a library for tweaking knobs) written by James Random Hacker.
|
||||
|
||||
<signature of Ty Coon>, 1 April 1990
|
||||
Ty Coon, President of Vice
|
||||
|
||||
That's all there is to it!
|
||||
@@ -1,97 +1,3 @@
|
||||
2003-07-22 Peter Williams <[email protected]>
|
||||
|
||||
* README: INSTALL.txt, not INSTALL.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* nunit20/nunit-console/Makefile (PROGRAM): Put nunit-console.exe
|
||||
in $(topdir)/class/lib so we can find our DLL's.
|
||||
|
||||
2003-07-18 Peter Williams <[email protected]>
|
||||
|
||||
* build/library.make (dist-local): Fancy make dist magic gives
|
||||
way to boring old 'for'.
|
||||
|
||||
* build/executable.make (dist-local): Ditto.
|
||||
|
||||
2003-07-17 Peter Williams <[email protected]>
|
||||
|
||||
* build/profiles/default.make: Actually fix this. Use the platform
|
||||
compiler all the way.
|
||||
|
||||
2003-07-17 Peter Williams <[email protected]>
|
||||
|
||||
* build/profiles/default.make: Try to make this smarter so
|
||||
that we can build on Windows. Specifically, don't require
|
||||
the mono runtime. Combined with the corlib $(BOOT_COMPILE) change,
|
||||
this should make corlib build out of the box, I think.
|
||||
|
||||
2003-07-16 Peter Williams <[email protected]>
|
||||
|
||||
A whole passel of build system changes. Doc updates:
|
||||
|
||||
* build/README.makefiles: Doc updates.
|
||||
|
||||
* build/profiles/net_1_0.make: Doc changes.
|
||||
|
||||
* INSTALL.txt: A few more touchups.
|
||||
|
||||
Better defaults:
|
||||
|
||||
* build/config-default.make (prefix): Default install prefix
|
||||
should be /usr/local.
|
||||
|
||||
* build/profiles/bootstrap.make: This profile ...
|
||||
|
||||
* build/profiles/default.make: ... is now the default.
|
||||
|
||||
* build/profiles/atomic.make: And the default is now this.
|
||||
|
||||
Fixes for pre-build checks:
|
||||
|
||||
* Makefile: Do the platform and (new) profile checks
|
||||
before the build, which took some infrastructure changes.
|
||||
|
||||
* build/rules.make: Allow a Makefile to specify its own all/install/etc
|
||||
targets.
|
||||
|
||||
* build/profiles/default.make (profile-check): Add a blank
|
||||
target here.
|
||||
|
||||
* build/profiles/atomic.make: Check for a full MCS install to
|
||||
build against.
|
||||
|
||||
HP/UX fixes with help from Bernie Solomon:
|
||||
|
||||
* build/config-default.make (ECHO_ESCAPE): HP/UX 'echo'
|
||||
doesn't need a -e parameter to interpret escape codes. Test for
|
||||
that and define a configuration parameter.
|
||||
|
||||
* build/library.make ($(makefrag)): Use $(ECHO_ESCAPE)
|
||||
instead of assuming that 'echo -e' will interpret escape
|
||||
codes.
|
||||
|
||||
* build/executable.make ($(makefrag)): Here too.
|
||||
|
||||
A make distcheck fix:
|
||||
|
||||
* Makefile: Inherit the current prefix so that the build can
|
||||
find the right System.Xml.dll.
|
||||
|
||||
And Windows build fixes with the invaluable help of Sebastian
|
||||
Pouliot (in various subdirectories).
|
||||
|
||||
2003-07-14 Peter Williams <[email protected]>
|
||||
|
||||
* build/rules.make (dist-recursive): Fix recursive rules
|
||||
to work on HP/UX /bin/sh. Patch from Bernie Solomon
|
||||
<[email protected]>.
|
||||
|
||||
2003-05-10 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* makefile:
|
||||
* makefile.gnu: don't use -C when running make.
|
||||
|
||||
2003-05-05 Ben Maurer <[email protected]>
|
||||
* AUTHORS: Added self.
|
||||
|
||||
|
||||
+29
-122
@@ -1,146 +1,53 @@
|
||||
Basic Installation
|
||||
==================
|
||||
|
||||
The Mono project has developed mono, a CLI runtime. The build process
|
||||
of each of these depends on nothing more than a C compiler and glib2.
|
||||
The Mono project has developed mono, an x86-specific CL JIT compiler and
|
||||
mint, a portable CLI interpreter. The build process of each of these
|
||||
depends on nothing more than a C compiler, glib2 and libgc.
|
||||
|
||||
However, to provide a working runtime environment, these programs must
|
||||
be supplemented by the class libraries, which are written in C#. This
|
||||
package contains the components written in C#: class libraries,
|
||||
compilers and tools.
|
||||
be supplemented by corlib, a CLR assembly to which they are closely
|
||||
tied. This package provides the C# sources for corlib as well as some
|
||||
additional assemblies and mcs, the Mono C# compiler.
|
||||
|
||||
Build Process for Users.
|
||||
========================
|
||||
To build this package, you must already have a C# compiler installed.
|
||||
Build instructions for *NIX and Microsoft Windows follow.
|
||||
|
||||
If you only want to build a snapshot or a fresh CVS checkout of the
|
||||
sources, you should go into the `mono' sibling directory and issue the
|
||||
following command:
|
||||
Building mcs on *NIX
|
||||
====================
|
||||
|
||||
./autogen --prefix=/usr/local
|
||||
make fullbuild
|
||||
|
||||
That will build and install the code in a single pass. The
|
||||
compilation is bundled with the build due to depedencies on the class
|
||||
libraries on the runtime.
|
||||
|
||||
Build Features for Developers.
|
||||
==============================
|
||||
|
||||
These instructions apply to both Linux and Windows. To build this
|
||||
package, you must already have a C# compiler installed. This means
|
||||
that to build on Linux, you need to get a distribution of the MCS
|
||||
binaries; these are called monocharges. See README.building for
|
||||
information on where to get them. On Windows, you can just use the
|
||||
Microsoft compiler. You also need GNU make to build the software (on
|
||||
Windows, you will need for example the Cygwin environment setup).
|
||||
mcs provides a set of makefiles which make it easy to build and install
|
||||
mcs on *NIX systems like Linux or FreeBSD where mcs is already
|
||||
installed.
|
||||
|
||||
To build the compiler and class libraries, run:
|
||||
|
||||
make
|
||||
make -f makefile.gnu
|
||||
|
||||
The libraries will be placed in the directory class/lib/ and the mcs
|
||||
compiler executable in mcs/.
|
||||
|
||||
To install them, run the following:
|
||||
To install them, run the following, where prefix identifies where you
|
||||
want the files installed:
|
||||
|
||||
make install
|
||||
|
||||
The default prefix is /usr/local. To change this configuration option type:
|
||||
|
||||
echo prefix=/your-prefix >> build/config.make
|
||||
|
||||
If you get "corlib out of sync" errors, try
|
||||
|
||||
make PROFILE="atomic"
|
||||
|
||||
The difference between the two modes is explained farther down.
|
||||
|
||||
Monocharges
|
||||
===========
|
||||
make -f makefile.gnu install prefix=/usr/local
|
||||
|
||||
If you are tracking Mono's development, you may sometimes need to share
|
||||
the compiled libraries with others, you can do:
|
||||
the compiled libraries with others. If you want to produce an easily
|
||||
distributable tarball, run:
|
||||
|
||||
make monocharge
|
||||
make -f makefile.gnu dist
|
||||
|
||||
Or a light version, which contains only the essential libraries and
|
||||
results in a much smaller file:
|
||||
Building mcs on Windows
|
||||
=======================
|
||||
|
||||
make monocharge-lite
|
||||
It is also possible to build mcs on Windows using the Microsoft .NET
|
||||
framework. This may be convenient if you do not have access to a working
|
||||
mcs setup. To build the compiler and class libraries, run:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
make
|
||||
|
||||
If you want to change the configuration options for the build process,
|
||||
place your configuration options in build/config.make
|
||||
The libraries will be placed in the directory class/lib/ and the mcs
|
||||
compiler executable in mcs/. They can then be copied to /usr/lib and
|
||||
/usr/bin or wherever desired on the target system.
|
||||
|
||||
A list of variables that control the build are listed in the file
|
||||
build/config-default.make.
|
||||
|
||||
Build profiles? What?
|
||||
======================
|
||||
|
||||
Don't worry about them too much. If you're wondering which to use:
|
||||
use the default if you can (that's why it's the default!) and use
|
||||
the atomic if you have to.
|
||||
|
||||
The default profile uses the C# compiler and class libaries as they
|
||||
are built. This lets you build MCS without needing to have already
|
||||
installed it, but can fail if the libraries change significantly.
|
||||
(This is the source of the dreaded "corlib out of sync" warning, most
|
||||
of the time.)
|
||||
|
||||
The atomic profile tries to use the system compiler and preexisting
|
||||
MCS libraries. New libaries are built against this constant reference
|
||||
point, so if a newly built library has a binary incompatibility, the
|
||||
rest of your build can proceed.
|
||||
|
||||
If you want to always use the atomic profile, run this command:
|
||||
|
||||
echo PROFILE=atomic >> build/config.make
|
||||
|
||||
More About the Build System
|
||||
===========================
|
||||
|
||||
More information is found in build/README.*. Here's a quick rundown
|
||||
of the features:
|
||||
|
||||
* Unified build system for Windows and Linux. Windows is still
|
||||
fairly untested, but "should work." Unfortunately I don't
|
||||
have a Windows machine to test on, but Gonzalo can get
|
||||
corlib to build I think and that's about as complicated as
|
||||
it gets.
|
||||
|
||||
* Profile support. 'make PROFILE=profilename' or 'export
|
||||
PROFILE=profilename ; make' will work. Profiles are defined
|
||||
in build/profiles/profilename.make ; right now there isn't
|
||||
too much going on. The 'bootstrap' profile will build the
|
||||
way makefile.gnu did on Linux, by setting MONO_PATH and
|
||||
using mcs/mcs.exe; the default profile will build against
|
||||
the existing system libraries and compile with 'mcs', which
|
||||
should reduce a lot of 'corlib out of sync' warnings.
|
||||
|
||||
* Important variables are shared among makefiles now; you can
|
||||
edit build/config.make (see build/config-default.make for a
|
||||
template) and give global settings, or just have a much
|
||||
saner time of writing new makefiles.
|
||||
|
||||
* Response files, stamps, and other build trivia now all land
|
||||
in build/deps/, making the library build directories
|
||||
cleaner.
|
||||
|
||||
* Test libraries now live in class/Library/Library_test.dll,
|
||||
not class/Library/Test. 'make test' will build the test DLL,
|
||||
'make run-test' will actually run the nunit tests. Set the
|
||||
variable TEST_HARNESS to run with a program other than
|
||||
nunit-console (for example, nunit-gtk).
|
||||
|
||||
* Standardized recursive targets: all, clean, install, test,
|
||||
run-test. Read build/README.makefiles for definitions of
|
||||
what they should do
|
||||
|
||||
* (Relatively) sane 'make dist' target; 'make distcheck'
|
||||
support; cute 'make monocharge' and 'make monocharge-lite'
|
||||
targets. They're made possible because 'make install' now
|
||||
supports DESTDIR a la automake, which I'm sure someone cares
|
||||
about.
|
||||
-29
@@ -1,29 +0,0 @@
|
||||
|
||||
The Mono code is licensed under various different licenses.
|
||||
|
||||
GNU GPL: details avaliable in the file LICENSE.GPL
|
||||
GNU LGPL: details available in the file LICENSE.LGPL
|
||||
MIT X11: text available in the file MIT.X11
|
||||
|
||||
For your convenience copies of the GNU GPL and GNU LGPL are
|
||||
located in the file COPYING and COPYING.LIB.
|
||||
|
||||
* Class Libraries:
|
||||
|
||||
All of the core classes licensed under the terms of
|
||||
the MIT X11 license.
|
||||
|
||||
Third party libraries that we distribute for
|
||||
convenience reasons are distributed under their own
|
||||
terms (all of them allow development of proprietary
|
||||
applications with them).
|
||||
|
||||
Third party libraries include: ByteFX.Data,
|
||||
ICSharpCode.SharpZipLib, Npgsql.
|
||||
|
||||
* Mono C# compiler: GNU GPL
|
||||
|
||||
* Mono Basic compiler: GNU GPL.
|
||||
|
||||
* Various tools in the `tools' directory: GNU GPL.
|
||||
|
||||
@@ -1,15 +0,0 @@
|
||||
Mono compilers and tools.
|
||||
Copyright (C) 2001, 2002, 2003, Ximian and contributors.
|
||||
|
||||
This program is free software; you can redistribute it and/or modify
|
||||
it under the terms of the GNU General Public License as published by
|
||||
the Free Software Foundation;
|
||||
|
||||
This program is distributed in the hope that it will be useful,
|
||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
||||
GNU General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with this program; if not, write to the Free Software
|
||||
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
|
||||
@@ -1,15 +0,0 @@
|
||||
Mono class libraries
|
||||
Copyright (C) Mono project (authors listed in individual ChangeLog entries)
|
||||
|
||||
This library is free software; you can redistribute it and/or
|
||||
modify it under the terms of the GNU Library General Public
|
||||
License as published by the Free Software Foundation.
|
||||
|
||||
This library is distributed in the hope that it will be useful,
|
||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
||||
Library General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU Library General Public
|
||||
License along with this library; if not, write to the Free
|
||||
Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
|
||||
-21
@@ -1,21 +0,0 @@
|
||||
Copyright (c) 2001, 2002, 2003 Ximian, Inc and the individuals listed
|
||||
on the ChangeLog entries.
|
||||
|
||||
Permission is hereby granted, free of charge, to any person obtaining
|
||||
a copy of this software and associated documentation files (the
|
||||
"Software"), to deal in the Software without restriction, including
|
||||
without limitation the rights to use, copy, modify, merge, publish,
|
||||
distribute, sublicense, and/or sell copies of the Software, and to
|
||||
permit persons to whom the Software is furnished to do so, subject to
|
||||
the following conditions:
|
||||
|
||||
The above copyright notice and this permission notice shall be
|
||||
included in all copies or substantial portions of the Software.
|
||||
|
||||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
||||
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
|
||||
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
|
||||
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
|
||||
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
|
||||
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
|
||||
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|
||||
-106
@@ -1,106 +0,0 @@
|
||||
thisdir := .
|
||||
SUBDIRS := build jay mcs class mbas nunit20 monoresgen ilasm tools tests errors docs
|
||||
OVERRIDE_BARE_TARGETS = hells yeah
|
||||
include build/rules.make
|
||||
|
||||
# Define these ourselves to that the platform checks come first
|
||||
|
||||
all: platform-check profile-check all-recursive #all-local
|
||||
|
||||
install: platform-check profile-check install-recursive #install-local
|
||||
|
||||
test: platform-check profile-check test-recursive #test-local
|
||||
|
||||
run-test: run-test-recursive #run-test-local
|
||||
|
||||
clean: clean-recursive #clean-local
|
||||
|
||||
# fun specialty targets
|
||||
|
||||
testcorlib:
|
||||
@cd class/corlib && $(MAKE) test run-test
|
||||
|
||||
# Disting. We need to override $(distdir) here.
|
||||
|
||||
package := mcs-$(VERSION)
|
||||
top_distdir = $(dots)/$(package)
|
||||
distdir = $(top_distdir)
|
||||
export package
|
||||
|
||||
DISTFILES = \
|
||||
AUTHORS \
|
||||
ChangeLog \
|
||||
COPYING \
|
||||
COPYING.LIB \
|
||||
INSTALL.txt \
|
||||
LICENSE \
|
||||
LICENSE.GPL \
|
||||
LICENSE.LGPL \
|
||||
Makefile \
|
||||
mkinstalldirs \
|
||||
MIT.X11 \
|
||||
MonoIcon.png \
|
||||
README \
|
||||
ScalableMonoIcon.svg \
|
||||
winexe.in
|
||||
|
||||
dist-pre:
|
||||
rm -rf $(package)
|
||||
|
||||
dist-post:
|
||||
tar cvzf $(package).tar.gz $(package)
|
||||
|
||||
dist-local: dist-default
|
||||
|
||||
dist-tarball: dist-pre dist-recursive dist-post
|
||||
|
||||
dist: dist-tarball
|
||||
rm -rf $(package)
|
||||
|
||||
# the egrep -v is kind of a hack (to get rid of the makefrags)
|
||||
# but otherwise we have to make dist then make clean which
|
||||
# is sort of not kosher. And it breaks with DIST_ONLY_SUBDIRS.
|
||||
#
|
||||
# We need to set prefix on make so class/System/Makefile can find
|
||||
# the installed System.Xml to build properly
|
||||
|
||||
distcheck:
|
||||
rm -rf InstallTest Distcheck-MCS ; \
|
||||
mkdir InstallTest ; \
|
||||
destdir=`cd InstallTest && pwd` ; \
|
||||
$(MAKE) dist-tarball || exit 1 ; \
|
||||
mv $(package) Distcheck-MCS ; \
|
||||
(cd Distcheck-MCS && \
|
||||
make prefix=$(prefix) && make test && make install DESTDIR="$$destdir" && \
|
||||
make clean && make dist || exit 1) || exit 1 ; \
|
||||
mv Distcheck-MCS $(package) ; \
|
||||
tar tzf $(package)/$(package).tar.gz |sed -e 's,/$$,,' |sort >distdist.list ; \
|
||||
rm $(package)/$(package).tar.gz ; \
|
||||
tar tzf $(package).tar.gz |sed -e 's,/$$,,' |sort >before.list ; \
|
||||
find $(package) |egrep -v '(makefrag|response)' |sed -e 's,/$$,,' |sort >after.list ; \
|
||||
cmp before.list after.list || exit 1 ; \
|
||||
cmp before.list distdist.list || exit 1 ; \
|
||||
rm -f before.list after.list distdist.list ; \
|
||||
rm -rf $(package) InstallTest
|
||||
|
||||
monocharge:
|
||||
chargedir=monocharge-`date -u +%Y%m%d` ; \
|
||||
mkdir "$$chargedir" ; \
|
||||
DESTDIR=`cd "$$chargedir" && pwd` ; \
|
||||
$(MAKE) install DESTDIR="$$DESTDIR" || exit 1 ; \
|
||||
tar cvzf "$$chargedir".tgz "$$chargedir" ; \
|
||||
rm -rf "$$chargedir"
|
||||
|
||||
# A bare-bones monocharge.
|
||||
|
||||
monocharge-lite:
|
||||
chargedir=monocharge-lite-`date -u +%Y%m%d` ; \
|
||||
mkdir "$$chargedir" ; \
|
||||
DESTDIR=`cd "$$chargedir" && pwd` ; \
|
||||
$(MAKE) -C mcs install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
$(MAKE) -C class/corlib install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
$(MAKE) -C class/System install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
$(MAKE) -C class/System.XML install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
$(MAKE) -C class/Mono.CSharp.Debugger install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
tar cvzf "$$chargedir".tgz "$$chargedir" ; \
|
||||
rm -rf "$$chargedir"
|
||||
+1
-1
@@ -2,7 +2,7 @@
|
||||
This contains the Mono C# compiler as well as the Mono runtime
|
||||
library.
|
||||
|
||||
See INSTALL.txt for a guide to building and installing mcs.
|
||||
See INSTALL for a guide to building and installing mcs.
|
||||
|
||||
Layout:
|
||||
|
||||
|
||||
@@ -0,0 +1,33 @@
|
||||
|
||||
[1] Building mono + mcs from CVS on *NIX. The Easy Way (tm)
|
||||
-------------------------------------------------------------
|
||||
1. Get mono and mcs from CVS (http://www.go-mono.com/download.html)
|
||||
|
||||
2. Use the script to build mono (mono/doc/mono-build.sh).
|
||||
|
||||
3. Copy the dlls and mcs.exe from the latest monocharge tarball
|
||||
(http://www.gnome-db.org/~gonzalo/mono/) to /where/you/installed/mono/lib and
|
||||
..../bin respectively.
|
||||
|
||||
|
||||
|
||||
[2] Keeping the stuff up to date
|
||||
----------------------------------
|
||||
Once you have followed the above steps, do these ones to keep your installation
|
||||
up to date:
|
||||
|
||||
1. In mcs directory,
|
||||
|
||||
cvs -z3 update -Pd
|
||||
make -f makefile.gnu
|
||||
|
||||
2. Use the mono-build.sh script to update, rebuild and install mono from CVS.
|
||||
Doing a cvs update of mono/doc/mono-build.sh file is also a good idea.
|
||||
|
||||
3. In mcs directory:
|
||||
|
||||
make -f makefile.gnu install prefix=/prefix/of/your/installation/path
|
||||
|
||||
4. In case of troubles (ie, unable to compile mcs/* sources) go to [1].
|
||||
|
||||
-Gonzalo
|
||||
@@ -1,2 +0,0 @@
|
||||
pre-config.make
|
||||
config.make
|
||||
@@ -1,73 +0,0 @@
|
||||
2003-08-03 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* config-default.make: the /nowarn arguments are now set on a per
|
||||
library basis.
|
||||
|
||||
2003-07-29 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* executable.make: install-local depends on the program too.
|
||||
|
||||
2003-07-25 Peter Williams <[email protected]>
|
||||
|
||||
* rules.make (run-test): Make it depend on 'test-local'
|
||||
then 'run-test-local' after 'run-test-recursive'. This way,
|
||||
'make run-test' from the toplevel doesn't recurse through all
|
||||
the directories doing a make test before we run anything.
|
||||
|
||||
2003-07-24 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* rules.make: run-test depends now on 'test'.
|
||||
|
||||
2003-07-24 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* rules.make: set corlib to PLATFORM_CORLIB if this is defined.
|
||||
|
||||
2003-07-22 Peter Williams <[email protected]>
|
||||
|
||||
* rules.make (withmcs): Add this developer utility target.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* README.platforms: Update docs for changes below.
|
||||
|
||||
* platforms/win32.make (PLATFORM_CORLIB): Set this variable
|
||||
to 'mscorlib.dll', instead of $(corlib) which everything links
|
||||
against. *Almost* everything should link against our corlib --
|
||||
with the exception of corlib_cmp and corlib_res.
|
||||
|
||||
* platforms/linux.make: Same here: corlib.dll
|
||||
|
||||
* rules.make: Define $(corlib) here.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* config-default.make (TEST_RUNTIME): Use the platform runtime
|
||||
to run tests, by default.
|
||||
|
||||
* profiles/default.make (TEST_RUNTIME): If our test runtime is
|
||||
mono, use the --debug flag.
|
||||
|
||||
* executable.make (sourcefile): Add a basename so that we can
|
||||
find the nunit sources and so we behave a bit more like
|
||||
library.make
|
||||
|
||||
* config-default.make (TEST_HARNESS): Find nunit-console in its
|
||||
new home.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* library.make ($(response)): Do a "Creating ..." line here.
|
||||
|
||||
* executable.make ($(response)): Same.
|
||||
|
||||
* config-default.make: Make warning more forceful.
|
||||
|
||||
* rules.make: Define a useful 'PLATFORM_MONO_NATIVE' that is
|
||||
set if the platform does not have a native runtime (ie, linux).
|
||||
Also reorder some definitions.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* Created. See ../ChangeLog for entries earlier than
|
||||
this.
|
||||
|
||||
@@ -1,22 +0,0 @@
|
||||
thisdir = build
|
||||
SUBDIRS =
|
||||
include ../build/rules.make
|
||||
|
||||
all-local install-local test-local run-test-local clean-local:
|
||||
|
||||
DISTFILES = \
|
||||
README.makefiles \
|
||||
README.platforms \
|
||||
README.configury \
|
||||
config-default.make \
|
||||
executable.make \
|
||||
library.make \
|
||||
rules.make \
|
||||
platforms/linux.make \
|
||||
platforms/win32.make \
|
||||
profiles/default.make \
|
||||
profiles/atomic.make \
|
||||
profiles/net_1_0.make
|
||||
|
||||
dist-local: dist-default
|
||||
mkdir $(distdir)/deps
|
||||
@@ -1,23 +0,0 @@
|
||||
Configuring the build (-*- outline -*-)
|
||||
Peter Williams <[email protected]>
|
||||
|
||||
** Configuring the build
|
||||
|
||||
It's pretty easy. You can create two files in this directory to tweak
|
||||
settings: pre-config.make and config.make.
|
||||
|
||||
pre-config.make is included before $(PLATFORM).make and
|
||||
$(PROFILE).make, so you can set either of these variables if you want
|
||||
to change the default.
|
||||
|
||||
Just about any other change should go in config.make, which is
|
||||
included after $(PLATFORM).make and $(PROFILE).make, so you can use
|
||||
the values defined in those files if you wish. For example,
|
||||
|
||||
MCS_FLAGS = $(DEFAULT_MCS_FLAGS) /my-experimental-optimizer-flag
|
||||
|
||||
or something.
|
||||
|
||||
(You shouldn't need to edit any of the existing Makefiles for
|
||||
site-specific hacks. CVS would complain at you and `make dist'
|
||||
wouldn't be happy.)
|
||||
@@ -1,736 +0,0 @@
|
||||
The MCS makefiles (-*- outline -*-)
|
||||
Peter Williams <[email protected]>
|
||||
|
||||
The new makefiles try to abstract building on Windows and Linux. They
|
||||
try to provide a consistent set of ways to express the things that our
|
||||
build system needs to let us do, specifically:
|
||||
|
||||
* Build recursively
|
||||
* Build libraries and executables easily
|
||||
* Let developers use different runtimes and class libaries
|
||||
* Make distributions easily
|
||||
* Provide a framework for testing
|
||||
* Build platform-independently whenever possible
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Makefile structure
|
||||
|
||||
A general makefile looks like this:
|
||||
|
||||
========================================
|
||||
thisdir = class/Mono.My.Library
|
||||
SUBDIRS =
|
||||
include ../../build/rules.make
|
||||
|
||||
all-local:
|
||||
do some stuff
|
||||
|
||||
install-local:
|
||||
$(MKINSTALLDIRS) $(DESTDIR)$(prefix)/share/
|
||||
$(INSTALL_DATA) myfile.txt $(DESTDIR)$(prefix)/share/myfiledir
|
||||
|
||||
clean-local:
|
||||
rm -f my-generated-file
|
||||
|
||||
test-local: my_test_program.exe
|
||||
|
||||
run-test-local:
|
||||
$(RUNTIME) my_test_program.exe
|
||||
|
||||
DISTFILES = myfile.txt my_test_source.cs
|
||||
|
||||
dist-local: dist-default
|
||||
|
||||
my_test_program.exe: my_test_source.cs
|
||||
$(CSCOMPILE) /target:exe /out:$@ $<
|
||||
========================================
|
||||
|
||||
Each makefile follows the same pattern: it does some setup, includes
|
||||
the standard make rules, and provides rules for six standard targets:
|
||||
all, install, test, run-test, clean, and dist.
|
||||
|
||||
"Some setup" is defining two variables: $(thisdir) and
|
||||
$(SUBDIRS). $(thisdir) is the directory that the makefile lives in,
|
||||
relative to the top directory (ie, class/corlib) and $(SUBDIRS)
|
||||
defines the subdirectories that should be built in.
|
||||
|
||||
The six targets do the following:
|
||||
|
||||
* all-local builds whatever someone would expect to be built
|
||||
when they just type 'make'. Most likely Foo.dll or Foo.exe
|
||||
|
||||
* install-local installs whatever got built by all-local.
|
||||
|
||||
* test-local _builds_ the test programs or libraries but does
|
||||
_not_ run them.
|
||||
|
||||
* run-test-local actually runs the tests. It shouldn't
|
||||
necessarily exit in an error if the test fails, but should make that
|
||||
situation obvious. It should only run tests that take care of
|
||||
themselves automatically; interactive tests should have an individual
|
||||
target. The idea is that 'make run-test' from the toplevel should be
|
||||
able to proceed unsupervised and test everything that can be tested in
|
||||
such a manner.
|
||||
|
||||
* clean-local removes built files; 'make clean' should leave
|
||||
only files that go into a distribution tarball. (But it is not necessarily
|
||||
true that all files that go into a tarball need to be left after a make clean.)
|
||||
|
||||
* dist-local copies files into the distribution tree, which is
|
||||
given by the variable $(distdir). dist-local always depends on the
|
||||
target 'dist-default'. See ** 'make dist' below.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Build configuration
|
||||
|
||||
In general, MCS needs to be able to build relying only on the
|
||||
existence of a runtime and core libraries (corlib, System,
|
||||
System.Xml). So there shouldn't be any checking for libraries or
|
||||
whatnot; MCS should be able to build out of the box. We try to keep
|
||||
platform detection and feature testing (ie, for HP/UX echo) inside
|
||||
the makefiles; right now, there's no configuration script, and it'd
|
||||
be nice to keep it that way. (I am told that some people build on
|
||||
both Windows and Linux in the same tree, which would be impossible to
|
||||
do if we cached platform-related configury values.)
|
||||
|
||||
That being said, it's very convenient for developers to be able to
|
||||
customize their builds to suit their needs. To allow this, the
|
||||
Makefile rules are set up to allow people to override pretty much any
|
||||
important variable.
|
||||
|
||||
Configuration variables are given defaults in `config-default.make';
|
||||
`rules.make' optionally includes `$(topdir)/build/config.make', so you
|
||||
can customize your build without CVS trying to commit your modified
|
||||
`config-default.make' all the time. Platform-specific variables are
|
||||
defined in `$(topdir)/build/platforms/$(PLATFORM).make', where
|
||||
$(PLATFORM) is detected in config-default.make. (Currently, the only
|
||||
choices are linux.make and win32.make.)
|
||||
|
||||
The best way to learn what the configuration variables are is to read
|
||||
`config.make' and `platform.make'. There aren't too many and hopefully
|
||||
they should be self-explanatory; see the numerous examples below for
|
||||
more information if you're confused.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Recommendations for platform specifics
|
||||
|
||||
If you find yourself needing a platform-specific customization, try
|
||||
and express it in terms of a feature, rather than a platform test. In
|
||||
other words, this is good:
|
||||
|
||||
========================================
|
||||
run-test-local: my-test.exe
|
||||
ifdef PLATFORM_NEEDS_CRAZY_CRAP
|
||||
crazy-crap
|
||||
endif
|
||||
$(RUNTIME) my-test.exe
|
||||
========================================
|
||||
|
||||
and this is bad:
|
||||
|
||||
========================================
|
||||
run-test-local: my-test.exe
|
||||
ifdef WINDOWS
|
||||
crazy-crap
|
||||
else
|
||||
ifdef AMIGA
|
||||
crazy-crap
|
||||
endif
|
||||
endif
|
||||
$(RUNTIME) my-test.exe
|
||||
========================================
|
||||
|
||||
The latter accumulates and gets unpleasant and it sucks. Granted,
|
||||
right now we only have two platforms, so it's not a big deal, but it's
|
||||
good form to get used to and practice. Anyway, take a look at how we
|
||||
do the various corlib building hacks for examples of how we've done
|
||||
platform-specificity. It certainly isn't pretty, but at least it's a
|
||||
little structured.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Saving effort
|
||||
|
||||
The point of the build system is to abstract things and take
|
||||
care of all the easy stuff. So if you find yourself writing a
|
||||
Makefile, know that there's probably already infrastructure to do what
|
||||
you want. Here are all the common cases I can think of ...
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Compiling C# code? use:
|
||||
|
||||
========================================
|
||||
my-program.exe: my-source.cs
|
||||
$(CSCOMPILE) /target:exe /out:$@ $^
|
||||
========================================
|
||||
|
||||
or
|
||||
|
||||
========================================
|
||||
my-lib.dll: my-source.cs
|
||||
$(CSCOMPILE) /target:library /out:$@ $^
|
||||
========================================
|
||||
|
||||
Note the '$@' and '$^' variables. The former means "the name of the
|
||||
file that I am trying to make" and the latter means "all the
|
||||
dependencies of the file I am trying to make." USE THESE VARIABLES
|
||||
AGGRESSIVELY. Say that you add a new source to your program:
|
||||
|
||||
========================================
|
||||
my-program.exe: my-source.cs my-new-source.cs
|
||||
$(CSCOMPILE) /target:exe /out:$@ $^
|
||||
========================================
|
||||
|
||||
Because of the $^ variable, you don't need to remember to add another
|
||||
file to the command line. Similarly, if you rename your program, you
|
||||
won't need to remember to change the rule:
|
||||
|
||||
========================================
|
||||
MonoVaporizer.exe: my-source.cs my-new-source.cs
|
||||
$(CSCOMPILE) /target:exe /out:$@ $^
|
||||
========================================
|
||||
|
||||
will still work. Another useful variable is $<, which means "the first
|
||||
dependency of whatever I'm building." If you order your dependencies
|
||||
carefully it can be extremely useful.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Just building an executable? use:
|
||||
|
||||
========================================
|
||||
PROGRAM = myprogram.exe
|
||||
LOCAL_MCS_FLAGS = /r:System.Xml.dll
|
||||
|
||||
include ../build/executable.make
|
||||
========================================
|
||||
|
||||
executable.make builds a program in the current directory. Its name is
|
||||
held in $(PROGRAM), and its sources are listed in the file
|
||||
$(PROGRAM).sources. It might seem to make more sense to just list the
|
||||
program's sources in the Makefile, but when we build on Windows we
|
||||
need to change slashes around, which is much easier to do if the
|
||||
sources are listed in a file. The variable $(LOCAL_MCS_FLAGS) changes
|
||||
the flags given to the compiler; it is included in $(CSCOMPILE) so you
|
||||
don't need to worry about it.
|
||||
|
||||
executable.make does a lot for you: it builds the program in 'make
|
||||
all-local', installs the program in $(prefix)/bin, distributes the
|
||||
sources, and defines empty test targets. Now, if your program has a
|
||||
test, set the variable HAS_TEST:
|
||||
|
||||
========================================
|
||||
PROGRAM = myprogram.exe
|
||||
LOCAL_MCS_FLAGS = /r:System.Xml.dll
|
||||
HAS_TEST = yes
|
||||
include ../build/executable.make
|
||||
|
||||
test-local: mytester.exe
|
||||
|
||||
run-test-local: mytester.exe
|
||||
$(RUNTIME) $<
|
||||
|
||||
mytester.exe: mytester.cs
|
||||
$(CSCOMPILE) /target:exe /out:$@ mytester.cs
|
||||
========================================
|
||||
|
||||
If your program has 'built sources', that is, source files generated
|
||||
from other files (say, generated by jay), define a variable called
|
||||
BUILT_SOURCES and do *not* list the sources in $(PROGRAM).sources:
|
||||
|
||||
========================================
|
||||
PROGRAM = myprogram.exe
|
||||
LOCAL_MCS_FLAGS = /r:System.Xml.dll
|
||||
BUILT_SOURCES = parser.cs
|
||||
CLEAN_FILES = y.output
|
||||
|
||||
include ../build/executable.make
|
||||
|
||||
parser.cs: parser.jay
|
||||
$(topdir)/jay/jay $< > $@
|
||||
========================================
|
||||
|
||||
executable.make will automatically delete the $(BUILT_SOURCES) files
|
||||
on 'make clean'. Since this situation is a common occurrence and jay
|
||||
happens to leave behind y.output files, you can also define a variable
|
||||
called $(CLEAN_FILES) that lists extra files to be deleted when 'make clean' is
|
||||
called. (That's in addition to your executable and the built sources).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Buildling a library? Use
|
||||
|
||||
========================================
|
||||
LIBRARY = Mono.MyLib.dll
|
||||
LIB_MCS_FLAGS = /unsafe
|
||||
TEST_MCS_FLAGS = /r:System.Xml.dll
|
||||
|
||||
include ../../build/library.make
|
||||
========================================
|
||||
|
||||
Where you library is called $(LIBRARY); it will be put into
|
||||
$(topdir)/class/lib. LIB_MCS_FLAGS is the set of MCS flags to use when
|
||||
compiling the library; in addition, a global set of flags called
|
||||
$(LIBRARY_FLAGS) is added (that variable is defined in
|
||||
config-defaults.make), as well as the usual $(LOCAL_MCS_FLAGS).
|
||||
|
||||
As in executable.make, the sources for your library are listed in
|
||||
$(LIBRARY).sources. Note: these source lists should have Unix forward
|
||||
slashes and Unix newlines (\n, not \r\n.) If you get an error about
|
||||
"touch: need a filename", that means your .sources file doesn't end in
|
||||
a newline. It should.
|
||||
|
||||
Now library.make also assumes that your library has an NUnit2 test
|
||||
harness. The files should be in a subdirectory called Test/, and if
|
||||
your library is called Mono.Foo.dll, they should be listed in
|
||||
Mono.Foo_test.dll.sources. The names in that files should *not* have
|
||||
the Test/ prefix. 'make test' will build Mono.Foo_test.dll in the
|
||||
current directory, automatically supplying the flags to reference the
|
||||
original library and NUnit.Framework.dll.
|
||||
|
||||
If you don't have a test, just do this:
|
||||
|
||||
========================================
|
||||
LIBRARY = Mono.MyLib.dll
|
||||
LIB_MCS_FLAGS = /unsafe
|
||||
NO_TEST = yes
|
||||
|
||||
include ../../build/library.make
|
||||
========================================
|
||||
|
||||
and feel ashamed. Every good library has a test suite!
|
||||
|
||||
Extra flags needed to compile the test library should be listed in
|
||||
$(TEST_MCS_FLAGS); often you will have a line like this:
|
||||
|
||||
========================================
|
||||
TEST_MCS_FLAGS = $(LIB_MCS_FLAGS)
|
||||
========================================
|
||||
|
||||
Again, library.make does a lot for you: it builds the dll, it
|
||||
generates makefile fragments to track the dependencies, it installs
|
||||
the library, it builds the test dll on 'make test', it runs
|
||||
$(TEST_HARNESS) on it on 'make run-test', it removes the appropriate
|
||||
files on 'make clean', and it distributes all the source files on
|
||||
'make dist'. (TEST_HARNESS defaults to be nunit-console.exe but it may
|
||||
be overridden to, say, nunit-gtk). If you have extra files to
|
||||
distribute when using either library.make or executable.make, use the
|
||||
variable $(EXTRA_DISTFILES):
|
||||
|
||||
========================================
|
||||
EXTRA_DISTFILES = \
|
||||
Test/testcase1.in \
|
||||
Test/testcase1.out \
|
||||
README
|
||||
========================================
|
||||
|
||||
Again, library.make and executable.make do the right things so that we
|
||||
can build on Windows, doing some trickery to invert slashes and
|
||||
overcome command-line length limitations. Use them unless you have a
|
||||
really good reason not to. If you're building a bunch of small
|
||||
executables, check out tools/Makefile or tools/security/Makefile; if
|
||||
all the files are in the current directory, changing slashes isn't a
|
||||
big deal, and command-line lengths won't be a problem, so
|
||||
executable.make isn't necessary (and indeed it won't work, since it
|
||||
can only build one .exe in a directory).
|
||||
|
||||
If you're building a library, library.make is highly recommended; the
|
||||
only DLL that doesn't use it is corlib, because building corlib is a
|
||||
fair bit more complicated than it should be. Oh well.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Running a C# program? Use $(RUNTIME)
|
||||
|
||||
========================================
|
||||
run-test-local: myprog.exe
|
||||
$(RUNTIME) myprog.exe
|
||||
========================================
|
||||
|
||||
$(RUNTIME) might be empty (if you're on windows), so don't expect to
|
||||
be able to give it any arguments. If you're on a platform which has an
|
||||
interpreter or jitter, $(RUNTIME_FLAGS) is included in $(RUNTIME), so
|
||||
set that variable.
|
||||
|
||||
$(TEST_RUNTIME) is the runtime to use when running tests. Right now it's
|
||||
just "mono --debug".
|
||||
|
||||
|
||||
|
||||
* Calling the compiler directly? Use $(MCS).
|
||||
|
||||
Really, you should use $(CSCOMPILE) whenever possible, but $(MCS) is
|
||||
out there. $(BOOTSTRAP_MCS) is the C# compiler that we use to build
|
||||
mcs.exe; on Linux, we then use mcs.exe to build everything else, but
|
||||
on Windows, we use csc.exe to build everything. Only use
|
||||
$(BOOTSTRAP_MCS) if you know what you're doing.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Compiling C code? Use $(CCOMPILE)
|
||||
|
||||
To give it flags, set $(LOCAL_CFLAGS). As with compiling C#, the
|
||||
variable $(CFLAGS) will automatically be included on the command line.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Installing files? Use $(MKINSTALLDIRS), $(INSTALL_DATA) or
|
||||
$(INSTALL_BIN), $(prefix), and $(DESTDIR).
|
||||
|
||||
Every time a file is installed the commands should look like this:
|
||||
|
||||
========================================
|
||||
install-local:
|
||||
$(MKINSTALLDIRS) $(DESTDIR)$(prefix)/my/dir
|
||||
$(INSTALL_DATA) myfile $(DESTDIR)$(prefix)/my/dir
|
||||
========================================
|
||||
|
||||
This way the directory is created recursively if needed (admittedly, we could
|
||||
probably rely on mkdir -p), the file is given the correct permissions,
|
||||
the user can override $(MKINSTALLDIRS) and $(INSTALL) if they need to,
|
||||
and we can support $(DESTDIR) installs. We use $(DESTDIR) to make
|
||||
monocharge tarballs, and it's useful otherwise, so try and use it
|
||||
consistently.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* 'make dist'? Use $(DISTFILES)
|
||||
|
||||
The 'dist-default' target will copy the files listed in $(DISTFILES)
|
||||
into the distribution directory, as well as Makefile and ChangeLog if
|
||||
they exist. This is almost always all that you need, so ideally your
|
||||
make dist support should only be:
|
||||
|
||||
========================================
|
||||
DISTFILES = README Test/thoughts.txt
|
||||
|
||||
dist-local: dist-default
|
||||
========================================
|
||||
|
||||
DISTFILES will cope correctly with files in subdirectories, by the
|
||||
way. Note that if you put a nonexistant file or a directory in
|
||||
DISTFILES it will *not* complain; it will just ignore it.
|
||||
|
||||
If you want to test your 'make dist' code, you can try
|
||||
|
||||
========================================
|
||||
$ cd class/Mono.MyClass
|
||||
$ make dist-local distdir=TEST
|
||||
========================================
|
||||
|
||||
And your files should be copied into TEST/ in the current directory.
|
||||
There is a toplevel 'make distcheck' target, which will build a dist
|
||||
tarball, try to build it, install files to a temporary prefix, make
|
||||
clean it, make a distribution, and compare the files left over to the
|
||||
files originally in the tarball: they should be the same. But this
|
||||
takes about 15 minutes to run on my 1.1 Ghz computer, so it's not for
|
||||
the faint of heart.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Lots of files? Use $(wildcard *.foo)
|
||||
|
||||
When specifying the sources to a library or executable, wildcards are
|
||||
not encouraged; in fact they're not allowed if you use library.make or
|
||||
executable.make. But there are times when they're useful, eg:
|
||||
|
||||
========================================
|
||||
DISTFILES = $(wildcard Test/*.in) $(wildcard Test/*.out)
|
||||
========================================
|
||||
|
||||
Just so you know that 'make' has this feature.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Referencing files in other directories? Use $(topdir).
|
||||
|
||||
$(topdir) is the path to the top directory from the current build
|
||||
directory. Basically it's a sequence of ../.. computed from the value
|
||||
that you give $(thisdir) at the top of your Makefile. Try to reference
|
||||
things from $(topdir), so your code can be moved or cut-and-pasted
|
||||
around with a minimum of fuss.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Conditional building? Use ifdef/ifndef/endif
|
||||
|
||||
Now in general we want to avoid conditional building, but sometimes
|
||||
something doesn't work on Linux or already exists on Windows or
|
||||
whatnot. (See below on recommended form for how to build
|
||||
platform-specifically.) GNU Make supports the following construction:
|
||||
|
||||
========================================
|
||||
BUILD_EXPERIMENTAL = yes
|
||||
|
||||
ifdef BUILD_EXPERIMENTAL
|
||||
experimental_stuff = my-experiment.exe
|
||||
else
|
||||
experimental_stuff =
|
||||
endif
|
||||
|
||||
all-local: my-sane.exe $(experimental_stuff)
|
||||
========================================
|
||||
|
||||
'ifdef' means 'if the variable is set to nonempty', so you could have
|
||||
|
||||
========================================
|
||||
BUILD_EXPERIMENTAL = colorless green ideas sleep furiously
|
||||
========================================
|
||||
|
||||
and Make would be happy. I hope that the meaning of 'ifndef' should be
|
||||
obvious. If you want to only sometimes build a target, the above
|
||||
construction is the recommended way to go about it; it's nice to have
|
||||
the rules exist in a Makefile even if they aren't invoked.
|
||||
|
||||
If you want to see why conditionals aren't nice, take a look at
|
||||
library.make or class/corlib/Makefile.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* 'Private' directories that shouldn't be built by default? Use DIST_ONLY_SUBDIRS
|
||||
|
||||
Several of the MCS class libraries have demo or experimental
|
||||
implementations that depend on things not included with MCS (say,
|
||||
Gtk#). We don't want to build them by default, because the user might
|
||||
not have those dependencies installed, but it's nice to have a
|
||||
Makefile for them to be built nicely.
|
||||
|
||||
First of all, there's nothing stopping you from writing a Makefile for
|
||||
such a directory; just don't put it in the SUBDIRS line of its parent
|
||||
directory. That way, you can do all the normal build things like 'make
|
||||
all' or 'make clean' in that directory, but people trying to bootstrap
|
||||
their system won't run into problems.
|
||||
|
||||
At the same time you probably want to include this directory in the
|
||||
distribution so that people can use your demo or experimental code if
|
||||
they know what they're doing. Hence the variable
|
||||
$(DIST_ONLY_SUBDIRS). As you might guess, it's like the SUBDIRS
|
||||
variable: it lists subdirectories that a regular shouldn't recurse
|
||||
into, but should have their 'make dist' rules invoked.
|
||||
|
||||
Say you've written Mono.MyFancyLib.dll and you have
|
||||
a demo app using Gtk# called MyFancyDemo. The Makefile rules might
|
||||
look like this:
|
||||
|
||||
class/Mono.MyFancyLib/Makefile
|
||||
========================================
|
||||
thisdir = class/Mono.MyFancyLib
|
||||
SUBDIRS =
|
||||
DIST_ONLY_SUBDIRS = MyFancyDemo
|
||||
include ../../build/rules.make
|
||||
|
||||
LIBRARY = Mono.MyFancyLib.dll
|
||||
LIB_MCS_FLAGS = /r:System.dll
|
||||
TEST_MCS_FLAGS = $(LIB_MCS_FLAGS)
|
||||
|
||||
include ../../build/library.make
|
||||
========================================
|
||||
|
||||
class/Mono.MyFancyLib/MyFancyDemo/Makefile
|
||||
========================================
|
||||
thisdir = class/Mono.MyFancyLib/MyFancyDemo
|
||||
SUBDIRS =
|
||||
include ../../../build/rules.make
|
||||
|
||||
PROGRAM = FancyDemo.exe
|
||||
LOCAL_MCS_FLAGS = /r:gtk-sharp.dll
|
||||
|
||||
include ../../../build/executable.make
|
||||
========================================
|
||||
|
||||
|
||||
|
||||
|
||||
* Special recursion needs? Use OVERRIDE_BARE_TARGETS
|
||||
|
||||
By default, rules.make defines the all, install, clean, etc. targets
|
||||
to look something like this:
|
||||
|
||||
all: all-recursive all-local
|
||||
|
||||
Sometimes that doesn't cut it; say for example you want to check for
|
||||
something before doing a lengthy recursive build (see
|
||||
$(topdir)/Makefile) or you have a something like this
|
||||
|
||||
class/MyLibrary:
|
||||
Build MyLibrary.dll
|
||||
class/MyLibrary/Test:
|
||||
Build TestMyLibrary.exe
|
||||
|
||||
'make clean test' will fail here, because the build will happen in
|
||||
the Test subdirectory first, so there will be no MyLibrary.dll to link
|
||||
against. (Unless you write a nasty evil relative path rule which is
|
||||
strongly discouraged.)
|
||||
|
||||
Anyway, to solve this problem you can do
|
||||
|
||||
========================================
|
||||
OVERRIDE_BARE_TARGETS = yes
|
||||
thisdir = class/MyLibrary
|
||||
SUBDIRS = Test
|
||||
include ../../build/rules.make
|
||||
|
||||
# This is normally "all-recursive all-local"
|
||||
all: all-local all-recursive
|
||||
|
||||
test: test-local test-recursive
|
||||
...
|
||||
========================================
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** A few implementation details
|
||||
|
||||
The way rules.make does its recursion is very standard; it maps
|
||||
{all,install,clean, dist,test} to $@-recursive, which executes that
|
||||
rule in each directory in $(SUBDIRS), and then calls $@-local in the
|
||||
current directory. So something that gets built in a subdirectory
|
||||
cannot rely on something that gets built in its parent directory. If
|
||||
this is a problem, see the bit about using OVERRIDE_BARE_TARGETS;
|
||||
since the recursive rules do $(MAKE) $* in their subdirectories,
|
||||
changing the 'all' target will do the right thing in a recursive
|
||||
build. Note that the recursive rule for 'dist' is different; it makes
|
||||
dist-recursive in subdirectories, so you at least have to define that
|
||||
rule, even if you use OVERRIDE_BARE_TARGETS.
|
||||
|
||||
Note that even a directory that doesn't, for example, have any tests
|
||||
must still define test-local; otherwise 'make test' run from the
|
||||
toplevel directory will break.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Flags for Tools
|
||||
|
||||
We want to make it so that the user can specify certain flags to
|
||||
always be given to a tool, so there's a general way of implementing
|
||||
FLAGS variables:
|
||||
|
||||
* $(foo_FLAGS) remains unset or defaulted to something
|
||||
sensible; the user can provide overrides this way.
|
||||
|
||||
* $(LOCAL_foo_FLAGS) is set in a specific Makefile to
|
||||
provide necessary values.
|
||||
|
||||
* $(PLATFORM_foo_FLAGS) is set in the platform configuration
|
||||
to provide platform-specific values.
|
||||
|
||||
* $(PROFILE_foo_FLAGS) is set in the profile configuration
|
||||
to provide profile-specific values.
|
||||
|
||||
* $(USE_foo_FLAGS) is defined to be the combination of all of
|
||||
the above, and it's what is actually passed to $(foo).
|
||||
|
||||
$(MCS_FLAGS) and $(CFLAGS) follow this model. If you end up finding
|
||||
that another tool is used commonly (hm, jay...), please follow this form.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Portability tips
|
||||
|
||||
Always use the icky Windows /argument way of passing parameters to the C#
|
||||
compiler so that csc can be used.
|
||||
|
||||
Always use /r:foo.dll, not /r:foo. Windows requires the former.
|
||||
|
||||
Use /r:$(corlib), not /r:corlib. Windows wants mscorlib.dll and Linux
|
||||
wants corlib.dll; eventually, the Mono runtime is supposed to accept
|
||||
mscorlib.dll too, but in the meantime, use the variable.
|
||||
|
||||
If you're writing shell script code as part of a make rule, remember
|
||||
that Windows has command-line length limits. So something like
|
||||
|
||||
========================================
|
||||
mytool $(all_the_sources_to_corlib)
|
||||
========================================
|
||||
|
||||
Is probably going to cause problems. As I understand it,
|
||||
|
||||
========================================
|
||||
for f in $(all_the_sources_to_corlib) ; do ...
|
||||
========================================
|
||||
|
||||
is ok, since the shell itself doesn't have those limitations. Other
|
||||
than that, you should still try to write fairly portable shell
|
||||
script. Linux and Cygwin both use the GNU utilities, but there's at
|
||||
least one hardy soul trying to build Mono on HP/UX, and no doubt there
|
||||
will be ports to more Unices as time goes on.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Misc
|
||||
|
||||
We still don't use /d:NET_1_1 ; it causes some build problems right
|
||||
now.
|
||||
|
||||
There's a hack in class/System.Data/Makefile to work around a very
|
||||
strange crash in the runtime with some custom attribute stuff. It'd be
|
||||
nice to fix it.
|
||||
|
||||
Also, there's a /lib:$(prefix)/lib in the System.dll Makefile, which
|
||||
is for some reason necessary if System.Xml.dll hasn't been built yet.
|
||||
(Well, it's necessary because of the /r:System.Xml.dll, but that
|
||||
should be in the search path, it seems.)
|
||||
|
||||
A lot of the weird targets in the old makefiles have been dropped; I
|
||||
have a feeling that a lot of them are archaic and not needed anymore.
|
||||
|
||||
I'd really like to write a build tool in C#. It would be nice to have
|
||||
something really extensible and well-designed and clean. NAnt is,
|
||||
IMHO, an apalling abomination and a tragically bad attempt at solving
|
||||
the software building problem. Just so you know.
|
||||
|
||||
(On the other hand, NUnit is really neat.)
|
||||
|
||||
Peter
|
||||
@@ -1,41 +0,0 @@
|
||||
A platform makefile should define the following variables:
|
||||
|
||||
PLATFORM_DEBUG_FLAGS
|
||||
The flags to pass to the C# compiler to generate appropriate
|
||||
debug information
|
||||
|
||||
PLATFORM_MCS_FLAGS
|
||||
Flags that are always passed to the C# compiler
|
||||
|
||||
PLATFORM_RUNTIME
|
||||
The system runtime for executing CLR programs. Blank on Win32,
|
||||
probably $(RUNTIME) (the Mono runtime) on everything else.
|
||||
|
||||
PLATFORM_CORLIB
|
||||
The name of the system's corlib. 'mscorlib.dll' for windows,
|
||||
corlib.dll for mono-based.
|
||||
|
||||
PLATFORM_MAKE_CORLIB_CMP
|
||||
Define it to something nonempty if corlib_cmp.dll should be built
|
||||
on this platform. Only should be done if the platform provides its
|
||||
own non-Mono runtime that we can compare corlibs with.
|
||||
|
||||
PLATFORM_TWEAK_CORLIB_SOURCES
|
||||
A command to futz around with the sources to corlib.dll. See linux.make
|
||||
and win32.make for examples. Should be 'cat' unless you know what you're
|
||||
doing.
|
||||
|
||||
PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
A command to change filename separators given on stdin. Leave undefined
|
||||
if Unixy filenames will work. See win32.make.
|
||||
|
||||
BOOTSTRAP_MCS
|
||||
The C# compiler used to compile mcs/mcs.exe, and possibly other
|
||||
assemblies if the user is doing a standalone build (that is, not
|
||||
a bootstrap).
|
||||
|
||||
hidden_prefix, hidden_suffix
|
||||
Prefix and suffix for hidden/temporary files. Unused right now, I think.
|
||||
|
||||
platform-check:
|
||||
A target to make sure that we can build on this platform.
|
||||
@@ -1,38 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# This makefile fragment has (default) configuration
|
||||
# settings for building MCS.
|
||||
|
||||
# DO NOT EDIT THIS FILE! Create config.make and override settings
|
||||
# there.
|
||||
|
||||
RUNTIME_FLAGS =
|
||||
TEST_HARNESS = $(topdir)/class/lib/nunit-console.exe
|
||||
MCS_FLAGS = $(PLATFORM_DEBUG_FLAGS)
|
||||
LIBRARY_FLAGS = /noconfig
|
||||
CFLAGS = -g -O2
|
||||
INSTALL = /usr/bin/install
|
||||
RUNTIME = mono $(RUNTIME_FLAGS)
|
||||
TEST_RUNTIME=$(PLATFORM_RUNTIME)
|
||||
prefix = /usr/local
|
||||
|
||||
# In case you want to add MCS_FLAGS, this lets you not have to
|
||||
# keep track of the default value
|
||||
|
||||
DEFAULT_MCS_FLAGS := $(MCS_FLAGS)
|
||||
|
||||
# Not all echos are alike. HP/UX doesn't need a -e command.
|
||||
# Test for this here
|
||||
|
||||
ifeq ($(shell echo -e foo),foo)
|
||||
ECHO_ESCAPE=echo -e
|
||||
else
|
||||
ECHO_ESCAPE=echo
|
||||
endif
|
||||
|
||||
# You shouldn't need to set these but might on a
|
||||
# weird platform.
|
||||
|
||||
# CC = cc
|
||||
# SHELL = /bin/sh
|
||||
# MAKE = gmake
|
||||
@@ -1,3 +0,0 @@
|
||||
*.makefrag
|
||||
*.response
|
||||
*.stamp
|
||||
Whitespace-only changes.
@@ -1,73 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# The rules for building a program.
|
||||
|
||||
# I'd rather not create a response file here,
|
||||
# but since on Win32 we need to munge the paths
|
||||
# anyway, we might as well.
|
||||
|
||||
base_prog = $(shell basename $(PROGRAM))
|
||||
sourcefile = $(base_prog).sources
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
response = $(depsdir)/$(base_prog).response
|
||||
else
|
||||
response = $(sourcefile)
|
||||
endif
|
||||
stampfile = $(depsdir)/$(base_prog).stamp
|
||||
makefrag = $(depsdir)/$(base_prog).makefrag
|
||||
pdb = $(patsubst %.exe,%.pdb,$(PROGRAM))
|
||||
|
||||
all-local: $(PROGRAM)
|
||||
|
||||
install-local: $(PROGRAM)
|
||||
$(MKINSTALLDIRS) $(DESTDIR)$(prefix)/bin
|
||||
$(INSTALL_BIN) $(PROGRAM) $(DESTDIR)$(prefix)/bin
|
||||
|
||||
clean-local:
|
||||
-rm -f *.exe $(BUILT_SOURCES) $(CLEAN_FILES) $(pdb) $(stampfile) $(makefrag)
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
-rm -f $(response)
|
||||
endif
|
||||
|
||||
ifndef HAS_TEST
|
||||
test-local: $(PROGRAM)
|
||||
|
||||
run-test-local:
|
||||
endif
|
||||
|
||||
DISTFILES = $(sourcefile) $(EXTRA_DISTFILES)
|
||||
|
||||
dist-local: dist-default
|
||||
for f in `cat $(sourcefile)` ; do \
|
||||
dest=`dirname $(distdir)/$$f` ; \
|
||||
$(MKINSTALLDIRS) $$dest && cp $$f $$dest || exit 1 ; \
|
||||
done
|
||||
|
||||
# Changing makefile probably means changing the
|
||||
# sources, so let's be safe and add a Makefile dep
|
||||
|
||||
$(PROGRAM): $(makefrag) $(response) $(stampfile)
|
||||
$(CSCOMPILE) /target:exe /out:$@ $(BUILT_SOURCES) @$(response)
|
||||
|
||||
$(makefrag): $(sourcefile)
|
||||
@echo Creating $@ ...
|
||||
@echo "HAVE_MAKEFRAG = yes" >[email protected]
|
||||
@echo "$(stampfile): $(BUILT_SOURCES) \\" >>[email protected]
|
||||
@cat $< |sed -e 's,\.cs[ \t]*$$,\.cs \\,' >>[email protected]
|
||||
@cat [email protected] |sed -e '$$s, \\$$,,' >$@
|
||||
@$(ECHO_ESCAPE) "\ttouch \$$@" >>$@
|
||||
@rm -rf [email protected]
|
||||
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
$(response): $(sourcefile)
|
||||
@echo Creating $@ ...
|
||||
@cat $< |$(PLATFORM_CHANGE_SEPARATOR_CMD) >$@
|
||||
endif
|
||||
|
||||
-include $(makefrag)
|
||||
|
||||
ifndef HAVE_MAKEFRAG
|
||||
$(stampfile):
|
||||
touch $@
|
||||
endif
|
||||
|
||||
@@ -1,132 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# The rules for building our class libraries.
|
||||
#
|
||||
# The NO_TEST stuff is not too pleasant but whatcha
|
||||
# gonna do.
|
||||
|
||||
# All the dep files now land in the same directory so we
|
||||
# munge in the library name to keep the files from clashing.
|
||||
|
||||
sourcefile = $(LIBRARY).sources
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
response = $(depsdir)/$(LIBRARY).response
|
||||
else
|
||||
response = $(sourcefile)
|
||||
endif
|
||||
makefrag = $(depsdir)/$(LIBRARY).makefrag
|
||||
stampfile = $(depsdir)/$(LIBRARY).stamp
|
||||
the_lib = $(topdir)/class/lib/$(LIBRARY)
|
||||
the_pdb = $(patsubst %.dll,%.pdb,$(the_lib))
|
||||
|
||||
ifndef NO_TEST
|
||||
test_lib = $(patsubst %.dll,%_test.dll,$(LIBRARY))
|
||||
test_pdb = $(patsubst %.dll,%.pdb,$(test_lib))
|
||||
test_sourcefile = $(test_lib).sources
|
||||
test_response = $(depsdir)/$(test_lib).response
|
||||
test_makefrag = $(depsdir)/$(test_lib).makefrag
|
||||
test_stampfile = $(depsdir)/$(test_lib).stamp
|
||||
test_flags = /r:$(the_lib) /r:$(topdir)/class/lib/NUnit.Framework.dll $(TEST_MCS_FLAGS)
|
||||
endif
|
||||
|
||||
all-local: $(the_lib)
|
||||
|
||||
install-local: $(the_lib)
|
||||
$(MKINSTALLDIRS) $(DESTDIR)$(prefix)/lib
|
||||
$(INSTALL_LIB) $(the_lib) $(DESTDIR)$(prefix)/lib
|
||||
|
||||
clean-local:
|
||||
-rm -f $(the_lib) $(makefrag) $(test_lib) \
|
||||
$(test_makefrag) $(test_response) \
|
||||
$(stampfile) $(test_stampfile) \
|
||||
$(the_pdb) $(test_pdb) \
|
||||
TestResult.xml
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
-rm -rf $(response)
|
||||
endif
|
||||
|
||||
ifndef NO_TEST
|
||||
test-local: $(the_lib) $(test_lib)
|
||||
|
||||
run-test-local:
|
||||
$(TEST_RUNTIME) $(TEST_HARNESS) $(test_lib)
|
||||
|
||||
else
|
||||
test-local: $(the_lib)
|
||||
|
||||
run-test-local:
|
||||
endif
|
||||
|
||||
DISTFILES = $(sourcefile) $(test_sourcefile) $(EXTRA_DISTFILES)
|
||||
|
||||
ifdef NO_TEST
|
||||
TEST_FILES =
|
||||
else
|
||||
TEST_FILES = `cat $(test_sourcefile) |sed -e 's,^\(.\),Test/\1,'`
|
||||
endif
|
||||
|
||||
dist-local: dist-default
|
||||
for f in `cat $(sourcefile)` $(TEST_FILES) ; do \
|
||||
dest=`dirname $(distdir)/$$f` ; \
|
||||
$(MKINSTALLDIRS) $$dest && cp $$f $$dest || exit 1 ; \
|
||||
done
|
||||
|
||||
# Fun with dependency tracking
|
||||
|
||||
$(the_lib): $(makefrag) $(stampfile) $(response)
|
||||
$(CSCOMPILE) $(LIBRARY_FLAGS) $(LIB_MCS_FLAGS) /target:library /out:$@ @$(response)
|
||||
|
||||
$(makefrag): $(sourcefile)
|
||||
@echo Creating $@ ...
|
||||
@echo "HAVE_MAKEFRAG = yes" >[email protected]
|
||||
@echo "$(stampfile): \\" >>[email protected]
|
||||
@cat $< |sed -e 's,\.cs[ \t]*$$,\.cs \\,' >>[email protected]
|
||||
@cat [email protected] |sed -e '$$s, \\$$,,' >$@
|
||||
@$(ECHO_ESCAPE) "\ttouch \$$@" >>$@
|
||||
@rm -rf [email protected]
|
||||
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
$(response): $(sourcefile)
|
||||
@echo Creating $@ ...
|
||||
@cat $< |$(PLATFORM_CHANGE_SEPARATOR_CMD) >$@
|
||||
endif
|
||||
|
||||
-include $(makefrag)
|
||||
|
||||
ifndef HAVE_MAKEFRAG
|
||||
$(stampfile):
|
||||
touch $@
|
||||
endif
|
||||
|
||||
# for now, don't give any /lib flags or set MONO_PATH, since we
|
||||
# give a full path to the assembly.
|
||||
|
||||
ifndef NO_TEST
|
||||
$(test_lib): $(test_makefrag) $(the_lib) $(test_response) $(test_stampfile)
|
||||
$(CSCOMPILE) /target:library /out:$@ $(test_flags) @$(test_response)
|
||||
|
||||
$(test_response): $(test_sourcefile)
|
||||
@echo Creating $@ ...
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
@cat $< |sed -e 's,^\(.\),Test/\1,' |$(PLATFORM_CHANGE_SEPARATOR_CMD) >$@
|
||||
else
|
||||
@cat $< |sed -e 's,^\(.\),Test/\1,' >$@
|
||||
endif
|
||||
|
||||
$(test_makefrag): $(test_response)
|
||||
@echo Creating $@ ...
|
||||
@echo "HAVE_TEST_MAKEFRAG = yes" >[email protected]
|
||||
@echo "$(test_stampfile): \\" >>[email protected]
|
||||
@cat $< |sed -e 's,\.cs[ \t]*$$,\.cs \\,' >>[email protected]
|
||||
@cat [email protected] |sed -e '$$s, \\$$,,' >$@
|
||||
@$(ECHO_ESCAPE) "\ttouch \$$@" >>$@
|
||||
@rm -rf [email protected]
|
||||
|
||||
-include $(test_makefrag)
|
||||
endif
|
||||
|
||||
ifndef HAVE_TEST_MAKEFRAG
|
||||
$(test_stampfile):
|
||||
touch $@
|
||||
endif
|
||||
|
||||
@@ -1,44 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# Platform-specific makefile rules. This one's for linux.
|
||||
#
|
||||
|
||||
PLATFORM_DEBUG_FLAGS = -g
|
||||
PLATFORM_MCS_FLAGS =
|
||||
PLATFORM_RUNTIME = $(RUNTIME)
|
||||
PLATFORM_CORLIB = corlib.dll
|
||||
|
||||
BOOTSTRAP_MCS = mcs
|
||||
|
||||
# Define this if this ever will work on Linux
|
||||
# PLATFORM_MAKE_CORLIB_CMP = yes
|
||||
|
||||
# This is for the security permission attribute problem
|
||||
# on windows
|
||||
PLATFORM_TWEAK_CORLIB_SOURCES = cat
|
||||
|
||||
# This is for changing / to \ on windows
|
||||
# Don't define it so we don't needlessly copy the sources
|
||||
# file. This command is handy for testing:
|
||||
#
|
||||
# PLATFORM_CHANGE_SEPARATOR_CMD=sed -e 's,/,/./,g'
|
||||
|
||||
hidden_prefix = .
|
||||
hidden_suffix =
|
||||
|
||||
platform-check:
|
||||
@if ! type $(BOOTSTRAP_MCS) >/dev/null 2>&1 ; then \
|
||||
echo "*** You need a C# compiler installed to build MCS." ; \
|
||||
echo "*** Read README.building for information on how to bootstrap" ; \
|
||||
echo "*** a Mono installation." ; \
|
||||
exit 1 ; \
|
||||
fi
|
||||
|
||||
|
||||
# I tried this but apparently Make's version strings aren't that
|
||||
# ... consistent between releases. Whatever.
|
||||
#
|
||||
# @if ! $(MAKE) --version |grep '^GNU Make version 3' 1>/dev/null 2>&1 ; then \
|
||||
# echo "*** You need to build MCS with GNU make. Try \`gmake'" ; \
|
||||
# exit 1 ; \
|
||||
# fi
|
||||
@@ -1,21 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# Win32 platform-specific makefile rules.
|
||||
#
|
||||
|
||||
PLATFORM_DEBUG_FLAGS = /debug+ /debug:full
|
||||
PLATFORM_MCS_FLAGS = /nologo /optimize
|
||||
PLATFORM_RUNTIME =
|
||||
PLATFORM_CORLIB = mscorlib.dll
|
||||
|
||||
BOOTSTRAP_MCS = csc.exe
|
||||
MCS = $(BOOTSTRAP_MCS)
|
||||
|
||||
PLATFORM_MAKE_CORLIB_CMP = yes
|
||||
PLATFORM_TWEAK_CORLIB_SOURCES=cat - corlib.dll.win32-excludes |sort |uniq -u
|
||||
PLATFORM_CHANGE_SEPARATOR_CMD=tr '/' '\\\\'
|
||||
|
||||
hidden_prefix =
|
||||
hidden_suffix = .tmp
|
||||
|
||||
platform-check:
|
||||
@@ -1,38 +0,0 @@
|
||||
# -*- Makefile -*-
|
||||
#
|
||||
# The 'atomic' profile.
|
||||
|
||||
# In this profile we compile everything relative to the already-installed
|
||||
# runtime, so we use the bootstrap (external) compiler for everything and
|
||||
# don't set MONO_PATH.
|
||||
#
|
||||
# (So the libraries are compiled and installed atomically, not incrementally.)
|
||||
|
||||
MCS = $(BOOTSTRAP_MCS)
|
||||
|
||||
# Causes some build errors
|
||||
#PROFILE_MCS_FLAGS = /d:NET_1_1 /lib:$(prefix)/lib
|
||||
|
||||
# Get our installed libraries (an issue on windows)
|
||||
|
||||
PROFILE_MCS_FLAGS = /lib:$(prefix)/lib
|
||||
|
||||
# Check that installed libraries even exist.
|
||||
|
||||
profile-check:
|
||||
@if test '!' -f $(prefix)/lib/I18N.dll ; then \
|
||||
echo ; \
|
||||
echo "$(prefix)/lib/I18N.dll does not exist." ; \
|
||||
echo ; \
|
||||
echo "This probably means that you are building from a miniature" ; \
|
||||
echo "distribution of MCS or don't yet have an installed MCS at all." ; \
|
||||
echo "The current build profile needs a complete installation of" ; \
|
||||
echo "MCS to build against; you need to build using the default" ; \
|
||||
echo "profile. Use this command:" ; \
|
||||
echo ; \
|
||||
echo " $(MAKE) PROFILE=default" ; \
|
||||
echo ; \
|
||||
exit 1 ; \
|
||||
fi
|
||||
|
||||
# Exciting, no?
|
||||
@@ -1,28 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# The default 'bootstrap' profile -- builds so that we link against
|
||||
# the libraries as we build them.
|
||||
#
|
||||
# We use the platform's native C# runtime and compiler if possible.
|
||||
|
||||
# Note that we have sort of confusing terminology here; BOOTSTRAP_MCS
|
||||
# is what allows us to bootstrap ourselves, but when we are bootstrapping,
|
||||
# we use INTERNAL_MCS.
|
||||
|
||||
# When bootstrapping, compile against our new assemblies.
|
||||
# (MONO_PATH doesn't just affect what assemblies are loaded to
|
||||
# run the compiler; /r: flags are by default loaded from whatever's
|
||||
# in the MONO_PATH too).
|
||||
|
||||
ifdef PLATFORM_MONO_NATIVE
|
||||
MCS = MONO_PATH="$(topdir)/class/lib:$$MONO_PATH" $(INTERNAL_MCS)
|
||||
TEST_RUNTIME = MONO_PATH=".:$$MONO_PATH" $(RUNTIME) --debug
|
||||
else
|
||||
MCS = $(PLATFORM_RUNTIME) $(BOOTSTRAP_MCS) /lib:$(topdir)/class/lib
|
||||
endif
|
||||
|
||||
# nuttzing!
|
||||
|
||||
profile-check:
|
||||
|
||||
PROFILE_MCS_FLAGS = -d:NET_1_1
|
||||
@@ -1,29 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# The default 'bootstrap' profile -- builds so that we link against
|
||||
# the libraries as we build them.
|
||||
#
|
||||
# We use the platform's native C# runtime and compiler if possible.
|
||||
|
||||
# Note that we have sort of confusing terminology here; BOOTSTRAP_MCS
|
||||
# is what allows us to bootstrap ourselves, but when we are bootstrapping,
|
||||
# we use INTERNAL_MCS.
|
||||
|
||||
# When bootstrapping, compile against our new assemblies.
|
||||
# (MONO_PATH doesn't just affect what assemblies are loaded to
|
||||
# run the compiler; /r: flags are by default loaded from whatever's
|
||||
# in the MONO_PATH too).
|
||||
|
||||
ifdef PLATFORM_MONO_NATIVE
|
||||
MCS = MONO_PATH="$(topdir)/class/lib:$$MONO_PATH" $(INTERNAL_MCS)
|
||||
TEST_RUNTIME = MONO_PATH=".:$$MONO_PATH" $(RUNTIME) --debug
|
||||
else
|
||||
MCS = $(PLATFORM_RUNTIME) $(BOOTSTRAP_MCS) /lib:$(topdir)/class/lib
|
||||
endif
|
||||
|
||||
# nuttzing!
|
||||
|
||||
profile-check:
|
||||
|
||||
# Causes some build errors
|
||||
PROFILE_MCS_FLAGS = -d:GENERICS -d:NET_1_1
|
||||
@@ -1,15 +0,0 @@
|
||||
# -*- Makefile -*-
|
||||
#
|
||||
# Only build .NET 1.0 classes.
|
||||
#
|
||||
# If we want to combine this with, say, the atomic profile,
|
||||
# we should create 'atomic-net_1_0.make' which includes both.
|
||||
#
|
||||
# Ideally you could say 'make PROFILE="bootstrap net_1_0"' but
|
||||
# that would be pretty hard to code.
|
||||
|
||||
include $(topdir)/build/profiles/default.make
|
||||
|
||||
PROFILE_MCS_FLAGS = /d:NET_1_0
|
||||
|
||||
# done
|
||||
@@ -1,145 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# This is the makefile fragment with default rules
|
||||
# for building things in MCS
|
||||
#
|
||||
# To customize the build, you should edit config.make.
|
||||
# If you need to edit this file, that's a bug; email
|
||||
# [email protected] about it.
|
||||
|
||||
# Some more variables. The leading period in the sed expression prevents
|
||||
# thisdir = . from being changed into '..' for the toplevel directory.
|
||||
|
||||
dots := $(shell echo $(thisdir) |sed -e 's,[^./][^/]*,..,g')
|
||||
topdir := $(dots)
|
||||
|
||||
VERSION = 0.26.99
|
||||
|
||||
USE_MCS_FLAGS = $(LOCAL_MCS_FLAGS) $(PLATFORM_MCS_FLAGS) $(PROFILE_MCS_FLAGS) $(MCS_FLAGS)
|
||||
USE_CFLAGS = $(LOCAL_CFLAGS) $(CFLAGS)
|
||||
CSCOMPILE = $(MCS) $(USE_MCS_FLAGS)
|
||||
CCOMPILE = $(CC) $(USE_CFLAGS)
|
||||
BOOT_COMPILE = $(BOOTSTRAP_MCS) $(USE_MCS_FLAGS)
|
||||
INSTALL_DATA = $(INSTALL) -m 644
|
||||
INSTALL_BIN = $(INSTALL) -m 755
|
||||
INSTALL_LIB = $(INSTALL_BIN)
|
||||
MKINSTALLDIRS = $(SHELL) $(topdir)/mkinstalldirs
|
||||
INTERNAL_MCS = $(RUNTIME) $(topdir)/mcs/mcs.exe
|
||||
corlib = corlib.dll
|
||||
|
||||
depsdir = $(topdir)/build/deps
|
||||
distdir = $(dots)/$(package)/$(thisdir)
|
||||
|
||||
# Make sure these propagate if set manually
|
||||
|
||||
export PLATFORM
|
||||
export PROFILE
|
||||
export MCS
|
||||
export MCS_FLAGS
|
||||
export CC
|
||||
export CFLAGS
|
||||
export INSTALL
|
||||
export MKINSTALLDIRS
|
||||
export TEST_HARNESS
|
||||
export BOOTSTRAP_MCS
|
||||
export DESTDIR
|
||||
|
||||
# Get this so the platform.make platform-check rule doesn't become the
|
||||
# default target
|
||||
|
||||
default: all
|
||||
|
||||
# Get initial configuration. pre-config is so that the builder can
|
||||
# override PLATFORM or PROFILE
|
||||
|
||||
include $(topdir)/build/config-default.make
|
||||
-include $(topdir)/build/pre-config.make
|
||||
|
||||
# Default PLATFORM and PROFILE if they're not already defined.
|
||||
|
||||
ifndef PLATFORM
|
||||
ifeq ($(OS),Windows_NT)
|
||||
PLATFORM = win32
|
||||
else
|
||||
PLATFORM = linux
|
||||
endif
|
||||
endif
|
||||
|
||||
# Platform config
|
||||
|
||||
include $(topdir)/build/platforms/$(PLATFORM).make
|
||||
|
||||
ifdef PLATFORM_CORLIB
|
||||
corlib = $(PLATFORM_CORLIB)
|
||||
endif
|
||||
# Useful
|
||||
|
||||
ifeq ($(PLATFORM_RUNTIME),$(RUNTIME))
|
||||
PLATFORM_MONO_NATIVE = yes
|
||||
endif
|
||||
|
||||
# Rest of the configuration
|
||||
|
||||
ifndef PROFILE
|
||||
PROFILE = default
|
||||
endif
|
||||
|
||||
include $(topdir)/build/profiles/$(PROFILE).make
|
||||
-include $(topdir)/build/config.make
|
||||
|
||||
# Simple rules
|
||||
|
||||
%-recursive:
|
||||
@list='$(SUBDIRS)'; for d in $$list ; do \
|
||||
(cd $$d && $(MAKE) $*) || exit 1 ; \
|
||||
done
|
||||
|
||||
# note: dist-local dep, extra subdirs, $* has become $@
|
||||
|
||||
dist-recursive: dist-local
|
||||
@list='$(SUBDIRS) $(DIST_ONLY_SUBDIRS)'; for d in $$list ; do \
|
||||
(cd $$d && $(MAKE) $@) || exit 1 ; \
|
||||
done
|
||||
|
||||
# We do this manually to not have a make[1]: blah message (That is,
|
||||
# instead of using a '%: %-recursive %-local' construct.)
|
||||
#
|
||||
# Let the makefile override these for special situations (running checks
|
||||
# in the toplevel makefile, or a directory that needs to be built before
|
||||
# its subdirectories).
|
||||
|
||||
ifndef OVERRIDE_BARE_TARGETS
|
||||
|
||||
all: all-recursive all-local
|
||||
|
||||
install: install-recursive install-local
|
||||
|
||||
test: test-recursive test-local
|
||||
|
||||
run-test: run-test-recursive test-local run-test-local
|
||||
|
||||
clean: clean-recursive clean-local
|
||||
|
||||
endif
|
||||
|
||||
# Can only do this from the top dir
|
||||
# ## dist: dist-recursive dist-local
|
||||
|
||||
# We invert the test here to not end in an error
|
||||
# if ChangeLog doesn't exist.
|
||||
#
|
||||
# Note that we error out if we try to dist a nonexistant
|
||||
# file. Seems reasonable to me.
|
||||
|
||||
dist-default:
|
||||
-mkdir $(distdir)
|
||||
test '!' -f ChangeLog || cp ChangeLog $(distdir)
|
||||
for f in Makefile $(DISTFILES) ; do \
|
||||
dest=`dirname $(distdir)/$$f` ; \
|
||||
$(MKINSTALLDIRS) $$dest && cp $$f $$dest || exit 1 ; \
|
||||
done
|
||||
|
||||
# Useful
|
||||
|
||||
withmcs:
|
||||
$(MAKE) MCS='$(INTERNAL_MCS)' BOOTSTRAP_MCS='$(INTERNAL_MCS)' all
|
||||
@@ -0,0 +1,38 @@
|
||||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
|
||||
<!-- NAnt build file for Accessibility.dll -->
|
||||
|
||||
<project name="System" default="build">
|
||||
<property name="debug" value="false"/>
|
||||
|
||||
<target name="build">
|
||||
<mkdir dir="../lib"/>
|
||||
<csc target="library" output="../lib/Accessibility.dll" debug="${debug}">
|
||||
<arg value="/nowarn:1595"/>
|
||||
<arg value="/unsafe"/>
|
||||
<arg value="/noconfig"/> <!-- don't reference ms assemblies -->
|
||||
<arg value="/lib:../lib/"/>
|
||||
|
||||
<!-- cor compare dies with these currently -->
|
||||
<!--arg value="/nostdlib"/--> <!-- don't reference mscorlib -->
|
||||
<!--arg value="/r:corlib.dll"/-->
|
||||
<sources>
|
||||
<includes name="**/*.cs"/>
|
||||
<excludes name="Test/**"/>
|
||||
</sources>
|
||||
</csc>
|
||||
<copy file="../lib/Accessibility.dll" tofile="Test/Accessibility.dll"/>
|
||||
<!-- TODO: missing tests & buildfile
|
||||
<nant basedir="Test" target="build"/>
|
||||
-->
|
||||
</target>
|
||||
|
||||
<target name="test" depends="build">
|
||||
<nant basedir="Test" target="test"/>
|
||||
</target>
|
||||
|
||||
<target name="clean">
|
||||
<nant basedir="Test" target="clean"/>
|
||||
<delete file="../lib/Accessibility.dll" failonerror="false"/>
|
||||
</target>
|
||||
</project>
|
||||
@@ -1,48 +0,0 @@
|
||||
//
|
||||
// AssemblyInfo.cs
|
||||
//
|
||||
// Author:
|
||||
// Andreas Nahr ([email protected])
|
||||
//
|
||||
// (C) 2003 Ximian, Inc. http://www.ximian.com
|
||||
//
|
||||
|
||||
using System;
|
||||
using System.Reflection;
|
||||
using System.Resources;
|
||||
using System.Security;
|
||||
using System.Runtime.CompilerServices;
|
||||
using System.Runtime.InteropServices;
|
||||
|
||||
// General Information about the system assembly
|
||||
|
||||
#if (NET_1_0)
|
||||
[assembly: AssemblyVersion("1.0.3300.0")]
|
||||
[assembly: SatelliteContractVersion("1.0.3300.0")]
|
||||
#endif
|
||||
#if (NET_1_1)
|
||||
[assembly: AssemblyVersion("1.0.5000.0")]
|
||||
[assembly: SatelliteContractVersion("1.0.5000.0")]
|
||||
[assembly: ComCompatibleVersion(1, 0, 3300, 0)]
|
||||
[assembly: TypeLibVersion(1, 10)]
|
||||
#endif
|
||||
|
||||
[assembly: AssemblyTitle("Accessibility.dll")]
|
||||
[assembly: AssemblyDescription("Accessibility.dll")]
|
||||
[assembly: AssemblyConfiguration("Development version")]
|
||||
[assembly: AssemblyCompany("MONO development team")]
|
||||
[assembly: AssemblyProduct("MONO CLI")]
|
||||
[assembly: AssemblyCopyright("(c) 2003 Various Authors")]
|
||||
[assembly: AssemblyTrademark("")]
|
||||
|
||||
[assembly: CLSCompliant(true)]
|
||||
[assembly: AssemblyDefaultAlias("Accessibility.dll")]
|
||||
[assembly: AssemblyInformationalVersion("0.0.0.1")]
|
||||
[assembly: NeutralResourcesLanguage("en-US")]
|
||||
|
||||
[assembly: ComVisible(false)]
|
||||
[assembly: AllowPartiallyTrustedCallers]
|
||||
[assembly: Guid("1ea4dbf0-3c3b-11cf-810c-00aa00389b71")]
|
||||
|
||||
//[assembly: AssemblyDelaySign(false)]
|
||||
//[assembly: AssemblyKeyFile("")]
|
||||
@@ -1,4 +0,0 @@
|
||||
2003-07-17 Andreas Nahr <[email protected]>
|
||||
|
||||
* AssemblyInfo.cs: Added
|
||||
* ChangeLog: Added
|
||||
@@ -1,8 +1,3 @@
|
||||
2003-07-17 Andreas Nahr <[email protected]>
|
||||
|
||||
* Accessibility.dll.sources:
|
||||
* list.unix: AssemblyInfo.cs added
|
||||
|
||||
2002-12-10 Jeroen Janssen <[email protected]>
|
||||
|
||||
* updated .build file to correctly build with Nant
|
||||
@@ -1,9 +0,0 @@
|
||||
thisdir = class/Accessibility
|
||||
SUBDIRS =
|
||||
include ../../build/rules.make
|
||||
|
||||
LIBRARY = Accessibility.dll
|
||||
LIB_MCS_FLAGS = /r:$(corlib)
|
||||
NO_TEST = yes
|
||||
|
||||
include ../../build/library.make
|
||||
@@ -1,3 +1,2 @@
|
||||
Accessibility/IAccessible.cs
|
||||
Accessibility/IAccessibleHandler.cs
|
||||
Assembly/AssemblyInfo.cs
|
||||
@@ -0,0 +1,16 @@
|
||||
topdir = ../..
|
||||
|
||||
TEST_DIR= Test
|
||||
LIBRARY = $(topdir)/class/lib/Accessibility.dll
|
||||
|
||||
LIB_LIST = list.unix
|
||||
LIB_FLAGS = -r corlib
|
||||
|
||||
SOURCES_INCLUDE=*.cs
|
||||
SOURCES_EXCLUDE=\
|
||||
./Test*
|
||||
|
||||
|
||||
export MONO_PATH_PREFIX = $(topdir)/class/lib:
|
||||
|
||||
include $(topdir)/class/library.make
|
||||
Executable
+44
@@ -0,0 +1,44 @@
|
||||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
|
||||
<!-- NAnt build file for ByteFX.Data.dll -->
|
||||
|
||||
<project name="ByteFX.Data" default="build">
|
||||
<property name="debug" value="false"/>
|
||||
|
||||
<target name="build">
|
||||
<csc target="library" output="../lib/ByteFX.Data.dll" debug="${debug}">
|
||||
<arg value="/nowarn:1595"/>
|
||||
<arg value="/nowarn:0067"/>
|
||||
<arg value="/nowarn:0109"/>
|
||||
<arg value="/nowarn:0169"/>
|
||||
<arg value="/nowarn:0649"/>
|
||||
<arg value="/unsafe"/>
|
||||
<arg value="/noconfig"/>
|
||||
<arg value="/r:../lib/System.dll"/>
|
||||
<arg value="/r:../lib/System.Xml.dll"/>
|
||||
<arg value="/r:../lib/System.Data.dll"/>
|
||||
<arg value="/r:../lib/ICSharpCode.SharpZipLib.dll"/>
|
||||
|
||||
<sources>
|
||||
<includes name="**/*.cs"/>
|
||||
<excludes name="Test/**"/>
|
||||
|
||||
</sources>
|
||||
<references>
|
||||
<includes name="../lib/corlib.dll"/>
|
||||
<includes name="../lib/System.dll"/>
|
||||
<includes name="../lib/System.Xml.dll"/>
|
||||
<includes name="../lib/System.Data.dll"/>
|
||||
<includes name="../lib/ICSharpCode.SharpZipLib.dll"/>
|
||||
|
||||
</references>
|
||||
</csc>
|
||||
</target>
|
||||
<target name="test" depends="build">
|
||||
<nant basedir="Test" target="test"/>
|
||||
</target>
|
||||
<target name="clean">
|
||||
<delete file="../lib/ByteFX.Data.dll" failonerror="false"/>
|
||||
|
||||
</target>
|
||||
</project>
|
||||
@@ -1,11 +0,0 @@
|
||||
thisdir = class/ByteFX.Data
|
||||
SUBDIRS =
|
||||
include ../../build/rules.make
|
||||
|
||||
LIBRARY = ByteFX.Data.dll
|
||||
LIB_MCS_FLAGS = /r:$(corlib) /r:System.dll /r:System.Xml.dll \
|
||||
/r:System.Data.dll /r:ICSharpCode.SharpZipLib.dll
|
||||
NO_TEST = yes
|
||||
EXTRA_DISTFILES = ChangeLog.txt lgpl.txt readme.txt
|
||||
|
||||
include ../../build/library.make
|
||||
File renamed without changes.
Executable
+14
@@ -0,0 +1,14 @@
|
||||
topdir = ../..
|
||||
|
||||
LIBRARY = $(topdir)/class/lib/ByteFX.Data.dll
|
||||
|
||||
LIB_LIST = list
|
||||
LIB_FLAGS = -r corlib -r System -r System.Xml -r System.Data -r ICSharpCode.SharpZipLib
|
||||
|
||||
SOURCES_INCLUDE=./*.cs ./Common/*.cs ./mysqlclient/*.cs
|
||||
SOURCES_EXCLUDE=\
|
||||
./Test*
|
||||
|
||||
export MONO_PATH_PREFIX = $(topdir)/class/lib:
|
||||
|
||||
include $(topdir)/class/library.make
|
||||
@@ -1,20 +1,3 @@
|
||||
2003-08-11 Duncan Mak <[email protected]>
|
||||
|
||||
* Makefile (SUBDIRS): Add Mono.Cairo.dll
|
||||
|
||||
2003-07-24 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* Makefile: only build Mono.CSharp.Debugger under linux.
|
||||
|
||||
2003-07-23 Peter Williams <[email protected]>
|
||||
|
||||
* Makefile (SUBDIRS): Add System.Drawing.Design.dll to the
|
||||
default build.
|
||||
|
||||
2003-07-22 Cesar Lopez Nataren <[email protected]>
|
||||
|
||||
* mcs/class/Makefile: Added Microsoft.Vsa.dll to the build.
|
||||
|
||||
2003-04-04 Miguel de Icaza <[email protected]>
|
||||
|
||||
*
|
||||
|
||||
@@ -1,8 +1,3 @@
|
||||
2003-05-19 Atsushi Enomoto <[email protected]>
|
||||
|
||||
* RdpPattern.cs : Some method name capitalization.
|
||||
Fixed RdpInterleave.StartTagOpenDeriv() which is logically incorrect.
|
||||
|
||||
2003-05-05 Atsushi Enomoto <[email protected]>
|
||||
|
||||
* RdpPattern.cs : added RdpAttribute.expandRef(). UnresolvedRef had
|
||||
|
||||
@@ -166,12 +166,12 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
throw new InvalidOperationException ();
|
||||
}
|
||||
|
||||
internal protected virtual RdpPattern ExpandRef (Hashtable defs)
|
||||
internal virtual RdpPattern expandRef (Hashtable defs)
|
||||
{
|
||||
return this;
|
||||
}
|
||||
|
||||
internal protected virtual RdpPattern ReduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
internal virtual RdpPattern reduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
{
|
||||
return this;
|
||||
}
|
||||
@@ -481,16 +481,16 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
}
|
||||
|
||||
bool expanded;
|
||||
internal protected override RdpPattern ExpandRef (Hashtable defs)
|
||||
internal override RdpPattern expandRef (Hashtable defs)
|
||||
{
|
||||
if (!expanded) {
|
||||
l = l.ExpandRef (defs);
|
||||
r = r.ExpandRef (defs);
|
||||
l = l.expandRef (defs);
|
||||
r = r.expandRef (defs);
|
||||
}
|
||||
return this;
|
||||
}
|
||||
|
||||
internal protected override RdpPattern ReduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
internal override RdpPattern reduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
{
|
||||
if (visited.Contains (this))
|
||||
return this;
|
||||
@@ -502,13 +502,13 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
return RdpNotAllowed.Instance;
|
||||
} else if (LValue.PatternType == RngPatternType.Empty) {
|
||||
result = true;
|
||||
return RValue.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
return RValue.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
} else if (RValue.PatternType == RngPatternType.Empty) {
|
||||
result = true;
|
||||
return LValue.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
return LValue.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
} else {
|
||||
LValue = LValue.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
RValue = RValue.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
LValue = LValue.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
RValue = RValue.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
return this;
|
||||
}
|
||||
}
|
||||
@@ -532,7 +532,7 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
}
|
||||
}
|
||||
|
||||
internal protected override RdpPattern ReduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
internal override RdpPattern reduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
{
|
||||
if (visited.Contains (this))
|
||||
return this;
|
||||
@@ -544,22 +544,22 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
return RdpNotAllowed.Instance;
|
||||
} else if (LValue.PatternType == RngPatternType.NotAllowed) {
|
||||
result = true;
|
||||
return RValue.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
return RValue.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
} else if (RValue.PatternType == RngPatternType.NotAllowed) {
|
||||
result = true;
|
||||
return LValue.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
return LValue.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
} else if (LValue.PatternType == RngPatternType.Empty &&
|
||||
RValue.PatternType == RngPatternType.Empty) {
|
||||
result = true;
|
||||
return RdpEmpty.Instance;
|
||||
} else if (RValue.PatternType == RngPatternType.Empty) {
|
||||
result = true;
|
||||
RValue = LValue.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
RValue = LValue.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
LValue = RdpEmpty.Instance;
|
||||
return this;
|
||||
} else {
|
||||
LValue = LValue.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
RValue = RValue.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
LValue = LValue.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
RValue = RValue.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
return this;
|
||||
}
|
||||
}
|
||||
@@ -637,7 +637,7 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
}
|
||||
}
|
||||
|
||||
internal protected override RdpPattern ReduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
internal override RdpPattern reduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
{
|
||||
if (visited.Contains (this))
|
||||
return this;
|
||||
@@ -648,8 +648,8 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
result = true;
|
||||
return RdpNotAllowed.Instance;
|
||||
} else {
|
||||
LValue = LValue.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
RValue = RValue.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
LValue = LValue.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
RValue = RValue.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
return this;
|
||||
}
|
||||
}
|
||||
@@ -667,8 +667,11 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
RdpPattern handledL = LValue.StartTagOpenDeriv (name, ns);
|
||||
RdpPattern handledR = RValue.StartTagOpenDeriv (name, ns);
|
||||
RdpFlip flipL = new RdpFlip (new RdpBinaryFunction (RdpUtil.Interleave), RValue);
|
||||
// FIXME: It is not flip in fact, but there are no proper class ;-(
|
||||
RdpFlip flipR = new RdpFlip (new RdpBinaryFunction (RdpUtil.Interleave), handledR);
|
||||
RdpPattern choiceL = handledL.ApplyAfter (new RdpApplyAfterHandler (flipL.Apply));
|
||||
RdpPattern choiceR = handledR.ApplyAfter (new RdpApplyAfterHandler (LValue.Interleave));
|
||||
RdpPattern choiceR = LValue.ApplyAfter (new RdpApplyAfterHandler (flipR.Apply));
|
||||
|
||||
return choiceL.Choice (choiceR);
|
||||
}
|
||||
|
||||
@@ -790,10 +793,10 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
RdpPattern child;
|
||||
bool isExpanded;
|
||||
|
||||
internal protected override RdpPattern ExpandRef (Hashtable defs)
|
||||
internal override RdpPattern expandRef (Hashtable defs)
|
||||
{
|
||||
if (!isExpanded)
|
||||
child = child.ExpandRef (defs);
|
||||
child = child.expandRef (defs);
|
||||
return this;
|
||||
}
|
||||
|
||||
@@ -820,7 +823,7 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
get { return Child.Nullable; }
|
||||
}
|
||||
|
||||
internal protected override RdpPattern ReduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
internal override RdpPattern reduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
{
|
||||
if (visited.Contains (this))
|
||||
return this;
|
||||
@@ -832,7 +835,7 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
} else if (Child.PatternType == RngPatternType.Empty)
|
||||
return RdpEmpty.Instance;
|
||||
else {
|
||||
Child = Child.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
Child = Child.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
return this;
|
||||
}
|
||||
}
|
||||
@@ -896,7 +899,7 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
{
|
||||
}
|
||||
|
||||
internal protected override RdpPattern ReduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
internal override RdpPattern reduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
{
|
||||
if (visited.Contains (this))
|
||||
return this;
|
||||
@@ -906,7 +909,7 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
result = true;
|
||||
return RdpNotAllowed.Instance;
|
||||
} else {
|
||||
Child = Child.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
Child = Child.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
return this;
|
||||
}
|
||||
}
|
||||
@@ -999,7 +1002,7 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
set { except = value; }
|
||||
}
|
||||
|
||||
internal protected override RdpPattern ReduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
internal override RdpPattern reduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
{
|
||||
if (visited.Contains (this))
|
||||
return this;
|
||||
@@ -1009,7 +1012,7 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
result = true;
|
||||
return new RdpData (this.Datatype, this.ParamList);
|
||||
} else {
|
||||
except = except.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
except = except.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
return this;
|
||||
}
|
||||
}
|
||||
@@ -1103,16 +1106,16 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
}
|
||||
|
||||
bool isExpanded;
|
||||
internal protected override RdpPattern ExpandRef (Hashtable defs)
|
||||
internal override RdpPattern expandRef (Hashtable defs)
|
||||
{
|
||||
if (!isExpanded) {
|
||||
isExpanded = true;
|
||||
children = children.ExpandRef (defs);
|
||||
children = children.expandRef (defs);
|
||||
}
|
||||
return this;
|
||||
}
|
||||
|
||||
internal protected override RdpPattern ReduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
internal override RdpPattern reduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
{
|
||||
if (visited.Contains (this))
|
||||
return this;
|
||||
@@ -1122,7 +1125,7 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
result = true;
|
||||
return RdpNotAllowed.Instance;
|
||||
} else {
|
||||
children = children.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
children = children.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
return this;
|
||||
}
|
||||
}
|
||||
@@ -1188,22 +1191,22 @@ namespace Commons.Xml.Relaxng.Derivative
|
||||
}
|
||||
|
||||
bool isExpanded;
|
||||
internal protected override RdpPattern ExpandRef (Hashtable defs)
|
||||
internal override RdpPattern expandRef (Hashtable defs)
|
||||
{
|
||||
if (!isExpanded) {
|
||||
isExpanded = true;
|
||||
children = children.ExpandRef (defs);
|
||||
children = children.expandRef (defs);
|
||||
}
|
||||
return this;
|
||||
}
|
||||
|
||||
internal protected override RdpPattern ReduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
internal override RdpPattern reduceEmptyAndNotAllowed (ref bool result, Hashtable visited)
|
||||
{
|
||||
if (visited.Contains (this))
|
||||
return this;
|
||||
visited.Add (this, this);
|
||||
|
||||
children = children.ReduceEmptyAndNotAllowed (ref result, visited);
|
||||
children = children.reduceEmptyAndNotAllowed (ref result, visited);
|
||||
return this;
|
||||
}
|
||||
|
||||
|
||||
@@ -0,0 +1,45 @@
|
||||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
|
||||
<!-- NAnt build file for Commons.Xml.Relaxng.dll -->
|
||||
|
||||
<project name="Commons.Xml.Relaxng" default="build">
|
||||
<property name="debug" value="true"/>
|
||||
|
||||
<target name="build">
|
||||
<mkdir dir="../lib"/>
|
||||
<csc target="library" output="../lib/Commons.Xml.Relaxng.dll" debug="${debug}">
|
||||
<!-- 'foo' is defined in multiple places; using definition from 'bar' -->
|
||||
<arg value="/nowarn:1595"/>
|
||||
<!-- Other languages may permit the internal virtual member 'foo' to be overridden -->
|
||||
<arg value="/nowarn:0679"/>
|
||||
<arg value="/nowarn:0649"/>
|
||||
<sources>
|
||||
<includes name="**/*.cs"/>
|
||||
<excludes name="Test/**"/>
|
||||
</sources>
|
||||
<!--
|
||||
<arg value="/nostdlib" />
|
||||
<references basedir="..\lib">
|
||||
<includes name="corlib.dll"/>
|
||||
<includes name="System.dll"/>
|
||||
<includes name="System.Xml.dll"/>
|
||||
</references>
|
||||
<arg value="/r:..\lib\System.dll" />
|
||||
<arg value="/r:..\lib\System.Xml.dll" />
|
||||
-->
|
||||
</csc>
|
||||
<nant basedir="Test" target="build"/>
|
||||
</target>
|
||||
|
||||
<target name="test" depends="build">
|
||||
<nant basedir="Test" target="test"/>
|
||||
</target>
|
||||
|
||||
<target name="clean">
|
||||
<nant basedir="Test" target="clean"/>
|
||||
<delete file="../lib/Commons.Xml.Relaxng.dll" failonerror="false"/>
|
||||
<delete file="Test/Commons.Xml.Relaxng.dll" failonerror="false"/>
|
||||
<delete file="Test/System.Xml.dll" failonerror="false"/>
|
||||
<delete file="../lib/Commons.Xml.Relaxng.pdb" failonerror="false"/>
|
||||
</target>
|
||||
</project>
|
||||
@@ -1,21 +1,3 @@
|
||||
2003-05-19 Atsushi Enomoto <[email protected]>
|
||||
|
||||
* RelaxngReader.cs :
|
||||
+ Now skips immaterial content correctly.
|
||||
+ Removed MoveToContent().
|
||||
+ Trimming attribute values and names.
|
||||
+ Fixed ReadNameClassChoice(), ReadNameClassExcept(),
|
||||
ReadPatternExcept (). They require one or more contents.
|
||||
+ QName resolver fix.
|
||||
+ ReadListPattern() failed to read actual content.
|
||||
* RelaxngValidatingReader.cs :
|
||||
+ Fixed incorrect error message.
|
||||
+ Fixed incorrect attribute namespace handling.
|
||||
* RngGrammar.cs : Some simplification stuff fix.
|
||||
Support for illegal recursion check.
|
||||
* RngNameClass.cs : fixed RngNsName ctor() (argument not passed).
|
||||
* RngPattern.cs : fixed ParentRef.Compile() (was treated same as Ref).
|
||||
|
||||
2003-05-05 Atsushi Enomoto <[email protected]>
|
||||
|
||||
* RelaxngReader.cs : ReadExternalRef() hadn't resolved base uri.
|
||||
|
||||
@@ -15,20 +15,7 @@ namespace Commons.Xml.Relaxng
|
||||
{
|
||||
public class RelaxngReader : XmlDefaultReader
|
||||
{
|
||||
// static members.
|
||||
static RngPattern relaxngGrammar;
|
||||
static XmlReader relaxngXmlReader;
|
||||
static RelaxngReader ()
|
||||
{
|
||||
// relaxngXmlReader = new XmlTextReader ("relaxng.rng");
|
||||
// relaxngGrammar = RngPattern.Read (relaxngXmlReader);
|
||||
}
|
||||
|
||||
public static string RngNS = "http://relaxng.org/ns/structure/1.0";
|
||||
// public static RngPattern RelaxngGrammar {
|
||||
// get { return relaxngGrammar; }
|
||||
// }
|
||||
|
||||
|
||||
// fields
|
||||
Stack nsStack = new Stack ();
|
||||
@@ -41,7 +28,6 @@ namespace Commons.Xml.Relaxng
|
||||
}
|
||||
|
||||
public RelaxngReader (XmlReader reader, string ns)
|
||||
// : base (reader == relaxngXmlReader ? reader : new RelaxngValidatingReader (reader, relaxngGrammar))
|
||||
: base (reader)
|
||||
{
|
||||
nsStack.Push (ns == null ? "" : ns);
|
||||
@@ -55,14 +41,10 @@ namespace Commons.Xml.Relaxng
|
||||
// public
|
||||
public override bool Read ()
|
||||
{
|
||||
bool skipRead = false;
|
||||
bool b = false;
|
||||
bool loop = true;
|
||||
do {
|
||||
if (!skipRead)
|
||||
b = Reader.Read ();
|
||||
else
|
||||
skipRead = false;
|
||||
b = Reader.Read ();
|
||||
switch (NodeType) {
|
||||
case XmlNodeType.ProcessingInstruction:
|
||||
case XmlNodeType.Comment:
|
||||
@@ -79,11 +61,9 @@ namespace Commons.Xml.Relaxng
|
||||
break;
|
||||
default:
|
||||
if (NamespaceURI != RngNS) {
|
||||
Reader.Skip ();
|
||||
skipRead = true;
|
||||
continue;
|
||||
}
|
||||
else
|
||||
loop = false;
|
||||
loop = false;
|
||||
break;
|
||||
}
|
||||
} while (b && loop);
|
||||
@@ -92,12 +72,12 @@ namespace Commons.Xml.Relaxng
|
||||
case XmlNodeType.Element:
|
||||
if (!IsEmptyElement) {
|
||||
if (MoveToAttribute ("ns"))
|
||||
nsStack.Push (Value.Trim ());
|
||||
nsStack.Push (Value);
|
||||
else
|
||||
nsStack.Push (nsStack.Peek ());
|
||||
|
||||
if (MoveToAttribute ("datatypeLibrary"))
|
||||
datatypeLibraryStack.Push (Value.Trim ());
|
||||
datatypeLibraryStack.Push (Value);
|
||||
else
|
||||
datatypeLibraryStack.Push (datatypeLibraryStack.Peek ());
|
||||
MoveToElement ();
|
||||
@@ -111,7 +91,6 @@ namespace Commons.Xml.Relaxng
|
||||
return b;
|
||||
}
|
||||
|
||||
/*
|
||||
public override XmlNodeType MoveToContent ()
|
||||
{
|
||||
MoveToElement ();
|
||||
@@ -130,7 +109,6 @@ namespace Commons.Xml.Relaxng
|
||||
}
|
||||
return NodeType;
|
||||
}
|
||||
*/
|
||||
|
||||
// Properties
|
||||
|
||||
@@ -166,7 +144,7 @@ namespace Commons.Xml.Relaxng
|
||||
RngStart s = new RngStart ();
|
||||
expect ("start");
|
||||
if (MoveToAttribute ("combine")) {
|
||||
s.Combine = Value.Trim ();
|
||||
s.Combine = Value;
|
||||
if (s.Combine != "choice" && s.Combine != "interleave")
|
||||
throw new RngException ("Invalid combine attribute: " + s.Combine);
|
||||
}
|
||||
@@ -178,17 +156,11 @@ namespace Commons.Xml.Relaxng
|
||||
return s;
|
||||
}
|
||||
|
||||
private string GetSpaceStrippedAttribute (string name)
|
||||
{
|
||||
string v = GetAttribute (name);
|
||||
return v != null ? v.Trim () : null;
|
||||
}
|
||||
|
||||
public RngDefine ReadDefine ()
|
||||
{
|
||||
RngDefine def = new RngDefine ();
|
||||
expect ("define");
|
||||
def.Name = GetSpaceStrippedAttribute ("name");
|
||||
def.Name = GetAttribute ("name");
|
||||
|
||||
Read ();
|
||||
while (NodeType == XmlNodeType.Element)
|
||||
@@ -201,8 +173,8 @@ namespace Commons.Xml.Relaxng
|
||||
{
|
||||
RngParam p = new RngParam ();
|
||||
expect ("param");
|
||||
p.Name = GetSpaceStrippedAttribute ("name");
|
||||
p.Value = ReadString ().Trim ();
|
||||
p.Name = GetAttribute ("name");
|
||||
p.Value = ReadString ();
|
||||
expectEnd ("param");
|
||||
return p;
|
||||
}
|
||||
@@ -225,7 +197,7 @@ namespace Commons.Xml.Relaxng
|
||||
|
||||
public RngName ReadNameClassName ()
|
||||
{
|
||||
string name = ReadString ().Trim ();
|
||||
string name = ReadString ();
|
||||
RngName rName = resolvedName (name);
|
||||
expectEnd ("name");
|
||||
return rName;
|
||||
@@ -255,7 +227,7 @@ namespace Commons.Xml.Relaxng
|
||||
|
||||
public RngNsName ReadNameClassNsName ()
|
||||
{
|
||||
RngNsName nn = new RngNsName (this.NS);
|
||||
RngNsName nn = new RngNsName ();
|
||||
if (!IsEmptyElement) {
|
||||
Read ();
|
||||
if (NodeType == XmlNodeType.EndElement) {
|
||||
@@ -275,16 +247,8 @@ namespace Commons.Xml.Relaxng
|
||||
public RngNameChoice ReadNameClassChoice ()
|
||||
{
|
||||
RngNameChoice nc = new RngNameChoice ();
|
||||
if (IsEmptyElement)
|
||||
throw new RngException ("Name choice must have at least one name class.");
|
||||
|
||||
Read ();
|
||||
while (NodeType != XmlNodeType.EndElement) {
|
||||
while (NodeType == XmlNodeType.EndElement)
|
||||
nc.Children.Add (ReadNameClass ());
|
||||
}
|
||||
if (nc.Children.Count == 0)
|
||||
throw new RngException ("Name choice must have at least one name class.");
|
||||
|
||||
expectEnd ("choice");
|
||||
return nc;
|
||||
}
|
||||
@@ -292,15 +256,8 @@ namespace Commons.Xml.Relaxng
|
||||
public RngExceptNameClass ReadNameClassExcept ()
|
||||
{
|
||||
RngExceptNameClass x = new RngExceptNameClass ();
|
||||
if (IsEmptyElement)
|
||||
throw new RngException ("Name choice must have at least one name class.");
|
||||
|
||||
Read ();
|
||||
while (NodeType != XmlNodeType.EndElement)
|
||||
while (NodeType == XmlNodeType.EndElement)
|
||||
x.Names.Add (ReadNameClass ());
|
||||
if (x.Names.Count == 0)
|
||||
throw new RngException ("Name choice must have at least one name class.");
|
||||
|
||||
expectEnd ("except");
|
||||
return x;
|
||||
}
|
||||
@@ -373,14 +330,8 @@ namespace Commons.Xml.Relaxng
|
||||
public RngExcept ReadPatternExcept ()
|
||||
{
|
||||
RngExcept x = new RngExcept ();
|
||||
if (IsEmptyElement)
|
||||
throw new RngException ("'except' must have at least one pattern.");
|
||||
Read ();
|
||||
while (NodeType != XmlNodeType.EndElement)
|
||||
while (NodeType == XmlNodeType.EndElement)
|
||||
x.Patterns.Add (ReadPattern ());
|
||||
if (x.Patterns.Count == 0)
|
||||
throw new RngException ("'except' must have at least one pattern.");
|
||||
|
||||
expectEnd ("except");
|
||||
return x;
|
||||
}
|
||||
@@ -389,7 +340,7 @@ namespace Commons.Xml.Relaxng
|
||||
{
|
||||
RngInclude i = new RngInclude ();
|
||||
expect ("include");
|
||||
string href = GetSpaceStrippedAttribute ("href");
|
||||
string href = GetAttribute ("href");
|
||||
i.Href = Util.ResolveUri (BaseURI, href);
|
||||
if (!IsEmptyElement) {
|
||||
Read ();
|
||||
@@ -443,7 +394,7 @@ namespace Commons.Xml.Relaxng
|
||||
private RngName resolvedName (string nameSpec)
|
||||
{
|
||||
int colonAt = nameSpec.IndexOf (':');
|
||||
string prefix = (colonAt < 0) ? "" : nameSpec.Substring (0, colonAt);
|
||||
string prefix = (colonAt < 0) ? "" : nameSpec.Substring (0, colonAt - 1);
|
||||
string local = (colonAt < 0) ? nameSpec : nameSpec.Substring (colonAt + 1, nameSpec.Length - colonAt - 1);
|
||||
string uri = NS;
|
||||
|
||||
@@ -461,7 +412,7 @@ namespace Commons.Xml.Relaxng
|
||||
|
||||
// try to get name from attribute.
|
||||
if (MoveToAttribute ("name")) {
|
||||
el.NameClass = resolvedName (Value.Trim ());
|
||||
el.NameClass = resolvedName (Value);
|
||||
}
|
||||
MoveToElement ();
|
||||
Read ();
|
||||
@@ -484,7 +435,7 @@ namespace Commons.Xml.Relaxng
|
||||
|
||||
// try to get name from attribute.
|
||||
if (MoveToAttribute ("name"))
|
||||
attr.NameClass = resolvedName (Value.Trim ());
|
||||
attr.NameClass = resolvedName (Value);
|
||||
|
||||
MoveToElement ();
|
||||
if (!IsEmptyElement) {
|
||||
@@ -516,7 +467,7 @@ namespace Commons.Xml.Relaxng
|
||||
{
|
||||
RngRef r = new RngRef ();
|
||||
expect ("ref");
|
||||
r.Name = GetSpaceStrippedAttribute ("name");
|
||||
r.Name = GetAttribute ("name");
|
||||
if (!IsEmptyElement) {
|
||||
Read ();
|
||||
expectEnd ("ref");
|
||||
@@ -530,7 +481,7 @@ namespace Commons.Xml.Relaxng
|
||||
{
|
||||
RngExternalRef r = new RngExternalRef ();
|
||||
expect ("externalRef");
|
||||
string href = GetSpaceStrippedAttribute ("href");
|
||||
string href = GetAttribute ("href");
|
||||
r.Href = Util.ResolveUri (BaseURI, href);
|
||||
r.NSContext = NS;
|
||||
if (!IsEmptyElement) {
|
||||
@@ -546,7 +497,7 @@ namespace Commons.Xml.Relaxng
|
||||
{
|
||||
RngParentRef r = new RngParentRef ();
|
||||
expect ("parentRef");
|
||||
r.Name = GetSpaceStrippedAttribute ("name");
|
||||
r.Name = GetAttribute ("name");
|
||||
if (!IsEmptyElement) {
|
||||
Read ();
|
||||
expectEnd ("parentRef");
|
||||
@@ -587,7 +538,7 @@ namespace Commons.Xml.Relaxng
|
||||
RngData data = new RngData ();
|
||||
|
||||
expect ("data");
|
||||
data.Type = GetSpaceStrippedAttribute ("type");
|
||||
data.Type = GetAttribute ("type");
|
||||
data.DatatypeLibrary = DatatypeLibrary;
|
||||
|
||||
if (!IsEmptyElement) {
|
||||
@@ -609,15 +560,14 @@ namespace Commons.Xml.Relaxng
|
||||
RngValue v = new RngValue ();
|
||||
expect ("value");
|
||||
if (MoveToAttribute ("type")) {
|
||||
v.Type = Value.Trim ();
|
||||
v.Type = Value;
|
||||
v.DatatypeLibrary = DatatypeLibrary;
|
||||
} else {
|
||||
v.Type = "token";
|
||||
v.DatatypeLibrary = "";
|
||||
}
|
||||
v.Namespace = GetSpaceStrippedAttribute ("ns");
|
||||
MoveToElement ();
|
||||
v.Value = ReadString ().Trim ();
|
||||
v.Namespace = GetAttribute ("ns");
|
||||
v.Value = ReadString ();
|
||||
expectEnd ("value");
|
||||
|
||||
return v;
|
||||
@@ -626,8 +576,8 @@ namespace Commons.Xml.Relaxng
|
||||
public RngList ReadListPattern ()
|
||||
{
|
||||
RngList list = new RngList ();
|
||||
|
||||
expect ("list");
|
||||
Read ();
|
||||
ReadPatterns (list);
|
||||
expectEnd ("list");
|
||||
return list;
|
||||
|
||||
@@ -73,21 +73,19 @@ namespace Commons.Xml.Relaxng
|
||||
vState = vState.StartTagOpenDeriv (
|
||||
reader.LocalName, reader.NamespaceURI);
|
||||
if (vState.PatternType == RngPatternType.NotAllowed)
|
||||
throw createValidationError (String.Format ("Invalid start tag found. LocalName = {0}, NS = {1}. ", reader.LocalName, reader.NamespaceURI));
|
||||
throw createValidationError ("Invalid start tag found. Name = {0}{1}");
|
||||
|
||||
// AttsDeriv equals to for each AttDeriv
|
||||
if (reader.AttributeCount > 0) {
|
||||
string elementNS = reader.NamespaceURI;
|
||||
reader.MoveToFirstAttribute ();
|
||||
do {
|
||||
if (reader.Name.IndexOf ("xml:") == 0 || reader.Name.IndexOf ("xmlns:") == 0 || reader.Name == "xmlns")
|
||||
continue;
|
||||
|
||||
prevState = vState;
|
||||
string attrNS = reader.NamespaceURI == "" ? elementNS : reader.NamespaceURI;
|
||||
vState = vState.AttDeriv (reader.LocalName, attrNS, reader.GetAttribute (reader.Name));
|
||||
vState = vState.AttDeriv (reader.LocalName, reader.NamespaceURI, reader.GetAttribute (reader.Name));
|
||||
if (vState.PatternType == RngPatternType.NotAllowed)
|
||||
throw createValidationError (String.Format ("Invalid attribute found. LocalName = {0}, NS = {1}. ", reader.LocalName, reader.NamespaceURI));
|
||||
throw createValidationError (String.Format ("Invalid attribute found. Name = {0} ", reader.Name));
|
||||
} while (reader.MoveToNextAttribute ());
|
||||
}
|
||||
MoveToElement ();
|
||||
@@ -96,7 +94,7 @@ namespace Commons.Xml.Relaxng
|
||||
prevState = vState;
|
||||
vState = vState.StartTagCloseDeriv ();
|
||||
if (vState.PatternType == RngPatternType.NotAllowed)
|
||||
throw createValidationError (String.Format ("Invalid start tag closing found. LocalName = {0}, NS = {1}. ", reader.LocalName, reader.NamespaceURI));
|
||||
throw createValidationError (String.Format ("Invalid start tag closing found. Name = {0} ", reader.Name));
|
||||
|
||||
// if it is empty, then redirect to EndElement
|
||||
if (reader.IsEmptyElement)
|
||||
@@ -107,14 +105,14 @@ namespace Commons.Xml.Relaxng
|
||||
prevState = vState;
|
||||
vState = vState.EndTagDeriv ();
|
||||
if (vState.PatternType == RngPatternType.NotAllowed)
|
||||
throw createValidationError (String.Format ("Invalid end tag found. LocalName = {0}, NS = {1}. ", reader.LocalName, reader.NamespaceURI));
|
||||
throw createValidationError (String.Format ("Invalid end tag found. Name = {0} ", reader.Name));
|
||||
break;
|
||||
case XmlNodeType.CDATA:
|
||||
case XmlNodeType.Text:
|
||||
prevState = vState;
|
||||
vState = vState.TextDeriv (this.Value);
|
||||
if (vState.PatternType == RngPatternType.NotAllowed)
|
||||
throw createValidationError (String.Format ("Invalid text found. Text value = {0} ", reader.Value));
|
||||
throw createValidationError (String.Format ("Validation error. Text value = {0} ", reader.Value));
|
||||
break;
|
||||
|
||||
}
|
||||
|
||||
@@ -13,11 +13,11 @@ using System.IO;
|
||||
using System.Net;
|
||||
using System.Xml;
|
||||
using Commons.Xml.Relaxng.Derivative;
|
||||
//using System.Xml.Serialization;
|
||||
using System.Xml.Serialization;
|
||||
|
||||
namespace Commons.Xml.Relaxng
|
||||
{
|
||||
// [XmlRoot (ElementName="grammar", Namespace="http://relaxng.org/ns/structure/1.0")]
|
||||
[XmlRoot (ElementName="grammar", Namespace="http://relaxng.org/ns/structure/1.0")]
|
||||
public class RngGrammar : RngPattern
|
||||
{
|
||||
// field
|
||||
@@ -35,23 +35,13 @@ namespace Commons.Xml.Relaxng
|
||||
|
||||
// compile cache fields.
|
||||
Hashtable assembledDefs = new Hashtable ();
|
||||
RngPattern assembledStart;
|
||||
RdpPattern compiledStart;
|
||||
RdpPattern assembledStart;
|
||||
|
||||
Hashtable includedUris = new Hashtable ();
|
||||
RngGrammar parentGrammar;
|
||||
ArrayList includedGrammars;
|
||||
Hashtable refPatterns = new Hashtable (); // key = RdpPattern of assembledDefs
|
||||
|
||||
// only for checkRecursion()
|
||||
Hashtable checkedDefs = new Hashtable ();
|
||||
|
||||
// this should be checked after its compilation finished to complete
|
||||
// missing-at-the-tracking patterns (especially of parent grammars).
|
||||
// key = RdpPattern, value = ArrayList of unresolvedPatterns.
|
||||
Hashtable unresolvedPatternsTable = new Hashtable ();
|
||||
ArrayList unresolvedPatterns = new ArrayList ();
|
||||
|
||||
// contents key = RdpElement and value = name of the parent define.
|
||||
private Hashtable ElementDefMap = new Hashtable ();
|
||||
|
||||
@@ -61,27 +51,27 @@ namespace Commons.Xml.Relaxng
|
||||
{
|
||||
}
|
||||
|
||||
// [XmlIgnore]
|
||||
[XmlIgnore]
|
||||
public override RngPatternType PatternType {
|
||||
get { return RngPatternType.Grammar; }
|
||||
}
|
||||
|
||||
// [XmlElement("start")]
|
||||
[XmlElement("start")]
|
||||
public IList Starts {
|
||||
get { return starts; }
|
||||
}
|
||||
|
||||
// [XmlElement("define")]
|
||||
[XmlElement("define")]
|
||||
public IList Defines {
|
||||
get { return defs; }
|
||||
}
|
||||
|
||||
// [XmlElement("include")]
|
||||
[XmlElement("include")]
|
||||
public IList Includes {
|
||||
get { return includes; }
|
||||
}
|
||||
|
||||
// [XmlElement("div")]
|
||||
[XmlElement("div")]
|
||||
public IList Divs {
|
||||
get { return divs; }
|
||||
}
|
||||
@@ -115,25 +105,32 @@ namespace Commons.Xml.Relaxng
|
||||
// see RELAX NG 4.17.
|
||||
assembleCombine ();
|
||||
|
||||
compiledStart = assembledStart.Compile (this);
|
||||
#if false
|
||||
// Collect defines whose child is element.
|
||||
foreach (string key in assembledDefs.Keys) {
|
||||
RdpElement el = assembledDefs [key] as RdpElement;
|
||||
if (el != null)
|
||||
this.ElementDefMap.Add (el, assembledDefs [key]);
|
||||
}
|
||||
#endif
|
||||
|
||||
// Assemble all define components into top grammar and
|
||||
// return start patterns for descendant grammars.
|
||||
// see RELAX NG 4.18.
|
||||
collectGrammars ();
|
||||
if (parentGrammar != null)
|
||||
return assembledStart.Compile (this);
|
||||
return assembledStart;
|
||||
|
||||
|
||||
// 4.19 (a) remove non-reachable defines
|
||||
// 4.19 (b) check illegal recursion
|
||||
checkRecursion (compiledStart, 0);
|
||||
// 4.19 (c) expandRef
|
||||
startPattern = compiledStart.ExpandRef (assembledDefs);
|
||||
startPattern = assembledStart.expandRef (assembledDefs);
|
||||
// 4.20,21 reduce notAllowed and empty.
|
||||
bool b;
|
||||
do {
|
||||
b = false;
|
||||
startPattern = startPattern.ReduceEmptyAndNotAllowed (ref b, new Hashtable ());
|
||||
startPattern = startPattern.reduceEmptyAndNotAllowed (ref b, new Hashtable ());
|
||||
} while (b);
|
||||
|
||||
Hashtable ht = new Hashtable ();
|
||||
@@ -147,93 +144,16 @@ namespace Commons.Xml.Relaxng
|
||||
return startPattern;
|
||||
}
|
||||
|
||||
private void checkRecursion (RdpPattern p, int depth)
|
||||
{
|
||||
|
||||
RdpAbstractBinary binary = p as RdpAbstractBinary;
|
||||
if (binary != null) {
|
||||
// choice, interleave, group
|
||||
checkRecursion (binary.LValue, depth);
|
||||
checkRecursion (binary.RValue, depth);
|
||||
return;
|
||||
}
|
||||
RdpAbstractSingleContent single = p as RdpAbstractSingleContent;
|
||||
if (single != null) {
|
||||
checkRecursion (single.Child, depth);
|
||||
return;
|
||||
}
|
||||
|
||||
switch (p.PatternType) {
|
||||
case RngPatternType.Ref:
|
||||
// get checkRecursionDepth from table.
|
||||
int checkRecursionDepth = -1;
|
||||
object checkedDepth = checkedDefs [p];
|
||||
if (checkedDepth != null)
|
||||
checkRecursionDepth = (int) checkedDepth;
|
||||
// get refPattern
|
||||
RdpUnresolvedRef pref = p as RdpUnresolvedRef;
|
||||
RngGrammar target = pref.IsParentRef ? parentGrammar : this;
|
||||
RdpPattern refPattern = target.assembledDefs [pref.Name] as RdpPattern;
|
||||
if (refPattern == null)
|
||||
throw new RngException ("No matching define found for " + pref.Name);
|
||||
|
||||
if (checkRecursionDepth == -1) {
|
||||
checkedDefs [p] = depth;
|
||||
checkRecursion (refPattern, depth);
|
||||
checkedDefs [p] = -2;
|
||||
}
|
||||
else if (depth == checkRecursionDepth)
|
||||
throw new RngException (String.Format ("Detected illegal recursion. Ref name is {0}.", pref.Name));
|
||||
|
||||
break;
|
||||
|
||||
case RngPatternType.Attribute:
|
||||
checkRecursion (((RdpAttribute) p).Children, depth);
|
||||
break;
|
||||
|
||||
case RngPatternType.DataExcept:
|
||||
checkRecursion (((RdpDataExcept) p).Except, depth);
|
||||
break;
|
||||
|
||||
case RngPatternType.Element:
|
||||
RdpElement el = p as RdpElement;
|
||||
checkRecursion (el.Children, depth + 1); // +1
|
||||
break;
|
||||
case RngPatternType.List:
|
||||
checkRecursion (((RdpList) p).Child, depth);
|
||||
break;
|
||||
}
|
||||
}
|
||||
|
||||
private void completeReference ()
|
||||
{
|
||||
foreach (RdpUnresolvedRef pref in this.unresolvedPatterns) {
|
||||
RdpPattern defP = assembledDefs [pref.Name] as RdpPattern;
|
||||
ArrayList al = refPatterns [defP] as ArrayList;
|
||||
if (al == null) {
|
||||
al = new ArrayList ();
|
||||
refPatterns [defP] = al;
|
||||
}
|
||||
al.Add (pref);
|
||||
}
|
||||
}
|
||||
|
||||
private void collectGrammars ()
|
||||
{
|
||||
// collect ref and parentRef for each define.
|
||||
includedGrammars = (parentGrammar != null) ?
|
||||
parentGrammar.includedGrammars : new ArrayList ();
|
||||
|
||||
// FIXME: This should be assembledStart.
|
||||
checkReferences (compiledStart);
|
||||
completeReference ();
|
||||
|
||||
checkReferences (assembledStart);
|
||||
Hashtable ht = assembledDefs.Clone () as Hashtable;
|
||||
foreach (string name in ht.Keys) {
|
||||
RdpPattern p = (RdpPattern) assembledDefs [name];
|
||||
this.unresolvedPatternsTable [p] = unresolvedPatterns;
|
||||
checkReferences (p);
|
||||
completeReference ();
|
||||
checkReferences (assembledDefs [name] as RdpPattern);
|
||||
}
|
||||
|
||||
// If it is child of any other pattern:
|
||||
@@ -269,7 +189,6 @@ namespace Commons.Xml.Relaxng
|
||||
pref.Name = newName;
|
||||
break;
|
||||
}
|
||||
idx++;
|
||||
}
|
||||
}
|
||||
|
||||
@@ -296,15 +215,13 @@ namespace Commons.Xml.Relaxng
|
||||
RngGrammar target = pref.IsParentRef ? parentGrammar : this;
|
||||
RdpPattern defP = target.assembledDefs [pref.Name] as RdpPattern;
|
||||
if (defP == null)
|
||||
target.unresolvedPatterns.Add (p);
|
||||
else {
|
||||
ArrayList al = target.refPatterns [defP] as ArrayList;
|
||||
if (al == null) {
|
||||
al = new ArrayList ();
|
||||
target.refPatterns [defP] = al;
|
||||
}
|
||||
al.Add (p);
|
||||
throw new RngException ("No matching define found for " + pref.Name);
|
||||
ArrayList al = target.refPatterns [defP] as ArrayList;
|
||||
if (al == null) {
|
||||
al = new ArrayList ();
|
||||
target.refPatterns [defP] = al;
|
||||
}
|
||||
al.Add (p);
|
||||
break;
|
||||
|
||||
case RngPatternType.Attribute:
|
||||
@@ -354,93 +271,6 @@ namespace Commons.Xml.Relaxng
|
||||
}
|
||||
}
|
||||
|
||||
#if false
|
||||
// remove ref and parentRef.
|
||||
// add new defines for each elements.
|
||||
private void checkReferences (RngPattern p)
|
||||
{
|
||||
RngBinaryContentPattern binary =
|
||||
p as RngBinaryContentPattern;
|
||||
if (binary != null) {
|
||||
// choice, interleave, group
|
||||
foreach (RngPattern cp in binary.Patterns)
|
||||
checkReferences (cp);
|
||||
return;
|
||||
}
|
||||
|
||||
RngSingleContentPattern single =
|
||||
p as RngSingleContentPattern;
|
||||
if (single != null) {
|
||||
// list, element, oneOrMore, zeroOrMore, optional, mixed
|
||||
foreach (RngPattern cp in single.Patterns)
|
||||
checkReferences (cp);
|
||||
return;
|
||||
}
|
||||
|
||||
switch (p.PatternType) {
|
||||
case RngPatternType.Ref:
|
||||
RdpUnresolvedRef pref = p as RdpUnresolvedRef;
|
||||
RngGrammar target = pref.IsParentRef ? parentGrammar : this;
|
||||
RdpPattern defP = target.assembledDefs [pref.Name] as RdpPattern;
|
||||
if (defP == null)
|
||||
throw new RngException ("No matching define found for " + pref.Name);
|
||||
ArrayList al = target.refPatterns [defP] as ArrayList;
|
||||
if (al == null) {
|
||||
al = new ArrayList ();
|
||||
target.refPatterns [defP] = al;
|
||||
}
|
||||
al.Add (p);
|
||||
break;
|
||||
|
||||
case RngPatternType.Attribute:
|
||||
checkReferences (((RngAttribute) p).Pattern);
|
||||
break;
|
||||
|
||||
case RngPatternType.DataExcept:
|
||||
foreach (RngPattern cp in ((RngData) p).Except.Patterns)
|
||||
checkReferences (cp);
|
||||
break;
|
||||
|
||||
case RngPatternType.Element:
|
||||
RngElement el = p as RngElement;
|
||||
checkReferences (el.Children);
|
||||
string name = ElementDefMap [el] as string;
|
||||
if (name == null) {
|
||||
// add new define
|
||||
int idx = 0;
|
||||
string newName = "element0";
|
||||
if (el.NameClass is RngName)
|
||||
newName = ((RngName) el.NameClass).LocalName;
|
||||
while (true) {
|
||||
if (assembledDefs [newName] == null) {
|
||||
assembledDefs.Add (newName, el.Children);
|
||||
break;
|
||||
}
|
||||
newName = "element" + ++idx;
|
||||
}
|
||||
}
|
||||
// Even though the element is replaced with ref,
|
||||
// derivative of ref is RdpElement in fact...
|
||||
break;
|
||||
|
||||
case RngPatternType.List:
|
||||
checkReferences (((RdpList) p).Child);
|
||||
break;
|
||||
|
||||
case RngPatternType.Empty:
|
||||
case RngPatternType.NotAllowed:
|
||||
case RngPatternType.Text:
|
||||
case RngPatternType.Value:
|
||||
break;
|
||||
|
||||
//case RngPatternType.ExternalRef:
|
||||
//case RngPatternType.Include:
|
||||
// Mixed, Optional, ZeroOrMore are already removed.
|
||||
// Choice, Group, Interleave, OneOrMore are already proceeded.
|
||||
}
|
||||
}
|
||||
#endif
|
||||
|
||||
// Assemble combines.
|
||||
private void assembleCombine ()
|
||||
{
|
||||
@@ -470,23 +300,17 @@ namespace Commons.Xml.Relaxng
|
||||
|
||||
// assemble starts and defines with "combine" attribute.
|
||||
|
||||
// 3.assemble starts.
|
||||
// 3assemble starts.
|
||||
if (starts.Count == 0)
|
||||
throw new RngException ("grammar must have at least one start component.");
|
||||
assembledStart = ((RngStart)starts [0]).Pattern;
|
||||
assembledStart = ((RngStart)starts [0]).Compile (this);
|
||||
for (int i=1; i<starts.Count; i++) {
|
||||
RngPattern p2 = ((RngStart) starts [i]).Pattern;;
|
||||
if (combineStart == "interleave") {
|
||||
RngInterleave intlv = new RngInterleave ();
|
||||
intlv.Patterns.Add (assembledStart);
|
||||
intlv.Patterns.Add (p2);
|
||||
assembledStart = intlv;
|
||||
} else {
|
||||
RngChoice c = new RngChoice ();
|
||||
c.Patterns.Add (assembledStart);
|
||||
c.Patterns.Add (p2);
|
||||
assembledStart = c;
|
||||
}
|
||||
RdpPattern p2 = ((RngStart) starts [i])
|
||||
.Compile (this);
|
||||
if (combineStart == "interleave")
|
||||
assembledStart = new RdpInterleave (assembledStart, p2);
|
||||
else
|
||||
assembledStart = new RdpChoice (assembledStart, p2);
|
||||
}
|
||||
|
||||
// 4.assemble defines
|
||||
|
||||
@@ -71,9 +71,8 @@ namespace Commons.Xml.Relaxng
|
||||
{
|
||||
string ns;
|
||||
RngExceptNameClass except;
|
||||
public RngNsName (string ns)
|
||||
public RngNsName ()
|
||||
{
|
||||
this.ns = ns;
|
||||
}
|
||||
|
||||
public override RdpNameClass Compile (RngGrammar g)
|
||||
|
||||
Loaded 100 of 3186 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user