Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
c47f6de70e | ||
|
|
7f0542b133 | ||
|
|
9f187b5dd0 |
No files matched your search
@@ -15,8 +15,3 @@ Makefile.in
|
||||
mono-*.tar.gz
|
||||
stamp-h
|
||||
stamp-h.in
|
||||
mono.pc
|
||||
mono.spec
|
||||
autom4te.cache
|
||||
mint.pc
|
||||
stamp-h1
|
||||
@@ -1,67 +1,3 @@
|
||||
AUTOMAKE_OPTIONS = foreign
|
||||
|
||||
SUBDIRS = @libgc_dir@ mono web docs runtime scripts man data samples support
|
||||
|
||||
# EXTRA_SUBDIRS = libgc
|
||||
|
||||
EXTRA_DIST= mono.pc.in mono.spec.in mint.pc.in
|
||||
|
||||
pkgconfigdir = $(libdir)/pkgconfig
|
||||
if JIT_SUPPORTED
|
||||
pkgconfig_DATA= mono.pc mint.pc
|
||||
else
|
||||
pkgconfig_DATA= mint.pc
|
||||
endif
|
||||
DISTCLEANFILES= mono.pc mint.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 BOOTSTRAP_MCS=mcs)
|
||||
(cd ../mcs/class/corlib; $(MAKE) MCS=mcs BOOTSTRAP_MCS=mcs)
|
||||
cp ../mcs/class/lib/mscorlib.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)
|
||||
(cd runtime; $(MAKE) install assemblies_DATA=mscorlib.dll monobins_DATA=mcs.exe)
|
||||
|
||||
mcs-rest:
|
||||
(cd ../mcs/class; $(MAKE))
|
||||
|
||||
remove-binaries:
|
||||
rm ../mcs/class/lib/mscorlib.dll ../mcs/mcs/mcs.exe runtime/*dll runtime/*.exe > /dev/null 2>&1; 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
|
||||
SUBDIRS = mono doc runtime scripts man
|
||||
@@ -1,146 +1,24 @@
|
||||
|
||||
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:
|
||||
|
||||
a. Build Requirements
|
||||
---------------------
|
||||
http://www.go-mono.com/download.html
|
||||
|
||||
To build Mono, you will need the following components:
|
||||
|
||||
* pkg-config
|
||||
|
||||
Available from: http://www.freedesktop.org/Software/pkgconfig
|
||||
|
||||
* glib 2.0
|
||||
|
||||
Available from: http://www.gtk.org/
|
||||
|
||||
Optional dependencies:
|
||||
|
||||
* ICU library
|
||||
|
||||
http://oss.software.ibm.com/icu/index.html
|
||||
|
||||
You will need this one to get complete support for the international
|
||||
features of the .NET Framework.
|
||||
|
||||
* Cairo and libgdiplus
|
||||
|
||||
If you want to get support for System.Drawing, you will need to get
|
||||
both Libgdiplus and Cairo.
|
||||
|
||||
b. Building the Software
|
||||
------------------------
|
||||
|
||||
If you obtained this package as an officially released tarball,
|
||||
this is very simple, use configure and make:
|
||||
|
||||
./configure --prefix=/usr/local
|
||||
make
|
||||
make install
|
||||
|
||||
Mono supports a JIT engine on x86, SPARC and PowerPC systems.
|
||||
The various commands that ship with Mono default to the JIT engine
|
||||
on x86 and SPARC, to turn it on for PPC systems, use the --with-jit=yes
|
||||
command line option to configure.
|
||||
|
||||
MacOS X Users: you will need to download the latest Boehm GC
|
||||
Alpha release for garbage collection to work properly.
|
||||
|
||||
If you obtained this as a snapshot, you will need an existing
|
||||
Mono installation. To upgrade your installation, unpack both
|
||||
mono and mcs:
|
||||
|
||||
tar xzf mcs-XXXX.tar.gz
|
||||
tar xzf mono-XXXX.tar.gz
|
||||
cd mono-XXXX
|
||||
./autogen.sh --prefix=/usr/local
|
||||
make fullbuild
|
||||
|
||||
c. Upgrade from CVS
|
||||
-------------------
|
||||
|
||||
If you are upgrading from CVS you will need an existing Mono installation.
|
||||
First verify that you have a working installation:
|
||||
|
||||
echo 'class X { static void Main () { System.Console.Write("OK");}}' > x.cs
|
||||
|
||||
Compile:
|
||||
|
||||
mcs x.cs
|
||||
|
||||
And run:
|
||||
|
||||
mono x.exe
|
||||
|
||||
If you get the output `OK' and no errors, you are ready to start your CVS upgrade.
|
||||
|
||||
First, make sure that you have up-to-date mcs and mono sources:
|
||||
|
||||
cvs co mono mcs
|
||||
|
||||
Then, go into the mono directory, and configure:
|
||||
|
||||
cd mono
|
||||
./autogen.sh --prefix=/usr/local
|
||||
|
||||
Then compile using the special target `fullbuild':
|
||||
|
||||
make fullbuild
|
||||
|
||||
This step will compile and install at the same time.
|
||||
|
||||
Failure to follow these steps will result in a broken installation.
|
||||
|
||||
|
||||
2. Using Mono
|
||||
=============
|
||||
|
||||
Once you have installed the software, you can run a few programs:
|
||||
|
||||
* runtime engine
|
||||
|
||||
mono program.exe
|
||||
or
|
||||
mint program.exe
|
||||
|
||||
* C# compiler
|
||||
|
||||
mcs program.cs
|
||||
|
||||
* CIL Disassembler
|
||||
|
||||
monodis program.exe
|
||||
|
||||
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 the web site contents.
|
||||
|
||||
docs/
|
||||
Technical documents about the Mono runtime.
|
||||
|
||||
data/
|
||||
Configuration files installed as part of the Mono runtime.
|
||||
Contains documentation and the web site contents.
|
||||
|
||||
mono/
|
||||
The core of the Mono Runtime.
|
||||
The core of the executable.
|
||||
|
||||
metadata/
|
||||
The object system and metadata reader.
|
||||
|
||||
jit/
|
||||
The Just in Time Compiler.
|
||||
The library to deal with executables and libraries for
|
||||
.NET
|
||||
|
||||
dis/
|
||||
CIL executable Disassembler
|
||||
@@ -148,10 +26,6 @@ This is Mono.
|
||||
cli/
|
||||
Common code for the JIT and the interpreter.
|
||||
|
||||
io-layer/
|
||||
The I/O layer and system abstraction for
|
||||
emulating the .NET IO model.
|
||||
|
||||
cil/
|
||||
Common Intermediate Representation, XML
|
||||
definition of the CIL bytecodes.
|
||||
@@ -159,20 +33,20 @@ This is Mono.
|
||||
interp/
|
||||
Interpreter for CLI executables.
|
||||
|
||||
arch/
|
||||
Architecture specific portions.
|
||||
* Using Mono
|
||||
|
||||
man/
|
||||
Once you have installed the software, you can run a few programs:
|
||||
|
||||
Manual pages for the various Mono commands and programs.
|
||||
monodis program.exe
|
||||
|
||||
scripts/
|
||||
That will dump the bytecodes for program.exe. Monodis support
|
||||
a number of options that dumps various metadata tables
|
||||
(chapter 23 of the Partition III).
|
||||
|
||||
You can try the interpreter like this:
|
||||
|
||||
mint program.exe
|
||||
|
||||
Scripts used to invoke Mono and the corresponding program.
|
||||
|
||||
runtime/
|
||||
|
||||
A directory holding a pre-compiled version of the Mono
|
||||
runtime.
|
||||
|
||||
|
||||
@@ -1,12 +1,10 @@
|
||||
#undef HAVE_INET_PTON
|
||||
#undef HAVE_INET_ATON
|
||||
#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
|
||||
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
|
||||
#undef USE_MONO_MUTEX
|
||||
#undef HAVE_LARGE_FILE_SUPPORT
|
||||
@@ -15,24 +13,3 @@
|
||||
#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 HAVE_GC_ENABLE
|
||||
#undef WITH_BUNDLE
|
||||
#undef HAVE_GETHOSTBYNAME2_R
|
||||
#undef HAVE_ICU
|
||||
#undef HAVE_KW_THREAD
|
||||
#undef HAVE_SIGNBIT
|
||||
#undef USE_MACH_SEMA
|
||||
#undef HAVE_SOCKLEN_T
|
||||
#undef HAVE_TRUNCL
|
||||
#undef HAVE_AINTL
|
||||
#undef HAVE_WORKING_SIGALTSTACK
|
||||
@@ -8,17 +8,8 @@ srcdir=`dirname $0`
|
||||
test -z "$srcdir" && srcdir=.
|
||||
|
||||
if [ -n "$MONO_PATH" ]; then
|
||||
# from -> /mono/lib:/another/mono/lib
|
||||
# to -> /mono /another/mono
|
||||
for i in `echo ${MONO_PATH} | tr ":" " "`; do
|
||||
i=`dirname ${i}`
|
||||
if [ -n "{i}" -a -d "${i}/share/aclocal" ]; then
|
||||
ACLOCAL_FLAGS="-I ${i}/share/aclocal $ACLOCAL_FLAGS"
|
||||
fi
|
||||
if [ -n "{i}" -a -d "${i}/bin" ]; then
|
||||
PATH="${i}/bin:$PATH"
|
||||
fi
|
||||
done
|
||||
ACLOCAL_FLAGS="-I $MONO_PATH/share/aclocal $ACLOCAL_FLAGS"
|
||||
PATH="$MONO_PATH/bin:$PATH"
|
||||
export PATH
|
||||
fi
|
||||
|
||||
@@ -30,15 +21,8 @@ fi
|
||||
DIE=1
|
||||
}
|
||||
|
||||
if [ -z "$LIBTOOL" ]; then
|
||||
LIBTOOL=`which glibtool 2>/dev/null`
|
||||
if [ ! -x "$LIBTOOL" ]; then
|
||||
LIBTOOL=`which libtool`
|
||||
fi
|
||||
fi
|
||||
|
||||
(grep "^AM_PROG_LIBTOOL" $srcdir/configure.in >/dev/null) && {
|
||||
($LIBTOOL --version) < /dev/null > /dev/null 2>&1 || {
|
||||
(libtool --version) < /dev/null > /dev/null 2>&1 || {
|
||||
echo
|
||||
echo "**Error**: You must have \`libtool' installed to compile Mono."
|
||||
echo "Get ftp://ftp.gnu.org/pub/gnu/libtool-1.2d.tar.gz"
|
||||
@@ -98,7 +82,7 @@ esac
|
||||
if grep "^AM_PROG_LIBTOOL" configure.in >/dev/null; then
|
||||
if test -z "$NO_LIBTOOLIZE" ; then
|
||||
echo "Running libtoolize..."
|
||||
${LIBTOOL}ize --force --copy
|
||||
libtoolize --force --copy
|
||||
fi
|
||||
fi
|
||||
|
||||
@@ -124,12 +108,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
|
||||
|
||||
|
||||
@@ -1,13 +1,15 @@
|
||||
/* config.h.in. Generated from configure.in by autoheader. */
|
||||
/* 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_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
|
||||
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
|
||||
#undef USE_MONO_MUTEX
|
||||
#undef HAVE_LARGE_FILE_SUPPORT
|
||||
@@ -16,144 +18,34 @@
|
||||
#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 HAVE_GC_ENABLE
|
||||
#undef WITH_BUNDLE
|
||||
#undef HAVE_GETHOSTBYNAME2_R
|
||||
#undef HAVE_ICU
|
||||
#undef HAVE_KW_THREAD
|
||||
#undef HAVE_SIGNBIT
|
||||
#undef USE_MACH_SEMA
|
||||
#undef HAVE_SOCKLEN_T
|
||||
#undef HAVE_TRUNCL
|
||||
#undef HAVE_AINTL
|
||||
#undef HAVE_WORKING_SIGALTSTACK
|
||||
|
||||
/* Define to 1 if you have the <aio.h> header file. */
|
||||
#undef HAVE_AIO_H
|
||||
/* The number of bytes in a void *. */
|
||||
#undef SIZEOF_VOID_P
|
||||
|
||||
/* Define to 1 if you have the <dlfcn.h> header file. */
|
||||
#undef HAVE_DLFCN_H
|
||||
|
||||
/* Define to 1 if you have the <elf.h> header file. */
|
||||
#undef HAVE_ELF_H
|
||||
|
||||
/* Define to 1 if you have the `finite' function. */
|
||||
#undef HAVE_FINITE
|
||||
|
||||
/* Define to 1 if you have the <gc/gc.h> header file. */
|
||||
#undef HAVE_GC_GC_H
|
||||
|
||||
/* Define to 1 if you have the <gc.h> header file. */
|
||||
#undef HAVE_GC_H
|
||||
|
||||
/* Define to 1 if you have the `inet_aton' function. */
|
||||
/* Define if you have the inet_aton function. */
|
||||
#undef HAVE_INET_ATON
|
||||
|
||||
/* Define to 1 if you have the `inet_pton' function. */
|
||||
/* Define if you have the inet_pton function. */
|
||||
#undef HAVE_INET_PTON
|
||||
|
||||
/* Define to 1 if you have the <inttypes.h> header file. */
|
||||
#undef HAVE_INTTYPES_H
|
||||
/* Define if you have the <dlfcn.h> header file. */
|
||||
#undef HAVE_DLFCN_H
|
||||
|
||||
/* Define to 1 if you have the `isfinite' function. */
|
||||
#undef HAVE_ISFINITE
|
||||
|
||||
/* Define to 1 if you have the <memory.h> header file. */
|
||||
#undef HAVE_MEMORY_H
|
||||
|
||||
/* Define to 1 if you have the <netdb.h> header file. */
|
||||
/* Define if you have the <netdb.h> header file. */
|
||||
#undef HAVE_NETDB_H
|
||||
|
||||
/* Define to 1 if you have the `poll' function. */
|
||||
#undef HAVE_POLL
|
||||
|
||||
/* Define to 1 if you have the `pthread_attr_setstacksize' function. */
|
||||
#undef HAVE_PTHREAD_ATTR_SETSTACKSIZE
|
||||
|
||||
/* Define to 1 if you have the <pthread.h> header file. */
|
||||
#undef HAVE_PTHREAD_H
|
||||
|
||||
/* Define to 1 if you have the `pthread_mutex_timedlock' function. */
|
||||
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
|
||||
|
||||
/* Define to 1 if you have the <semaphore.h> header file. */
|
||||
#undef HAVE_SEMAPHORE_H
|
||||
|
||||
/* Define to 1 if you have the <stdint.h> header file. */
|
||||
#undef HAVE_STDINT_H
|
||||
|
||||
/* Define to 1 if you have the <stdlib.h> header file. */
|
||||
#undef HAVE_STDLIB_H
|
||||
|
||||
/* Define to 1 if you have the <strings.h> header file. */
|
||||
#undef HAVE_STRINGS_H
|
||||
|
||||
/* Define to 1 if you have the <string.h> header file. */
|
||||
#undef HAVE_STRING_H
|
||||
|
||||
/* Define to 1 if you have the <sys/filio.h> header file. */
|
||||
/* Define if you have the <sys/filio.h> header file. */
|
||||
#undef HAVE_SYS_FILIO_H
|
||||
|
||||
/* Define to 1 if you have the <sys/sockio.h> header file. */
|
||||
/* Define if you have the <sys/sockio.h> header file. */
|
||||
#undef HAVE_SYS_SOCKIO_H
|
||||
|
||||
/* Define to 1 if you have the <sys/stat.h> header file. */
|
||||
#undef HAVE_SYS_STAT_H
|
||||
|
||||
/* Define to 1 if you have the <sys/types.h> header file. */
|
||||
#undef HAVE_SYS_TYPES_H
|
||||
|
||||
/* Define to 1 if you have the <sys/un.h> header file. */
|
||||
#undef HAVE_SYS_UN_H
|
||||
|
||||
/* Define to 1 if you have the `truncl' function. */
|
||||
#undef HAVE_TRUNCL
|
||||
|
||||
/* Define to 1 if you have the <unistd.h> header file. */
|
||||
#undef HAVE_UNISTD_H
|
||||
|
||||
/* Define to 1 if you have the <utime.h> header file. */
|
||||
/* Define if you have the <utime.h> header file. */
|
||||
#undef HAVE_UTIME_H
|
||||
|
||||
/* Define to 1 if you have the <valgrind/memcheck.h> header file. */
|
||||
#undef HAVE_VALGRIND_MEMCHECK_H
|
||||
|
||||
/* Define to 1 if you have the <wchar.h> header file. */
|
||||
#undef HAVE_WCHAR_H
|
||||
|
||||
/* Name of package */
|
||||
#undef PACKAGE
|
||||
|
||||
/* Define to the address where bug reports for this package should be sent. */
|
||||
#undef PACKAGE_BUGREPORT
|
||||
|
||||
/* Define to the full name of this package. */
|
||||
#undef PACKAGE_NAME
|
||||
|
||||
/* Define to the full name and version of this package. */
|
||||
#undef PACKAGE_STRING
|
||||
|
||||
/* Define to the one symbol short name of this package. */
|
||||
#undef PACKAGE_TARNAME
|
||||
|
||||
/* Define to the version of this package. */
|
||||
#undef PACKAGE_VERSION
|
||||
|
||||
/* The size of a `void *', as computed by sizeof. */
|
||||
#undef SIZEOF_VOID_P
|
||||
|
||||
/* Define to 1 if you have the ANSI C header files. */
|
||||
#undef STDC_HEADERS
|
||||
|
||||
/* Version number of package */
|
||||
#undef VERSION
|
||||
|
||||
@@ -1,137 +1,14 @@
|
||||
|
||||
AC_INIT(README)
|
||||
AC_CANONICAL_SYSTEM
|
||||
AM_CONFIG_HEADER(config.h)
|
||||
AM_INIT_AUTOMAKE(mono,0.31)
|
||||
AM_INIT_AUTOMAKE(mono, 0.10)
|
||||
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
|
||||
#
|
||||
libmono_cflags=""
|
||||
libmono_ldflags=""
|
||||
AC_SUBST(libmono_cflags)
|
||||
AC_SUBST(libmono_ldflags)
|
||||
|
||||
dnl if linker handles the version script
|
||||
no_version_script=no
|
||||
|
||||
# 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"
|
||||
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*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -D_THREAD_SAFE"
|
||||
libmono_cflags="-D_THREAD_SAFE"
|
||||
LDFLAGS="$LDFLAGS -pthread"
|
||||
libmono_ldflags="-pthread"
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
AC_DEFINE(PTHREAD_POINTER_ID)
|
||||
libdl=
|
||||
libgc_threads=pthreads
|
||||
;;
|
||||
*-*-linux*)
|
||||
platform_win32=no
|
||||
CPPFLAGS="$CPPFLAGS -DGC_LINUX_THREADS -DMONO_USE_EXC_TABLES -D_GNU_SOURCE -D_REENTRANT -fexceptions"
|
||||
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"
|
||||
CFLAGS="$CFLAGS +ESdbgasm"
|
||||
LDFLAGS="$LDFLAGS -z"
|
||||
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
|
||||
CPPFLAGS="$CPPFLAGS -no-cpp-precomp -D_THREAD_SAFE"
|
||||
libmono_cflags="-D_THREAD_SAFE"
|
||||
LDFLAGS="$LDFLAGS -pthread"
|
||||
libmono_ldflags="-pthread"
|
||||
AC_DEFINE(NEED_LINK_UNLINK)
|
||||
AC_DEFINE(PTHREAD_POINTER_ID)
|
||||
AC_DEFINE(USE_MACH_SEMA)
|
||||
no_version_script=yes
|
||||
libdl=
|
||||
libgc_threads=no
|
||||
gc_default=none
|
||||
;;
|
||||
*)
|
||||
AC_MSG_WARN([*** Please add $host to configure.in checks!])
|
||||
platform_win32=no
|
||||
libdl="-ldl"
|
||||
;;
|
||||
esac
|
||||
AC_MSG_RESULT(ok)
|
||||
AM_CONDITIONAL(PLATFORM_WIN32, test x$platform_win32 = xyes)
|
||||
AM_CONDITIONAL(NO_VERSION_SCRIPT, test x$no_version_script = xyes)
|
||||
|
||||
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";
|
||||
then
|
||||
AC_MSG_ERROR([You need to install bison])
|
||||
fi
|
||||
|
||||
dnl may require a specific autoconf version
|
||||
dnl AC_PROG_CC_FOR_BUILD
|
||||
@@ -151,35 +28,15 @@ AC_HEADER_STDC
|
||||
AC_LIBTOOL_WIN32_DLL
|
||||
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)
|
||||
AC_CHECK_HEADERS(sys/filio.h sys/sockio.h netdb.h utime.h)
|
||||
|
||||
# for mono/metadata/debug-symfile.c
|
||||
AC_CHECK_HEADERS(elf.h)
|
||||
|
||||
# for mono/dis
|
||||
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'
|
||||
# The runtime code does not respect ANSI C strict aliasing rules
|
||||
CFLAGS="$CFLAGS -fno-strict-aliasing"
|
||||
else
|
||||
# The Sun Forte compiler complains about inline functions that access static variables
|
||||
# so disable all inlining.
|
||||
case "$host" in
|
||||
*-*-solaris*)
|
||||
CFLAGS="$CFLAGS -Dinline="
|
||||
;;
|
||||
esac
|
||||
fi
|
||||
CFLAGS="$CFLAGS -g $WARN"
|
||||
CFLAGS='-g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations'
|
||||
|
||||
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
|
||||
if test "x$PKG_CONFIG" = "xno"; then
|
||||
@@ -188,8 +45,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)
|
||||
|
||||
@@ -211,8 +68,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`
|
||||
|
||||
@@ -221,101 +78,50 @@ 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])
|
||||
AC_CHECK_LIB(gc, GC_malloc, found_boehm="yes")
|
||||
gc=none
|
||||
AC_ARG_WITH(gc, [ --with-gc=boehm,none],[gc=$with_gc])
|
||||
|
||||
# Enable support for NPTL only features like fast thread-local storage
|
||||
# We can't reliably detect nptl at compile & run time
|
||||
# so this option will stay until nptl becomes more widespread
|
||||
AC_ARG_WITH(nptl, [ --with-nptl=yes,no enable/disable support for NPTL],[],[with_nptl=yes])
|
||||
|
||||
# Enable support for using sigaltstack for SIGSEGV and stack overflow handling
|
||||
# This does not work on some platforms (bug #55253)
|
||||
AC_ARG_WITH(sigaltstack, [ --with-sigaltstack=yes,no enable/disable support for sigaltstack],[],[with_sigaltstack=yes])
|
||||
|
||||
if test x$with_sigaltstack = "xyes"; then
|
||||
AC_DEFINE(HAVE_WORKING_SIGALTSTACK)
|
||||
fi
|
||||
|
||||
# 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)
|
||||
|
||||
xboehm|xyes)
|
||||
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.")
|
||||
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.")
|
||||
AC_MSG_ERROR("GC requested but libgc not found!")
|
||||
fi
|
||||
|
||||
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
|
||||
AC_CHECK_LIB(gc, GC_enable, found_gc_enable="yes",,$libdl)
|
||||
if test "x$found_gc_enable" = "xyes"; then
|
||||
AC_DEFINE(HAVE_GC_ENABLE)
|
||||
fi
|
||||
;;
|
||||
|
||||
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)
|
||||
AC_DEFINE(HAVE_GC_ENABLE)
|
||||
;;
|
||||
|
||||
xnone)
|
||||
AC_MSG_WARN("Compiling mono without GC.")
|
||||
LIBS="$LIBS -lgc"
|
||||
;;
|
||||
*)
|
||||
AC_MSG_ERROR([Invalid argument to --with-gc.])
|
||||
dnl When the JIT works with libgc, use this chunk.
|
||||
dnl # If libgc was found, use it. Otherwise just warn.
|
||||
if test "x$found_boehm" != "xyes"; then
|
||||
AC_MSG_WARN("Compiling mono without GC.")
|
||||
else
|
||||
AC_DEFINE(HAVE_BOEHM_GC)
|
||||
AC_SUBST(HAVE_BOEHM_GC)
|
||||
LIBS="$LIBS -lgc"
|
||||
gc="boehm"
|
||||
fi
|
||||
dnl AC_MSG_WARN("Compiling mono without GC.")
|
||||
;;
|
||||
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
|
||||
dnl ****************************************
|
||||
dnl *** Check if we're building on win32 ***
|
||||
dnl ****************************************
|
||||
AC_MSG_CHECKING([if building for some Win32 platform])
|
||||
case "$host" in
|
||||
*-*-mingw*|*-*-cygwin*)
|
||||
platform_win32=yes
|
||||
AC_DEFINE(PLATFORM_WIN32)
|
||||
;;
|
||||
*)
|
||||
platform_win32=no
|
||||
;;
|
||||
esac
|
||||
AC_MSG_RESULT($platform_win32)
|
||||
AM_CONDITIONAL(PLATFORM_WIN32, test x$platform_win32 = xyes)
|
||||
|
||||
if test x$platform_win32 = xno; then
|
||||
dnl ******************************************************************
|
||||
@@ -325,7 +131,7 @@ if test x$platform_win32 = xno; then
|
||||
|
||||
# Check that off_t can represent 2**63 - 1 correctly, working around
|
||||
# potential compiler bugs. Defines LARGE_FILE_SUPPORT, adds $1 to
|
||||
# CPPFLAGS and sets $large_offt to yes if the test succeeds
|
||||
# CFLAGS and sets $large_offt to yes if the test succeeds
|
||||
large_offt=no
|
||||
AC_DEFUN(LARGE_FILES, [
|
||||
large_CPPFLAGS=$CPPFLAGS
|
||||
@@ -347,7 +153,7 @@ if test x$platform_win32 = xno; then
|
||||
], [
|
||||
AC_MSG_RESULT(ok)
|
||||
AC_DEFINE(HAVE_LARGE_FILE_SUPPORT)
|
||||
large_CPPFLAGS="$large_CPPFLAGS $1"
|
||||
CFLAGS="$CFLAGS $1"
|
||||
large_offt=yes
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
@@ -370,21 +176,6 @@ if test x$platform_win32 = xno; then
|
||||
dnl *****************************
|
||||
AC_CHECK_LIB(socket, socket, LIBS="$LIBS -lsocket")
|
||||
|
||||
dnl *******************************
|
||||
dnl *** Checks for MSG_NOSIGNAL ***
|
||||
dnl *******************************
|
||||
AC_MSG_CHECKING(for MSG_NOSIGNAL)
|
||||
AC_TRY_COMPILE([#include <sys/socket.h>], [
|
||||
int f = MSG_NOSIGNAL;
|
||||
], [
|
||||
# Yes, we have it...
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_MSG_NOSIGNAL)
|
||||
], [
|
||||
# We'll have to use signals
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for SOL_IP ***
|
||||
dnl *****************************
|
||||
@@ -400,21 +191,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 *****************************
|
||||
@@ -456,33 +232,7 @@ 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
|
||||
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)
|
||||
], [
|
||||
# We'll just have to use struct ip_mreq
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
@@ -493,237 +243,99 @@ if test x$platform_win32 = xno; then
|
||||
|
||||
AC_CHECK_FUNCS(inet_pton inet_aton)
|
||||
|
||||
dnl ***********************************************
|
||||
dnl *** Checks for size of sockaddr_un.sun_path ***
|
||||
dnl ***********************************************
|
||||
# AC_CHECK_SIZEOF can't cope with struct members :-(
|
||||
AC_MSG_CHECKING(size of sockaddr_un.sun_path)
|
||||
AC_CACHE_VAL(cv_mono_sizeof_sunpath,
|
||||
[AC_TRY_RUN([
|
||||
#include <sys/types.h>
|
||||
#include <stdio.h>
|
||||
#include <sys/un.h>
|
||||
|
||||
int main(void) {
|
||||
struct sockaddr_un sock_un;
|
||||
FILE *f=fopen("conftestval", "w");
|
||||
if(!f) exit(1);
|
||||
fprintf(f, "%d\n", sizeof(sock_un.sun_path));
|
||||
exit(0);
|
||||
}
|
||||
], cv_mono_sizeof_sunpath=`cat conftestval`,
|
||||
cv_mono_sizeof_sunpath=0,
|
||||
cv_mono_sizeof_sunpath=0)])dnl
|
||||
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 *****************************
|
||||
case "${host}" in
|
||||
*solaris* )
|
||||
AC_MSG_CHECKING(for Solaris XPG4 support)
|
||||
if test -f /usr/lib/libxnet.so; then
|
||||
CPPFLAGS="$CPPFLAGS -D_XOPEN_SOURCE=500"
|
||||
CPPFLAGS="$CPPFLAGS -D__EXTENSIONS__"
|
||||
CPPFLAGS="$CPPFLAGS -D_XOPEN_SOURCE_EXTENDED=1"
|
||||
LIBS="$LIBS -lxnet"
|
||||
AC_MSG_RESULT(yes)
|
||||
else
|
||||
AC_MSG_RESULT(no)
|
||||
fi
|
||||
|
||||
if test "$GCC" = "yes"; then
|
||||
CFLAGS="$CFLAGS -Wno-char-subscripts"
|
||||
fi
|
||||
;;
|
||||
esac
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for libpthread ***
|
||||
dnl *****************************
|
||||
AC_CHECK_LIB(pthread, main, LIBS="$LIBS -lpthread")
|
||||
AC_CHECK_HEADERS(pthread.h)
|
||||
AC_CHECK_FUNCS(pthread_mutex_timedlock)
|
||||
AC_MSG_CHECKING(for PTHREAD_MUTEX_RECURSIVE)
|
||||
AC_TRY_COMPILE([ #include <pthread.h>], [
|
||||
pthread_mutexattr_t attr;
|
||||
pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
|
||||
], [
|
||||
AC_MSG_RESULT(ok)
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
AC_MSG_WARN(Using mono_mutex_t for recursive mutexes)
|
||||
AC_DEFINE(USE_MONO_MUTEX)
|
||||
])
|
||||
AC_CHECK_FUNCS(pthread_attr_setstacksize)
|
||||
AC_SEARCH_LIBS(pthread_create, pthread, [
|
||||
AM_CONDITIONAL(THREADS_PTHREAD, true)
|
||||
AC_DEFINE(HAVE_PTHREAD)
|
||||
|
||||
dnl ***********************************
|
||||
dnl *** Checks for working __thread ***
|
||||
dnl ***********************************
|
||||
AC_MSG_CHECKING(for working __thread)
|
||||
AC_TRY_RUN([
|
||||
#include <pthread.h>
|
||||
|
||||
__thread int i;
|
||||
static int res1, res2;
|
||||
|
||||
void thread_main (void *arg)
|
||||
{
|
||||
i = arg;
|
||||
sleep (1);
|
||||
if (arg == 1)
|
||||
res1 = (i == arg);
|
||||
else
|
||||
res2 = (i == arg);
|
||||
}
|
||||
|
||||
int main () {
|
||||
pthread_t t1, t2;
|
||||
|
||||
i = 5;
|
||||
|
||||
pthread_create (&t1, NULL, thread_main, 1);
|
||||
pthread_create (&t2, NULL, thread_main, 2);
|
||||
|
||||
pthread_join (t1, NULL);
|
||||
pthread_join (t2, NULL);
|
||||
|
||||
return !(res1 + res2 == 2);
|
||||
}
|
||||
], [
|
||||
if test "x$with_nptl" != "xyes"; then
|
||||
AC_MSG_RESULT(disabled)
|
||||
else
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_KW_THREAD)
|
||||
fi
|
||||
], [
|
||||
# Need pthread_mutex_timedlock
|
||||
pthread_CFLAGS=""
|
||||
orig_CPPFLAGS=$CPPFLAGS
|
||||
# This is a gcc-specific error, but we already set
|
||||
# gcc-specific options in CFLAGS
|
||||
CPPFLAGS="$CPPFLAGS -Werror-implicit-function-declaration"
|
||||
AC_MSG_CHECKING(for pthread_mutex_timedlock)
|
||||
AC_TRY_COMPILE([ #include <pthread.h>], [
|
||||
pthread_mutex_t mut=PTHREAD_MUTEX_INITIALIZER;
|
||||
pthread_mutex_timedlock(&mut, NULL);
|
||||
], [
|
||||
# Works!
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_PTHREAD_MUTEX_TIMEDLOCK)
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
|
||||
# glibc requires -D_GNU_SOURCE before it will declare
|
||||
# this function
|
||||
AC_MSG_CHECKING(whether _GNU_SOURCE is needed for pthread_mutex_timedlock)
|
||||
CPPFLAGS="$CPPFLAGS -D_GNU_SOURCE"
|
||||
AC_TRY_COMPILE([ #include <pthread.h>], [
|
||||
pthread_mutex_t mut=PTHREAD_MUTEX_INITIALIZER;
|
||||
pthread_mutex_timedlock(&mut, NULL);
|
||||
], [
|
||||
AC_MSG_RESULT(yes)
|
||||
pthread_CFLAGS="-D_GNU_SOURCE"
|
||||
AC_DEFINE(HAVE_PTHREAD_MUTEX_TIMEDLOCK)
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
dnl Add other variants here
|
||||
AC_MSG_WARN(Working around pthread_mutex_timedlock)
|
||||
])
|
||||
])
|
||||
CPPFLAGS=$orig_CPPFLAGS
|
||||
CFLAGS="$CFLAGS $pthread_CFLAGS"
|
||||
|
||||
# Need PTHREAD_MUTEX_RECURSIVE
|
||||
pthread_CFLAGS=""
|
||||
orig_CPPFLAGS=$CPPFLAGS
|
||||
# This is a gcc-specific error, but we already set
|
||||
# gcc-specific options in CFLAGS
|
||||
CPPFLAGS="$CPPFLAGS -Werror-implicit-function-declaration"
|
||||
AC_MSG_CHECKING(for PTHREAD_MUTEX_RECURSIVE)
|
||||
AC_TRY_COMPILE([ #include <pthread.h>], [
|
||||
pthread_mutexattr_t attr;
|
||||
pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
|
||||
], [
|
||||
# Works!
|
||||
AC_MSG_RESULT(ok)
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
|
||||
# glibc requires -D_GNU_SOURCE before it will declare
|
||||
# this macro
|
||||
AC_MSG_CHECKING(whether _GNU_SOURCE is needed for PTHREAD_MUTEX_RECURSIVE)
|
||||
CPPFLAGS="$CPPFLAGS -D_GNU_SOURCE"
|
||||
AC_TRY_COMPILE([ #include <pthread.h>], [
|
||||
pthread_mutexattr_t attr;
|
||||
pthread_mutexattr_settype(&attr, PTHREAD_MUTEX_RECURSIVE);
|
||||
], [
|
||||
AC_MSG_RESULT(ok)
|
||||
pthread_CFLAGS="-D_GNU_SOURCE"
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
dnl Add other variants here
|
||||
AC_MSG_WARN(Using mono_mutex_t for recursive mutexes)
|
||||
AC_DEFINE(USE_MONO_MUTEX)
|
||||
])
|
||||
])
|
||||
CPPFLAGS=$orig_CPPFLAGS
|
||||
CFLAGS="$CFLAGS $pthread_CFLAGS"
|
||||
], [
|
||||
AC_MSG_ERROR([libpthread is required on non-win32 hosts])
|
||||
])
|
||||
|
||||
dnl ********************************
|
||||
dnl *** Checks for semaphore lib ***
|
||||
dnl ********************************
|
||||
# 'Real Time' functions on Solaris
|
||||
# posix4 on Solaris 2.6
|
||||
# pthread (first!) on Linux
|
||||
AC_SEARCH_LIBS(sem_init, pthread rt posix4)
|
||||
|
||||
dnl ********************************
|
||||
dnl *** Checks for timezone stuff **
|
||||
dnl ********************************
|
||||
AC_CACHE_CHECK(for tm_gmtoff in struct tm, ac_cv_struct_tm_gmtoff,
|
||||
AC_TRY_COMPILE([
|
||||
#include <time.h>
|
||||
], [
|
||||
struct tm tm;
|
||||
tm.tm_gmtoff = 1;
|
||||
], ac_cv_struct_tm_gmtoff=yes, ac_cv_struct_tm_gmtoff=no))
|
||||
if test $ac_cv_struct_tm_gmtoff = yes; then
|
||||
AC_DEFINE(HAVE_TM_GMTOFF)
|
||||
else
|
||||
AC_CACHE_CHECK(for timezone variable, ac_cv_var_timezone,
|
||||
AC_TRY_COMPILE([
|
||||
#include <time.h>
|
||||
], [
|
||||
timezone = 1;
|
||||
], ac_cv_var_timezone=yes, ac_cv_var_timezone=no))
|
||||
if test $ac_cv_var_timezone = yes; then
|
||||
AC_DEFINE(HAVE_TIMEZONE)
|
||||
else
|
||||
AC_ERROR(unable to find a way to determine timezone)
|
||||
fi
|
||||
fi
|
||||
|
||||
dnl *********************************
|
||||
dnl *** Checks for math functions ***
|
||||
dnl *********************************
|
||||
LIBS="$LIBS -lm";
|
||||
AC_CHECK_FUNCS(finite, , AC_MSG_CHECKING(for finite in math.h)
|
||||
AC_TRY_LINK([#include <math.h>],
|
||||
[ finite(0.0); ],
|
||||
AC_DEFINE(HAVE_FINITE) AC_MSG_RESULT(yes),
|
||||
AC_MSG_RESULT(no)))
|
||||
AC_CHECK_FUNCS(isfinite, , AC_MSG_CHECKING(for isfinite in math.h)
|
||||
AC_TRY_LINK([#include <math.h>],
|
||||
[ isfinite(0.0); ],
|
||||
AC_DEFINE(HAVE_ISFINITE) AC_MSG_RESULT(yes),
|
||||
AC_MSG_RESULT(no)))
|
||||
|
||||
dnl ****************************************************************
|
||||
dnl *** Checks for working poll() (macosx defines it but doesn't ***
|
||||
dnl *** have it in the library (duh)) ***
|
||||
dnl ****************************************************************
|
||||
AC_CHECK_FUNCS(poll)
|
||||
|
||||
dnl *************************
|
||||
dnl *** Check for signbit ***
|
||||
dnl *************************
|
||||
AC_MSG_CHECKING(for signbit)
|
||||
AC_TRY_LINK([#include <math.h>], [
|
||||
int s = signbit(1.0);
|
||||
], [
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_SIGNBIT)
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
dnl *********************
|
||||
dnl *** Check for AIO ***
|
||||
dnl *********************
|
||||
AC_CHECK_HEADERS(aio.h)
|
||||
AC_CHECK_LIB(rt, aio_read, [ LIBS="$LIBS -lrt" ],)
|
||||
AC_CHECK_LIB(rt, sem_init, LIBS="$LIBS -lrt")
|
||||
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?))
|
||||
fi
|
||||
|
||||
dnl socklen_t check
|
||||
AC_MSG_CHECKING(for socklen_t)
|
||||
AC_TRY_COMPILE([
|
||||
#include <sys/types.h>
|
||||
#include <sys/socket.h>
|
||||
],[
|
||||
socklen_t foo;
|
||||
],[
|
||||
ac_cv_c_socklen_t=yes
|
||||
AC_DEFINE(HAVE_SOCKLEN_T)
|
||||
AC_MSG_RESULT(yes)
|
||||
],[
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
AC_CHECK_FUNCS(truncl, , AC_MSG_CHECKING(for truncl in math.h)
|
||||
AC_TRY_LINK([#include <math.h>],
|
||||
[ truncl(0.0); ],
|
||||
[
|
||||
AC_DEFINE(HAVE_TRUNCL)
|
||||
AC_MSG_RESULT(yes)
|
||||
ac_cv_truncl=yes
|
||||
],
|
||||
AC_MSG_RESULT(no)))
|
||||
|
||||
if test "x$ac_cv_truncl" != "xyes"; then
|
||||
AC_CHECK_LIB(sunmath, aintl, [ AC_DEFINE(HAVE_AINTL) LIBS="$LIBS -lsunmath"])
|
||||
# This is a kludge, we really ought to test for libws2_32, but
|
||||
# I can't make AC_CHECK_LIB link (the symbols seem to be mangled
|
||||
# with @num suffixes)
|
||||
LIBS="$LIBS -lws2_32"
|
||||
CFLAGS="$CFLAGS -mno-cygwin"
|
||||
fi
|
||||
|
||||
dnl ****************************
|
||||
@@ -791,148 +403,42 @@ if test "x$ac_cv_have_dev_random" = "xno" \
|
||||
***]])
|
||||
fi
|
||||
|
||||
AC_MSG_CHECKING([if inter-process shared handles are requested])
|
||||
AC_ARG_ENABLE(shared-handles, [ --disable-shared-handles disable inter-process shared handles], try_shared_handles=$enableval, try_shared_handles=yes)
|
||||
AC_MSG_RESULT($try_shared_handles)
|
||||
if test "x$try_shared_handles" != "xyes"; then
|
||||
AC_DEFINE(DISABLE_SHARED_HANDLES)
|
||||
AC_SUBST(DISABLE_SHARED_HANDLES)
|
||||
fi
|
||||
|
||||
ICU_CFLAGS=""
|
||||
ICU_LIBS=""
|
||||
enable_icu=no
|
||||
AC_PATH_PROG(ICU_CONFIG, icu-config, no)
|
||||
if test "x$ICU_CONFIG" = "xno" -o ! -x "$ICU_CONFIG"; then
|
||||
AC_MSG_WARN([Only invariant locale available; install ICU for I18N support])
|
||||
enable_icu="no, if you want full i18n support download it from: http://oss.software.ibm.com/icu/index.html"
|
||||
if test "x$cross_compiling" = "xno"; then
|
||||
# check for new iconv version
|
||||
AC_MSG_CHECKING(for new iconv)
|
||||
AC_CACHE_VAL(new_iconv,[
|
||||
AC_TRY_RUN([#include <stdio.h>
|
||||
#include <iconv.h>
|
||||
|
||||
int main()
|
||||
{
|
||||
exit (iconv_open ("UTF-16le", "UTF-8") == (iconv_t)-1);
|
||||
}
|
||||
],
|
||||
new_iconv=yes,new_iconv=)])
|
||||
if test -n "$new_iconv"; then
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_NEW_ICONV)
|
||||
else
|
||||
enable_icu="yes. Version: `$ICU_CONFIG --version`"
|
||||
AC_DEFINE(HAVE_ICU)
|
||||
ICU_CFLAGS=`$ICU_CONFIG --cppflags`
|
||||
ICU_LIBS=`$ICU_CONFIG --ldflags`
|
||||
AC_MSG_RESULT(no)
|
||||
fi
|
||||
fi
|
||||
AC_SUBST(ICU_CFLAGS)
|
||||
AC_SUBST(ICU_LIBS)
|
||||
|
||||
TARGET="unknown"
|
||||
ACCESS_UNALIGNED="yes"
|
||||
|
||||
JIT_SUPPORTED=no
|
||||
LIBC="libc.so.6"
|
||||
|
||||
jit_wanted=false
|
||||
case "$host" in
|
||||
# mips-sgi-irix5.* | mips-sgi-irix6.*)
|
||||
# TARGET=MIPS;
|
||||
# ACCESS_UNALIGNED="no"
|
||||
# ;;
|
||||
i*86-*-*)
|
||||
TARGET=X86;
|
||||
arch_target=x86;
|
||||
JIT_SUPPORTED=yes
|
||||
jit_wanted=true
|
||||
;;
|
||||
x86_64-*-* | amd64-*-*)
|
||||
TARGET=AMD64;
|
||||
arch_target=x86-64;
|
||||
JIT_SUPPORTED=no
|
||||
;;
|
||||
sparc*-*-*)
|
||||
TARGET=SPARC;
|
||||
arch_target=sparc;
|
||||
JIT_SUPPORTED=yes
|
||||
ACCESS_UNALIGNED="no"
|
||||
jit_wanted=true
|
||||
;;
|
||||
# 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
|
||||
# ;;
|
||||
hppa2.0w-hp-hpux11.00 | hppa64-hp-hpux11.00)
|
||||
TARGET=HPPA;
|
||||
arch_target=hppa;
|
||||
ACCESS_UNALIGNED="no"
|
||||
;;
|
||||
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;;
|
||||
powerpc-*-linux* | powerpc-*-sysv*) TARGET=POWERPC; arch_target=ppc;;
|
||||
arm-*-linux-*) TARGET=ARM; arch_target=arm; ACCESS_UNALIGNED="no";;
|
||||
esac
|
||||
|
||||
AC_ARG_WITH(jit, [ --with-jit=yes,no If you want to build scripts that default to the JIT],[
|
||||
jit_wanted=true
|
||||
])
|
||||
|
||||
USEJIT=false
|
||||
if test x$JIT_SUPPORTED = xyes; then
|
||||
if $jit_wanted; then
|
||||
USEJIT=true
|
||||
jit_status="Building and using the JIT"
|
||||
else
|
||||
jit_status="Building the JIT, defaulting to the interpreter"
|
||||
fi
|
||||
else
|
||||
jit_status="interpreter"
|
||||
fi
|
||||
|
||||
AM_CONDITIONAL(USE_JIT, test x$USEJIT = xtrue)
|
||||
|
||||
libsuffix=".so"
|
||||
|
||||
case "$host" in
|
||||
powerpc-*-darwin*)
|
||||
libsuffix=".dylib"
|
||||
;;
|
||||
esac
|
||||
AC_SUBST(libsuffix)
|
||||
|
||||
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"
|
||||
CFLAGS="$CFLAGS -DNO_PORT"
|
||||
AC_MSG_WARN("mono has not been ported to $host: some things may not work.")
|
||||
fi
|
||||
|
||||
@@ -944,73 +450,41 @@ AM_CONDITIONAL(MIPS_GCC, test ${TARGET}${ac_cv_prog_gcc} = MIPSyes)
|
||||
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(AMD64, test x$TARGET = xAMD64)
|
||||
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(HPPA, test x$TARGET = xHPPA)
|
||||
|
||||
AM_CONDITIONAL(JIT_SUPPORTED, test x$JIT_SUPPORTED = xyes)
|
||||
|
||||
AC_SUBST(LIBC)
|
||||
|
||||
AC_SUBST(arch_target)
|
||||
AC_SUBST(CFLAGS)
|
||||
AC_SUBST(CPPFLAGS)
|
||||
AC_SUBST(LDFLAGS)
|
||||
|
||||
AC_OUTPUT([
|
||||
Makefile
|
||||
mint.pc
|
||||
mono.pc
|
||||
mono/Makefile
|
||||
mono/utils/Makefile
|
||||
mono/metadata/Makefile
|
||||
mono/dis/Makefile
|
||||
mono/cil/Makefile
|
||||
mono/arch/Makefile
|
||||
mono/os/Makefile
|
||||
mono/os/win32/Makefile
|
||||
mono/os/unix/Makefile
|
||||
mono/arch/x86/Makefile
|
||||
mono/arch/amd64/Makefile
|
||||
mono/arch/hppa/Makefile
|
||||
mono/arch/ppc/Makefile
|
||||
mono/arch/sparc/Makefile
|
||||
mono/arch/s390/Makefile
|
||||
mono/arch/arm/Makefile
|
||||
mono/arch/alpha/Makefile
|
||||
mono/interpreter/Makefile
|
||||
mono/tests/Makefile
|
||||
mono/tests/tests-config
|
||||
mono/benchmark/Makefile
|
||||
mono/wrapper/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
|
||||
web/Makefile
|
||||
docs/Makefile
|
||||
data/Makefile
|
||||
samples/Makefile
|
||||
support/Makefile
|
||||
data/config
|
||||
mono.spec
|
||||
doc/Makefile
|
||||
])
|
||||
|
||||
echo "
|
||||
|
||||
GC: $gc
|
||||
ICU: $enable_icu
|
||||
NPTL: $with_nptl
|
||||
SIGALTSTACK: $with_sigaltstack
|
||||
Engine: $jit_status
|
||||
|
||||
GC: $gc
|
||||
|
||||
"
|
||||
@@ -1,5 +0,0 @@
|
||||
Makefile.in
|
||||
Makefile
|
||||
config
|
||||
.cvsignore
|
||||
browscap.ini
|
||||
@@ -1,15 +0,0 @@
|
||||
monodir = $(sysconfdir)/mono
|
||||
|
||||
EXTRA_DIST = config.in \
|
||||
machine.config \
|
||||
DefaultWsdlHelpGenerator.aspx \
|
||||
browscap.ini.gz
|
||||
|
||||
mono_DATA = config \
|
||||
machine.config \
|
||||
DefaultWsdlHelpGenerator.aspx \
|
||||
browscap.ini
|
||||
|
||||
browscap.ini: browscap.ini.gz
|
||||
gunzip -c $^ > $@
|
||||
|
||||
@@ -1,21 +0,0 @@
|
||||
<configuration>
|
||||
<dllmap dll="cygwin1.dll" target="@LIBC@" />
|
||||
<dllmap dll="libc" target="@LIBC@" />
|
||||
<dllmap dll="libxslt.dll" target="libxslt.so" />
|
||||
<dllmap dll="libmySQL.dll" target="libmysqlclient.so" />
|
||||
<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" />
|
||||
<dllmap dll="libgdk_pixbuf-2.0-0.dll" target="libgdk_pixbuf-2.0.so" />
|
||||
<dllmap dll="libgtk-win32-2.0-0.dll" target="libgtk-x11-2.0.so" />
|
||||
<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" />
|
||||
<dllmap dll="db2cli" target="libdb2_36.so"/>
|
||||
<dllmap dll="gstreamer" target="libgstreamer-0.6.so" />
|
||||
</configuration>
|
||||
@@ -1,196 +0,0 @@
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
|
||||
<configuration>
|
||||
|
||||
<configSections>
|
||||
<section name="appSettings" type="System.Configuration.NameValueFileSectionHandler, System" />
|
||||
<section name="system.diagnostics" type="System.Diagnostics.DiagnosticsConfigurationHandler, System" />
|
||||
<section name="system.runtime.remoting" type="System.Configuration.IgnoreSectionHandler, System" allowLocation="false"/>
|
||||
<sectionGroup name="system.web">
|
||||
<section name="httpHandlers"
|
||||
type="System.Web.Configuration.HttpHandlersSectionHandler, System.Web" />
|
||||
<section name="httpModules"
|
||||
type="System.Web.Configuration.HttpModulesConfigurationHandler, System.Web" />
|
||||
<section name="machineKey"
|
||||
type="System.Web.Configuration.MachineKeyConfigHandler, System.Web" />
|
||||
<section name="authentication"
|
||||
type="System.Web.Configuration.AuthenticationConfigHandler, System.Web" />
|
||||
<section name="authorization"
|
||||
type="System.Web.Configuration.AuthorizationConfigHandler, System.Web" />
|
||||
<section name="globalization"
|
||||
type="System.Web.Configuration.GlobalizationConfigurationHandler, System.Web" />
|
||||
<section name="sessionState"
|
||||
type="System.Web.SessionState.SessionStateSectionHandler, System.Web" />
|
||||
<section name="trace"
|
||||
type="System.Web.Configuration.TraceConfigurationHandler, System.Web" />
|
||||
<section name="webServices"
|
||||
type="System.Web.Services.Configuration.WebServicesConfigurationSectionHandler, System.Web.Services" />
|
||||
<section name="webControls"
|
||||
type="System.Web.Configuration.WebControlsSectionHandler, System.Web" />
|
||||
<section name="compilation"
|
||||
type="System.Web.Configuration.CompilationConfigurationHandler, System.Web" />
|
||||
<section name="httpRuntime"
|
||||
type="System.Web.Configuration.HttpRuntimeConfigurationHandler, System.Web" />
|
||||
<section name="customErrors"
|
||||
type="System.Web.Configuration.CustomErrorsConfigHandler, System.Web" />
|
||||
<section name="pages"
|
||||
type="System.Web.Configuration.PagesConfigurationHandler, System.Web" />
|
||||
</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" />
|
||||
<add type="System.Net.DigestClient" />
|
||||
<add type="System.Net.NtlmClient" />
|
||||
</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="Trace.axd" type="System.Web.Handlers.TraceHandler, System.Web" />
|
||||
<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="GET" path="WebResource.axd" type="System.Web.Handlers.AssemblyResourceLoader, 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="*" path="*.rem" type="System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory, System.Runtime.Remoting" validate="false" />
|
||||
<add verb="*" path="*.soap" type="System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory, System.Runtime.Remoting" validate="false" />
|
||||
<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="OutputCache" type="System.Web.Caching.OutputCacheModule, System.Web" />
|
||||
</httpModules>
|
||||
<authentication mode="Forms">
|
||||
<forms name=".MONOAUTH" loginUrl="login.aspx" protection="All" timeout="30" path="/">
|
||||
<credentials passwordFormat="Clear">
|
||||
<!--<user name="gonzalo" password="gonz"/>-->
|
||||
</credentials>
|
||||
</forms>
|
||||
</authentication>
|
||||
<machineKey validationKey="AutoGenerate" decryptionKey="AutoGenerate" validation="SHA1" />
|
||||
<globalization requestEncoding="utf-8"
|
||||
responseEncoding="utf-8"
|
||||
fileEncoding="utf-8"/>
|
||||
<!--
|
||||
culture="en-US"
|
||||
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>
|
||||
<webControls clientScriptsLocation="/web_scripts" />
|
||||
<compilation debug="false" defaultLanguage="c#">
|
||||
<compilers>
|
||||
<compiler language="cs;c#;csharp" extension=".cs" warningLevel="1" compilerOptions=""
|
||||
type="Microsoft.CSharp.CSharpCodeProvider, System" />
|
||||
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb"
|
||||
warningLevel="1" compilerOptions=""
|
||||
type="Microsoft.VisualBasic.VBCodeProvider, System" />
|
||||
</compilers>
|
||||
<assemblies>
|
||||
<!--<add assembly="mscorlib" /> -->
|
||||
<add assembly="System" />
|
||||
<add assembly="System.Xml" />
|
||||
<add assembly="System.Data" />
|
||||
<add assembly="System.Web" />
|
||||
<add assembly="System.Web.Services" />
|
||||
<add assembly="System.Drawing" />
|
||||
<add assembly="*" /> <!-- Add assemblies in bin directory -->
|
||||
</assemblies>
|
||||
</compilation>
|
||||
<httpRuntime executionTimeout="90"
|
||||
maxRequestLength="4096"
|
||||
useFullyQualifiedRedirectUrl="false"
|
||||
minFreeThreads="8"
|
||||
minLocalRequestFreeThreads="4"
|
||||
appRequestQueueLimit="100" />
|
||||
<pages buffer="true"
|
||||
enableSessionState="true"
|
||||
autoEventWireup="true"
|
||||
validateRequest="true" />
|
||||
</system.web>
|
||||
|
||||
<system.runtime.remoting>
|
||||
<application>
|
||||
<channels>
|
||||
<channel ref="http client" displayName="http client (delay loaded)" delayLoadAsClientChannel="true" />
|
||||
<channel ref="tcp client" displayName="tcp client (delay loaded)" delayLoadAsClientChannel="true" />
|
||||
</channels>
|
||||
</application>
|
||||
<channels>
|
||||
<channel id="http" type="System.Runtime.Remoting.Channels.Http.HttpChannel, System.Runtime.Remoting" />
|
||||
<channel id="http client" type="System.Runtime.Remoting.Channels.Http.HttpClientChannel, System.Runtime.Remoting" />
|
||||
<channel id="http server" type="System.Runtime.Remoting.Channels.Http.HttpServerChannel, System.Runtime.Remoting" />
|
||||
<channel id="tcp" type="System.Runtime.Remoting.Channels.Tcp.TcpChannel, System.Runtime.Remoting" />
|
||||
<channel id="tcp client" type="System.Runtime.Remoting.Channels.Tcp.TcpClientChannel, System.Runtime.Remoting" />
|
||||
<channel id="tcp server" type="System.Runtime.Remoting.Channels.Tcp.TcpServerChannel, System.Runtime.Remoting" />
|
||||
</channels>
|
||||
<channelSinkProviders>
|
||||
<clientProviders>
|
||||
<formatter id="soap" type="System.Runtime.Remoting.Channels.SoapClientFormatterSinkProvider, System.Runtime.Remoting" />
|
||||
<formatter id="binary" type="System.Runtime.Remoting.Channels.BinaryClientFormatterSinkProvider, System.Runtime.Remoting" />
|
||||
</clientProviders>
|
||||
<serverProviders>
|
||||
<formatter id="soap" type="System.Runtime.Remoting.Channels.SoapServerFormatterSinkProvider, System.Runtime.Remoting" />
|
||||
<formatter id="binary" type="System.Runtime.Remoting.Channels.BinaryServerFormatterSinkProvider, System.Runtime.Remoting" />
|
||||
<provider id="wsdl" type="System.Runtime.Remoting.MetadataServices.SdlChannelSinkProvider, System.Runtime.Remoting" />
|
||||
</serverProviders>
|
||||
</channelSinkProviders>
|
||||
</system.runtime.remoting>
|
||||
|
||||
<appSettings>
|
||||
<!--<add key="yourkey" value="your value" /> -->
|
||||
<!--<remove key="a key defined higher in the hierarchy" /> -->
|
||||
<!--<clear/> Removes all defined settings -->
|
||||
</appSettings>
|
||||
<system.diagnostics>
|
||||
<trace autoflush="false" indentsize="4" />
|
||||
</system.diagnostics>
|
||||
<system.drawing>
|
||||
</system.drawing>
|
||||
</configuration>
|
||||
|
||||
|
||||
@@ -0,0 +1,4 @@
|
||||
Makefile.in
|
||||
Makefile
|
||||
all-docs
|
||||
pending-classes.in
|
||||
@@ -0,0 +1,32 @@
|
||||
WEB_FILES= \
|
||||
c-sharp class-library contact contributing documentation download \
|
||||
faq gcc-frontend ideas index passport rationale resources \
|
||||
roadmap runtime status team testing thanks tools porting anoncvs monodoc-xml
|
||||
|
||||
OTHERS= pending resources-pending todo mono-build.sh mono-build-w32.sh
|
||||
|
||||
EXTRA_DIST = $(WEB_FILES) README $(OTHERS)
|
||||
|
||||
all-docs: $(WEB_FILES)
|
||||
cat rationale roadmap c-sharp tools class-library \
|
||||
runtime documentation download faq contributing \
|
||||
resources status > all-docs
|
||||
|
||||
class-status: class-status.in pending-classes Makefile.am
|
||||
cat class-status.in pending-classes > class-status
|
||||
|
||||
pending-classes:
|
||||
|
||||
#pending-classes: pending-classes.in Makefile.am
|
||||
# echo "This is a list of pending classes, and links to their documentation on MSDN.Microsoft.com<p><p>" > pending-classes
|
||||
# for i in `cat pending-classes.in`; do x=`echo $$i | sed s/\\\.//g`; link=`echo http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrf@@@ClassTopic.asp | sed "s/@@@/$$x/"`; echo " <a href=\"$$link\">$$i</a><br>" >> pending-classes; done
|
||||
|
||||
|
||||
webit: dummy
|
||||
(cd web; make && make push)
|
||||
|
||||
push-notes:
|
||||
scp release-notes/mono* www@www:/web/cvsmodules/mono/archive
|
||||
|
||||
dummy:
|
||||
|
||||
@@ -0,0 +1,17 @@
|
||||
To edit the website appearance:
|
||||
|
||||
cd doc/web
|
||||
edit template.html.in
|
||||
make
|
||||
|
||||
To edit website content:
|
||||
|
||||
cd doc (this directory)
|
||||
edit files carefully
|
||||
cd web
|
||||
make
|
||||
|
||||
To publish changes:
|
||||
|
||||
cd web
|
||||
make push
|
||||
@@ -0,0 +1,70 @@
|
||||
* Anonymous CVS access
|
||||
|
||||
Anonymous access to the Mono is available currently from three
|
||||
servers (anoncvs-spain-1.go-mono.com,
|
||||
anoncvs-spain-2.go-mono.com and anoncvs-us-1.go-mono.com).
|
||||
|
||||
You can also use `anoncvs.go-mono.com', and that will pick a
|
||||
server automatically for you.
|
||||
|
||||
Sources are currently being updated every hour.
|
||||
|
||||
** Checking out the sources
|
||||
|
||||
To check out the sources for the first time from the
|
||||
repository, use this command:
|
||||
|
||||
<pre>
|
||||
export CVSROOT=:pserver:[email protected]:/mono
|
||||
cvs login
|
||||
cvs -z3 co mcs mono gtk-sharp
|
||||
</pre>
|
||||
|
||||
That will get you the compiler and class libraries (mcs), the
|
||||
interpreter and JITer (mono) and the Gtk# bindings.
|
||||
|
||||
The server is located in Spain.
|
||||
|
||||
** Updating the sources
|
||||
|
||||
To update your sources every day, you use this command:
|
||||
|
||||
<pre>
|
||||
export CVSROOT=:pserver:[email protected]:/mono
|
||||
cvs -z3 update -dP mcs mono gtk-sharp
|
||||
</pre>
|
||||
|
||||
** Thanks
|
||||
|
||||
Thanks to <a href="http://www.hispalinux.es">HispaLinux</a>
|
||||
for providing this Anon CVS server. The server is located in
|
||||
Spain.
|
||||
|
||||
Special thanks to Jesus Climent, Rodrigo Moya, Juantomás
|
||||
García and Ismael Olea for making this happen.
|
||||
|
||||
<a name="#mirror">
|
||||
** Becoming an AnonCVS mirror
|
||||
|
||||
To become an AnonCVS mirror, you currently need about 20
|
||||
megabytes of free disk space and bandwidth that you do not
|
||||
mind sharing (you probably want enough to spare).
|
||||
|
||||
I need to be able to rsync to your machine from the main CVS
|
||||
server. The preferred method to rsync is to setup ssh in your
|
||||
machine.
|
||||
|
||||
The requirements are:
|
||||
<ul>
|
||||
* An account where we can ssh into.
|
||||
|
||||
* rsync.
|
||||
|
||||
* AnonCVS setup with the same paths as the rest of the
|
||||
servers.
|
||||
|
||||
* Currently, about 40 megabytes of disk space, but this
|
||||
will likely grow as the project evolves.
|
||||
|
||||
* A sysadmin contact e-mail address.
|
||||
</ul>
|
||||
@@ -0,0 +1,32 @@
|
||||
* C# Books
|
||||
|
||||
A Programmer's Introduction to C# - Second Edition: Eric Gunnerson
|
||||
|
||||
* Compiler Implementation
|
||||
|
||||
Compilers - Principles, Techniques, and Tools: Alfred V. Aho, Ravi Sethi,
|
||||
Jeffrey D. Ullman
|
||||
|
||||
Advanced Compiler Design Implementation: Steven S. Muchnick
|
||||
|
||||
Modern Compiler Implementation in C: Andrew W. Appel
|
||||
|
||||
A Retargetable C Compiler - Design and Implementation: C. Fraser, David
|
||||
Hanson
|
||||
|
||||
* Reference Manuals
|
||||
|
||||
<a
|
||||
href="http://developer.intel.com/design/pentium/manuals/24319101.pdf">Intel
|
||||
Architecture Software Developer's Manual, Volume 2 - Instruction Set Reference Manual</a>
|
||||
|
||||
<a
|
||||
href="http://www.caldera.com/developers/devspecs/abi386-4.pdf">System V ABI
|
||||
- i386 Architecture Processor Supplement</a>
|
||||
|
||||
<a
|
||||
href="http://www.caldera.com/developers/devspecs/mipsabi.pdf">System V ABI -
|
||||
MIPS Processor supplement</a>
|
||||
|
||||
<a href="http://www.sparc.org/standards/V8.pdf">The SPARC Architecture
|
||||
Manual Version 8</a>
|
||||
@@ -0,0 +1,220 @@
|
||||
* MCS: The Ximian C# compiler
|
||||
|
||||
MCS is currently able to compile itself and many more C#
|
||||
programs (there is a test suite included that you can use).
|
||||
|
||||
We are in feature completion mode right now. There are still
|
||||
a couple of areas that are not covered by the Mono compiler, but
|
||||
they are very very few at this point.
|
||||
|
||||
MCS was able to parse itself on April 2001, MCS compiled itself
|
||||
for the first time on December 28 2001. MCS became self hosting
|
||||
on January 3rd, 2002.
|
||||
|
||||
A test suite is maintained to track the progress of
|
||||
the compiler and various programs are routinely compiled and
|
||||
ran.
|
||||
|
||||
** Obtaining MCS
|
||||
|
||||
The Mono C# compiler is part of the `mcs' module in the Mono CVS
|
||||
you can get it from our <a href="anoncvs.html">Anonymous CVS</a> server,
|
||||
or you can get nightly <a href="download.html">download page</a>.
|
||||
|
||||
** Running MCS
|
||||
|
||||
MCS is written in C# and uses heavily the .NET APIs. MCS runs
|
||||
on Linux (with the Mono runtime) and Windows (with the .NET
|
||||
framework runtime)
|
||||
|
||||
** Reporting Bugs in MCS
|
||||
|
||||
When you report a bug, try to provide a small test case that would
|
||||
show the error so we can include this as part of the Mono C# regression
|
||||
test suite.
|
||||
|
||||
If the bug is an error or a warning that we do not flag, write
|
||||
a sample program called `csXXXX.cs' where XXXX is the code number
|
||||
that is used by the Microsoft C# compiler that illustrates the
|
||||
problem. That way we can also do regression tests on the invalid
|
||||
input.
|
||||
|
||||
** Phases of the compiler
|
||||
|
||||
The compiler has a number of phases:
|
||||
|
||||
<ul>
|
||||
* Lexical analyzer: hand-coded lexical analyzer that
|
||||
provides tokens to the parser.
|
||||
|
||||
* The Parser: the parser is implemented using Jay (A
|
||||
Berkeley Yacc port to Java, that I ported to C#).
|
||||
The parser does minimal work and syntax checking,
|
||||
and only constructs a parsed tree.
|
||||
|
||||
Each language element gets its own class. The code
|
||||
convention is to use an uppercase name for the
|
||||
language element. So a C# class and its associated
|
||||
information is kept in a "Class" class, a "struct"
|
||||
in a "Struct" class and so on. Statements derive
|
||||
from the "Statement" class, and Expressions from the
|
||||
Expr class.
|
||||
|
||||
* Parent class resolution: before the actual code
|
||||
generation, we need to resolve the parents and
|
||||
interfaces for interface, classe and struct
|
||||
definitions.
|
||||
|
||||
* Semantic analysis: since C# can not resolve in a
|
||||
top-down pass what identifiers actually mean, we
|
||||
have to postpone this decision until the above steps
|
||||
are finished.
|
||||
|
||||
* Code generation: The code generation is done through
|
||||
the System.Reflection.Emit API.
|
||||
</ul>
|
||||
|
||||
** CIL Optimizations.
|
||||
|
||||
The compiler performs a number of simple optimizations on its input:
|
||||
constant folding (this is required by the C# language spec) and
|
||||
can perform dead code elimination.
|
||||
|
||||
Other more interesting optimizations like hoisting are not possible
|
||||
at this point since the compiler output at this point does not
|
||||
generate an intermediate representation that is suitable to
|
||||
perform basic block computation.
|
||||
|
||||
Adding an intermediate layer to enable the basic block
|
||||
computation to the compiler should be a simple task, but we
|
||||
are considering having a generic CIL optimizer. Since all the
|
||||
information that is required to perform basic block-based
|
||||
optimizations is available at the CIL level, we might just skip
|
||||
this step altogether and have just a generic IL optimizer that
|
||||
would perform hoisting on arbitrary CIL programs, not only
|
||||
those produced by MCS.
|
||||
|
||||
If this tool is further expanded to perform constant folding
|
||||
(not needed for our C# compiler, as it is already in there)
|
||||
and dead code elimination, other compiler authors might be
|
||||
able to use this generic CIL optimizer in their projects
|
||||
reducing their time to develop a production compiler.
|
||||
|
||||
<a name="tasks">
|
||||
** Current pending tasks
|
||||
|
||||
Simple tasks:
|
||||
|
||||
<ul>
|
||||
* Redo the way we deal with built-in operators.
|
||||
</ul>
|
||||
|
||||
Larger tasks:
|
||||
<ul>
|
||||
|
||||
* Jay does not work correctly with `error'
|
||||
productions, making parser errors hard to point. It
|
||||
would be best to port the Bison-To-Java compiler to
|
||||
become Bison-to-C# compiler.
|
||||
|
||||
Nick Drochak has started a project on SourceForge for this.
|
||||
You can find the project at: <a href="http://sourceforge.net/projects/jb2csharp/">
|
||||
http://sourceforge.net/projects/jb2csharp/</a>
|
||||
|
||||
* Semantic Analysis: Return path coverage and
|
||||
initialization before use coverage are two great
|
||||
features of C# that help reduce the number of bugs
|
||||
in applications. It is one interesting hack.
|
||||
|
||||
</ul>
|
||||
|
||||
** Questions and Answers
|
||||
|
||||
Q: Why not write a C# front-end for GCC?
|
||||
|
||||
A: I wanted to learn about C#, and this was an exercise in this
|
||||
task. The resulting compiler is highly object-oriented, which has
|
||||
lead to a very nice, easy to follow and simple implementation of
|
||||
the compiler.
|
||||
|
||||
I found that the design of this compiler is very similar to
|
||||
Guavac's implementation.
|
||||
|
||||
Targeting the CIL/MSIL byte codes would require to re-architecting
|
||||
GCC, as GCC is mostly designed to be used for register machines.
|
||||
|
||||
The GCC Java engine that generates Java byte codes cheats: it does
|
||||
not use the GCC backend; it has a special backend just for Java, so
|
||||
you can not really generate Java bytecodes from the other languages
|
||||
supported by GCC.
|
||||
|
||||
Q: If your C# compiler is written in C#, how do you plan on getting
|
||||
this working on a non-Microsoft environment.
|
||||
|
||||
We will do this through an implementation of the CLI Virtual
|
||||
Execution System for Unix (our JIT engine).
|
||||
|
||||
Our JIT engine is working for the purposes of using the compiler.
|
||||
The supporting class libraries are being worked on to fully support
|
||||
the compiler.
|
||||
|
||||
Q: Do you use Bison?
|
||||
|
||||
A: No, currently I am using Jay which is a port of Berkeley Yacc to
|
||||
Java that I later ported to C#. This means that error recovery is
|
||||
not as nice as I would like to, and for some reason error
|
||||
productions are not being caught.
|
||||
|
||||
In the future I want to port one of the Bison/Java ports to C# for
|
||||
the parser.
|
||||
|
||||
Q: Should someone work on a GCC front-end to C#?
|
||||
|
||||
A: I would love if someone does, and we would love to help anyone that
|
||||
takes on that task, but we do not have the time or expertise to
|
||||
build a C# compiler with the GCC engine. I find it a lot more fun
|
||||
personally to work on C# on a C# compiler, which has an intrinsic
|
||||
beauty.
|
||||
|
||||
We can provide help and assistance to anyone who would like to work
|
||||
on this task.
|
||||
|
||||
Q: Should someone make a GCC backend that will generate CIL images?
|
||||
|
||||
A: I would love to see a backend to GCC that generates CIL images. It
|
||||
would provide a ton of free compilers that would generate CIL
|
||||
code. This is something that people would want to look into
|
||||
anyways for Windows interoperation in the future.
|
||||
|
||||
Again, we would love to provide help and assistance to anyone
|
||||
interested in working in such a project.
|
||||
|
||||
Q: What about making a front-end to GCC that takes CIL images and
|
||||
generates native code?
|
||||
|
||||
A: I would love to see this, specially since GCC supports this same
|
||||
feature for Java Byte Codes. You could use the metadata library
|
||||
from Mono to read the byte codes (ie, this would be your
|
||||
"front-end") and generate the trees that get passed to the
|
||||
optimizer.
|
||||
|
||||
Ideally our implementation of the CLI will be available as a shared
|
||||
library that could be linked with your application as its runtime
|
||||
support.
|
||||
|
||||
Again, we would love to provide help and assistance to anyone
|
||||
interested in working in such a project.
|
||||
|
||||
Q: But would this work around the GPL in the GCC compiler and allow
|
||||
people to work on non-free front-ends?
|
||||
|
||||
A: People can already do this by targeting the JVM byte codes (there
|
||||
are about 130 compilers for various languages that target the JVM).
|
||||
|
||||
Q: Why are you writing a JIT engine instead of a front-end to GCC?
|
||||
|
||||
A: The JIT engine and runtime engine will be able to execute CIL
|
||||
executables generated on Windows.
|
||||
|
||||
You might also want to look at the <a href="faq.html#gcc">GCC</a>
|
||||
section on the main FAQ
|
||||
@@ -0,0 +1,138 @@
|
||||
* CVS Access
|
||||
|
||||
If you are an active Mono developer, you can get a CVS account
|
||||
that hosts the Mono source code.
|
||||
|
||||
If you are not a developer, but want to track the development, please
|
||||
see the <a href="anoncvs.html">AnonCVS</a> instructions.
|
||||
|
||||
Send an e-mail to miguel with your public SSH key for this
|
||||
purpose. Please specify if the key was generated with SSH1 or SSH2.
|
||||
|
||||
If you are using SSH2, please generate your key using:
|
||||
|
||||
<pre>
|
||||
ssh-keygen -t rsa
|
||||
</pre>
|
||||
|
||||
And mail me the id_rsa.pub file.
|
||||
|
||||
If you are using SSH1, run:
|
||||
<pre>
|
||||
ssh-keygen
|
||||
</pre>
|
||||
|
||||
And mail me your identity.pub file.
|
||||
|
||||
You will need CVS and SSH. Windows users can get both by
|
||||
installing Cygwin (<a
|
||||
href="http://www.cygwin.com">http://www.cygwin.com</a>)
|
||||
|
||||
Unix users will probably have those tools installed already.
|
||||
|
||||
** Checking out the sources
|
||||
|
||||
To check out the sources for the first time from the
|
||||
repository, use this command:
|
||||
|
||||
<pre>
|
||||
export CVS_RSH=ssh
|
||||
export [email protected]:/cvs/public
|
||||
cvs -z3 co mcs mono
|
||||
</pre>
|
||||
|
||||
** Updating your sources
|
||||
|
||||
Every day people will be making changes, to get your latest
|
||||
updated sources, use:
|
||||
|
||||
<pre>
|
||||
cvs -z3 update -Pd mcs mono
|
||||
</pre>
|
||||
|
||||
Note: The '-z3' enables compression for the whole cvs action.
|
||||
The '-Pd' makes the update operation (P)rune directories that
|
||||
have been deleted and get new (d)irectories added to the
|
||||
repository.
|
||||
|
||||
** Making patches
|
||||
|
||||
Usually you will want to make a patch to contribute, and let
|
||||
other people review it before commiting it. To obtain such a
|
||||
"patch", you type:
|
||||
|
||||
<pre>
|
||||
cd directory-you-want-to-diff
|
||||
cvs -z3 diff -u > file.diff
|
||||
mail [email protected] < file.diff
|
||||
</pre>
|
||||
|
||||
** Keeping track of changes.
|
||||
|
||||
We provide two e-mail based mechanisms to keep track of
|
||||
changes to the code base:
|
||||
|
||||
<ul>
|
||||
* <a href="mailto:[email protected]">
|
||||
[email protected]</a>: This mailing list receives
|
||||
in patch form all the changes that are being made to the
|
||||
CVS.
|
||||
|
||||
* <a href="mailto:[email protected]">
|
||||
[email protected]</a>: This mailing list only
|
||||
receives the CVS commit logs with a list of files
|
||||
modified.
|
||||
</ul>
|
||||
|
||||
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 List
|
||||
|
||||
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'.
|
||||
|
||||
This will send you an email message every time a change is
|
||||
made to the CVS repository, together with the information that
|
||||
the author of the changes submitted.
|
||||
|
||||
** Recommendations
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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).
|
||||
|
||||
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.
|
||||
@@ -0,0 +1,190 @@
|
||||
* The Class Library
|
||||
|
||||
The Class Library should be compatible with Microsoft's .NET
|
||||
implementation.
|
||||
|
||||
Please see the <a href="class-status.html">Class Status</a>
|
||||
page for a status of who is working on which classes.
|
||||
|
||||
We will write as much code as possible in C#. We may need to
|
||||
interface with code written in C to gain access to the
|
||||
functionality of libraries like libart, Gtk+, and libc.
|
||||
|
||||
** Contributing
|
||||
|
||||
We welcome contributions to the the Class Library. To get
|
||||
started, check the status page for information about which
|
||||
APIs are being worked on, and how to get in touch with
|
||||
individual maintainers.
|
||||
|
||||
If you want to work on a class, first check the <a
|
||||
href="download.html">Classes Distribution</a> to see if it is
|
||||
not implemented yet, if not, check the <a
|
||||
href="class-status.html">Class Status</a> to see if someone is
|
||||
already working on it, and maybe contact them.
|
||||
|
||||
If nobody is working on it, mail <a
|
||||
href="mailto:[email protected]">[email protected]</a>
|
||||
with the class you want to implement and CC <a
|
||||
href="mailto:[email protected]">[email protected]</a>.
|
||||
|
||||
You can also track live the activities of the Mono CVS module
|
||||
by subscribing to the <a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-cvs-list">mono-cvs-list</a>
|
||||
|
||||
|
||||
** Missing features
|
||||
|
||||
Our class libraries miss some features, for example, most classes
|
||||
do not implement the serialization bits at all, it would be a good
|
||||
contribution to add this to each class.
|
||||
|
||||
This is a simple task, but it needs to be done in a compatible way
|
||||
with the Microsoft.NET classes: using the same arguments to serialize
|
||||
and reincarnate data.
|
||||
|
||||
** Layout
|
||||
|
||||
The Class Library resides in the `mcs' module in the directoy
|
||||
`class'.
|
||||
|
||||
Each directory in the directory represents the assembly where
|
||||
the code belongs to, and inside each directory we divide the
|
||||
code based on the namespace they implement.
|
||||
|
||||
There are two cases when we should consider portability: when
|
||||
we are dealing with a couple of classes only that differ from
|
||||
system to system (Consider System.Net and System.IO for Win32
|
||||
and Unix). In those cases we will just place the files for
|
||||
example on <t>corlib/System/System.IO/Unix-Console.cs</t> and
|
||||
<t>corlib/System/System.IO/Win32-Console.cs</t>.
|
||||
|
||||
For classes that might differ more (for example, the
|
||||
implementation of Windows.Forms), we might have different
|
||||
directories altogether: <t>System.Windows.Forms/Win32</t>,
|
||||
<t>System.Windows.Forms/Gtk+</t> and
|
||||
<t>System.Windows.Forms/Cocoa</t>.
|
||||
|
||||
** Using existing components from GNOME.
|
||||
|
||||
Our current plan is to implement the GUI tools on top of
|
||||
Gtk+. The only obstacle here is that applications from Windows
|
||||
might expect to be able to pull the HWND property from the
|
||||
widgets and use PInvoke to call Windows functions.
|
||||
|
||||
** Class Library and Win32 dependencies.
|
||||
|
||||
There are a few spots where the Win32 foundation is exposed to
|
||||
the class library (for example, the HDC and HWND properties in
|
||||
the GDI+). Casual inspection suggests that these can be
|
||||
safely mapped to Gdk's GC and GdkWindow pointers without
|
||||
breaking anything.
|
||||
|
||||
The only drawback is that support for PInvoke of Win32 code
|
||||
won't be available. An alternate solution would be to use
|
||||
portions of Wine, or even to use Wine as our toolkit.
|
||||
|
||||
*** Initial GDI+ and WinForms implementation
|
||||
|
||||
The initial implementation will use Gtk+ as the underlying
|
||||
toolkit. Since GTK+ has already been ported to many windowing
|
||||
systems other than X (including frame buffer, Win32, and BeOS)
|
||||
its use should cover most applications for most users.
|
||||
|
||||
*** Database access
|
||||
|
||||
We will implement ADO.NET functionality by reusing <a
|
||||
href="http://www.gnome-db.org">GNOME-DB</a>. This is an ideal
|
||||
choice, since GNOME-DB was implemented precisely to provide an
|
||||
ADO-like system for GNOME.
|
||||
|
||||
*** Component Integration
|
||||
|
||||
We will provide a new namespace to use GNOME specific features
|
||||
as well as a namespace to host Bonobo interfaces and classes
|
||||
in Mono.
|
||||
|
||||
** Licensing
|
||||
|
||||
The class library is being licensed under the terms of the
|
||||
<a
|
||||
href="http://www.opensource.org/licenses/mit-license.html">MIT
|
||||
license.</a> This is the same license used by the X11 window
|
||||
system.
|
||||
|
||||
** Class Library testing
|
||||
|
||||
We need to write regression tests that will verify
|
||||
the correctness of the class library, compiler, and JIT
|
||||
engine.
|
||||
|
||||
Please write your regression tests using <a
|
||||
href="http://nunit.sourceforge.net">NUnit</a>
|
||||
|
||||
** Coding conventions
|
||||
|
||||
Please follow the conventions on the ECMA specification (On
|
||||
the Annex Partition) for your coding your libraries.
|
||||
|
||||
Use 8 space tabs for writing your code (hopefully we can keep
|
||||
this consistent). If you are modifying someone else's code, try
|
||||
to keep the coding style similar.
|
||||
|
||||
For a rationale on 8 space tabs, read Linus Torvald's Coding
|
||||
Style guidelines in the Linux kernel source for a rationale.
|
||||
|
||||
*** Missing implementation bits
|
||||
|
||||
If you implement a class and you are missing implementation bits,
|
||||
please put in the code the word "TODO" and a description of what
|
||||
is missing to be implemented.
|
||||
|
||||
*** Tagging buggy code
|
||||
|
||||
If there is a bug in your implementation tag the problem by using
|
||||
the word "FIXME" in the code, together with a description of the
|
||||
problem.
|
||||
|
||||
Do not use XXX or obscure descriptions, because otherwise people
|
||||
will not be able to understand what you mean.
|
||||
|
||||
*** Tagging Lame specs
|
||||
|
||||
Sometimes the specification will be lame (consider Version.ToString (fieldCount)
|
||||
where there is no way of knowing how many fields are available, making the API
|
||||
not only stupid, but leading to unreliable code).
|
||||
|
||||
In those cases, use the keyword "LAMESPEC".
|
||||
|
||||
** Namespaces
|
||||
|
||||
We are using a number of namespaces in the class libraries for
|
||||
private classes when we need them, you are encouraged to use these:
|
||||
|
||||
<pre>
|
||||
Mono
|
||||
.Languages // General Compiler classes
|
||||
.CSharp // Specific C# parsing/tokenizing classes
|
||||
.MonoBASIC // Specific VB.NET/MonoBASIC parsing/tokenizing classes
|
||||
.Python // Specific Python parsing/tokenizing classes
|
||||
.Runtime
|
||||
.LateBind // General latebinding-support for MonoBASIC/Python
|
||||
.MonoBASIC // Specific runtime classes for MonoBASIC programs
|
||||
.Python // Specific runtime classes for Python programs
|
||||
.Web
|
||||
.UI
|
||||
.Utils // Gaurav utility classes
|
||||
</pre>
|
||||
|
||||
** FAQ
|
||||
|
||||
Frequently asked questions about the class library:
|
||||
|
||||
Q: I am writing a new class that overrides one of the system classes,
|
||||
and I am getting a 1595 warning from the compiler. Should we use a
|
||||
different namespace?
|
||||
|
||||
A: There is a quick solution to the problem, you can pass the command
|
||||
line argument /nowarn:1595 and this will effectively let you use
|
||||
your implementation of the code, while overriding the ones from the
|
||||
system assemblies.
|
||||
@@ -0,0 +1,26 @@
|
||||
* Status of the various pieces of the class library
|
||||
|
||||
You can browse the status of the class library and see who has
|
||||
registered to work on what parts of the system. These list
|
||||
work-in-progress components currently.
|
||||
|
||||
Browse the current <a href="class-status/index.html">status</a>.
|
||||
|
||||
You can also download the XML <a
|
||||
href="class-status/maintainers.xml">maintainers</a> file that
|
||||
contains the actual maintainers list.
|
||||
|
||||
You can also download the master <a
|
||||
href="class-status/class.xml">Class Status XML</a> file.
|
||||
|
||||
* List of not-implemented classes
|
||||
|
||||
Pick from the list of assemblies in the menu on the left to
|
||||
view the current status of that assembly.
|
||||
|
||||
The tree shows items that are either missing or that have TODO
|
||||
attributes associated with them.
|
||||
You can use the checkboxes to show only missing or only TODO items.
|
||||
|
||||
Clicking on a name will take you to the <a href="http://msdn.microsoft.com/">MSDN documentation</a> for that item.
|
||||
CTRL-Clicking will take you to the <a href="http://cvs.hispalinux.es/cgi-bin/cvsweb/?cvsroot=Mono">mono CVS tree</a>.
|
||||
@@ -0,0 +1,105 @@
|
||||
* Class Library Documentation
|
||||
|
||||
** Summary
|
||||
|
||||
<em>
|
||||
[This documentation is in progress. Comments to
|
||||
<a href="mailto:[email protected]">[email protected]</a>.]
|
||||
</em>
|
||||
|
||||
While using inline XML tags to document classes is certainly
|
||||
convenient, properly verbose documentation quickly overwhelms
|
||||
the code, making the source quite difficult to read. Furthermore,
|
||||
multilingual documentation makes for significant additional text.
|
||||
|
||||
With these considerations in mind, Mono will use external XML files
|
||||
for type documentation, rather than documenting the source inline.
|
||||
|
||||
Several tools will be created for managing, verifying, generating,
|
||||
and updating class library documentation, including:
|
||||
|
||||
<ul>
|
||||
<li><a href="#docstub">docstub</a></li>
|
||||
<li><a href="#docverify">docverify</a></li>
|
||||
<li><a href="#docconv">docconv</a></li>
|
||||
<li><a href="#docgen">docgen</a></li>
|
||||
<li><a href="#monodoc">monodoc</a></li>
|
||||
</ul>
|
||||
|
||||
** XML Documentation Files and Formats
|
||||
|
||||
|
||||
*** Monodoc XML
|
||||
This XML is similar to the XML documentation described in the
|
||||
C# standard, with added tags for internationalization and a
|
||||
slightly different structure. Documentation and a DTD/Schema
|
||||
for Monodoc XML is forthcoming.
|
||||
|
||||
Monodoc XML does not contain any definitive type information,
|
||||
and is only useful in conjunction with the Type definition for
|
||||
whatever is being documented.
|
||||
|
||||
This XML could be generated by hand, by monostub, or by monodoc.
|
||||
|
||||
*** Assembly XML
|
||||
This XML is generated by combining runtime type information for
|
||||
an Assembly with a collection of Monodoc XML files. The resultant
|
||||
XML (in the best of cases) contains both complete type and
|
||||
documentary information for each type in the assembly.
|
||||
|
||||
This XML contains enough information to be transformed into
|
||||
user-accessible documentation. It is likely that scripts
|
||||
will be created to generate reference docs as HTML and other
|
||||
formats.
|
||||
|
||||
Documentation and a DTD/Schema for Assembly XML is forthcoming.
|
||||
|
||||
** Documentation Tools
|
||||
|
||||
*** <a name="docstub">docstub</a>
|
||||
Given a type name and an assembly, generates stub Monodoc XML
|
||||
documentation for the type. Optionally, docstub can attempt to
|
||||
populate initial documentation from an XML file in the format
|
||||
published along with the ECMA standard.
|
||||
|
||||
*** <a name="docverify">docverify</a>
|
||||
Given a Monodoc XML file and an assembly, verifies that the
|
||||
documentation matches the compiled type. Checks signatures,
|
||||
parameters, et cetera.
|
||||
|
||||
*** <a name="docconv">docconv</a>
|
||||
Converts from Monodoc XML to the standard C# compiler-emitted
|
||||
XML format and vice versa.
|
||||
|
||||
*** <a name="docgen">docgen</a>
|
||||
Given an assembly and a collection of Monodoc XML files, creates
|
||||
an Assembly XML file containing all documentation and type information
|
||||
available. This output is suitable for transforming into user
|
||||
documentation.
|
||||
|
||||
*** <a name="monodoc">monodoc</a>
|
||||
A GUI tool for documentation and translation, this encapsulates
|
||||
the capabilities of docstub, docverify, docconv, and docgen in
|
||||
a friendly user interface. In addition, monodoc provides features
|
||||
to ease translation, such as side-by-side editing and coverage
|
||||
statistics.
|
||||
|
||||
** Status and Roadmap
|
||||
|
||||
*** 2 January 2002
|
||||
|
||||
As I write the initial version of this document, very little has been
|
||||
implemented. Currently, there is a:
|
||||
|
||||
<ul>
|
||||
<li>Preliminary version of the Monodoc XML format</li>
|
||||
<li>Preliminary version of the docstub utility</li>
|
||||
</ul>
|
||||
|
||||
Here's hoping for frequent, productive updates.
|
||||
|
||||
** Get Involved
|
||||
|
||||
Help us define Mono's documentation structure! Subscribe to
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list</a>
|
||||
and wade right in.
|
||||
@@ -0,0 +1,13 @@
|
||||
* Contacting the Mono team.
|
||||
|
||||
You can contact the general forum of discussion by sending
|
||||
e-mail to <a href="mailto:[email protected]">[email protected]</a>
|
||||
|
||||
You can contact me (Miguel de Icaza) by sending e-mail to <a
|
||||
href="mailto:[email protected]">[email protected]</a>. My web
|
||||
page is <a
|
||||
href="http://primates.ximian.com/~miguel">http://primates.ximian.com/~miguel"</a>
|
||||
|
||||
You can also <a
|
||||
href="http://www.ximian.com/about/contact.php3">reach Ximian.</a>
|
||||
|
||||
@@ -0,0 +1,189 @@
|
||||
* Contributing to the Mono project
|
||||
|
||||
There are many ways in which you can help in the Mono project:
|
||||
|
||||
<ul>
|
||||
* <b>Programmers:</b> You can work on a free
|
||||
implementation of the <a
|
||||
href="class-library.html">class libraries</a>, the
|
||||
<a href="runtime.html">runtime engine</a>, <a
|
||||
href="tools.html">the tools</a>, the <a
|
||||
href="testing.html">testing framework</a>
|
||||
|
||||
* <b>Writers:</b> You can help us bywriting <a
|
||||
href="documentation.html">documentation</a>.
|
||||
</ul>
|
||||
|
||||
Those are just broad things that need to be worked on, but
|
||||
something that would help tremendously would be to help with
|
||||
small duties in the project that need to be addressed.
|
||||
|
||||
You can see what needs to be done in the class libraries <a href="class-status.html">here</a>
|
||||
|
||||
** To start contributing
|
||||
|
||||
As a programmer, you can contribute in three different scenarios to Mono:
|
||||
|
||||
<ul>
|
||||
* If you only have Linux/Unix.
|
||||
* If you only have Windows.
|
||||
|
||||
* If you have both Linux and Windows.
|
||||
</ul>
|
||||
|
||||
You might also want to check our <a href="#setup">common
|
||||
setups</a> section that describes some common setups that people
|
||||
use while working on Mono.
|
||||
|
||||
*** Contributing to the class library, regression tests or the compiler
|
||||
|
||||
This only requires Windows currently.
|
||||
|
||||
To start developing classes or to contribute to the compiler,
|
||||
you only need Windows and the .NET Framework 1.0 SDK. Please notice
|
||||
that you do not need Visual Studio (although you can use it if
|
||||
you want). The .NET Framework SDK requires some version of
|
||||
Windows XP or Windows NT. If you are running Windows 98, 95
|
||||
or Me, you could use instead the <a
|
||||
href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/001/829/msdncompositedoc.xml">.NET Redist package</a>, but it
|
||||
lacks the documentation browser and the ildasm program (C#, VB, JScript and IL
|
||||
assembler are included).
|
||||
|
||||
You can get it <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>
|
||||
|
||||
If you are new to .NET, writing regression tests is a good way
|
||||
of starting to contribute: it will help you get used to C# as
|
||||
well as getting comfortable with the .NET APIs.
|
||||
|
||||
This helps because at this point you might be the best
|
||||
qualified person to fix a problem found by the regression
|
||||
test, or you might have a new class to implement in the .NET
|
||||
world that only has a test suite.
|
||||
|
||||
To get started writing tests see the <a href="testing.html">Test Suite</a>
|
||||
section.
|
||||
|
||||
*** Contributing to the runtime engine
|
||||
|
||||
This only requires Linux, currently some tasks are easier if you
|
||||
have access to Windows as well.
|
||||
|
||||
Here are a few things you can do:
|
||||
<ul>
|
||||
* Port the runtime to other architectures.
|
||||
* Port the runtime to other operating systems.
|
||||
* Finish the IL code verifier in the runtime.
|
||||
* Hack the JIT, improve the code generator, add new
|
||||
pattern rules, improve the register allocator.
|
||||
* Implement the debugging interfaaces
|
||||
</ul>
|
||||
|
||||
** Bug reporting
|
||||
|
||||
If you find bugs in Mono, please make sure you enter a bug
|
||||
report so we can keep track of problems in Mono.
|
||||
|
||||
To enter bug reports go to <a href="http://bugzilla.ximian.com">
|
||||
http://bugzilla.ximian.com</a> and enter bug reports against
|
||||
your favorite component (Mono, Runtime, C# compiler).
|
||||
|
||||
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>
|
||||
|
||||
** Small tasks
|
||||
|
||||
A few smaller tasks are here, dropped in no particular order:
|
||||
<ul>
|
||||
* <b>Mono/doc and web site:</b> They need to be
|
||||
packaged up in the official `distribution'
|
||||
|
||||
* Adding serialization support to all the classes.
|
||||
|
||||
We have many classes, but we have not implemented in
|
||||
many cases the serialization and re-incarnation support in
|
||||
them (this is pretty straight forward code, and simple,
|
||||
but there is a lot to be done here).
|
||||
</ul>
|
||||
|
||||
* Emacs support
|
||||
|
||||
Brad Merryl's C# mode for Emacs is available: <a
|
||||
href="http://www.cybercom.net/~zbrad/DotNet/Emacs/">http://www.cybercom.net/~zbrad/DotNet/Emacs/</a>
|
||||
|
||||
* Books on C# and DotNet.
|
||||
|
||||
<ul>
|
||||
* Dotnet Books (<a href="http://www.dotnetbooks.com">http://www.dotnetbooks.com</a>)
|
||||
|
||||
* Dotnet Resources (<a href="http://www.dotnetexperts.com/resources/">
|
||||
http://www.dotnetexperts.com/resources</a>)
|
||||
|
||||
* O'Reilly C# Essentials (<a href="http://www.oreilly.com/catalog/csharpess/">
|
||||
http://www.oreally.com/catalog/csharpess</a>)
|
||||
|
||||
* O'Really .NET Essentials (<a href="http://www.oreilly.com/catalog/dotnetfrmess/">
|
||||
http://www.oreally.com/catalog/dotnetfrmess</a>)
|
||||
</ul>
|
||||
|
||||
<a name="setup">
|
||||
* Common Setups
|
||||
|
||||
People running both Linux and Windows while contributing to
|
||||
Mono use a number of tricks to increase their productivity.
|
||||
|
||||
Scenarios:
|
||||
|
||||
<ul>
|
||||
* <b>Linux host and Windows host</b>
|
||||
|
||||
The Windows file system is shared (right click on
|
||||
your hard drive icon, and select sharing, allow this
|
||||
to be shared).
|
||||
|
||||
The Windows machine has the required build tools
|
||||
(cygwin, and the .NET framework). On the Windows
|
||||
machine, you want to setup the ssh server (run the
|
||||
ssh-host-config program to configure your ssh) and
|
||||
run it (from a cygwin terminal, type: /usr/sbin/sshd).
|
||||
|
||||
From the Linux side, you want to mount the Windows
|
||||
file system, using something like this:
|
||||
|
||||
<tt><pre>
|
||||
mount -t smbfs -o uid=miguel,username="Miguel de Icaza" "//quack/c$" /mnt
|
||||
</pre></tt>
|
||||
|
||||
In the above example, my Linux user name is
|
||||
`miguel', and this will allow this user to have
|
||||
read/write access to the share.
|
||||
|
||||
The host name is `quack', and the name of the share
|
||||
is `c$' (that is the C: partition).
|
||||
|
||||
The file system is accessible on /mnt.
|
||||
|
||||
You can perform your cvs update and cvs commits from
|
||||
the /mnt directory, and run Emacs or your favorite
|
||||
Linux text editor on the Unix side in this way.
|
||||
|
||||
Then from another terminal, you can ssh into your
|
||||
Windows box using ssh, like this: ssh "Miguel de Icaza@quack"
|
||||
</ul>
|
||||
|
||||
* Special Note
|
||||
|
||||
If you have looked at Microsoft's implementation of .NET or
|
||||
their shared source code, you may not be able to contribute
|
||||
to Mono. Details will follow when we know more about this.
|
||||
|
||||
In general be careful when you are implementing free software
|
||||
and you have access to proprietary code. We need to make sure
|
||||
that we are not using someone else's copyrighted code
|
||||
accidentally.
|
||||
|
||||
Please do not use the <b>ildasm</b> program to disassemble
|
||||
proprietary code when you are planning to reimplement a class
|
||||
for Mono. If you have done this, we might not be able to use
|
||||
your code.
|
||||
|
||||
Please stick to published documentation for implementing any
|
||||
classes.
|
||||
@@ -0,0 +1,190 @@
|
||||
* Developer FAQ
|
||||
|
||||
** New classes
|
||||
|
||||
Q: Should we write classes which are not part of the .NET or ECMA specs?
|
||||
|
||||
A: Yes. The ECMA and .NET specifications are far from complete, and
|
||||
to produce a complete platform we will need a number of other
|
||||
classes and components.
|
||||
|
||||
Any new classes that are not part of .NET or ECMA should be
|
||||
designed to be reusable on anyone's CLI implementation. So that
|
||||
Windows developers can also use any new classes that we come up
|
||||
with.
|
||||
|
||||
We have a few existing <a href="ideas.html">Ideas on missing
|
||||
classes</a>
|
||||
|
||||
** Language Compatibility
|
||||
|
||||
Q: What is the magic that allow multiple languages to co-exist?
|
||||
|
||||
A: From Fergus Henderson:
|
||||
|
||||
<i><blockquote>
|
||||
There are different levels of interoperability.
|
||||
The ECMA spec defines different categories of
|
||||
CLS (Common Language Specification) conformance.
|
||||
There are also some useful categories that don't
|
||||
correspond to any of the levels defined in the ECMA spec.
|
||||
In increasing degree of difficulty, your language implementation
|
||||
can
|
||||
|
||||
<ul>
|
||||
* (a) just generate IL
|
||||
|
||||
* (b) be a CLS "consumer", which means that it can read in
|
||||
meta-data describing component interfaces,
|
||||
and that it provides a way to declare variables of
|
||||
CLS-complaint types and to call CLS-complaint methods.
|
||||
|
||||
* (c) be a CLS "extender", which means that it can in addition
|
||||
derive from CLS-compliant classes
|
||||
and implement CLS-compliant interfaces
|
||||
|
||||
* (d) be able to produce components with *any* CLS-compliant
|
||||
component interface.
|
||||
</ul>
|
||||
|
||||
Supporting some of these may require extending your language. However,
|
||||
you can get quite a lot of interoperability by just putting appropriate
|
||||
functionality in your compiler, without extending your language.
|
||||
|
||||
For some things, e.g. ASP.NET, your language implementation also needs to be
|
||||
able to
|
||||
|
||||
<ul>
|
||||
* (e) consume CodeDom trees. CodeDom trees are an abstract
|
||||
representation of programs in a form similar to a C# parse
|
||||
tree, with embedded code snippets (unparsed strings).
|
||||
Given a CodeDom tree, with the snippets in your language,
|
||||
your language implementation needs to generate a (i) .NET
|
||||
assembly and possibly also (ii) a source file in your language.
|
||||
|
||||
* (f) produce CodeDom trees. For some applications,
|
||||
your language implementation also needs to be able to
|
||||
round-trip from CodeDom -> your language -> CodeDom.
|
||||
</ul>
|
||||
|
||||
and for some things it needs to
|
||||
|
||||
<ul>
|
||||
* (g) generate *verifiable* IL
|
||||
</ul>
|
||||
|
||||
So when you hear all the hype about how language XYZ is a
|
||||
".NET language", make sure you ask which of these different
|
||||
things are supported.
|
||||
|
||||
[For the record, Mercury currently supports (a). We're working on
|
||||
(b) and (g), and on parts of (c) and (e). We're never going to do (f), I very
|
||||
strongly doubt we'll ever do (d), and for (c) we might only ever support
|
||||
implementing interfaces, not deriving from classes.]
|
||||
|
||||
</blockquote></i>
|
||||
|
||||
** PInvoke
|
||||
|
||||
Q: What are the two major initiatives to implement PInvoke?
|
||||
|
||||
A: Fergus Henderson answers:
|
||||
|
||||
<i><blockquote>
|
||||
Many of the .NET APIs will need to be implemented using code that calls C/Unix
|
||||
APIs, such as stat(). The standard way of interfacing with native code from
|
||||
.NET code is to use "PInvoke". However, there is a difficulty: many of
|
||||
these APIs are defined in terms of types such as C's `long' or `size_t'
|
||||
or the Posix `struct stat' whose representation varies depending on the
|
||||
platform (architecture/OS/C compiler). There's no *portable* way of
|
||||
accessing those from .NET managed code.
|
||||
|
||||
So, there are a couple of different approaches.
|
||||
One possibility is to access such routines by writing a wrapper, e.g. in C,
|
||||
that provides the same functionality without using types with a system-dependent
|
||||
representation. The wrapper can then be directly accessed from portable
|
||||
.NET code. The .NET code remains both source- and binary-portable;
|
||||
the wrapper code is source-portable, but needs to be compiled
|
||||
seperately for each target platform. The drawback of this approach is
|
||||
that you have to write a lot of cumbersome wrapper code.
|
||||
|
||||
Another possibility is to extend the .NET VM with support for an
|
||||
additional custom attribute, e.g. "[PosixType]". The VM would then
|
||||
represent types tagged with this attribute in the same way that the
|
||||
underlying system represents those types. With this approach, no
|
||||
wrapper code would be needed. A drawback of this approach is that it
|
||||
pushes quite a bit of complexity into the VM; the VM would have to know
|
||||
the native representation of all types annotated with this attribute.
|
||||
Another drawback is that code using this extension might not work on
|
||||
different VMs.
|
||||
|
||||
There have also been some other suggestions, but those are the two that
|
||||
I think are the best.
|
||||
</blockquote></i>
|
||||
|
||||
Q: What is the problem implementing PInvoke?
|
||||
|
||||
A: Again, from Fergus Henderson:
|
||||
|
||||
<i><blockquote>
|
||||
There's no problem implementing PInvoke as specified in the ECMA
|
||||
specs and/or MS documentation. It's just that PInvoke by itself
|
||||
doesn't solve all of the problems; in particular it doesn't solve
|
||||
the problem of C types whose representation is different on different
|
||||
systems.
|
||||
</blockquote></i>
|
||||
|
||||
** CVS use
|
||||
|
||||
Q: Why do we keep ChangeLogs and make the CVS commit messages be the
|
||||
same? One could be generated from the other
|
||||
|
||||
A: There are a number of reasons for keeping ChangeLog files as well as
|
||||
CVS commit files:
|
||||
|
||||
<ul>
|
||||
* Offline programming: when people are traveling, CVS logs are
|
||||
not available.
|
||||
|
||||
* Slow CVS access: Many people work over modem lines (very
|
||||
typical for contributors in Europe, Asia, Latin America)
|
||||
using CVS is slow and might not be available to you (cvs
|
||||
server down, no anoncvs server available).
|
||||
|
||||
* ChangeLogs travel in a released tarball package, so it is
|
||||
possible to study the rationale of changes even after a
|
||||
project is long "released", or you only have the sources for
|
||||
the code.
|
||||
|
||||
* ChangeLog are not metadata for each file, they are live
|
||||
files that you can browse in the package that is being
|
||||
distributed.
|
||||
</ul>
|
||||
|
||||
Making the CVS commit message be the same as the ChangeLog has other
|
||||
benefits:
|
||||
|
||||
<ul>
|
||||
* You can track down with `cvs log' what things were changed,
|
||||
and match those to meaningful reports on the intentions of
|
||||
the commit.
|
||||
|
||||
* When reading the commits-list, you can get a glimpse of the
|
||||
changes without having to diff out or cvs update your tree.
|
||||
|
||||
* You can read off-line the changes that are being made
|
||||
(asyncrouns operation).
|
||||
</ul>
|
||||
|
||||
This mechanism works very well for GNOME and other projects.
|
||||
|
||||
Q: Should I use any of the special RCS keywords like $Id: devel-faq,v 1.1 2001/07/31 21:13:05 miguel Exp $, $Author: miguel $,
|
||||
$Date: 2001/07/31 21:13:05 $, or $Revision: 1.1 $?
|
||||
|
||||
A: Please avoid using those in the source code in the CVS. They
|
||||
are not really useful, and they cause a lot of conflicts when
|
||||
people have separate CVS trees.
|
||||
|
||||
It was a nightmare with the Linux kernel when two people had their
|
||||
private CVS trees and were submitting patches to the core.
|
||||
|
||||
@@ -0,0 +1,35 @@
|
||||
* Documentation
|
||||
|
||||
Although most of the concepts from Microsoft.NET can
|
||||
be applied to the completed Mono platform, we do need to
|
||||
have a complete set of free documentation written specifically
|
||||
for Mono.
|
||||
|
||||
The documentation license we have chosen is the GNU Free
|
||||
Documentation License (FDL), the standard for most documents
|
||||
in the free software world.
|
||||
|
||||
We need documentation on a number of topics:
|
||||
|
||||
<ul>
|
||||
|
||||
* The development tools (compilers, assembler tools,
|
||||
language reference, design time features).
|
||||
|
||||
* Frequently Asked Question compilations.
|
||||
|
||||
* HOWTO documents.
|
||||
|
||||
* The Class Libraries
|
||||
|
||||
* Tutorials on Mono and the specifics of running it.
|
||||
|
||||
* A guide to Mono as compared to the Microsoft.NET
|
||||
Framework SDK
|
||||
|
||||
</ul>
|
||||
|
||||
** Class Library documentation
|
||||
|
||||
We are moving to a new setup for documenting the class libraries,
|
||||
you can read about it <a href="classlib-doc.html">here</a>
|
||||
@@ -0,0 +1,332 @@
|
||||
* Software Availability
|
||||
|
||||
The Virtual Execution System is available in package `mono'.
|
||||
Currently this contains a metadata library and the
|
||||
disassembler. Please refer to our <a
|
||||
href="runtime.html">Runtime</a> description for more details
|
||||
on this part of the project.
|
||||
|
||||
The code for the C# compiler as well as the language error
|
||||
test suite and the class library are in the `mcs' package, we
|
||||
will move this later into `mono' itself.
|
||||
|
||||
In order to make mcs and the class libraries you will need a computer
|
||||
running Windows with the <strong>GNU make tools</strong> from the
|
||||
<strong>Cygwin</strong> environment, <strong>Microsoft's .NET Framework
|
||||
SDK</strong>, <strong>GLIB 1.3</strong> and
|
||||
<strong>pkg-config</strong>.
|
||||
|
||||
When installing Cygwin, don't forget to include
|
||||
<tt>mingw-runtime</tt>. If you omit this, you will encounter
|
||||
configure problems regarding not being able to generate
|
||||
executables.
|
||||
|
||||
<a name="sources">
|
||||
*** Sources
|
||||
|
||||
Stay up to date on the Mono team's development using the
|
||||
<a href="http://lists.ximian.com/mailman/listinfo/mono-cvs-list">
|
||||
mono-cvs-list</a> mailing list. The CVS source code can also
|
||||
be browsed <a href="http://cvs.hispalinux.es/cgi-bin/cvsweb/mcs/mcs/cfold.cs?cvsroot=Mono">here</a>
|
||||
|
||||
<a name="feb-22">
|
||||
<b>Mono 0.9</b>
|
||||
|
||||
New packaged versions of the Mono C# compiler and Mono runtime
|
||||
are now available. The latest version is 0.9.
|
||||
|
||||
<ul>
|
||||
* <a href="archive/mono-0.9">Mono 0.9 release notes</a>
|
||||
|
||||
* <a href="archive/mcs-0.9.tar.gz">mcs-0.9.tar.gz</a>
|
||||
Mono C# compiler
|
||||
* <a href="archive/mono-0.9.tar.gz">mono-0.9.tar.gz</a>
|
||||
Mono runtime
|
||||
</ul>
|
||||
|
||||
<a name="snapshots">
|
||||
For up to date sources, it is recommended that you use the Mono
|
||||
source code from either the
|
||||
<a href="http://www.go-mono.com/snapshots">nightly snapshots</a> or
|
||||
the <a href="anoncvs.html">Anonymous CVS</a>. The nightly
|
||||
snapshots are done every night at 10pm EST (Boston Time).
|
||||
|
||||
The nightly snapshots are not guaranteed to build, but most of the
|
||||
time they should. They should give you a window to see what we are
|
||||
up to.
|
||||
|
||||
You can download the GNU make tools and the Cygwin environment from
|
||||
<a href="http://www.cygwin.com">www.cygwin.com</a>.
|
||||
|
||||
You can download Microsoft's .NET Framework SDK from
|
||||
<a href="http://msdn.microsoft.com/downloads">
|
||||
msdn.microsoft.com/downloads</a>.
|
||||
|
||||
There are scripts to help build mono for both Unix and Windows. Get
|
||||
<a href="mono-build.sh">mono-build.sh</a> for Unix, or <a
|
||||
href="mono-build-w32.sh">mono-build-w32.sh</a> for Windows.
|
||||
These scripts automate the installation of GLIB and pkgconfig
|
||||
(building from source on Unix, and using binary packages
|
||||
provided by the GIMP for Windows project on Windows.) To use
|
||||
the script, follow these simple steps:
|
||||
|
||||
<ul>
|
||||
* Save the script for your platform somewhere (e.g. /usr/local/bin)
|
||||
* Make the script executable (i.e chmod 755 /usr/local/bin/mono-build.sh)
|
||||
* Create a directory to hold the mono source, and the compiled binaries (e.g. mkdir ~/mono)
|
||||
* Change to the new directory (i.e. cd ~/mono)
|
||||
* run the script (i.e. /usr/local/bin/mono-build.sh)
|
||||
</ul>
|
||||
|
||||
The script requires wget on either platform, and building the
|
||||
software requires make, gcc, automake, autoconf, and libtool.
|
||||
You should install these packages from your distribution or
|
||||
with the cygwin installer.
|
||||
|
||||
The script will download required packages from
|
||||
www.go-mono.com and do a cvs checkout of mono in the current
|
||||
directory. The cvs server chosen defaults to anonymous cvs;
|
||||
set your CVSROOT environment variable before running the script to
|
||||
select a particular cvs server.
|
||||
|
||||
<a name="install">
|
||||
** Building the software manually
|
||||
|
||||
*** Download the required software.
|
||||
|
||||
<ul>
|
||||
|
||||
* Microsoft's .NET Framework SDK from
|
||||
<a href="http://msdn.microsoft.com/downloads">
|
||||
msdn.microsoft.com/downloads</a>.
|
||||
|
||||
* Cygwin and the GNU Make tools from
|
||||
<a href="http://www.cygwin.com">www.cygwin.com</a>.
|
||||
Some people observed problems with autoconf 2.52. Installing
|
||||
autoconf 2.13 helped in those cases.
|
||||
|
||||
* Precompiled GLIB 1.3 and pkg-config packages (and
|
||||
their dependencies) by the <a href="http://www.gimp.org/~tml/gimp/win32//index.html">GIMP for Windows</a> project from
|
||||
<a href="http://www.go-mono.com/archive/pkgconfig-0.80-tml-20020101.zip">http://www.go-mono.com/archive/pkgconfig-0.80-tml-20020101.zip</a>
|
||||
<a href="http://www.go-mono.com/archive/glib-1.3.12-20020101.zip">http://www.go-mono.com/archive/glib-1.3.12-20020101.zip</a>
|
||||
<a href="http://www.go-mono.com/archive/glib-dev-1.3.12-20020101.zip">http://www.go-mono.com/archive/glib-dev-1.3.12-20020101.zip</a>
|
||||
<a href="http://www.go-mono.com/archive/libiconv-1.7.zip">http://www.go-mono.com/archive/libiconv-1.7.zip</a>
|
||||
<a href="http://www.go-mono.com/archive/libiconv-dev-1.7.zip">http://www.go-mono.com/archive/libiconv-dev-1.7-20020101.zip</a>
|
||||
<a href="http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip">http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip</a>
|
||||
|
||||
* Download the Mono source code from the
|
||||
<a href="#feb-11">packaged versions</a> or
|
||||
the <a href="http://www.go-mono.com/snapshots">
|
||||
nightly snapshots</a> or the <a href="anoncvs.html">
|
||||
Anonymous CVS</a>. The nightly snapshots are done every
|
||||
night at 10pm EST (Boston Time). The nightly snapshots are
|
||||
not guaranteed to build, but most of the time they should.
|
||||
|
||||
|
||||
</ul>
|
||||
|
||||
|
||||
*** Install Cygwin and the GNU build tools, Microsoft's .NET Framework SDK and the precompiled GLIB 1.3 and pkg-config libraries.
|
||||
|
||||
<ul>
|
||||
|
||||
* Install <a href="http://www.cygwin.com">Cygwin</a>.
|
||||
|
||||
* Install <a href="http://msdn.microsoft.com/downloads">
|
||||
Microsoft .NET Framework SDK</a>.
|
||||
|
||||
* Change to the <strong>/usr/local</strong> directory
|
||||
of your Cygwin installation.<br>
|
||||
Unzip the precompiled packages listed above.
|
||||
|
||||
</ul>
|
||||
|
||||
*** On Windows, to install and work on the compiler and the class libraries:
|
||||
|
||||
<ul>
|
||||
|
||||
* If you downloaded the Mono
|
||||
<a href="http://www.go-mono.com/snapshots">nightly snapshot
|
||||
</a>, untar the snapshot.
|
||||
|
||||
* Change directories to <strong>"mcs"</strong>.
|
||||
|
||||
* Compile:
|
||||
|
||||
<pre>
|
||||
<strong>make windows</strong>
|
||||
</pre>
|
||||
|
||||
</ul>
|
||||
|
||||
*** On Windows, to compile the mono runtime:
|
||||
|
||||
<ul>
|
||||
|
||||
* If you downloaded the Mono
|
||||
<a href="http://www.go-mono.com/snapshots">nightly snapshot
|
||||
</a>, untar the snapshot.
|
||||
|
||||
* Change directories to <strong>"mono"</strong>.
|
||||
|
||||
* Configure, compile and install:
|
||||
|
||||
<pre><strong>
|
||||
./configure --prefix=c:/mono
|
||||
make
|
||||
make install
|
||||
</strong></pre>
|
||||
|
||||
</ul>
|
||||
|
||||
*** On Unix, to compile the mono runtime:
|
||||
|
||||
<ul>
|
||||
|
||||
* Install <a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a>.
|
||||
|
||||
* Install glib 1.3. You can download it
|
||||
from <a href="ftp://ftp.gtk.org/pub/gtk/v1.3/glib-1.3.12.tar.gz">ftp.gtk.org</a>. Maybe you need
|
||||
to modify your ACLOCAL_FLAGS for pkg-config, for example if
|
||||
your install prefix is /usr/local:
|
||||
<pre>
|
||||
<strong>export ACLOCAL_FLAGS="-I /usr/local/share/aclocal"</strong>
|
||||
</pre>
|
||||
|
||||
* If you downloaded the Mono
|
||||
<a href="http://www.go-mono.com/snapshots">nightly snapshots
|
||||
</a>, untar the snapshot.
|
||||
|
||||
* Change directories to <strong>"mono"</strong>.
|
||||
|
||||
* Configure, compile and install:
|
||||
<pre><strong>
|
||||
./configure
|
||||
make
|
||||
make install</strong>
|
||||
</pre>
|
||||
</ul>
|
||||
|
||||
*** Notes on compiling GLIB 1.3 and pkg-config from source:
|
||||
|
||||
|
||||
<ul>
|
||||
|
||||
* Some people observed problems with autoconf 2.52. Installing
|
||||
autoconf 2.13 helped in those cases (don't forget to do a
|
||||
`make maintainer-clean' after the update).
|
||||
|
||||
* Download, compile and install <a href="http://www.freedesktop.org/software/pkgconfig">pkg-config</a> from source.
|
||||
(I had to change line 674 of
|
||||
<nobr><tt>pkg-config-0.8.0/glib-1.2.8/gstrfuncs.c</tt></nobr> from
|
||||
<nobr><tt>extern char *strsignal (int sig);</tt></nobr> to
|
||||
<nobr><tt>extern const char *strsignal (int sig);</tt></nobr>.
|
||||
|
||||
<pre><strong>
|
||||
tar xzvf pkg-config-0.8.0.tar.gz
|
||||
cd pkg-config-0.8.0
|
||||
./configure --prefix=/usr
|
||||
make
|
||||
make install</strong>
|
||||
</pre>
|
||||
|
||||
* Download, compile and install <a href="ftp://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.7.tar.gz">libiconv</a> from source.<br>
|
||||
If you dont have MS Visual C/C++ 4.0 or 5.0 or 6.0 you can also try
|
||||
the binary package available at <a
|
||||
href="http://www.gimp.org/win32/libiconv-dev-20001007.zip">
|
||||
http://www.gimp.org/win32/libiconv-dev-20001007.zip</a>.
|
||||
|
||||
|
||||
* Download, compile and install the
|
||||
<a href="ftp://ftp.gtk.org/pub/gtk/v1.3/glib-1.3.12.tar.gz">
|
||||
glib 1.3</a> from source.
|
||||
|
||||
</ul>
|
||||
|
||||
|
||||
<a name="oldreleases">
|
||||
|
||||
*** Very old releases.
|
||||
|
||||
<ul>
|
||||
<a name="feb-11">
|
||||
<b>February 11, 2002</b>
|
||||
* <a href="archive/mcs-0.8.tar.gz">mcs-0.8.tar.gz</a>
|
||||
Mono C# compiler
|
||||
* <a href="archive/mono-0.8.tar.gz">mono-0.8.tar.gz</a>
|
||||
Mono runtime
|
||||
</ul>
|
||||
|
||||
<a name="sep-18">
|
||||
<b>September 18, 2001</b>
|
||||
<ul>
|
||||
* <a href="archive/mono-0.7.tar.gz">mono-0.7.tar.gz</a>: Mono Runtime 0.7 release.
|
||||
* <a href="archive/mcs-0.7.tar.gz">mcs-0.7.tar.gz</a>: Mono Compiler and Classes 0.7 release.
|
||||
* <a href="archive/mono-0.7">Release Notes.</a>
|
||||
</ul>
|
||||
|
||||
<a name="august-22">
|
||||
<b>August 22, 2001</b>
|
||||
<ul>
|
||||
* <a href="archive/mono-0.6.tar.gz">mono-0.6.tar.gz</a>: Mono Runtime 0.6 release.
|
||||
* <a href="archive/mono-compiler-classes-0.6.tar.gz">mono-compiler-classes-0.6.tar.gz</a>: Mono Compiler and Classes 0.6 release.
|
||||
* <a href="archive/mono-0.6">Release Notes.</a>
|
||||
</ul>
|
||||
|
||||
|
||||
<a name="july-29">
|
||||
<b>July 29, 2001</b>
|
||||
<ul>
|
||||
* <a href="archive/mono-0.5.tar.gz">mono-0.5.tar.gz</a>: Mono Runtime 0.5 release.
|
||||
* <a href="archive/mono-0.5">Release Notes.</a>
|
||||
</ul>
|
||||
|
||||
|
||||
<a name="july-22">
|
||||
<b>July 22, 2001</b>
|
||||
<ul>
|
||||
* <a href="archive/mcs-22-Jul-2001.tar.gz">mcs-22-Jul-2001.tar.gz</a>: CVS snapshot.
|
||||
* <a href="archive/mcs-Jul-22-Jul-19-2001.tar.gz">Differences since 19</a>: CVS snapshot.
|
||||
* <a href="archive/mcs-22">Release Notes.</a>
|
||||
</ul>
|
||||
|
||||
<a name="july-19">
|
||||
<b>July 19th, 2001</b>
|
||||
<ul>
|
||||
* <a href="archive/mcs-19-Jul-2001.tar.gz">mcs-19-Jul-2001.tar.gz</a>: CVS snapshot.
|
||||
* <a href="archive/mcs-Jul-17-Jul-19-2001.tar.gz">Differences since 17</a>: CVS snapshot.
|
||||
* <a href="archive/mcs-19">Release Notes.</a>
|
||||
</ul>
|
||||
|
||||
<a name="july-17">
|
||||
<b>July 17th, 2001</b>
|
||||
<ul>
|
||||
* <a href="archive/mcs-17-Jul-2001.tar.gz">mcs-17-Jul-2001.tar.gz</a>: CVS snapshot.
|
||||
* <a href="archive/mcs-Jul-15-Jul-17-2001.tar.gz">Differences since 15</a>: CVS snapshot.
|
||||
* <a href="archive/mcs-17">Release Notes.</a>
|
||||
</ul>
|
||||
|
||||
<a name="july-15">
|
||||
<b>July 15th, 2001</b>
|
||||
<ul>
|
||||
* <a href="archive/mcs-15-Jul-2001.tar.gz">mcs-15-Jul-2001.tar.gz</a>: CVS snapshot.
|
||||
* <a href="archive/mono-0.4.tar.gz">mono-0.4.tar.gz</a>: Packaged Source Code.
|
||||
* <a href="archive/mono-0.4">Release Notes.</a>
|
||||
</ul>
|
||||
|
||||
<a name="july-14">
|
||||
<b>July 14th, 2001</b>
|
||||
<ul>
|
||||
* <a href="archive/mcs-12-Jul-2001.tar.gz">mcs-12-Jul-2001.tar.gz</a>: CVS snapshot.
|
||||
* <a href="archive/mono-0.3.tar.gz">mono-0.3.tar.gz</a>: Packaged Source Code.
|
||||
</ul>
|
||||
|
||||
<a name="july-8">
|
||||
<b>July 8th, 2001</b>
|
||||
|
||||
<ul>
|
||||
* <a href="archive/mcs-08-Jul-2001.tar.gz">mcs-08-Jul-2001.tar.gz</a>: CVS Snapshot
|
||||
* <a href="archive/mono-08-Jul-2001.tar.gz">mono-08-Jul-2001.tar.gz</a>: CVS Snapshot
|
||||
</ul>
|
||||
</ul>
|
||||
|
||||
@@ -0,0 +1,690 @@
|
||||
<a href="#basics">Basics</a><br>
|
||||
<a href="#ximian">The Ximian Role in the Mono project</a><br>
|
||||
<a href="#gnome">Mono and GNOME</a><br>
|
||||
<a href="#gui">Building GUI applications with Mono</a><br>
|
||||
<a href="#msft">Mono and Microsoft</a><br>
|
||||
<a href="#pnpproject">Mono and the Portable.NET Project</a><br>
|
||||
<a href="#webservices">Web Services</a><br>
|
||||
<a href="#devel">Development Tools and Issues</a><br>
|
||||
<a href="#java">Mono and Java</a><br>
|
||||
<a href="#extending">Extending Mono</a><br>
|
||||
<a href="#portability">Portability</a><br>
|
||||
<a href="#reuse">Reusing Existing Code</a><br>
|
||||
<a href="#gcc">Mono and GCC</a><br>
|
||||
<a href="#performance">Performance</a><br>
|
||||
<a href="#licensing">Licensing</a><br>
|
||||
<a href="#patents">Patents</a><br>
|
||||
<a href="#etc">Miscellaneous Questions</a><br>
|
||||
|
||||
|
||||
<a name="basics"></a>
|
||||
** Basics
|
||||
|
||||
Q: What is Mono exactly?
|
||||
|
||||
A: The Mono Project is an open development initiative sponsored by
|
||||
Ximian that is working to develop an open source, Linux-based
|
||||
version of the Microsoft .NET development platform. Its objective
|
||||
is to enable Linux developers to build and
|
||||
deploy cross-platform .NET Applications. The project will
|
||||
implement various technologies developed by Microsoft that have now
|
||||
been submitted to the ECMA for standardization.
|
||||
|
||||
Q: What is the difference between Mono and the .NET Initiative?
|
||||
|
||||
A: The ".NET Initiative" is a somewhat nebulous company-wide effort by
|
||||
Microsoft, one part of which is a cross-platform development
|
||||
framework. Mono is an implementation of the development framework,
|
||||
but not an implementation of anything else related to the .NET
|
||||
Initiative, such as Passport, software-as-a-service, or
|
||||
corporate rebranding.
|
||||
|
||||
Q: What technologies are included in Mono?
|
||||
|
||||
A: Mono contains a number of components useful for building new
|
||||
software:
|
||||
|
||||
<ul>
|
||||
* A Common Language Infrastructure (CLI) virtual
|
||||
machine that contains a class loader, Just-in-time
|
||||
compiler, and a garbage collecting runtime.
|
||||
|
||||
* A class library that can work with any language
|
||||
which works on the CLR.
|
||||
|
||||
* A compiler for the C# language. In the future we
|
||||
might work on other compilers that target the Common
|
||||
Language Runtime.
|
||||
</ul>
|
||||
|
||||
|
||||
Windows has compilers that target the virtual machine from <a
|
||||
href="http://msdn.microsoft.com/net/thirdparty/default.asp#lang">a
|
||||
number of languages:</a> Managed C++, Java Script, Eiffel,
|
||||
Component Pascal, APL, Cobol, Oberon, Perl, Python, Scheme,
|
||||
Smalltalk, Standard ML, Haskell, Mercury and Oberon.
|
||||
|
||||
The CLR and the Common Type System (CTS) enables applications and
|
||||
libraries to be written in a collection of different languages that
|
||||
target the byte code
|
||||
|
||||
This means for example that if you define a class to do algebraic
|
||||
manipulation in C#, that class can be reused from any other
|
||||
language that supports the CLI. You could create a class in C#,
|
||||
subclass it in C++ and instantiate it in an Eiffel program.
|
||||
|
||||
A single object system, threading system, class libraries, and
|
||||
garbage collection system can be shared across all these languages.
|
||||
|
||||
Q: Where can I find the specification for these technologies?
|
||||
|
||||
A: You can find the work-in-progress documentation from the T3G ECMA
|
||||
group here:
|
||||
|
||||
<a href="http://www.dotnetexperts.com">http://www.dotnetexperts.com</a>
|
||||
|
||||
Q: Will you implement the .NET Framework SDK class libraries?
|
||||
|
||||
A: Yes, we will be implementing the APIs of the .NET Framework SDK
|
||||
class libraries.
|
||||
|
||||
Q: Will you offer an ECMA-compliant set of class libraries?
|
||||
|
||||
A: Eventually we will. Our current focus is on interoperating
|
||||
with the Microsoft SDK, but we will also offer an ECMA compliant
|
||||
set of libraries.
|
||||
|
||||
Q: What does the name "Mono" mean?
|
||||
|
||||
A: Mono is the word for `monkey' in Spanish. We like monkeys.
|
||||
|
||||
Q: Is Mono usable?
|
||||
|
||||
A: The JIT engine is usable on Intel x86 machines. An interpreter
|
||||
can be used on other non-Intel x86 machines.
|
||||
|
||||
The class libraries are not yet mature enough to run real applications,
|
||||
but if you are interested in trying out Mono, you can definetly start
|
||||
testing things out as many programs run.
|
||||
|
||||
The C# compiler has made significant progress, it can even compile
|
||||
itself now, but it can not yet be ran with our class libraries as
|
||||
they are missing some features.
|
||||
|
||||
Q: When will you ship it?
|
||||
|
||||
A: It is premature to target a shipdate for the code, but we
|
||||
anticipate that it will be available some time in the middle of
|
||||
2002.
|
||||
|
||||
Q: How can I contribute?
|
||||
|
||||
A: Check the <a href="contributing.html">contributing</a> section.
|
||||
|
||||
Q: Aren't you just copying someone else's work?
|
||||
|
||||
A: We are interested in providing the best tools for programmers to
|
||||
develop applications for Free Operating Systems. We also want to help
|
||||
provide the interoperability that will allow those systems to fit in
|
||||
with other standards.
|
||||
|
||||
For more background, read the <a href="http://www.go-mono.com/rationale.html">Mono
|
||||
Project white paper</a>.
|
||||
the project.
|
||||
|
||||
|
||||
<a name="ximian"></a>
|
||||
|
||||
** The Ximian Role in the Mono Project
|
||||
|
||||
Q: Why is Ximian working on .NET?
|
||||
|
||||
A: Ximian is interested in providing the best tools for programmers to
|
||||
develop applications for Free Operating Systems.
|
||||
|
||||
For more information, read the project <a
|
||||
href="rationale.html">rationale</a> page.
|
||||
|
||||
Q: Will Ximian be able to take on a project of this size?
|
||||
|
||||
A: Of course not. Ximian a supporter of the Mono project, but the only way
|
||||
to implement something of this size is for the entire free software
|
||||
community to get involved. Visit the <a href="contributing.html">contributing</a>
|
||||
page if you'd like to help out.
|
||||
|
||||
Q: What pieces will Ximian be working on?
|
||||
|
||||
A: We will devote most of our resources to work on the pieces which are
|
||||
on the critical path to release a development and execution
|
||||
environment. Once the project is at a stage where it is useful in
|
||||
the real world, it will achieve a critical mass of developers to
|
||||
improve it further.
|
||||
|
||||
Q: Will Ximian offer Mono commercially?
|
||||
|
||||
A: When Mono is ready to be shipped Ximian will offer a commercial
|
||||
support and services for Mono.
|
||||
|
||||
Q: Will you wait until Mono is finished?
|
||||
|
||||
A: Mono will ship on various stages as they mature. Some people
|
||||
require only a subset of the technologies, those will ship first.
|
||||
|
||||
More advanced features will take more time to develop. A support
|
||||
timeline will be available in June 2002.
|
||||
|
||||
<a name="gnome"></a>
|
||||
** Mono and GNOME
|
||||
|
||||
Q: How is Mono related to GNOME?
|
||||
|
||||
A: In a number of ways. This project was born out of the need of
|
||||
providing improved tools for the GNOME community, and will use
|
||||
existing components that have been developed for GNOME when they
|
||||
are available. For example, we plan to use Gtk+ and Libart to
|
||||
implement Winforms and the Drawing2D API and are considering
|
||||
GObject support.
|
||||
|
||||
Q: Has the GNOME Foundation or the GNOME team adopted Mono?
|
||||
|
||||
A: Mono is too new to be adopted by those groups. We hope that the
|
||||
tools that we will provide will be adopted by free software
|
||||
programmers including the GNOME Foundation members and the GNOME
|
||||
project generally.
|
||||
|
||||
Q: Should GNOME programmers switch over to Mono now?
|
||||
|
||||
A: It is still far to early for discussions of "switching over." No
|
||||
pieces of Mono will be ready within the next six months, and a
|
||||
complete implementation is roughly one year away.
|
||||
|
||||
We encourage GNOME developers to continue using the existing tools,
|
||||
libraries and components. Improvements made to GNOME will have an
|
||||
impact on Mono, as they would be the "backend" for various classes.
|
||||
|
||||
Q: Will Mono include compatibility with Bonobo components? What is the
|
||||
relationship between Mono and Bonobo?
|
||||
|
||||
A: Yes, we will provide a set of classes for implementing and using
|
||||
Bonobo components from within Mono. Mono should allow you to write
|
||||
Bonobo components more easily, just like .NET on Windows allows you
|
||||
to export .NET components to COM.
|
||||
|
||||
Q: Does Mono depend on GNOME?
|
||||
|
||||
A: No, Mono does not depend on GNOME. We use a few packages produced by
|
||||
the GNOME team like the `glib' library.
|
||||
|
||||
Q: But will I be able to build GNOME applications?
|
||||
|
||||
A: Yes, we will enable people to write GNOME applications using Mono.
|
||||
|
||||
<a name="gui"></a>
|
||||
** GUI applications
|
||||
|
||||
Q: Will Mono enable GUI applications to be authored?
|
||||
|
||||
A: Yes, you will be able to build GUI applications. Indeed, that is our
|
||||
main focus. We will provide both the Windows.Forms API and the Gtk# AP(I.
|
||||
|
||||
Q: What is the difference between Gtk# and System.Windows.Forms?
|
||||
|
||||
A: Gtk# is a set of bindings for the Gtk+ toolkit for C# (and other
|
||||
CIL-enabled languages). System.Windows.Forms is an API defined
|
||||
by Microsoft to build GUI applications.
|
||||
|
||||
Q: Will I be able to run my smart clients on systems powered by Mono?
|
||||
|
||||
A: As long as your applications are 100% .NET and do not make use
|
||||
of P/Invoke to call Win32 functions, your smart client applications
|
||||
will run on Mono platforms.
|
||||
|
||||
<a name="msft"></a>
|
||||
** Mono and Microsoft
|
||||
|
||||
Q: Is Microsoft helping Ximian with this project?
|
||||
|
||||
A: No. Ximian CTO Miguel de Icaza had a friendly conversation with
|
||||
Microsoft software architect David Stutz, but that's about the
|
||||
extent of the contact. Microsoft is interested in other
|
||||
implementations of .NET and are willing to help make the ECMA spec
|
||||
more accurate for this purpose.
|
||||
|
||||
Ximian representatives have also spoken with Sam Ruby at the ECMA
|
||||
TG3 committee to discuss the same issues.
|
||||
|
||||
Q: Is Microsoft or Corel paying Ximian to do this?
|
||||
|
||||
A: No.
|
||||
|
||||
Q: Do you fear that Microsoft will change the spec and render Mono
|
||||
useless?
|
||||
|
||||
A: No. Microsoft proved with the CLI and the C# language that it was
|
||||
possible to create a powerful foundation for many languages to
|
||||
interoperate. We will always have that.
|
||||
|
||||
Even if changes happened in the platform which were undocumented,
|
||||
the existing platform would a value on its own.
|
||||
|
||||
Q: Are you writing Mono from the ECMA specs?
|
||||
|
||||
A: Yes, we are writing them from the ECMA specs and the published
|
||||
materials in print about .NET.
|
||||
|
||||
Q: If my applications use Mono, will I have to pay a service fee?
|
||||
|
||||
A: No. Mono is not related to Microsoft's initiative of
|
||||
software-as-a-service.
|
||||
|
||||
Q: Is the Mono Project is related to the Microsoft Hailstorm effort? Is
|
||||
Ximian endorsing Hailstorm?
|
||||
|
||||
A: No. The Mono Project is focused on providing a compatible set of
|
||||
tools for the Microsoft .NET development platform. It does not
|
||||
address, require, or otherwise endorse the MS Passport-based
|
||||
Hailstorm single sign-on system that is part of Windows XP and
|
||||
other services.
|
||||
|
||||
Q: Will Mono or .NET applications depend on Microsoft Passport?
|
||||
|
||||
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?
|
||||
|
||||
A: The Shared Source implementation will be expensive and its uses
|
||||
will be tightly restricted, especially for commercial use. We are
|
||||
working towards an implementation that will grant a number of
|
||||
important rights to recipients: use for any purpose,
|
||||
redistribution, modification, and redistribution of modifications.
|
||||
|
||||
This is what we call <a
|
||||
href="http://www.gnu.org/philosophy/free-sw.html">Free Software</a>
|
||||
|
||||
Q: Is Mono a free implementation of Passport?
|
||||
|
||||
A: No. Mono is just a runtime, a compiler and a set of class
|
||||
libraries.
|
||||
|
||||
Q: Will the System.Web.Security.PassportIdentity class mean
|
||||
that my software will depend on Passport?
|
||||
|
||||
A: No. Applications may use that API to contact a Passport site, but
|
||||
are not required to do so.
|
||||
|
||||
As long as your application does not use Passport, you will not
|
||||
need Passport.
|
||||
|
||||
Q: Will Mono running on Linux make Passport available for Linux?
|
||||
|
||||
A: No. However, the Passport toolkit for Linux-based web servers is
|
||||
available from Microsoft.
|
||||
|
||||
Q: Will Mono allow me to run Microsoft Office on Linux?
|
||||
|
||||
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>.
|
||||
|
||||
<a name="pnpproject"></a>
|
||||
** Mono and Portable.NET
|
||||
|
||||
Q: What are the differences between Mono and Portable.NET?
|
||||
|
||||
A: Most of Mono is being written using C#, with only
|
||||
a few parts written in C (The JIT engine, the runtime, the
|
||||
interfaces to the garbage collection system). The Portable.NET
|
||||
Project is using C for development.
|
||||
|
||||
<a name="webservices"></a>
|
||||
** Web Services
|
||||
|
||||
Q: How is Mono related to Web Services?
|
||||
|
||||
A: Mono is only related to Web Services in that it will implement the
|
||||
same set of classes that have been authored in the .NET Framework
|
||||
to simplify and streamline the process of building Web Services.
|
||||
|
||||
But most importantly, Mono is an Open Source implementation of the
|
||||
.NET Framework.
|
||||
|
||||
Q: Can I author Web Services with Mono?
|
||||
|
||||
A: You will be able to write Web Services on .NET that run on Mono and
|
||||
viceversa.
|
||||
|
||||
Q: If Mono implements the SDK classes, will I be able to write and
|
||||
execute .NET Web Services with it?
|
||||
|
||||
A: Yes. When the project is finished, you will be able to use the
|
||||
same technologies that are available through the .NET Framework SDK
|
||||
on Windows to write Web Services.
|
||||
|
||||
Q: What about Soup? Can I use Soup without Mono?
|
||||
|
||||
A: Soup is a library for GNOME applications to create SOAP servers and
|
||||
SOAP clients, and can be used without Mono. You can browse the
|
||||
source code for soup using <a
|
||||
href="http://cvs.gnome.org/bonsai">GNOME's Bonsai</a>.
|
||||
|
||||
Q: Can I use CORBA?
|
||||
|
||||
A: Yes. The CLI contains enough information about a class that
|
||||
exposing it to other RPC systems (like CORBA) is really simple, and
|
||||
does not even require support from an object.
|
||||
|
||||
We will be implementing CORBA interoperation as an extension to the
|
||||
Mono classes so that we can integrate with Bonobo, just like
|
||||
Microsoft provides COM interoperation classes and support
|
||||
mechanisms.
|
||||
|
||||
Q: Can I serialize my objects to other things other than XML?
|
||||
|
||||
A: Yes, although the serializing tools have not yet been planned, and
|
||||
you would probably have to implement them yourself.
|
||||
|
||||
<a name="devel"></a>
|
||||
** Development Tools and Issues
|
||||
|
||||
Q: Will it be possible to use the CLI features without using bytecodes
|
||||
or the JIT?
|
||||
|
||||
A: Yes. The CLI engine will be made available as a shared library.
|
||||
The garbage collection engine, the threading abstraction, the
|
||||
object system, the dynamic type code system and the JIT will be
|
||||
available for C developers to integreate with their applications if
|
||||
they wish to do so.
|
||||
|
||||
Q: Will you have new development tools?
|
||||
|
||||
A: With any luck, Free Software enthusiasts will contribute tools to
|
||||
improve the developer environment. These tools could be developed
|
||||
initially using the Microsoft implementation of the CLI and then
|
||||
executed later with Mono.
|
||||
|
||||
Q: What kind of rules make the Common Intermediate Language useful for
|
||||
JITers?
|
||||
|
||||
A: The main rule is that the stack in the CLI is not a general purpose
|
||||
stack. You are not allowed to use it for other purposes than
|
||||
computing values and passing arguments to functions or return
|
||||
values.
|
||||
|
||||
At any given call or return instruction, the types on the stack
|
||||
have to be the same independently of the flow of execution of your
|
||||
code.
|
||||
|
||||
Q: Is it true that the CIL is ideal for JITing and not efficient for
|
||||
interpreters?
|
||||
|
||||
A: The CIL is better suited to be JITed than JVM byte codes, but you
|
||||
can interpret them as trivially as you can interpret JVM byte
|
||||
codes.
|
||||
|
||||
<a name="java">
|
||||
** Mono and Java
|
||||
|
||||
Q: Why don't you use Java? After all, there are many languages that
|
||||
target the Java VM.
|
||||
|
||||
A: You can get very good tools for doing Java development on free
|
||||
systems right now. <a href="http://www.redhat.com">Red Hat</a> has
|
||||
contributed a <a href="http://gcc.gnu.org">GCC</a> <a
|
||||
href="http://gcc.gnu.org/java">frontend for Java</a> that can take
|
||||
Java sources or Java byte codes and generate native executables; <a
|
||||
href="http://www.transvirtual.com">Transvirtual</a> has implemented
|
||||
<a href="http://www.kaffe.org">Kaffe</a> a JIT engine for Java;
|
||||
Intel also has a Java VM called <a
|
||||
href="http://www.intel.com/research/mrl/orp">ORP</a>.
|
||||
|
||||
The JVM is not designed to be a general purpose virtual machine.
|
||||
The Common Intermediate Language (CIL), on the other hand, is
|
||||
designed to be a target for a
|
||||
wide variety of programming languages, and has a set of rules
|
||||
designed to be optimal for JITers.
|
||||
|
||||
Q: Could Java target the CLI?
|
||||
|
||||
A: Yes, Java could target the CLI. We have details on a <a
|
||||
href="ideas.html#guavac">project</a> that someone could take on to
|
||||
make this happen.
|
||||
|
||||
Microsoft has an implemenation of the Java language called J# that
|
||||
can target the CIL execution engine.
|
||||
|
||||
Q: Is it possible to write a JVM byte code to CIL convertor?
|
||||
|
||||
A: Yes, it is possible. Here are a few starting point:
|
||||
|
||||
<ul>
|
||||
* A byte code representation is really a flattened forest of
|
||||
trees. Look at the Mono JIT engine to see how we compute
|
||||
the basic blocks (this is used to figure out the "trees").
|
||||
|
||||
The forest is just an array of trees.
|
||||
|
||||
Indeed, run the JIT engine with -d (mono -d prog.exe) and
|
||||
you will see how these trees look like.
|
||||
|
||||
You will have to do something similar for Java.
|
||||
|
||||
* Each "forest of trees" has a meaning. This meaning can now
|
||||
be translated into the equivalent "meaning" in CLR-land.
|
||||
</ul>
|
||||
|
||||
<a name="extending"></a>
|
||||
** Extending Mono
|
||||
|
||||
Q: Would you allow other classes other than those in the
|
||||
specification?
|
||||
|
||||
A: Yes. The Microsoft class collection is very big, but it is by no
|
||||
means complete. It would be nice to have a port of `Camel' (the
|
||||
Mail API used by Evolution inspired by Java Mail) for Mono
|
||||
applications.
|
||||
|
||||
You might also want to look into implementing CORBA for Mono. Not
|
||||
only because it would be useful, but because it sounds like a fun
|
||||
thing to do, given the fact that the CLI is such a type rich
|
||||
system.
|
||||
|
||||
For more information on extending Mono, see our <a
|
||||
href="ideas.html">ideas</a> page.
|
||||
|
||||
Q: Do you plan to Embrace and Extend .NET?
|
||||
|
||||
A: Embracing a good technology is good. Extending technologies in
|
||||
incompatible ways is bad for the users, so we do not plan on
|
||||
extending the technologies.
|
||||
|
||||
If you have innovative ideas, and want to create new classes, we
|
||||
encourage you to make those classes operate correctly well in both
|
||||
Mono and .NET
|
||||
|
||||
<a name="portability"></a>
|
||||
** Portability
|
||||
|
||||
Q: Will Mono only work on Linux?
|
||||
|
||||
A: Currently, we are doing our work on Linux-based systems and
|
||||
Windows. We do not expect many Linux-isms in the code, so it
|
||||
should be easy to port Mono to other UNIX variants.
|
||||
|
||||
Q: What about Mono on non X-based systems?
|
||||
|
||||
A: Our main intention at Ximian is to be able to develop GNOME
|
||||
applications with Mono, but if you are interested in providing a
|
||||
port of the Winform classes to other platforms (frame buffer or
|
||||
MacOS X for example), we would gladly integrate them, as long
|
||||
they are under an open source license.
|
||||
|
||||
Q: Will Mono run on Windows?
|
||||
|
||||
A: We hope so. Currently some parts of Mono only run on Windows
|
||||
(the C# compiler is a .NET executable) and other parts have only
|
||||
been compiled on Linux, but work on Windows with Cygwin.
|
||||
|
||||
Q: Will Mono depend on GNOME?
|
||||
|
||||
A: It will depend only if you are using a particular assembly (for
|
||||
example, for doing GUI applications). If you are just interested
|
||||
in Mono for implementing a `Hello World Enterprise P2P Web
|
||||
Service', you will not need any GNOME components.
|
||||
|
||||
<a name="reuse"></a>
|
||||
** Reusing Existing Code
|
||||
|
||||
Q: What projects will you reuse or build upon?
|
||||
|
||||
A: We want to get Mono in the hands of programmers soon. We are
|
||||
interested in reusing existing open source software.
|
||||
|
||||
Q: What about Intel's research JIT framework, ORP?
|
||||
|
||||
A: At this time, we are investigating whether we can use elements of
|
||||
ORP for Mono. ORP is a research JIT engine that has a clearly
|
||||
defined API that splits the JIT from the GC system and the actual
|
||||
byte code implementation.
|
||||
|
||||
Q: What about using GNU Lightning?
|
||||
|
||||
A: We are also researching <a
|
||||
href="http://www.gnu.org/software/lightning/lightning.html">GNU
|
||||
Lightning</a>.
|
||||
|
||||
<a name="gcc"></a>
|
||||
** Mono and GCC
|
||||
|
||||
Q: Are you working on a GCC front-end to C#? A GCC backend that will
|
||||
generate CIL images? What about making a front-end to GCC that
|
||||
takes CIL images and generates native code?
|
||||
|
||||
A: We are currently seeking volunteers for those projects.
|
||||
Visit the <a href="contributing.html">contributing</a> section if
|
||||
you are interested.
|
||||
|
||||
Q: But would this work around the GPL in the GCC compiler and allow
|
||||
people to work on non-free front-ends?
|
||||
|
||||
A: People can already do this by targeting the JVM byte codes (there
|
||||
are about 130 compilers for various languages that target the JVM).
|
||||
|
||||
Q: Why are you writing a JIT engine instead of a front-end to GCC?
|
||||
|
||||
A: We want the JIT engine and runtime engine because they will be able
|
||||
to execute CIL executables generated on Windows, and so no recompilation
|
||||
will be necessary.
|
||||
|
||||
<a name="performance"></a>
|
||||
** Performance
|
||||
|
||||
Q: How fast will Mono be?
|
||||
|
||||
A: We can not predict the future, but a conservative estimate is that
|
||||
it would be at least `as fast as other JIT engines'.
|
||||
|
||||
We would like to ship various JIT engines with Mono, just like
|
||||
Microsoft has done with their .NET development platform. We could
|
||||
provide a faster, JIT for fast load times but lower performance,
|
||||
and an and an optimizing JIT that would be slower at generating
|
||||
code but produce more optimal output.
|
||||
|
||||
The CIL has some advantages over the Java byte code: it is really
|
||||
an intermediate representation and there are a number of
|
||||
restrictions on how you can emit CIL code that simplify creating
|
||||
better JIT engines.
|
||||
|
||||
For example, on the CIL, the stack is not really an abstraction
|
||||
available for the code generator to use at will. Rather, it is a
|
||||
way of creating a postfix representation of the parsed tree. At
|
||||
any given call point or return point, the contents of the stack are
|
||||
expected to contain the same object types independently of how the
|
||||
instruction was reached.
|
||||
|
||||
<a name="licensing"></a>
|
||||
** Licensing
|
||||
|
||||
Q: Will I be able to write proprietary applications that run with
|
||||
Mono?
|
||||
|
||||
A: Yes. The licensing scheme is planned to allow proprietary
|
||||
developers to write applications with Mono.
|
||||
|
||||
Q: What license or licenses are you using for the Mono Project?
|
||||
|
||||
A: The C# Compiler is released under the terms of the <a
|
||||
href="http://www.opensource.org/licenses/gpl-license.html">GNU GPL</a>. The runtime
|
||||
libraries are under the <a
|
||||
href="http://www.opensource.org/licenses/lgpl-license.html">GNU
|
||||
Library GPL</a>. And the class libraries are released
|
||||
under the terms of the <a
|
||||
href="http://www.opensource.org/licenses/mit-license.html">MIT X11</a>
|
||||
license.
|
||||
|
||||
Q: I would like to contribute code to Mono under a particular
|
||||
license. What licenses will you accept?
|
||||
|
||||
A: We will have to evaluate the licenses for compatibility first,
|
||||
but as a general rule, we will accept the code under the same
|
||||
terms of the "container" module.
|
||||
|
||||
<a name="patents></a>
|
||||
** Patents
|
||||
|
||||
Q: Could patents be used to completely disable Mono (either submarine
|
||||
patents filed now, or changes made by Microsoft specifically to
|
||||
create patent problems)?
|
||||
|
||||
A: No. First, its basic functional capabilities have pre-existed too
|
||||
long to be held up by patents. The basic components of Mono are
|
||||
technologically equivalent to Sun's Java technology, which has been
|
||||
around for years. Mono will also implement multi-language and
|
||||
multi-architecture support, but there are previous technologies
|
||||
such as UCSD p-code and ANDF that also support multiple languages
|
||||
using a common intermediate language. The libraries are similar
|
||||
to other language's libraries, so again, they're too similar to
|
||||
be patentable in large measure.
|
||||
|
||||
However, if Microsoft does patent some technology, then our plan is
|
||||
to either (1) work around it, (2) chop out patented pieces, (3)
|
||||
find prior art that would render the patent useless.
|
||||
|
||||
Not providing a patented capability would weaken the
|
||||
interoperability, but it would still provide the free software /
|
||||
open source software community with good development tools, which
|
||||
is the primary reason for developing Mono.
|
||||
|
||||
<a name="etc"></a> **
|
||||
Miscellaneous Questions
|
||||
|
||||
Q: You say that the CLI allows multiple languages to execute on the
|
||||
same environment. Isn't this the purpose of CORBA?
|
||||
|
||||
A: The key difference between CORBA (and COM) and the CLI is that the
|
||||
CLI allows "data-level interoperability" because every
|
||||
language/component uses the same data layout and memory management.
|
||||
|
||||
This means you can operate directly upon the datatypes that someone
|
||||
else provides, without having to go via their interfaces. It also
|
||||
means you don't have to "marshall" (convert) parameters (data
|
||||
layouts are the same, so you can just pass components directly) and
|
||||
you don't have to worry about memory managment, because all
|
||||
languages/components share the same garbage collector and address
|
||||
space. This means much less copying and no need for reference
|
||||
counting.
|
||||
|
||||
Q: Will you support COM?
|
||||
|
||||
A: The runtime will support XPCOM on Unix systems and COM on Windows.
|
||||
Most of the code for dynamic trampolines exists already.
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
* The GCC front-end
|
||||
|
||||
The GCC front-end will accept input in a binary file with
|
||||
codes in the Common Intermediate Language (CIL), and generate
|
||||
native code.
|
||||
|
||||
This will allow pre-compilation and full optimization to take
|
||||
place before a program is executed.
|
||||
|
||||
@@ -0,0 +1,112 @@
|
||||
* Ideas
|
||||
|
||||
There are many pending classes that need to be implemented. Those have
|
||||
the highest impact in the Mono project: the sooner they are done,
|
||||
the sooner we can start using this platform to create new and
|
||||
exciting applications.
|
||||
|
||||
That being said, if you are not very excited about working on class
|
||||
libraries, here is a list of other related projects or tools that might
|
||||
be useful to the Mono project.
|
||||
|
||||
Here are a few ideas of tools, classes and projects that you
|
||||
could start. More are forthcoming.
|
||||
|
||||
<a name="runtime">
|
||||
** Runtime
|
||||
|
||||
We need a verifier that can be run on an executable (assembly)
|
||||
and tells whether the metadata for the executable is correct
|
||||
or not. It should report any anomalies.
|
||||
|
||||
For a list of anomalies in assemblies, check the various assertions
|
||||
that are described on the ECMA documentation.
|
||||
|
||||
This will help test our generated executables and can be also
|
||||
used as an external verifier.
|
||||
|
||||
<a name="classes">
|
||||
** Classes
|
||||
|
||||
<ul>
|
||||
TODO=jxta,The JXTA Peer to Peer foundation
|
||||
* Implement a JXTA protocol implementation:
|
||||
<a href="http://www.jxta.org">http://www.jxta.org</a>
|
||||
|
||||
TODO=camel,Mail API
|
||||
* Implement a Mail API, similar to Camel or JavaMail (Camel has
|
||||
significant architecture features that are required on a real
|
||||
mailer).
|
||||
|
||||
You can check the current C
|
||||
<a href="http://cvs.gnome.org/bonsai/rview.cgi?dir=evolution%2Fcamel">
|
||||
Camel implementation</a>.
|
||||
|
||||
Such an implementation could be used both with
|
||||
Microsoft .NET and Mono.
|
||||
|
||||
TODO=multimedia
|
||||
* Interfacing to Multimedia systems. You might want
|
||||
to look into the Quicktime API. I know <a
|
||||
href="mailto:[email protected]">Vladimir</a> has
|
||||
researched the problem before
|
||||
|
||||
</ul>
|
||||
|
||||
<a name="projects">
|
||||
** Projects
|
||||
|
||||
<ul>
|
||||
TODO=xmlStorage,
|
||||
* Implement an xmlStorageSystem for the CLI:
|
||||
<a href="http://www.soapware.org/xmlStorageSystem">
|
||||
http://www.soapware.org/xmlStorageSystem</a>
|
||||
|
||||
TODO=guavac,Java compiler for .NET
|
||||
* You could take one of the existing Java compilers
|
||||
(Guavac comes to mind as it is so nice) and modify
|
||||
it to generate .NET code rather than JVM byte
|
||||
codes.
|
||||
|
||||
This should be a pretty straightforward task.
|
||||
Guavac has the advantage of being written in C++ and
|
||||
it could be compiled with the Microsoft Managed C++
|
||||
compiler and produce a .NET executable with it.
|
||||
|
||||
TODO=CORBA,CORBA implementation
|
||||
* Build a CORBA interoperability engine for the CLR.
|
||||
You do not need to do all of the work, just talking
|
||||
the protocol will get us a long way (<a
|
||||
href="http://www.omg.org">The OMG site</a> has the
|
||||
CORBA specs).
|
||||
|
||||
Get in touch with David Taylor (dtaylo11 at bigpond
|
||||
dot net dot au) as he has been working on this
|
||||
project.
|
||||
|
||||
TODO=Bonobo,Bonobo for Mono
|
||||
* Once CORBA is done, implement the Bonobo interfaces
|
||||
to allow people to use Bonobo components in Mono and
|
||||
Mono components with Bonobo. The best of both worlds!
|
||||
|
||||
TODO=moniker,Object Naming System with Monikers
|
||||
* A naming space for Mono. An object naming space is
|
||||
a very powerful tool. Bonobo implements a moniker
|
||||
system that is more powerful than the original
|
||||
moniker concept that was pioneered by COM/OLE in the
|
||||
Microsoft world.
|
||||
|
||||
Our implementation builds on a concept, and we have
|
||||
made it simpler, more powerful, more extensible and
|
||||
a much better mechanism than the equivalent monikers
|
||||
on Windows.
|
||||
|
||||
Implementing Mono monikers would benefit both
|
||||
Windows users using .NET and Mono users on Unix and
|
||||
Windows.
|
||||
|
||||
Here is <a
|
||||
href="http://primates.ximian.com/~miguel/monikers.html">an
|
||||
overview of the moniker system</a> in Bonobo.
|
||||
|
||||
</ul>
|
||||
@@ -0,0 +1,908 @@
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<a href="http://www.ximian.com">Ximian</a> announced the
|
||||
launch of the Mono project, an effort to create an Open Source
|
||||
implementation of the .NET Development Framework.
|
||||
|
||||
Mono includes: <a href="c-sharp.html">a compiler</a> for the
|
||||
C# language, a <a href="runtime.html">runtime</a> for the
|
||||
Common Language Infrastructure and a set of <a
|
||||
href="class-library.html">class libraries</a>.
|
||||
|
||||
You can read our <a href="rationale.html">rationale</a> for
|
||||
this project. If you have questions about the project, please
|
||||
read our list of <a href="faq.html">Frequently Asked
|
||||
Questions</a> or <a href="mailto:[email protected]">contact us.</a>
|
||||
|
||||
You might also want to <a href="download.html">Download the
|
||||
source</a> for our work so far. Grab a <a
|
||||
href="snapshots">snapshot</a> of our current work, or <a
|
||||
href="http://cvs.hispalinux.es/cgi-bin/cvsweb/?hidenonreadable=1&f=u&logsort=date&sortby=file&hideattic=1&cvsroot=Mono">browse
|
||||
the sources</a>
|
||||
|
||||
You might want to <a
|
||||
href="mailing-lists.html">subscribe</a> to our mono-list
|
||||
and mono-announce-list
|
||||
|
||||
You can contact the team at: <a
|
||||
href="mailto:[email protected]">[email protected]</a>
|
||||
</td>
|
||||
<td>
|
||||
<table border=1 bgcolor>
|
||||
<tr>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a href="c-sharp.html">C# Compiler</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Self hosting on Linux and Windows.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b>JIT</b>
|
||||
</td>
|
||||
<td>
|
||||
Linux/x86 working.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b>Interpreter</b>
|
||||
</td>
|
||||
<td>
|
||||
Working:<br>
|
||||
Linux/x86, Linux/PPC<br>
|
||||
In progress: StrongARM, SPARC.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a href="class-status.html">Classes</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Corlib is self hosting.
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
** Mar 26, 2002
|
||||
|
||||
Paolo finally fixed the last bug in the JITer that stopped
|
||||
us from using it to run the Mono C# compiler. Goodies are on
|
||||
CVS.
|
||||
|
||||
<a href="http://gtk-sharp.sourceforge.net">Gtk#</a> runs <a
|
||||
href="http://gtk-sharp.sourceforge.net/gtk-hello-world.png">Hello
|
||||
World</a>
|
||||
|
||||
** Mar 19, 2002
|
||||
|
||||
Martin has been working on our debugging infrastructure, both
|
||||
on the JIT side of things (adding dward support) as well as on
|
||||
the class libraries (so that MCS can start generating
|
||||
debugging information).
|
||||
|
||||
Jason and Kral keep working on the System.Xml namespace,
|
||||
allowing Mike to move more to self-hosting his Gtk# code.
|
||||
|
||||
The System.Web classes are now part of the build (and they are
|
||||
also part of the class status now). Ajay contributed a large
|
||||
chunk of code to the System.Xml.Schema namespace
|
||||
|
||||
Dan (of regex fame) has been working on internal calls
|
||||
support: moving more code from the old monowrapper to become
|
||||
internal calls.
|
||||
|
||||
Paolo and Dietmar are working steadily on our runtime
|
||||
environment, fixing bugs, adding missing features and allowing
|
||||
us to run the compiler on Linux.
|
||||
|
||||
Remember to post your bug reports.
|
||||
|
||||
The nice class status on the right is brought to you by
|
||||
endless hacking hours from Piers and Nick. These status
|
||||
report pages have been helping us track down various mistakes
|
||||
in our classes (very useful, check it out for yourself)
|
||||
|
||||
** Mar 12, 2002
|
||||
|
||||
At midnight, in Italy, Paolo got the Mono C# compiler to self
|
||||
host on Linux, the last bug has been squashed to self
|
||||
hostingness. We have now a fully self hosting compiler in Linux.
|
||||
|
||||
A release will follow up shortly.
|
||||
|
||||
** Mar 9, 2002
|
||||
|
||||
Updated the <a href="class-status.html">class status</a>, now
|
||||
it is possible to use the right-side menu to browse a specific
|
||||
assembly.
|
||||
|
||||
** Mar 7, 2002
|
||||
|
||||
MCS compiles on Linux!
|
||||
|
||||
Today Paolo got the <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-March/003726.html">MCS
|
||||
compiler compiling itself on Linux</a>
|
||||
completely for the first time! The resulting image still contains
|
||||
some errors, but the whole compiler process goes now.
|
||||
|
||||
We are very close to have a complete self hosting environment now.
|
||||
|
||||
Mono is temporarly using the Bohem GC garbage collector while
|
||||
we deploy the more advanced ORP one.
|
||||
|
||||
** Mar 5, 2002
|
||||
|
||||
The CVS repository <a href="http://cvs.hispalinux.es/cgi-bin/cvsweb/?hidenonreadable=1&f=u&logsort=date&sortby=file&hideattic=1&cvsroot=Mono">can be browsed</a>
|
||||
|
||||
Jason has got an incredible amount of work on the Xml
|
||||
classes during the weekend, and Gaurav is very close to have
|
||||
the complete System.Web.UI.WebControls namespace implemented.
|
||||
|
||||
Martin and Duco have been killing bugs by using the recently
|
||||
revamped regression test suite.
|
||||
|
||||
Piers has updated our <a href="class-status.html">class
|
||||
status</a> page again, with even more information available.
|
||||
|
||||
The C# compiler has full constant folding implemented now and Ravi
|
||||
killed bugs of bugs in the <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">Mono Bug List</a>
|
||||
|
||||
** Mar 1, 2002
|
||||
|
||||
RPMs of Mono 0.9 are available at <a href="http://mono.baselabs.org/#download">mono.baselabs.com</a>
|
||||
|
||||
** Feb 28, 2002
|
||||
|
||||
<a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-February/003464.html">Christophe</a>
|
||||
has setup his <a href="http://mono.baselabs.org">First Steps in Mono</a> web site, which
|
||||
shows you a step-by-step process on getting Mono running on your system.
|
||||
|
||||
RPMs of Mono 0.9 are available at <a href="http://mono.baselabs.org/index.php/software/">mono.baselabs.org</a>
|
||||
|
||||
** Feb 27, 2002
|
||||
|
||||
New <a href="class-status.html">class status</a> engine that
|
||||
provides detailed information about missing functionality in
|
||||
our class libraries. Nick built the cormissing tool and Piers
|
||||
did the XSLT and DHTML magic.
|
||||
|
||||
More compiler progress on Linux: our support runtime now
|
||||
enables the compiler to compile `MIS' on Linux (MIS being
|
||||
Dick's Mono sample HTTP server ;-)
|
||||
|
||||
** Feb 26, 2002
|
||||
|
||||
Paolo posted a list of <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-February/003266.html">ways
|
||||
you can help</a> if you do not have Windows right now. Sergey followed up with
|
||||
<a href="http://lists.ximian.com/archives/public/mono-list/2002-February/003268.html">his</a>
|
||||
suggestions.
|
||||
|
||||
** Feb 25, 2002
|
||||
|
||||
StrongARM port from Sergey Chaban has been checked into CVS.
|
||||
|
||||
** Feb 24, 2002
|
||||
|
||||
SPARC: 44 out of 74 tests pass now (Jeff)
|
||||
|
||||
Power PC: delegates are working now (Radek)
|
||||
|
||||
** Feb 22, 2002
|
||||
|
||||
<b>Mono 0.9 has been released!</b>
|
||||
|
||||
A new version of the runtime, compiler and class libraries has
|
||||
been packaged for your download pleasure. The <a
|
||||
href="archive/mono-0.9">Release Notes</a>
|
||||
|
||||
You can get it <a
|
||||
href="download.html#feb-22">Here</a> (quick links: <a
|
||||
href="archive/mono-0.9.tar.gz">runtime</a> and <a
|
||||
href="archive/mcs-0.9.tar.gz">compiler/classes</a>).
|
||||
|
||||
** Feb 21, 2002
|
||||
|
||||
Paolo got our compiler natively to compile 117 of our tests.
|
||||
Self hosting is closer every day.
|
||||
|
||||
Unsafe support is finished in the C# compiler.
|
||||
|
||||
** Feb 20, 2002
|
||||
|
||||
Gaurav got DataGrid and DataGridItemCollection done.
|
||||
|
||||
C# compiler: Unsafe support is mostly complete (only stackalloc is missing).
|
||||
|
||||
New easy to run scripts for compiling Mono on Unix and Windows
|
||||
is <a href="download.html">available</a>. We can now easily compile
|
||||
Mono on Windows and Linux. If you had trouble before, use the
|
||||
above scripts which will get the setup right for you.
|
||||
|
||||
There are now three machines that can provide AnonCVS, just
|
||||
use anoncvs.go-mono.com as the hostname for your CVSROOT and
|
||||
you will get one of the machines.
|
||||
|
||||
** Feb 19, 2002
|
||||
|
||||
Do you want to see what <a href="http://people.debian.org/~lupus/mono/">Mono Looks Like?</a>
|
||||
|
||||
** Feb 18, 2002
|
||||
|
||||
Application Domains now support the two LoaderOptimization
|
||||
modes: share code or do not share code, and you can control
|
||||
this with the --share-code command line option.
|
||||
|
||||
Paolo has now 100+ test cases run on Linux now with our class
|
||||
libraries.
|
||||
|
||||
PowerPC and SPARC ports are moving along (Radek and Jeff)
|
||||
|
||||
** Feb 13, 2002
|
||||
|
||||
Excellent news since the 11th, here is a quick rundown:
|
||||
|
||||
AppDomains have been deployed (Dietmar). Socket work is done
|
||||
(Dick). Corlib compiled with no refs to mscorlib (Dan). New
|
||||
comprehensive tests for colib bits (David). Nick is driving the
|
||||
regression test suite efforts and class library completeness.
|
||||
New System.Data work (Chris). Bug fixes (Paolo, Duncan, Ravi, Miguel)
|
||||
|
||||
Miguel is off to the <a
|
||||
href="http://www.fosdem.org">FOSDEM</a> conference in Brussels.
|
||||
|
||||
** Feb 11, 2002
|
||||
|
||||
<b>Mono 0.8 has been released!</b>
|
||||
|
||||
A new version of the runtime, compiler and class libraries has
|
||||
been packaged for your download pleasure.
|
||||
|
||||
You can get it <a
|
||||
href="download.html#feb-11">Here</a> (quick links: <a
|
||||
href="archive/mono-0.8.tar.gz">runtime</a> and <a
|
||||
href="archive/mcs-0.8.tar.gz">compiler/classes</a>)
|
||||
|
||||
** Feb 11, 2002
|
||||
|
||||
We would like to welcome all the new developers that have
|
||||
joined the project in the last couple of days. The classes
|
||||
are rapidly moving.
|
||||
|
||||
An explanation of the relationship between <a
|
||||
href="http://mail.gnome.org/archives/gnome-hackers/2002-February/msg00031.html">GNOME
|
||||
and Mono</a>.
|
||||
|
||||
Nick is still leading our test suite platform. I can not
|
||||
stress how important it is to have a good regression test suite
|
||||
for our platform, as buggy class libraries are what are
|
||||
stopping the compiler from running completely on Linux.
|
||||
|
||||
We are of course psyched to see Mono run on
|
||||
non-Linux systems. Work is moving on native code generation
|
||||
for StrongARM, PowerPC, and SPARC as well as porting Mono to
|
||||
other systems.
|
||||
|
||||
There are a couple of debates on the Mono list on implementing
|
||||
a set of web server classes for <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-February/002911.html">enabling
|
||||
ASP.NET</a> on Mono.
|
||||
|
||||
Paolo also <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-February/002944.html">
|
||||
posted a list of pending tasks</a> to enable the compiler to run on Linux
|
||||
|
||||
** Feb 10, 2002
|
||||
|
||||
Mike Kestner has posted an <a
|
||||
href="http://lists.ximian.com/archives/public/gtk-sharp-list/2002-February/000024.html">Update
|
||||
on his Gtk#</a> activities.
|
||||
|
||||
** Feb 4, 2002
|
||||
|
||||
Adam has done <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-February/002808.html">Qt
|
||||
bindings</a> for .NET. Adam is cool.
|
||||
|
||||
** Jan 29, 2002
|
||||
|
||||
Dan Lewis has contributed a major missing set of classes to
|
||||
Mono: <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2002-January/002745.html">
|
||||
System.Text.RegularExpressions</a>.
|
||||
|
||||
This is a fully .NET compatible implementation of the .NET regular expressions,
|
||||
fully Unicode aware. This contribution is very appreciated, as implementing this
|
||||
was not entirely trivial (supporting Unicode, plus a regex engine which is a super
|
||||
set of the Perl regex engine).
|
||||
|
||||
** Jan 28, 2002
|
||||
|
||||
The Mono contributors have relicensed the Class Libraries under
|
||||
the terms of the
|
||||
<a href="http://www.opensource.org/licenses/mit-license.html">MIT X11</a> license.
|
||||
|
||||
This license is an Open Source license, and is used by other projects
|
||||
(most notably, the XFree86 project).
|
||||
|
||||
The runtime (JIT, metadata library, interpreter) remains under
|
||||
the LGPL and the C# compiler remains under the GPL.
|
||||
|
||||
Our <a
|
||||
href="http://www.ximian.com/about_us/press_center/press_releases/mono_partners.html">Press
|
||||
Release</a>
|
||||
|
||||
Press coverage: <a
|
||||
href="http://news.com.com/2100-1001-823734.html">CNet</a>, <a
|
||||
href="http://www.wired.com/news/technology/0,1282,50037-2,00.html">Wired</a>,
|
||||
<a href="http://www.infoworld.com/articles/hn/xml/02/01/28/020128hnopennet.xml">InfoWorld</a>,
|
||||
<a href="http://www.newsforge.com/article.pl?sid=02/01/27/2232231">NewsForge</a>.
|
||||
|
||||
** Jan 23, 2002
|
||||
|
||||
New mailing list: <a href="mailto:[email protected]">[email protected]</a>.
|
||||
This mailing list will receive automatically the patches that are submitted
|
||||
to the Mono CVS to any of its modules.
|
||||
|
||||
This allows anyone who wants to participate in the peer-review of the
|
||||
code submitted to CVS to receive patches on e-mail. It should also
|
||||
expose to everyone the changes that are being done by the team every day.
|
||||
|
||||
** Jan 21, 2002
|
||||
|
||||
Dick has got a simple web server running with Mono (`MIS: Mono
|
||||
Internet Server') that is mostly used to test our IO layer, a
|
||||
<a href="http://primates.ximian.com/~miguel/dick-mis-server.png">screenshot</a>
|
||||
|
||||
Paolo and Dietmar are busy making our runtime self sufficient on
|
||||
non-Windows platforms.
|
||||
|
||||
C# compiler front: A lot of focus in the past weeks after
|
||||
the C# became self hosting has been in making the compiler a useful
|
||||
tool for development: improve error handling, provide better error
|
||||
reports, fixing all known bugs, and finally profiling of the compiler
|
||||
has begun.
|
||||
|
||||
** Jan 8, 2002
|
||||
|
||||
Our compiler has been self-supporting since January 3rd. In
|
||||
the meantime, we have been busy working on making it run on
|
||||
Linux. Today Paolo got more work done on Reflection.Emit and
|
||||
the compiler compiled `console.cs' (a sample Mono program) on
|
||||
Linux.
|
||||
|
||||
** Jan 4, 2002
|
||||
|
||||
Dietmar landed the Unicode support patch. Class libraries and
|
||||
runtimes are now fully Unicode aware. The details are <a href=
|
||||
"http://lists.ximian.com/archives/public/mono-list/2002-January/002409.html">
|
||||
here</a>
|
||||
|
||||
Last minute breaking news: Paolo got our compiler in Linux to
|
||||
compile fib.cs, patches are comming tomorrow once we have
|
||||
ChangeLog entries.
|
||||
|
||||
** Jan 4, 2002
|
||||
|
||||
Mike Kestner posted an update on Gtk# <a
|
||||
href="http://lists.ximian.com/archives/public/gtk-sharp-list/2002-January/000021.html"><i>New
|
||||
year, new direction</i></a>.
|
||||
|
||||
Gtk# will be our foundation on which we will be implementing
|
||||
System.Windows.Forms.
|
||||
|
||||
** Jan 3, 2002
|
||||
|
||||
Mono C# compiler becomes self-sufficient. We can now continue
|
||||
development of the compiler with itself.
|
||||
|
||||
Work on the class libraries is still underway for having a full
|
||||
self hosting system. We hope to achieve our goal of self-hosting
|
||||
on Linux before the end of the month.
|
||||
|
||||
Join the fun by downloading either tonight's <a
|
||||
href="snapshots">snapshot</a> or getting your sources from our
|
||||
<a href="anoncvs.html">Anonymous CVS server</a>.
|
||||
|
||||
** Dec 28, 2001
|
||||
|
||||
After a lot of work, the C# compiler can compile itself.
|
||||
There are still errors in the generated image, but they are
|
||||
being fixed quickly.
|
||||
|
||||
We will soon have the first non-Microsoft C# implementation!
|
||||
|
||||
** Dec 18, 2001
|
||||
|
||||
JIT: More work on our IO abstraction layer (Dick).
|
||||
|
||||
JIT: exception handling for unmanaged code (Dietmar)
|
||||
|
||||
System.Reflection: Support for PropertyInfo and
|
||||
PropertyBuilder as well as the various queries for MethodBase.
|
||||
|
||||
C#: Pre-processor; Rewrite of MemberLookup which fixed many of
|
||||
the outstanding issues. More bug fixing allows it to compile
|
||||
more programs.
|
||||
|
||||
** Dec 14, 2001
|
||||
|
||||
Dietmar has improved the register allocation and now Mono performs
|
||||
two to three times as fast as it did yesterday. Amazing.
|
||||
|
||||
The compiler keeps moving along, explicit interface
|
||||
implementation is there.
|
||||
|
||||
** Dec 11, 2001
|
||||
|
||||
The JIT engine can now run all the compiler regression tests as
|
||||
well as assorted other programs, many more opcodes added
|
||||
recently. Currently the JIT engine uses a very simplistic register
|
||||
allocator (just enough to allow us to focus on feature completeness)
|
||||
and that will be the next major task to improve performance and
|
||||
reduce spills and reloads.
|
||||
|
||||
On the C# compiler front: language features are now pretty
|
||||
much complete. The big missing tasks are unsafe code support,
|
||||
visibility, explicit interface implementation plus static flow
|
||||
analysis. There are many small bugs that need to be addressed.
|
||||
|
||||
You can get your copy of the <a href="snapshots">latest Mono</a>
|
||||
|
||||
More work is also required on fixing the foundation class
|
||||
libraries, it is easy to find spots now since Nick got the
|
||||
`make test' going.
|
||||
|
||||
** Dec 1, 2001
|
||||
|
||||
AnonCVS access to Mono is here (updated every hour). Thanks
|
||||
to <a href="http://www.hispalinux.es">HispaLinux</a> and Jesus
|
||||
Climent for helping to set this up.
|
||||
|
||||
** Nov 30, 2001
|
||||
|
||||
All tests from the mono runtime work with the JIT engine now
|
||||
(Dietmar).
|
||||
|
||||
Recursive enumeration definition in the C# compiler are
|
||||
working now (Ravi).
|
||||
|
||||
More work on the Web classes (Gaurav).
|
||||
|
||||
** Nov 28, 2001
|
||||
|
||||
JIT land: Paolo got GDB support into the JIT engine while
|
||||
Dietmar added exceptions support to it.
|
||||
|
||||
The C# compiler supports all array initializations now, and the
|
||||
switch statement as well as fixing many existing bugs. Many
|
||||
new more tests.
|
||||
|
||||
Nick keeps working on improving our class library test suite.
|
||||
|
||||
Dick has almost completed the Mono IO layer.
|
||||
|
||||
** Nov 16, 2001
|
||||
|
||||
<blockquote>
|
||||
Mike Kestner has posted an <a
|
||||
href="http://lists.ximian.com/archives/public/gtk-sharp-list/2001-November/000015.html">update</a>
|
||||
on Gtk# development.
|
||||
</blockquote>
|
||||
|
||||
** Nov 14, 2001
|
||||
|
||||
<blockquote>
|
||||
Paolo today got the Mono C# compiler running <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2001-November/001941.html">on
|
||||
Linux</a>. It compiles a sample program and then the sample
|
||||
program is executed.
|
||||
|
||||
Mutator unary operators (++ and --) in the compiler are fully
|
||||
functional, they used to only work on variables, and now they
|
||||
are complete.
|
||||
|
||||
To sum things up: The Mono C# compiler is written in C# and
|
||||
uses the .NET classes to get its work done. To make this work
|
||||
on Linux work has to happen in various fronts:
|
||||
<ul>
|
||||
* The C# compiler is being worked on and can compile
|
||||
many programs now (our test suite at this point is
|
||||
made up of 40 tests).
|
||||
|
||||
* The class libraries need to be mature enough to support
|
||||
the compiler, particularly System.Reflection.Emit (which is
|
||||
what Paolo has been working on lately).
|
||||
|
||||
The compiler currently requires 103 classes from the
|
||||
.NET runtime (you can get the list by running: <b>monodis --typeref mcs.exe</b>
|
||||
|
||||
* The interpreter should be mature enough to run the actual
|
||||
compiler byte codes and the corlib bytecodes.
|
||||
</ul>
|
||||
|
||||
At the same time, Dietmar is working on the JIT engine which will
|
||||
replace our interpreter in production.
|
||||
</blockquote>
|
||||
|
||||
** Nov 12, 2001
|
||||
|
||||
<blockquote>
|
||||
Dietmar got value types working on the JIT engine. Sean has
|
||||
got assembly loading in the runtime (required for NUnit).
|
||||
|
||||
More progress on enumerations and attributes from Ravi.
|
||||
|
||||
Nick keeps working on improving our class libraries.
|
||||
</blockquote>
|
||||
|
||||
** Nov 8, 2001
|
||||
|
||||
<blockquote>
|
||||
Enumerations, array access and attributes for the C# compiler are into the CVS now.
|
||||
|
||||
Full array support is not complete, but moving along.
|
||||
</blockquote>
|
||||
|
||||
** Nov 5, 2001
|
||||
|
||||
<blockquote>
|
||||
Dietmar's new set of patches to the JIT have 20 out of 33
|
||||
tests running now.
|
||||
</blockquote>
|
||||
|
||||
** Nov 4, 2001
|
||||
|
||||
<blockquote>
|
||||
Mike Kestner, main Gtk# contributor has posted a very interesting <a
|
||||
href="http://lists.ximian.com/archives/public/gtk-sharp-list/2001-November/000013.html">
|
||||
update</a> on his work on Gtk#.
|
||||
|
||||
Ravi commited the initial support for Attributes in the
|
||||
compiler.
|
||||
|
||||
Many HTML Controls from Leen checked into CVS.
|
||||
|
||||
Paolo checked in his new System.Reflection and
|
||||
System.Reflection.Emit implementations. He has been working
|
||||
steadily on this huge task for a few weeks now. This is the
|
||||
foundation for the Mono C# compiler, and hence a very
|
||||
important piece of the puzzle.
|
||||
</blockquote>
|
||||
|
||||
** Nov 3, 2001
|
||||
|
||||
<blockquote>
|
||||
Many clean ups have been going into the class library by Nick Drochak.
|
||||
|
||||
Mega patch from Dietmar: he commited the flow analysis code
|
||||
for the JITer.
|
||||
|
||||
A lot of work has been going into the WebControls by Gaurav (4
|
||||
new controls plus improved and bug fixed base classes).
|
||||
</blockquote>
|
||||
|
||||
** Nov 1, 2001
|
||||
|
||||
<blockquote>
|
||||
Ravi commited the caller-side method selection of methods with
|
||||
variable length arguments. Now he depends on Miguel finishing
|
||||
the array handling support.
|
||||
</blockquote>
|
||||
|
||||
** Oct 27, 2001
|
||||
|
||||
<blockquote>
|
||||
Lots of classes for System.Web from Gaurav were commited this
|
||||
morning.
|
||||
|
||||
Some large recent developments:
|
||||
|
||||
The Decimal implementation from Martin Weindel has been
|
||||
partially integrated (we need to put the internalcalls in
|
||||
place now and compile and link the decimal code).
|
||||
|
||||
Derek Holden commited recently the IntegerFormatter code into
|
||||
the CVS, so we got a pretty comprehensive integer formatting
|
||||
engine that we can finally use all over the place.
|
||||
|
||||
Compiler got support for lock as well as assorted bug fixes.
|
||||
Ravi is still working on array support (and then we can
|
||||
optimize foreach for the array case).
|
||||
|
||||
Dietmar is busy working on flow analysis on the JITer, the
|
||||
previous mechanism of generating the forest was wrong. Paolo
|
||||
has been a busy bee reworking the System.Reflection.Emit
|
||||
support code, and we should have some pretty nice stuff next
|
||||
week. Dick on the other hand is still working on the
|
||||
WaitOne/WaitAll emulation code. WaitAll is like select on
|
||||
steroids: it can wait for different kinds of objects: files,
|
||||
mutexes, events and a couple of others.
|
||||
|
||||
Mike Kestner is busy working on Gtk# which is now using the
|
||||
.defs files to quickly wrap the API.
|
||||
</blockquote>
|
||||
|
||||
** Oct 18, 2001
|
||||
|
||||
<blockquote>
|
||||
Reworking expressions to support cleanly indexers and
|
||||
properties. <a href="http://www.nat.org/evolution.php3">11
|
||||
days</a> until Evolution 1.0 ships.
|
||||
|
||||
Ximian users around the world <!--a
|
||||
href="http://www.bez.it/IMAGES/nora.jpg"-->rejoice<!--/a--> with
|
||||
recent C# compiler progress.
|
||||
</blockquote>
|
||||
|
||||
** Oct 17, 2001
|
||||
|
||||
<blockquote>
|
||||
Delegate support has been checked into the compiler
|
||||
(definition and invocation); break/continue implemented.
|
||||
</blockquote>
|
||||
|
||||
** Oct 15, 2001
|
||||
|
||||
<blockquote>
|
||||
JIT engine supports many of the object constructs now (object
|
||||
creation, vtable setup, interface table setup).
|
||||
|
||||
The C# compiler now has almost full property support (only
|
||||
missing bit are pre-post increment/decrement operations),
|
||||
delegates are now created (still missing delegate invocation).
|
||||
try/catch/finally is also supported in the compiler now.
|
||||
|
||||
System.Decimal implementation is in, as well as many crypto
|
||||
classes.
|
||||
</blockquote>
|
||||
|
||||
** Oct 5, 2001
|
||||
|
||||
<blockquote>
|
||||
Sergey has released his first version of the <b>ilasm</b>
|
||||
assembler written in C#. You can get it from his web page:
|
||||
<a
|
||||
href="http://mono.eurosoft.od.ua">http://mono.eurosoft.od.ua</a>.
|
||||
|
||||
The plan is to integrate ildasm into the Mono CVS soon. This
|
||||
component should in theory also be reusable for SharpDevelop
|
||||
eventually.
|
||||
</blockquote>
|
||||
|
||||
** Oct 4, 2001
|
||||
|
||||
<blockquote>
|
||||
Our System.Reflection.Emit implementation created its first
|
||||
executable today. This means that a very simple .NET program
|
||||
that was compiled on Windows was able to generate a .NET program
|
||||
while running on Linux using the Mono runtime.
|
||||
|
||||
The various piece of the puzzle are starting to get together:
|
||||
the compiler can compile simple programs now and we are
|
||||
basically focusing on completeness now.
|
||||
</blockquote>
|
||||
|
||||
** Sep 28, 2001
|
||||
|
||||
<blockquote>
|
||||
<a
|
||||
href="http://www.icsharpcode.net/OpenSource/SD/default.asp">Sharp
|
||||
Develop 0.80</a> was released today.
|
||||
</blockquote>
|
||||
|
||||
** Sep 26, 2001
|
||||
|
||||
<blockquote>
|
||||
More progress: more opcodes are working (Paolo); The compiler
|
||||
runs up to a point in Mint (Paolo); operator overloading works
|
||||
(both unary and binary) all over the place (Miguel); Completed decimal
|
||||
type conversions (Miguel); New build system in place based on
|
||||
Ant (Sean and Sergey); Refactored and documented the
|
||||
internals of the JIT engine (Dietmar); StatementExpressions
|
||||
handled correctly (Miguel).
|
||||
</blockquote>
|
||||
|
||||
** Sep 21, 2001
|
||||
|
||||
<blockquote>
|
||||
A couple of news-worthy items: Dick got the initial thread
|
||||
support into mint; Paolo implemented many new opcodes; Dietmar
|
||||
got long operations and mul/div working on the JITer; Ravi rewrote
|
||||
the Method selector for expressions to be conformant; Miguel
|
||||
got i++ working. All in tonight's snapshot
|
||||
</blockquote>
|
||||
|
||||
** Sep 19, 2001
|
||||
|
||||
<blockquote>
|
||||
Paolo has written a section on <a href="porting.html">Porting
|
||||
Mono</a> to othre architectures.
|
||||
</blockquote>
|
||||
|
||||
** Sep 18, 2001
|
||||
|
||||
<blockquote>
|
||||
<A a href="download.html#sep-18">Mono 0.7</a> has been
|
||||
released (runtime engine, class libraries
|
||||
and C# compiler). Check the <a href="archive/mono-0.7">Mono
|
||||
0.7 announcement</a> for details
|
||||
</blockquote>
|
||||
|
||||
** Sep 17, 2001
|
||||
|
||||
<blockquote>
|
||||
Mike Kestner's Gtk# (Gtk-sharp) was checked into the CVS
|
||||
repository. Gtk# can run a simple hello world application.
|
||||
The binding is nice, as it maps Gtk+ signals to delegates in
|
||||
C#. You can see the Gtk# Hello World program <a href="src/HelloWorld.cs">here</a>
|
||||
|
||||
Gtk-sharp should be available on the next snapshot set.
|
||||
</blockquote>
|
||||
|
||||
** Sep 10, 2001
|
||||
|
||||
<blockquote>
|
||||
Dietmar checked in his CIL tree/forest regeneration and most
|
||||
importantly, the x86 instruction selector burg grammar.
|
||||
</blockquote>
|
||||
|
||||
|
||||
** Sep 5, 2001
|
||||
|
||||
<blockquote>
|
||||
The MCS compiler <b>can compile the sample Hello World</b>
|
||||
application and generate a Windows/CIL executable that runs!
|
||||
|
||||
This executable runs with the Mono Interpreter of course (see
|
||||
August 28)
|
||||
</blockquote>
|
||||
|
||||
** Sep 4, 2001
|
||||
|
||||
<blockquote>
|
||||
Dietmar checked into CVS the `monoburg' architecture
|
||||
independent instruction selector for the JIT engine.
|
||||
</blockquote>
|
||||
|
||||
** Aug 28, 2001
|
||||
|
||||
<blockquote>
|
||||
<b>.NET Hello World is working under Mono!</b> The latest snapshots
|
||||
will let you run it.
|
||||
|
||||
Hello World consits of 1821 CIL instructions,
|
||||
performs 66 subroutine calls and loads 12 classes from the corlib.dll
|
||||
|
||||
Good work Mono team!
|
||||
</blockquote>
|
||||
|
||||
** Aug 23, 2001
|
||||
|
||||
<blockquote>
|
||||
Lloyd Dupont has announced his OpenGL bindings for C#, they
|
||||
are available here: <a
|
||||
href="http://csgl.sourceforge.net">http://csgl.sourceforge.net</a>
|
||||
</blockquote>
|
||||
|
||||
** Aug 22, 2001
|
||||
|
||||
<blockquote>
|
||||
New version of the Mono Runtime, Compiler and Classes has been
|
||||
<a
|
||||
href="download.html#august-22">released.</a> Check the <a
|
||||
href="archive/mono-0.6">0.6 announcement</a>.
|
||||
</blockquote>
|
||||
|
||||
** Aug 20, 2001
|
||||
|
||||
<blockquote>
|
||||
A new <a href="contributing.html#compile-service">Compilation
|
||||
service</a> has been made available by Derek to allow people
|
||||
without access to the <a
|
||||
href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true">.NET SDK</a>
|
||||
</blockquote>
|
||||
|
||||
** Aug 3, 2001
|
||||
|
||||
<blockquote>
|
||||
Daily snapshots of mcs and mono are now available, they will
|
||||
run every night at 10pm Boston time.
|
||||
</blockquote>
|
||||
|
||||
** Jul 29, 2001
|
||||
|
||||
<blockquote>
|
||||
Mono Runtime 0.5 has been <a
|
||||
href="download.html#july-29">released.</a> Check the <a
|
||||
href="archive/mono-0.5">release notes</a>
|
||||
</blockquote>
|
||||
|
||||
** Jul 25, 2001
|
||||
|
||||
<blockquote>
|
||||
The slides for <A href="Presentations/O-Reilly">my
|
||||
presentation</a> at <a href="http://www.oreilly.com">O'Reilly
|
||||
Open Source Software Convention</a>
|
||||
</blockquote>
|
||||
|
||||
** Jul 22, 2001
|
||||
|
||||
<blockquote>
|
||||
Another release of the class libraries is out, check the <a
|
||||
href="archive/mcs-22">MCS 22-July Release Notes</a>. You can
|
||||
get the new class libraries from <a
|
||||
href="download.html#july-22">here</a>
|
||||
</blockquote>
|
||||
|
||||
** Jul 19, 2001
|
||||
|
||||
<blockquote>
|
||||
Another release of the class libraries is out, check the <a
|
||||
href="archive/mcs-19">MCS 19-July Release Notes</a>. You can
|
||||
get the new class libraries from <a
|
||||
href="download.html#july-19">here</a>
|
||||
</blockquote>
|
||||
|
||||
** Jul 17, 2001
|
||||
|
||||
<blockquote>
|
||||
Another release of the class libraries is out, check the <a
|
||||
href="archive/mcs-17">MCS 17-July Release Notes</a>. You can
|
||||
get the new class libraries from <a
|
||||
href="download.html#july-17">here</a>
|
||||
|
||||
Do not forget to check out the updated <a href="faq.html">FAQ</a>.
|
||||
|
||||
Got Sean's new <a href="class-status/index.html">Class
|
||||
Status</a> web pages up. These are a lot better than mine, and
|
||||
we are now keeping better track of contributors.
|
||||
</blockquote>
|
||||
|
||||
** Jul 15, 2001
|
||||
|
||||
<blockquote>
|
||||
Another release of Mono is out, check the <a
|
||||
href="archive/mono-0.4">Mono 0.4 Release Notes</a>. Get it <a
|
||||
href="download.html#july-15">here</a>.
|
||||
</blockquote>
|
||||
|
||||
** Jul 14, 2001
|
||||
|
||||
<blockquote>
|
||||
A <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2001-July/000399.html">new
|
||||
release</a> of the
|
||||
runtime, compiler and classes has been made. Get it <a href="download.html#july-14">here</a>
|
||||
</blockquote>
|
||||
|
||||
** Jul 12, 2001
|
||||
|
||||
<blockquote>
|
||||
I keep getting questions about my opinion on Passport, even when
|
||||
Mono has <b>nothing</b> to do with it. I finally <a
|
||||
href="passport.html">wrote something.</a>
|
||||
</blockquote>
|
||||
|
||||
** Jul 9, 2001
|
||||
|
||||
<blockquote>
|
||||
Project launched.
|
||||
</blockquote>
|
||||
|
||||
** O'Reilly
|
||||
|
||||
<blockquote>
|
||||
Brian posted a story on <a
|
||||
href="http://www.oreillynet.com/dotnet">O'Reilly Network .NET</a>
|
||||
</blockquote>
|
||||
@@ -0,0 +1,90 @@
|
||||
* Mailing Lists
|
||||
|
||||
There are a number of mailing lists for Mono
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-list">mono-list</a></b>
|
||||
</td>
|
||||
<td>
|
||||
The general Mono discussion list.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-announce-list">mono-announce-list</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Announcements of Mono developments.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-gc-list">mono-gc-list</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Discussion on the GC system of Mono.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-patches">mono-patches</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Track the CVS activity of Mono on this mailing list (patches are sent to recipients).
|
||||
You can get <a href="http://www.go-mono.com/snapshots">daily snapshots</a> as well.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-cvs-list">mono-cvs-list</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Track the CVS activity of Mono on this mailing list.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-docs-list">mono-docs-list</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Discussion on the documentation of Mono.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-patches">mono-patches</a></b>
|
||||
</td>
|
||||
<td>
|
||||
Track the development of Mono in realtime: receive patches to the Mono repository
|
||||
by email.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<b><a href="http://lists.ximian.com/mailman/listinfo/mono-bugs">mono-bugs</a></b>
|
||||
</td>
|
||||
<td>
|
||||
This mailing list is used to keep track of the bugs in Mono as reported
|
||||
in <a href="http://bugzilla.ximian.com">Bugzilla.ximian.com</a>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
Other mailing lists of interest:
|
||||
|
||||
<ul>
|
||||
* <b><a
|
||||
href="http://discuss.develop.com/dotnet.html">Dotnet mailing
|
||||
list at Develop.com:</a></b> The guys at Develop Mentor run
|
||||
this general purpose mailing list.
|
||||
</ul>
|
||||
</ul>
|
||||
@@ -0,0 +1,142 @@
|
||||
#!/bin/bash
|
||||
|
||||
# Script to automate the building of mono and its dependencies on
|
||||
# cygwin. Relies on wget being installed (could make it fall back to
|
||||
# using lynx, links, w3, curl etc), assumes that gcc, make, tar,
|
||||
# automake, etc are already installed too (may be worth testing for
|
||||
# all that right at the top and bailing out if missing/too old/too new
|
||||
# etc).
|
||||
|
||||
|
||||
# See where we are. This will become the top level directory for the
|
||||
# installation, unless we are given an alternative location
|
||||
here=$1
|
||||
test -z "$here" && here=`pwd`
|
||||
|
||||
echo "Building Mono and dependencies in $here, installing to $here/install"
|
||||
|
||||
PATH=$here/install/bin:$here/install/lib:$PATH
|
||||
|
||||
# Check mono out first, so we can run aclocal from inside the mono dir (it
|
||||
# needs to see which version of the real aclocal to run)
|
||||
test -z "$CVSROOT" && CVSROOT=:pserver:[email protected]:/mono
|
||||
export CVSROOT
|
||||
|
||||
echo "Updating mono"
|
||||
|
||||
# cvs checkout does the same as cvs update, except that it copes with
|
||||
# new modules being added
|
||||
|
||||
# Older versions of cvs insist on a cvs login for :pserver: methods
|
||||
# Make sure cvs is using ssh for :ext: methods
|
||||
|
||||
if [ ${CVSROOT:0:5} = ":ext:" ]; then
|
||||
CVS_RSH=ssh
|
||||
export CVS_RSH
|
||||
elif [ ${CVSROOT:0:9} = ":pserver:" ]; then
|
||||
if ! grep $CVSROOT ~/.cvspass > /dev/null 2>&1 ; then
|
||||
echo "Logging into CVS server. Anonymous CVS password is probably empty"
|
||||
cvs login || exit -1
|
||||
fi
|
||||
fi
|
||||
|
||||
cvs checkout mono || exit -1
|
||||
|
||||
# Need to install pkgconfig and set ACLOCAL_FLAGS if there is not a
|
||||
# pkgconfig installed already. Otherwise set PKG_CONFIG_PATH to the
|
||||
# glib we're about to install in $here/install. This script could
|
||||
# attempt to be clever and see if glib 2 is already installed, too.
|
||||
|
||||
|
||||
# --print-ac-dir was added in 1.2h according to the ChangeLog. This
|
||||
# should mean that any automake new enough for us has it.
|
||||
|
||||
# This sets ACLOCAL_FLAGS to point to the freshly installed pkgconfig
|
||||
# if it doesnt already exist on the system (otherwise auto* breaks if
|
||||
# it finds two copies of the m4 macros). The GIMP for Windows
|
||||
# pkgconfig sets its prefix based on the location of its binary, so we
|
||||
# dont need PKG_CONFIG_PATH (the internal pkgconfig config file
|
||||
# $prefix is handled similarly).
|
||||
|
||||
function aclocal_scan () {
|
||||
# Quietly ignore the rogue '-I' and other aclocal flags that
|
||||
# aren't actually directories...
|
||||
#
|
||||
# cd into mono/ so that the aclocal wrapper can work out which version
|
||||
# of aclocal to run
|
||||
for i in `(cd mono && aclocal --print-ac-dir)` $ACLOCAL_FLAGS
|
||||
do
|
||||
if [ -f $i/$1 ]; then
|
||||
return 0
|
||||
fi
|
||||
done
|
||||
|
||||
return 1
|
||||
}
|
||||
|
||||
function install_package() {
|
||||
zipfile=$1
|
||||
markerfile=$2
|
||||
name=$3
|
||||
|
||||
echo "Installing $name..."
|
||||
if [ ! -f $here/$zipfile ]; then
|
||||
wget http://www.go-mono.com/archive/$zipfile
|
||||
fi
|
||||
|
||||
# Assume that the package is installed correctly if the marker
|
||||
# file is there
|
||||
if [ ! -f $here/install/$markerfile ]; then
|
||||
(cd $here/install || exit -1; unzip -o $here/$zipfile || exit -1) || exit -1
|
||||
fi
|
||||
}
|
||||
|
||||
if ! aclocal_scan pkg.m4 ; then
|
||||
ACLOCAL_FLAGS="-I $here/install/share/aclocal $ACLOCAL_FLAGS"
|
||||
fi
|
||||
|
||||
export PATH
|
||||
export ACLOCAL_FLAGS
|
||||
|
||||
# Grab pkg-config, glib etc
|
||||
if [ ! -d $here/install ]; then
|
||||
mkdir $here/install || exit -1
|
||||
fi
|
||||
|
||||
# Fetch and install pkg-config, glib, iconv, intl
|
||||
|
||||
install_package pkgconfig-0.80-tml-20020101.zip bin/pkg-config.exe pkgconfig
|
||||
install_package glib-1.3.12-20020101.zip lib/libglib-1.3-12.dll glib
|
||||
install_package glib-dev-1.3.12-20020101.zip lib/glib-1.3.lib glib-dev
|
||||
install_package libiconv-1.7.zip lib/iconv.dll iconv
|
||||
install_package libiconv-dev-1.7.zip lib/iconv.lib iconv-dev
|
||||
install_package libintl-0.10.40-20020101.zip lib/libintl-1.dll intl
|
||||
install_package libgc-dev.zip lib/gc.dll gc-dev
|
||||
|
||||
# Needed to find the libiconv bits
|
||||
CPPFLAGS="$CPPFLAGS -I$here/install/include"
|
||||
LDFLAGS="$LDFLAGS -L$here/install/lib"
|
||||
export CPPFLAGS
|
||||
export LDFLAGS
|
||||
|
||||
# Make sure we build native w32, not cygwin
|
||||
CC="gcc -mno-cygwin"
|
||||
export CC
|
||||
|
||||
# --prefix is used to set the class library dir in mono, and it needs
|
||||
# to be in windows-native form. It also needs to have '\' turned into
|
||||
# '/' to avoid quoting issues during the build.
|
||||
prefix=`cygpath -w $here/install | sed -e 's@\\\\@/@g'`
|
||||
|
||||
# Build and install mono
|
||||
echo "Building and installing mono"
|
||||
|
||||
(cd $here/mono; ./autogen.sh --prefix=$prefix || exit -1; make || exit -1; make install || exit -1) || exit -1
|
||||
|
||||
|
||||
echo ""
|
||||
echo ""
|
||||
echo "All done."
|
||||
echo "Add $here/install/bin and $here/install/lib to \$PATH"
|
||||
echo "Don't forget to copy the class libraries to $here/install/lib"
|
||||
|
||||
@@ -0,0 +1,182 @@
|
||||
#!/bin/bash
|
||||
|
||||
# Script to automate the building of mono and its dependencies.
|
||||
# Relies on wget being installed (could make it fall back to using
|
||||
# lynx, links, w3, curl etc), assumes that gcc, make, tar, automake,
|
||||
# etc are already installed too (may be worth testing for all that
|
||||
# right at the top and bailing out if missing/too old/too new etc).
|
||||
|
||||
|
||||
# See where we are. This will become the top level directory for the
|
||||
# installation, unless we are given an alternative location
|
||||
here=$1
|
||||
test -z "$here" && here=`pwd`
|
||||
|
||||
echo "Building Mono and dependencies in $here, installing to $here/install"
|
||||
|
||||
PATH=$here/install/bin:$PATH
|
||||
LD_LIBRARY_PATH=$here/install/lib:$LD_LIBRARY_PATH
|
||||
|
||||
# Need to install pkgconfig and set ACLOCAL_FLAGS if there is not a
|
||||
# pkgconfig installed already. Otherwise set PKG_CONFIG_PATH to the
|
||||
# glib we're about to install in $here/install. This script could
|
||||
# attempt to be clever and see if glib 2 is already installed, too.
|
||||
|
||||
|
||||
# --print-ac-dir was added in 1.2h according to the ChangeLog. This
|
||||
# should mean that any automake new enough for us has it.
|
||||
|
||||
function aclocal_scan () {
|
||||
# Quietly ignore the rogue '-I' and other aclocal flags that
|
||||
# aren't actually directories...
|
||||
for i in `aclocal --print-ac-dir` $ACLOCAL_FLAGS
|
||||
do
|
||||
if [ -f $i/$1 ]; then
|
||||
return 0
|
||||
fi
|
||||
done
|
||||
|
||||
return 1
|
||||
}
|
||||
|
||||
function pkgconfig_scan () {
|
||||
module=$1
|
||||
|
||||
echo "Finding pkgconfig files for $module..."
|
||||
|
||||
# Should we use locate? or just a list of well-known directories?
|
||||
# locate has the problem of false positives in src dirs
|
||||
for i in /usr/lib/pkgconfig /usr/local/lib/pkgconfig
|
||||
do
|
||||
echo "Looking in $i..."
|
||||
if [ -f $i/${module}.pc ]; then
|
||||
echo $i
|
||||
return
|
||||
fi
|
||||
done
|
||||
}
|
||||
|
||||
function install_package() {
|
||||
tarfile=$1
|
||||
dirname=$2
|
||||
name=$3
|
||||
|
||||
echo "Installing $name..."
|
||||
if [ ! -f $here/$tarfile ]; then
|
||||
wget http://www.go-mono.org/archive/$tarfile
|
||||
fi
|
||||
|
||||
# Assume that the package built correctly if the dir is there
|
||||
if [ ! -d $here/$dirname ]; then
|
||||
# Build and install package
|
||||
tar xzf $here/$tarfile || exit -1
|
||||
(cd $here/$dirname; ./configure --prefix=$here/install || exit -1; make || exit -1; make install || exit -1)
|
||||
success=$?
|
||||
if [ $success -ne 0 ]; then
|
||||
echo "***** $name build failure. Run rm -rf $here/$dirname to have this script attempt to build $name again next time"
|
||||
exit -1
|
||||
fi
|
||||
fi
|
||||
}
|
||||
|
||||
if aclocal_scan pkg.m4 ; then
|
||||
install_pkgconfig=no
|
||||
else
|
||||
install_pkgconfig=yes
|
||||
fi
|
||||
|
||||
if aclocal_scan glib-2.0.m4 ; then
|
||||
install_glib=no
|
||||
if [ $install_pkgconfig = "yes" ]; then
|
||||
# We have to tell the newly-installed pkgconfig about the
|
||||
# system-installed glib
|
||||
PKG_CONFIG_PATH=`pkgconfig_scan glib-2.0`:$PKG_CONFIG_PATH
|
||||
fi
|
||||
else
|
||||
install_glib=yes
|
||||
PKG_CONFIG_PATH="$here/install/lib/pkgconfig:$PKG_CONFIG_PATH"
|
||||
fi
|
||||
|
||||
if [ -f /usr/include/gc/gc.h ]; then
|
||||
install_libgc=no
|
||||
else
|
||||
install_libgc=yes
|
||||
fi
|
||||
|
||||
if [ $install_pkgconfig = "yes" -o $install_glib = "yes" ]; then
|
||||
ACLOCAL_FLAGS="-I $here/install/share/aclocal $ACLOCAL_FLAGS"
|
||||
fi
|
||||
|
||||
export PATH
|
||||
export LD_LIBRARY_PATH
|
||||
export ACLOCAL_FLAGS
|
||||
export PKG_CONFIG_PATH
|
||||
|
||||
CPPFLAGS="$CPPFLAGS -I$here/install/include"
|
||||
LDFLAGS="$LDFLAGS -L$here/install/lib"
|
||||
export CPPFLAGS
|
||||
export LDFLAGS
|
||||
|
||||
# Grab pkg-config-0.8, glib-1.3.12 if necessary
|
||||
|
||||
if [ $install_pkgconfig = "yes" ]; then
|
||||
install_package pkgconfig-0.8.0.tar.gz pkgconfig-0.8.0 pkgconfig
|
||||
else
|
||||
echo "Not installing pkgconfig, you already seem to have it installed"
|
||||
fi
|
||||
|
||||
if [ $install_glib = "yes" ]; then
|
||||
install_package glib-1.3.13.tar.gz glib-1.3.13 glib
|
||||
else
|
||||
echo "Not installing glib, you already seem to have it installed"
|
||||
fi
|
||||
|
||||
if [ $install_libgc = "yes" ]; then
|
||||
install_package gc6.0.tar.gz gc6.0 libgc
|
||||
# make install didnt do the headers!
|
||||
mkdir -p $here/install/include/gc
|
||||
cp -r $here/gc6.0/include/* $here/install/include/gc
|
||||
else
|
||||
echo "Not installing libgc, you already seem to have it installed"
|
||||
fi
|
||||
|
||||
# End of build dependencies, now get the latest mono checkout and build that
|
||||
|
||||
test -z "$CVSROOT" && CVSROOT=:pserver:[email protected]:/mono
|
||||
export CVSROOT
|
||||
|
||||
echo "Updating mono"
|
||||
|
||||
# cvs checkout does the same as cvs update, except that it copes with
|
||||
# new modules being added
|
||||
|
||||
# Older versions of cvs insist on a cvs login for :pserver: methods
|
||||
# Make sure cvs is using ssh for :ext: methods
|
||||
|
||||
if [ ${CVSROOT:0:5} = ":ext:" ]; then
|
||||
CVS_RSH=ssh
|
||||
export CVS_RSH
|
||||
elif [ ${CVSROOT:0:9} = ":pserver:" ]; then
|
||||
# Chop off the trailing /mono because cvs 1.11 adds the port number
|
||||
# into the .cvspass line
|
||||
if ! grep ${CVSROOT%:/mono} ~/.cvspass > /dev/null 2>&1 ; then
|
||||
echo "Logging into CVS server. Anonymous CVS password is probably empty"
|
||||
cvs login
|
||||
fi
|
||||
fi
|
||||
|
||||
cvs checkout mono || exit -1
|
||||
|
||||
# Build and install mono
|
||||
echo "Building and installing mono"
|
||||
|
||||
(cd $here/mono; ./autogen.sh --prefix=$here/install || exit -1; make || exit -1; make install || exit -1) || exit -1
|
||||
|
||||
|
||||
echo ""
|
||||
echo ""
|
||||
echo "All done."
|
||||
echo "Add $here/install/bin to \$PATH"
|
||||
echo "Add $here/install/lib to \$LD_LIBRARY_PATH"
|
||||
echo "Don't forget to copy the class libraries to $here/install/lib"
|
||||
|
||||
@@ -0,0 +1,755 @@
|
||||
* MonoDoc XML Tag Reference
|
||||
|
||||
** Introduction
|
||||
|
||||
<em>
|
||||
[This documentation is in progress. Comments to
|
||||
<a href="mailto:[email protected]">[email protected]</a> and/or
|
||||
<a href="mailto:[email protected]">[email protected]</a>.]
|
||||
</em>
|
||||
|
||||
MonoDoc XML, our format for multilingual API documentation stored outside of
|
||||
source files, is very similar to the output of Microsoft's csc /doc. Minor
|
||||
alterations have been made to ease human parsing and hand-editing, but
|
||||
the majority of the tags are identical. In fact, many of the descriptions
|
||||
and examples below are taken from the ECMA C# Language Specification with
|
||||
little or no alteration.
|
||||
|
||||
This document provides a list of all available MonoDoc XML tags, with
|
||||
syntax and examples. A complete example can be found in
|
||||
<a href="#appendix-a">Appendix A</a>, and both a <a href="#">DTD</a> and
|
||||
<a href="#">XSD schema</a> will be available very shortly.
|
||||
|
||||
** MonoDoc XML Tags
|
||||
|
||||
<dl>
|
||||
<dt><code><a href="#c"><c></a></code></dt>
|
||||
<dd>Mark short sections of text as code.</dd>
|
||||
|
||||
<dt><code><code><a href="#code"><code></a></code></dt></code>
|
||||
<dd>Mark one or more lines as code or output.</dd>
|
||||
|
||||
<dt><code><a href="#doc"><doc></a></dt></code>
|
||||
<dd>Root element of documentation XML.</dd>
|
||||
|
||||
<dt><code><a href="#event"><event></a></dt></code>
|
||||
<dd>Describe an event.</dd>
|
||||
|
||||
<dt><code><a href="#example"><example></a></dt></code>
|
||||
<dd>An example.</dd>
|
||||
|
||||
<dt><code><a href="#exception"><exception></a></dt></code>
|
||||
<dd>Specify an exception a method can throw.</dd>
|
||||
|
||||
<dt><code><a href="#field"><field></a></dt></code>
|
||||
<dd>Describe a field.</dd>
|
||||
|
||||
<dt><code><a href="#list"><list></a></dt></code>
|
||||
<dd>Create a list or table.</dd>
|
||||
|
||||
<dt><code><a href="#method"><method></a></dt></code>
|
||||
<dd>Describe a method.</dd>
|
||||
|
||||
<dt><code><a href="#para"><para></a></dt></code>
|
||||
<dd>Allow text to be structured in paragraphs.</dd>
|
||||
|
||||
<dt><code><a href="#param"><param></a></dt></code>
|
||||
<dd>Specify a parameter for a method.</dd>
|
||||
|
||||
<dt><code><a href="#paramref"><paramref></a></dt></code>
|
||||
<dd>Mark a word as a parameter.</dd>
|
||||
|
||||
<dt><code><a href="#permission"><permission></a></dt></code>
|
||||
<dd>Define the access level of a member.</dd>
|
||||
|
||||
<dt><code><a href="#property"><property></a></dt></code>
|
||||
<dd>Describe a property.</dd>
|
||||
|
||||
<dt><code><a href="#remarks"><remarks></a></dt></code>
|
||||
<dd>Provide verbose information for a type or member.</dd>
|
||||
|
||||
<dt><code><a href="#returns"><returns></a></dt></code>
|
||||
<dd>Specify the return value of a method.</dd>
|
||||
|
||||
<dt><code><a href="#see"><see></a></dt></code>
|
||||
<dd>Specify a link.</dd>
|
||||
|
||||
<dt><code><a href="#seealso"><seealso></a></dt></code>
|
||||
<dd>Specify a 'see also' entry.</dd>
|
||||
|
||||
<dt><code><a href="#summary"><summary></a></dt></code>
|
||||
<dd>Provide a brief (usually one sentence) description of a member or type.</dd>
|
||||
|
||||
<dt><code><a href="#type"><type></a></dt></code>
|
||||
<dd>Describe a type.</dd>
|
||||
</dl>
|
||||
|
||||
** Definitions and Examples
|
||||
|
||||
*** <a name="c"><c></a>
|
||||
|
||||
This tag can be used to mark short, inline fragments of text that should
|
||||
be considered source code or program output. User agents should render
|
||||
this tag in a special -- likely monospace -- font. For larger sections,
|
||||
use <a href="#code"><code><code></code></a>.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<pre>
|
||||
<c>code or output text</c>
|
||||
</pre>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<remarks>
|
||||
Class <c>Point</c> models a point in two-dimensional space.
|
||||
</remarks>
|
||||
</pre>
|
||||
|
||||
*** <a name="code"><code></a>
|
||||
|
||||
This tag can be used to mark one or more lines of text as source code or
|
||||
program output. User agents should render this tag in a special (likely
|
||||
monospace) font, and preserve both whitespace and newlines.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><code>source or program output</code></code>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
This method changes the point's location by the given
|
||||
x- and y-offsets.
|
||||
<example lang="C#">
|
||||
A C# example:
|
||||
<code>
|
||||
Point p = new Point(3, 5);
|
||||
p.Translate(-1, 3);
|
||||
// p == (2, 8);
|
||||
</code>
|
||||
</example>
|
||||
</summary>
|
||||
</pre>
|
||||
|
||||
*** <a name="doc"><doc></a>
|
||||
|
||||
This tag is the root element of the documentation file. It can contain
|
||||
any number of <type> elements.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><doc lang="language" assembly="assembly">typedocs</doc></code>
|
||||
|
||||
<blockquote>
|
||||
<em>lang="language"</em><br />
|
||||
The two-letter ISO code that specifies what language the contained
|
||||
documentation is written in.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<doc lang="en">
|
||||
<type name="Graphics.Point">
|
||||
<!-- ... -->
|
||||
</type>
|
||||
</doc>
|
||||
</pre>
|
||||
|
||||
*** <a name="event"><event></a>
|
||||
|
||||
This tag documents an event.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><event name="eventname">documentation</event></code>
|
||||
|
||||
<blockquote>
|
||||
<em>name="eventname"</em><br />
|
||||
The name of the event being documented.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<event name="Click">
|
||||
<summary>
|
||||
Occurs when the control is clicked.
|
||||
</summary>
|
||||
<data>
|
||||
The event handler receives an argument of type EventArgs
|
||||
containing data related to this event.
|
||||
</data>
|
||||
<remarks>
|
||||
<para>The ControlStyles.StandardClick style must be set
|
||||
for this event to be raised.</para>
|
||||
<para>For more information about handling events, see
|
||||
Consuming Events.</para>
|
||||
</remarks>
|
||||
</event>
|
||||
</pre>
|
||||
|
||||
*** <a name="example"><example></a>
|
||||
|
||||
This tag marks a section of text as an example, and optionally specifies
|
||||
what programming language <code><a href="#code"><code></a></code> portions of the example are written in.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><example lang="language">example text and code</example></code>
|
||||
|
||||
<blockquote>
|
||||
<em>lang="language"</em><br />
|
||||
(optional) The name of the programming language <code><a href="#code"><code></a></code> blocks in this example
|
||||
use. This information can be used by user agents to provide
|
||||
intelligent access to examples in multiple languages.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
See <code><a href="#code"><code><a/></code> for an example.
|
||||
|
||||
*** <a name="exception"><exception></a>
|
||||
|
||||
This tag provides a way to specify the exceptions a method can throw.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><exception cref="exception-type">description</exception></code>
|
||||
|
||||
<blockquote>
|
||||
<em>cref="exception-type"</em><br />
|
||||
The name of an exception type.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<exception cref="System.IO.FileNotFoundException">
|
||||
Thrown when the requested file is not found.
|
||||
</exception>
|
||||
</pre>
|
||||
|
||||
*** <a name="field"><field></a>
|
||||
|
||||
This tag is used to describe a field.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><field name="fieldname">documentation</field></code>
|
||||
|
||||
<blockquote>
|
||||
<em>name="fieldname"</em><br />
|
||||
The name of the field being documented.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<field name="x">
|
||||
<summary>
|
||||
Instance variable <c>x</c> represents the point's
|
||||
x-coordinate.
|
||||
</summary>
|
||||
</field>
|
||||
</pre>
|
||||
|
||||
*** <a name="list"><list></a>
|
||||
|
||||
This tag is used to create a list or table of items. It may contain a
|
||||
<code><listheader></code> block to define the heading row of either a table or
|
||||
definition list. (When defining a table, only an entry for 'term' in the
|
||||
heading need be supplied.)
|
||||
|
||||
Each item in the list is specified with an <code><item></code> block. When creating a
|
||||
definition list, both <code><term></code> and <code><description></code> must be specified.
|
||||
However, for a table, bulleted list, or numbered list, only <code><description></code>
|
||||
need be specified.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<pre>
|
||||
<list type="bullet" | "number" | "table">
|
||||
<listheader>
|
||||
<term>term</term>
|
||||
<description>description</description>
|
||||
</listheader>
|
||||
<item>
|
||||
<term>term</term>
|
||||
<description>description</description>
|
||||
</item>
|
||||
|
||||
...
|
||||
|
||||
</list>
|
||||
</pre>
|
||||
|
||||
<blockquote>
|
||||
<em>term</em><br />
|
||||
The term to define, whose definition is in <code><description></code>.
|
||||
<br /><br />
|
||||
<em>description</em><br />
|
||||
Either an item in a bullet or numbered list, or the definition of a <code><term></code>.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<list type="bullet">
|
||||
<item>
|
||||
<description>Item 1</description>
|
||||
</item>
|
||||
<item>
|
||||
<description>Item 2</description>
|
||||
</item>
|
||||
</list>
|
||||
</pre>
|
||||
|
||||
*** <a name="method"><method></a>
|
||||
|
||||
This tag is the overall containing tag for documenting a method.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><method name="methodname">documentation</method></code>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<method name="op_Equality(Graphics.Point,Graphics.Point)">
|
||||
<summary>
|
||||
This operator determines whether two points have
|
||||
the same location.
|
||||
</summary>
|
||||
<param name="p1">
|
||||
<c>p1</c> is the first Point to be compared.
|
||||
</param>
|
||||
<param name="p2">
|
||||
<c>p2</c> is the second Point to be compared.
|
||||
</param>
|
||||
<returns>
|
||||
True if the points have the same location and they
|
||||
have the exact same type; otherwise, false.
|
||||
</returns>
|
||||
<seealso cref="Equals(System.Object)" />
|
||||
<seealso cref="op_Inequality(Graphics.Point,Graphics.Point)" />
|
||||
</method>
|
||||
</pre>
|
||||
|
||||
*** <a name="para"><para></a>
|
||||
|
||||
|
||||
This tag is for use inside other tags such as <code><remarks></code> or <code><returns></code>, and
|
||||
allows text to be structured into paragraphs.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><para>text</para></code>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
<para>
|
||||
This is the entry point of the <c>Point</c> class testing
|
||||
program.
|
||||
</para>
|
||||
<para>
|
||||
This program tests each method and operator, and
|
||||
is intended to be run after any non-trivial maintenance has
|
||||
been performed on the <c>Point</c> class.
|
||||
</para>
|
||||
</summary>
|
||||
</pre>
|
||||
|
||||
*** <a name="param"><param></a>
|
||||
|
||||
This tag is used to describe a parameter for a method, constructor, or
|
||||
indexer.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><param name="name">description</param></code>
|
||||
|
||||
<blockquote>
|
||||
<em>name</em><br />
|
||||
The name of the parameter.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
This is the entry point of the <c>Point</c>
|
||||
class.
|
||||
</summary>
|
||||
<param name="xor"><c>xor</c> is the new x-coordinate.</param>
|
||||
<param name "yor"><c>yor</c> is the new y-coordinate.</param>
|
||||
</pre>
|
||||
|
||||
*** <a name="paramref"><paramref></a>
|
||||
|
||||
This tag is used to indicate that a word is a parameter. User agents
|
||||
could use this information for special formatting or hyperlink insertion.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><paramref name="name" /></code>
|
||||
|
||||
<blockquote>
|
||||
<em>name</em><br />
|
||||
The name of the parameter.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
This constructor initializes the new Point to
|
||||
(<paramref name="xor" />,<paramref name="yor" />).
|
||||
</summary>
|
||||
<param name="xor"><c>xor</c> is the new x-coordinate.</param>
|
||||
<param name "yor"><c>yor</c> is the new y-coordinate.</param>
|
||||
</pre>
|
||||
|
||||
*** <a name="permission"><permission></a>
|
||||
|
||||
This tag allows the security accessibility of a member to be documented.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><permission cref="member">description</permission></code>
|
||||
|
||||
<blockquote>
|
||||
<em>cref="member"</em><br />
|
||||
The name of a member.</br>
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<permission cref="System.Security.PermissionSet">
|
||||
Everyone can access this method.
|
||||
</permission>
|
||||
</pre>
|
||||
|
||||
*** <a name="property"><property></a>
|
||||
|
||||
This tag is the overall containing tag for documenting a property.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><property name="propertyname">documentation</property></code>
|
||||
|
||||
<blockquote>
|
||||
<em>name="propertyname"</em><br />
|
||||
The name of the property.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<property name="X">
|
||||
<summary>
|
||||
Gets or sets the point's x-coordinate.
|
||||
<value>
|
||||
The point's x-coordinate.
|
||||
</value>
|
||||
</property>
|
||||
</pre>
|
||||
|
||||
|
||||
*** <a name="remarks"><remarks></a>
|
||||
|
||||
This tag contains extended discussion and information about a member or
|
||||
a type. <em>[jbarn: This differs from both the ECMA docs and
|
||||
portions of Microsoft's documentation, but seems consistent with both
|
||||
common usage, and, more importantly, NDoc convention.]</em>
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><remarks>description</remarks></code>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<type name="Graphics.Point">
|
||||
<summary>
|
||||
Models a point in a two-dimensional plane.
|
||||
</summary>
|
||||
<remarks>
|
||||
Herein I might have an extended discussion of
|
||||
the validity of Cartesian coordinate systems,
|
||||
with examples pro and con, and perhaps
|
||||
some code.
|
||||
</remarks>
|
||||
|
||||
<!-- ... -->
|
||||
</type>
|
||||
</pre>
|
||||
|
||||
*** <a name="returns"><returns></a>
|
||||
|
||||
This tag is used to describe the return value of a method.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><returns>description</returns></code>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<method name="op_Inequality(Graphics.Point,Graphics.Point)">
|
||||
<summary>
|
||||
This operator determines whether two points have the
|
||||
same location.
|
||||
</summary>
|
||||
<param name="p1"><c>p1</c> is the first Point to be compared.</param>
|
||||
<param name="p2"><c>p2</c> is the second Point to be compared.</param>
|
||||
<returns>
|
||||
True if the points do not have the same location and they
|
||||
have the exact same type; otherwise, false.
|
||||
</returns>
|
||||
</method>
|
||||
</pre>
|
||||
|
||||
*** <a name="see"><see></a>
|
||||
|
||||
This tag allows a link to be specified within documentation text. (Use
|
||||
<code><seealso></code> to indicate links that should appear in a 'See Also' section.)
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><see cref="destination" /></code>
|
||||
|
||||
<blockquote>
|
||||
<em>cref="destination"</em><br />
|
||||
A destination, such as a type or a member of a type.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
This method changes the point's location to the given
|
||||
coordinates. This is an asinine way to insert a link,
|
||||
but <see cref="Equals(Object)" /> to understand
|
||||
how points are compared.
|
||||
</summary>
|
||||
</pre>
|
||||
|
||||
*** <a name="seealso"><seealso></a>
|
||||
|
||||
This tag allows an entry to be generated for the 'See Also' section. (Use
|
||||
<code><see></code> to specify a link from within text.)
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><seealso cref="destination" /></code>
|
||||
|
||||
<blockquote>
|
||||
<em>cref="destination"</em><br />
|
||||
A destination, such as a type or a member of a type.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
This method determines whether two Points have the
|
||||
same location.
|
||||
</summary>
|
||||
<seealso cref="op_Equality(Graphics.Point,Graphics.Point)" />
|
||||
<seealso cref="op_Inequality(Graphics.Point,Graphics.Point" />
|
||||
</pre>
|
||||
|
||||
*** <a name="summary"><summary></a>
|
||||
|
||||
This tag contains a short summary of a member or type,
|
||||
often one sentence. <em>[jbarn: This differs from both the ECMA docs and
|
||||
portions of Microsoft's documentation, but seems consistent with both
|
||||
common usage, and, more importantly, NDoc convention.]</em>
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><summary>description</summary></code>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<summary>
|
||||
This is the entry point of the <c>Point</c> class testing
|
||||
program.
|
||||
</summary>
|
||||
<remarks>
|
||||
This program tests each method an operator, and is intended
|
||||
to be run after any non-trivial maintenance is performed
|
||||
on the <c>Point</c> class.
|
||||
</remarks>
|
||||
</pre>
|
||||
|
||||
*** <a name="type"><type></a>
|
||||
|
||||
This tag is the overall containing tag for documenting a type.
|
||||
|
||||
**** Syntax
|
||||
|
||||
<code><type name="typename" assembly="assemblyname">documentation</type></code>
|
||||
|
||||
<blockquote>
|
||||
<em>name="typename"</em><br />
|
||||
The name of the type being documented.
|
||||
<br /><br />
|
||||
<em>assembly="assemblyname"</em><br />
|
||||
The assembly this type resides in. This attribute is not required for nested types.
|
||||
</blockquote>
|
||||
|
||||
**** Example
|
||||
|
||||
<pre>
|
||||
<type name="Graphics.Point" assembly="Point">
|
||||
<summary>
|
||||
Models a point in two-dimensional space.
|
||||
</summary>
|
||||
|
||||
<!-- members -->
|
||||
|
||||
<field name="x">
|
||||
<summary>
|
||||
Represents the point's x-coordinate.
|
||||
</summary>
|
||||
</field>
|
||||
</type>
|
||||
</pre>
|
||||
|
||||
** <a name="appendix-a">Appendix A: Complete Example</a>
|
||||
|
||||
<em>[jbarn: Please, please, don't take the human-readable portions of
|
||||
this example to be good guidelines for writing your own documentation.
|
||||
this XML is intended only to show structure.]</em>
|
||||
|
||||
<pre>
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<doc lang="en">
|
||||
<type name="Graphics.Point" assembly="Point">
|
||||
<summary>
|
||||
Models a point in a two-dimensional plane.
|
||||
</summary>
|
||||
<remarks>
|
||||
No useful remarks.
|
||||
</remarks>
|
||||
|
||||
<!-- fields -->
|
||||
<field name="x">
|
||||
<summary>
|
||||
Instance variable <c>x</c> represents the point's x-coordinate.
|
||||
</summary>
|
||||
</field>
|
||||
|
||||
<field name="y">
|
||||
<summary>
|
||||
Instance variable <c>y</c> represents the point's y-coordinate.
|
||||
</summary>
|
||||
</field>
|
||||
|
||||
<!-- methods -->
|
||||
<method name="#ctor">
|
||||
<summary>
|
||||
Initializes the new point to <c>(0,0)</c>.
|
||||
</summary>
|
||||
</method>
|
||||
|
||||
<method name="#ctor(System.Int32,System.Int32)">
|
||||
<summary>
|
||||
Initializes the new Point to (<paramref name="xor" />,<paramref name="yor" />).
|
||||
</summary>
|
||||
<param name="xor"><c>xor</c> is the new x-coordinate.</param>
|
||||
<param name="yor"><c>yor</c> is the new y-coordinate.</param>
|
||||
</method>
|
||||
|
||||
<method name="Move(System.Int32,System.Int32)">
|
||||
<summary>
|
||||
This method changes the point's location to the given coordinates.
|
||||
</summary>
|
||||
<param name="xor"><c>xor</c> is the new x-coordinate.</param>
|
||||
<param name="yor"><c>yor</c> is the new y-coordinate.</param>
|
||||
<seealso cref="Translate(System.Int32,System.Int32)" />
|
||||
</method>
|
||||
|
||||
<method name="Translate(System.Int32,System.Int32)">
|
||||
<summary>This method changes the point's location by the given x- and y-offsets.</summary>
|
||||
<remarks>
|
||||
<example lang="C#">
|
||||
A C# example:
|
||||
<code>
|
||||
Point p = new Point(3, 5);
|
||||
p.Translate(-1, 3);
|
||||
</code>
|
||||
This code results in <c>p</c> having the value (2,8).
|
||||
</example>
|
||||
</remarks>
|
||||
<param name="xor"><c>xor</c> is the relative x-offset.</param>
|
||||
<param name="yor"><c>yor</c> is the relative y-offset.</param>
|
||||
<seealso cref="Move(System.Int32,System.Int32)" />
|
||||
</method>
|
||||
|
||||
<method name="Equals(System.Object)">
|
||||
<summary>This method determines whether two points have the same location.</summary>
|
||||
<param name="o"><c>o</c> is the object to be compared to the current object.</param>
|
||||
<returns>True if the Points have the same location and they have the exact same
|
||||
type; otherwise, false.</returns>
|
||||
<seealso cref="op_Equality(Graphics.Point,Graphics.Point)" />
|
||||
<seealso cref="op_Inequality(Graphics.Point,Graphics.Point" />
|
||||
</method>
|
||||
|
||||
<method name="ToString">
|
||||
<summary>Report a point's location as a string.</summary>
|
||||
<returns>A string representing a point's location, in the form (x,y), without any
|
||||
leading, trailing, or embedded whitespace.</returns>
|
||||
</method>
|
||||
|
||||
<method name="op_Equality(Graphics.Point,Graphics.Point)">
|
||||
<summary>This operator determines whether two points have the same location.</summary>
|
||||
<param name="p1"><c>p1</c> is the first Point to be compared.</param>
|
||||
<param name="p2"><c>p2</c> is the second Point to be compared.</param>
|
||||
<returns>True if the points have the same location and they have the exact same
|
||||
type; otherwise, false.</returns>
|
||||
<seealso cref="Equals(System.Object)" />
|
||||
<seealso cref="op_Inequality(Graphics.Point,Graphics.Point)" />
|
||||
</method>
|
||||
|
||||
<method name="op_Inequality(Graphics.Point,Graphics.Point)">
|
||||
<summary>This operator determines whether two points have the same location.</summary>
|
||||
<param name="p1"><c>p1</c> is the first Point to be compared.</param>
|
||||
<param name="p2"><c>p2</c> is the second Point to be compared.</param>
|
||||
<returns>True if the points do not have the same location and they have the exact same
|
||||
type; otherwise, false.</returns>
|
||||
<seealso cref="Equals(System.Object)" />
|
||||
<seealso cref="op_Equality(Graphics.Point,Graphics.Point)" />
|
||||
</method>
|
||||
|
||||
<method name="Main">
|
||||
<summary>
|
||||
This is the entry point of the Point class testing program.
|
||||
</summary>
|
||||
<remarks>
|
||||
<para>This program tests each method and operator, and is intended to be run after
|
||||
any non-trivial maintenance has been performed on the Point class.</para>
|
||||
</remarks>
|
||||
</method>
|
||||
|
||||
<!-- properties -->
|
||||
<property name="X">
|
||||
<value>Property <c>X</c> represents the point's x-coordinate.</value>
|
||||
</property>
|
||||
|
||||
<property name="Y">
|
||||
<value>Property <c>y</c> represents the point's y-coordinate.</value>
|
||||
</property>
|
||||
</type>
|
||||
</doc>
|
||||
</pre>
|
||||
|
||||
@@ -0,0 +1,55 @@
|
||||
* JIT Compiler
|
||||
|
||||
<a
|
||||
href="http://cui.unige.ch/OSG/publications/OO-articles/TechnicalReports/98/efficient.pdf">
|
||||
Efficient Type Inclusion Tests: Jahn Vitek, R. Nigel Horspool, Andres
|
||||
Krall</a>
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/rd/2822939%2C410249%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/20094/http%253AzSzzSzwww.math.tau.ac.ilzSz%257EguyzSzjava-optzSzssa.pdf/cytron91efficiently.pdf">
|
||||
Efficiently Computing Static Single Assignment Form and the Control
|
||||
Dependence Graph: Ron Cytron, Jeanne Ferrante</a>
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/rd/14269422%2C217684%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/9476/http%253AzSzzSzwww.cs.ucsb.eduzSzconferenceszSzjava98zSzpaperszSzcacao.pdf/krall98monitors.pdf">
|
||||
Monitors and Exceptions - How to implement Java efficiently: Andreas Krall,
|
||||
Mark Probst</a>
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/rd/78588775%2C217642%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/9476/http%253AzSzzSzwww.complang.tuwien.ac.atzSzandizSzpact_98.pdf/krall98efficient.pdf">
|
||||
Efficient JavaVM Just-in-Time Compilation: Andreas Krall</a>
|
||||
|
||||
<a
|
||||
href="http://www.complang.tuwien.ac.at/andi/scicom_01.ps">Java for
|
||||
Large-Scale Scientific Computations: Andreas Krall, Phillip Thomsich</a>
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/rd/62076894%2C117522%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/642/ftp%253AzSzzSzftp.cs.princeton.eduzSzpubzSzlcczSzcontribzSziburg.pdf/fraser92engineering.pdf">
|
||||
Engineering Simple, Efficient Code Generator Generator: Christopher
|
||||
W. Fraser, David R. Hanson, Todd A. Proebsting</a>
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/rd/8408515%2C54698%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/815/http%253AzSzzSzcuiwww.unige.chzSzOSGzSzpeoplezSzjvitekzSzResourceszSzArchivezSzProebsting.pdf/proebsting92code.pdf">
|
||||
Code Generation Techniques: Todd Alan Proebsting</a>
|
||||
|
||||
* Register Allocation
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/rd/28309937%2C283402%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/12458/http%253AzSzzSzwww.pdos.lcs.mit.eduzSzpaperszSztoplas-linearscan.pdf/poletto99linear.pdf">
|
||||
Linear Scan Register Allocation: Massimiliano Poletto, Vivek Sarkar</a>
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/rd/19916683%2C91122%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/468/http%253AzSzzSzwww.eecs.harvard.eduzSzhubezSzpaperszSzpldi98-binpack.pdf/traub98quality.pdf">
|
||||
Quality and Speed in Linear-scan Register Allocation: Omri Traub, Glenn
|
||||
Holloway, Michael D. Smith</a>
|
||||
|
||||
* Interpreter
|
||||
|
||||
<a
|
||||
href="http://citeseer.nj.nec.com/rd/62076894%2C470069%2C1%2C0.25%2CDownload/http%253A%252F%252Fciteseer.nj.nec.com/cache/papers/cs/24640/http%253AzSzzSzwww.complang.tuwien.ac.atzSzpaperszSzertlzPz01.pdf/ertl01vmgen.pdf">
|
||||
vmgen-A Generator of Efficient Virtual Machine Interpreters: M. Anton
|
||||
Ertl, David Gregg, Andreas Krall, Bernd Paysan</a>
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,293 @@
|
||||
* Updates
|
||||
|
||||
<b>Sep 20, 2001:</b> Microsoft has just announced some changes
|
||||
to passport that are rather interesting. This document
|
||||
reflects the Passport system without taking into account the
|
||||
new changes.
|
||||
|
||||
Read about it <a href="http://www.microsoft.com/presspass/features/2001/sep01/09-20passport.asp">here</a>.
|
||||
|
||||
For an analysis of security problems with passport, check <a
|
||||
href="http://avirubin.com/passport.html">http://avirubin.com/passport.html</a>.
|
||||
The bottom line is that you should not put any sensitive
|
||||
information on passport.
|
||||
|
||||
I have received many comments from people, and I have updated
|
||||
the page accordingly. From removing incorrect statements, to
|
||||
fixing typos, to include mentions to other software pieces.
|
||||
|
||||
I also corrected my statement about IIS and a trojan horse, I
|
||||
should read a more educated press in the future. My apologies
|
||||
to Microsoft and its employees on this particular topic. IIS
|
||||
did not have a trojan horse built in.
|
||||
|
||||
* Microsoft Hailstorm and Passport
|
||||
|
||||
Microsoft Passport is a centralized database hosted by
|
||||
Microsoft that enhances the consumer experience with the Web
|
||||
by providing a single logon system that they can use across a
|
||||
number of participant web sites.
|
||||
|
||||
As you might know by now from our extensive <a
|
||||
href="faq.html">FAQ</a>, the Mono project has nothing to do
|
||||
with Microsoft Hailstorm or <a
|
||||
href="http://www.passport.com">Microsoft Passport.</a>
|
||||
|
||||
Still a lot of people have asked us our opinion on them.
|
||||
|
||||
** Passport
|
||||
|
||||
Passport is important not because of it being a breakthrough
|
||||
technologically speaking, but because the company is in a
|
||||
position to drive most people toward being suscribers of it.
|
||||
|
||||
At the time of this writing passport is required to use the
|
||||
free mail service <a href="http://www.hotmail.com">Hotmail</a>
|
||||
to get customized support for the <a
|
||||
href="http://www.msn.com">MSN portal</a>, <a
|
||||
href="http://msdn.microsoft.com">Microsoft Developers
|
||||
Network</a> and according to the original announcement from
|
||||
Microsoft <a href="http://www.americanexpress.com">American
|
||||
Express</a> and <a href="http://www.ebay.com">EBay</a> will be
|
||||
adopting it.
|
||||
|
||||
There is already a <a
|
||||
href="http://www.passport.com/Directory/Default.asp?PPDir=C&lc=1033">Large
|
||||
list</a> of participating sites.
|
||||
|
||||
There are many current users of it and Microsoft will be
|
||||
driving more users towards Passport as it <a
|
||||
href="http://news.cnet.com/news/0-1003-200-6343275.html">integrates
|
||||
it</a> in their upcoming release of Windows.
|
||||
|
||||
Microsoft has also <a
|
||||
href="http://www.passport.com/Business/JoinPassportNetwork.asp?lc=1033">developed
|
||||
a toolkit</a> to enable current web merchants to integrate
|
||||
their services with passport.
|
||||
|
||||
To the end user, there is a clear benefit: they only have to
|
||||
log into a single network and not remember multiple passwords
|
||||
across sites on the internet. Companies that adopt passport
|
||||
will have a competition advantage over those that dont.
|
||||
Microsoft lists a list of <a
|
||||
href="http://www.passport.com/Business/Default.asp?lc=1033">benefits</a>
|
||||
to companies.
|
||||
|
||||
|
||||
** The problems of Passport
|
||||
|
||||
There are a number of concerns that different groups have over
|
||||
Passport. Sometimes I have some, sometimes I do not. But
|
||||
overall, consumers and businesses can have better solutions.
|
||||
|
||||
<ul>
|
||||
* <b>Single Point of Failure:</b> As more services and
|
||||
components depend on remote servers, functionality can
|
||||
grind to a halt if there is a failure on the
|
||||
centralized Passport system.
|
||||
|
||||
Such a failure was predicted, and we recently <a
|
||||
href="http://news.cnet.com/news/0-1005-200-6473003.html">witnessed</a>
|
||||
got a lot of people worried.
|
||||
|
||||
The outgage lasted for seven days. Think what this
|
||||
could do to your business.
|
||||
|
||||
* <b>Trust:</b> Not everyone trusts Microsoft to keep
|
||||
their information confidential. Concerns are not only
|
||||
at the corporate level policy, but also the fact that
|
||||
the source code for Microsoft products is not
|
||||
available, means that trojans or worms could be built
|
||||
into the products by malicious engineers.
|
||||
|
||||
* <b>Security:</b> With a centralized system like
|
||||
Passport, imagine the repercussions of a malicious
|
||||
hacker gaining access to the Passport database.
|
||||
Personal information and credit card information about
|
||||
almost everyone using a computer could be stored there.
|
||||
|
||||
Hackers have already <a
|
||||
href="http://slashdot.org/articles/00/10/27/1147248.shtml">broken
|
||||
into Microsoft</a> in the past. And the company was
|
||||
unable to figure out for how long their systems had
|
||||
been hacked.
|
||||
|
||||
Security holes have been found in <a
|
||||
href="http://slashdot.org/articles/00/04/14/0619206.shtml">IIS
|
||||
in the past.</a> If all the world's data is stored on
|
||||
a central location, when a single security hole is
|
||||
detected, it would allow an intruder to install a
|
||||
backdoor within seconds into the corporate network
|
||||
without people ever noticing.
|
||||
|
||||
Microsoft itself has been recently hit by worms,
|
||||
imagine if all your business depended on a single
|
||||
provider for providing all or your authentication
|
||||
needs
|
||||
</ul>
|
||||
|
||||
Microsoft might or might not realize this. The idea behind
|
||||
Passport is indeed a good one (I can start to get rid of my
|
||||
file that keeps track of the 30 logins and passwords or so
|
||||
that I use across the various services on the net myself).
|
||||
|
||||
** Alternatives to Microsoft Passport
|
||||
|
||||
An alternative to Microsoft Passport needs to take the above
|
||||
problems into consideration. Any solution of the form `We
|
||||
will just have a competing offering' will not work.
|
||||
|
||||
The system thus has to be:
|
||||
|
||||
<ul>
|
||||
* <b>Distributed:</b> The entire authentication
|
||||
system should not create an internet `blackout' in the
|
||||
case of failure.
|
||||
|
||||
A distributed system using different software
|
||||
platforms and different vendors would be more
|
||||
resistent to an attack, as holes in a particular
|
||||
implementation of the server software would not affect
|
||||
every person at the same time.
|
||||
|
||||
A security hole attack might not even be relevant to
|
||||
other software vendors software.
|
||||
|
||||
* <b>Allow for multiple registrars:</b> Users should
|
||||
be able to choose a registrar (their banks, local
|
||||
phone company, service provider, Swiss bank, or any
|
||||
other entity they trust.
|
||||
|
||||
* <b>Mandate good security measures:</b> As a
|
||||
principle, only Open Source software should be used
|
||||
for servers in the registrar, and they should conform
|
||||
to a standard set of tools and software that can be
|
||||
examined by third parties.
|
||||
</ul>
|
||||
|
||||
An implementation of this protocol could use the DNS or a
|
||||
DNS-like setup to distribute the information of users with the
|
||||
possibility of replicating and caching public information
|
||||
about the user.
|
||||
|
||||
For instant messaging (another piece of the Hailstorm bit),
|
||||
you want to use a non-centralized system like Sun's <a
|
||||
href="http://www.jxta.org">JXTA</a>. Some people mailed me to
|
||||
mention Jabber as a messaging platform and other people
|
||||
pointed out to the <a
|
||||
href="http://java.sun.com/products/jms/">Java Message
|
||||
Service</a>. The JMS does support a number of very
|
||||
interesting features that are worth researching.
|
||||
|
||||
It could also just use the user e-mail address as the `key' to
|
||||
choose the registrar (msn.com, hotmail.com -> passport.com;
|
||||
aol.com -> aol.passport.com; you get the idea).
|
||||
|
||||
The <a
|
||||
href="http://www.soapware.org/xmlStorageSystem">xmlStorage</a>
|
||||
idea from <a href="http://www.scripting.com">Dave Winer</a>
|
||||
could be used to store the information.
|
||||
|
||||
A toolkit for various popular web servers could be provided,
|
||||
authenticated and should be open sourced (for those of you who
|
||||
think that a binary program would give more security and would
|
||||
prevent people from tampering: you are wrong. You can always
|
||||
use a proxy system that "behaves" like the binary, and passes
|
||||
information back and forth from the real program, and snoops
|
||||
in-transit information).
|
||||
|
||||
Good cryptographers need to be involved in this problem to
|
||||
figure out the details and the possible insecure pieces of a
|
||||
proposal like this.
|
||||
|
||||
** Implementation: In short
|
||||
|
||||
To keep it short: <b>DNS, JXTA, xmlStorage.</b>
|
||||
|
||||
|
||||
** Deploying it
|
||||
|
||||
The implementation of such a system should be a pretty
|
||||
straightforward task once security cryptographers have
|
||||
designed such a beast.
|
||||
|
||||
The major problems are:
|
||||
|
||||
<ul>
|
||||
* <b>People might just not care:</b> In a poll to US
|
||||
citizens a couple of decades ago, it was found that
|
||||
most people did not care about the rights they were
|
||||
given by the Bill of Rights, which lead to a number of
|
||||
laws to be passed in the US that eliminated most of
|
||||
the rights people had.
|
||||
|
||||
* <b>The industry will move way too slow:</b>
|
||||
Microsoft's implementation is out in the open now: it
|
||||
is being deployed, and soon it will be insinuated to
|
||||
many, many users. The industry needs to get together
|
||||
soon if they care about this issue.
|
||||
|
||||
By the time the industry reacts, it might be too
|
||||
late.
|
||||
</ul>
|
||||
|
||||
** Passport and Mono
|
||||
|
||||
The .NET class libraries include a Passport class that
|
||||
applications might use to authenticate with Passport. Since
|
||||
we do not have information at this point on the exact protocol
|
||||
of Passport, it is not even feasible to implement it.
|
||||
|
||||
If at some point the information is disclosed, it could be
|
||||
implemented.
|
||||
|
||||
If a competing system to Passport existed, we could probably
|
||||
hide all the authentication information to use a number of
|
||||
different passport-like systems.
|
||||
|
||||
If a user does not want to use Passport at all, he could
|
||||
always turn it off (or completely remove the class from the
|
||||
library). After all, this is free software.
|
||||
|
||||
Currently, we are too far from the point where this is a real
|
||||
issue.
|
||||
|
||||
** Passport and endangering Open Source.
|
||||
|
||||
A few people have said: `Mono will allow Passport to be
|
||||
available for Linux and that is bad'. This is plain
|
||||
misinformation.
|
||||
|
||||
Currently, you can obtain Passport for Linux from Microsoft
|
||||
itself and deploy it today on your Web server. Mono does not
|
||||
even enter the picture here. Go to passport.com and download
|
||||
the toolkit and you will see with your own eyes that passport
|
||||
is <B>already</b> available for Linux.
|
||||
|
||||
** Disclaimer
|
||||
|
||||
This is just a group of personal thoughts of mine that I have
|
||||
placed here because I get asked this question a lot lately.
|
||||
The views of this page are not a statement from my employer
|
||||
(Ximian, Inc).
|
||||
|
||||
This is not part of Mono. We are not trying to deal with this
|
||||
problem.
|
||||
|
||||
Nat Friedman (Ximian's co-founder) has his own ideas on how a
|
||||
competing system to Passport could be designed, but I will let
|
||||
<a href="http://www.nat.org/">him</a> post his own story.
|
||||
|
||||
** Other Passport Comments
|
||||
|
||||
An interesting study on the security of passport is available at: <a
|
||||
href="http://avirubin.com/passport.html">http://avirubin.com/passport.html</a>
|
||||
|
||||
** Other Alternatives
|
||||
|
||||
Some people have pointed out <a
|
||||
href="http://www.xns.org">XNS</a>
|
||||
|
||||
Send comments to me: Miguel de Icaza (<a
|
||||
href="mailto:[email protected]">[email protected]</a>)
|
||||
|
||||
@@ -0,0 +1,14 @@
|
||||
** Microsoft and GNU and Linux.
|
||||
|
||||
Q: Does this mean that Microsoft is better than Linux?
|
||||
|
||||
A: Many of us are working on <a
|
||||
href="http://www.gnu.org/philosophy/free-sw.html">free software<a>
|
||||
and want to have an <a href="http://www.opensource.org">open
|
||||
source</a> environment that we can change, modify, improve, learn
|
||||
from, and share with others. Some of us also think that this will
|
||||
lead on the long run to better software: more efficient, faster,
|
||||
more robust and more.
|
||||
|
||||
We are willing to take good ideas from any source they come from.
|
||||
|
||||
@@ -0,0 +1,63 @@
|
||||
* How to port Mono to your preferred architecture
|
||||
|
||||
** Endian, 64 bits and unaligned access issues
|
||||
|
||||
The first thing to do is to check that the metadata handling
|
||||
library works on your target processor. You may use the disassembler
|
||||
on simple programs and check that you get sensible results
|
||||
(assuming it compiles at all on your system:-).
|
||||
|
||||
The main issue is to write macros that read unaligned
|
||||
little endian shorts/ints/longs/float/doubles: look into
|
||||
mono/metadata/endian.h. There may be other spots in the code that are
|
||||
unsafe at reading/writing to some datatypes that require special
|
||||
alignment, but there should be few such issues and they need to be fixed.
|
||||
|
||||
Once this stuff is sorted out, you should be able to run the interpreter
|
||||
on simple programs that don't require delegates, P/Invoke functions etc..
|
||||
|
||||
** Generating assembly bytecodes for the target processor
|
||||
|
||||
Next, you need to provide the support code for generating assembly bytecode
|
||||
for your target platform (in mono/arch/{ppc,sparc,alpha,*}).
|
||||
The code should be more or less like the code in x86-codegen.h:
|
||||
macros that produce fast in-line code. You don't need to provide
|
||||
code to create every possible code, at first, just the code to
|
||||
create trampolines and execute them is fine (you'll need to research
|
||||
how the call convention works on your platform): that would be, for
|
||||
example, the prolog and epilog code in a function, code to pass function
|
||||
parameters and deal with the return value and so on.
|
||||
|
||||
libffi in gcc or the xptcall sources in mozilla may be helpful to
|
||||
understand how the calling convention works, if you can't find a specification.
|
||||
You'd need a processor manual to know how to create the assembly binary data.
|
||||
This requires a lot of reading if you're not familiar with the assembly for your
|
||||
target platform. Manuals for many processors are available as PDF files on the
|
||||
web site of the respective vendors. Note that some processors require you to
|
||||
flush the I-cache before executing the code: have a look at how the same thing is
|
||||
done in GNU lightning.
|
||||
|
||||
** Getting the interpreter to work
|
||||
|
||||
Once you can generate binary code, you can start working on a
|
||||
mono_create_trampoline() function for your platform: this function will receive
|
||||
a MonoMethod that describes the arguments and the return type of a C function
|
||||
and will create the code to call such function. When this function is complete
|
||||
you'll be able to run more sample programs, that use System.IO, P/Invoke
|
||||
functions etc.
|
||||
|
||||
To support delegates you'll need to write a mono_create_method_pointer()
|
||||
function that creates a native function: this can be used to call the
|
||||
method using the runtime's calling convention (it's basically the reverse
|
||||
of mono_create_trampoline()).
|
||||
|
||||
** The final step: porting the JIT
|
||||
|
||||
At this point you'd need to have a more complete code generation header file
|
||||
and you can start writing the machine description file for the monoburg
|
||||
system. This code (jit/tesjit.c) will require some machine specific tweaks,
|
||||
but hopefully all you have to do is create the grammar that emit assembly
|
||||
code from the IR tree. Work is at the early stages also for x86 on this stuff
|
||||
as we are still testing various solutions: you'd want to read about burg-like
|
||||
code-generator generators (the LCC book is a good starting point).
|
||||
|
||||
@@ -0,0 +1,173 @@
|
||||
|
||||
* The Mono Project
|
||||
|
||||
** Background.
|
||||
|
||||
The GNOME project goal was to bring missing technologies to
|
||||
Unix and make it competitive in the current market place for
|
||||
desktop applications. We also realized early on that language
|
||||
independence was important, and that is why GNOME APIs were
|
||||
coded using a standard that allowed the APIs to be easily
|
||||
wrapped for other languages. Our APIs are available to most
|
||||
programming languages on Unix (Perl, Python, Scheme, C++,
|
||||
Objective-C, Ada).
|
||||
|
||||
Later on we decided to use better methods for encapsulating
|
||||
our APIs, and we started to use CORBA to define interfaces to
|
||||
components. We complemented it with policy and a set of
|
||||
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/tech/bonobo.html">Bonobo</a>.
|
||||
Interfaces to Bonobo exist for C, Perl, Python, and
|
||||
Java.
|
||||
|
||||
CORBA is good when you define coarse interfaces, and most
|
||||
Bonobo interfaces are coarse. The only problem is that
|
||||
Bonobo/CORBA interfaces are not good for small interfaces.
|
||||
For example, an XML parsing Bonobo/CORBA component would be
|
||||
inefficient compared to a C API.
|
||||
|
||||
** Another explanation
|
||||
|
||||
I recently explained our motivations to Dave Winer, and he posted
|
||||
it <a
|
||||
href="http://scriptingnews.userland.com/stories/storyReader$1275">here</a>
|
||||
|
||||
** Microsoft's .NET
|
||||
|
||||
The Microsoft .NET initiative is confusing because it is a
|
||||
company wide effort that ranges from development tools to end
|
||||
user applications. .NET is a branding formative that
|
||||
has been applied to:
|
||||
|
||||
<ul>
|
||||
* The .NET development platform, a new platform for
|
||||
writing software.
|
||||
|
||||
* Web services.
|
||||
|
||||
* Microsoft Server Applications.
|
||||
|
||||
* New tools that use the new development platform.
|
||||
|
||||
* Hailstorm, the Passport centralized single-signon
|
||||
system that is being integrated into Windows XP.
|
||||
|
||||
</ul>
|
||||
|
||||
Mono is an implementation of the .NET development platform.
|
||||
|
||||
** The Common Language Infrastructure platform.
|
||||
|
||||
Microsoft has created a new development platform. The
|
||||
highlights of this new development platform are:
|
||||
|
||||
<ul>
|
||||
* A runtime environment that provides garbage
|
||||
collection, threading and a virtual machine
|
||||
specification (The Virtual Execution System, VES)
|
||||
|
||||
* A comprehensive class library.
|
||||
|
||||
* A new language, C#. Very similar to Java, C#
|
||||
allows programmers to use all the features available
|
||||
on the .NET runtime.
|
||||
|
||||
* A language specification that compilers can
|
||||
follow if they want to generate classes and code
|
||||
that can interoperate with other programming
|
||||
languages (The Common Language Specification: CLS)
|
||||
</ul>
|
||||
|
||||
The Common Language Infrastructure platform is similar to the
|
||||
goals we had in GNOME of giving language independence to
|
||||
programmers. It is more mature, documented, larger in scope,
|
||||
and has a consistent design.
|
||||
|
||||
Any API that is written using a CLS provider language can be
|
||||
used by any language that is a CLS consumer. Compilers
|
||||
generate code in a format called Common Intermediate Language
|
||||
(CIL) which is an intermediate representation of a compiled
|
||||
program and is easy to compile to native code or compiled
|
||||
using Just-in-Time (JIT) engines. The restrictions placed by
|
||||
the runtime on the CIL byte codes ensures that it is possible
|
||||
to do a good job at optimizing the code in a JIT compiler.
|
||||
|
||||
There is not really a lot of innovation in this platform: we
|
||||
have seen all of these concepts before, and we are all
|
||||
familiar with how these things work.
|
||||
|
||||
What makes the Common Language Infrastructure development
|
||||
platform interesting is that it is a good mix of technologies
|
||||
that have been nicely integrated.
|
||||
|
||||
The .NET development platform is essentially a new foundation
|
||||
for program development that gives Microsoft a room to grow
|
||||
for the coming years.
|
||||
|
||||
** ECMA standards.
|
||||
|
||||
Microsoft has submitted the
|
||||
specifications of C#, the runtime, the metadata and the
|
||||
other various bits of the .NET development platform to the
|
||||
<a href="http://www.ecma.ch">ECMA</a> for standarization.
|
||||
|
||||
You can get a copy of the specifications submitted to ECMA
|
||||
from: <a href="http://www.dotnetexperts.com/ecma">http://www.dotnetexperts.com/ecma</a>
|
||||
|
||||
** Mono: an Open Source Common Language Infrastructure implementation.
|
||||
|
||||
Ximian has begun work on Mono, a project that aims to bring
|
||||
the Common Language Infrastructure platform to free systems.
|
||||
|
||||
When the GNU project was launched, they picked the best
|
||||
operating system that was available out there, and they
|
||||
began to clone it: Unix.
|
||||
|
||||
The .NET development platform is a very rich, powerful, and
|
||||
well designed platform that would help improve the free
|
||||
software development platform. Just like the GNU project
|
||||
began to clone Unix sixteen years ago, we will be cloning the
|
||||
.NET development platform because it is a great platform to
|
||||
build on.
|
||||
|
||||
** What makes up Mono?
|
||||
|
||||
There are various pieces that will make up Mono:
|
||||
|
||||
<ul>
|
||||
* A C# compiler.
|
||||
|
||||
* The Virtual Execution System: that will have the
|
||||
Just-in-Time compiler, garbage collector, loader,
|
||||
threading engine.
|
||||
|
||||
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 library.
|
||||
|
||||
* Visual development tools.
|
||||
|
||||
* A CIL GCC frontend.
|
||||
</ul>
|
||||
|
||||
** Why use GNOME components?
|
||||
|
||||
GNOME is an umbrella project that consists of infrastructural
|
||||
components (GUI toolkit, XML libraries, CORBA implementation,
|
||||
printing architecture, imaging system), a desktop environment,
|
||||
and productivity applications.
|
||||
|
||||
The GNOME infrastructural components can be used to quickly
|
||||
implement various pieces of the class libraries without reinventing
|
||||
the wheel, and since all those components are licensed under
|
||||
the terms of the GNU LGPL it is a perfect fit.
|
||||
|
||||
Libart will be used to implement the Drawing.2D API; Gtk+ and
|
||||
the GNOME libraries will be used to implement the WinForms
|
||||
API and of course Glib and libxml will be used in various
|
||||
places.
|
||||
@@ -0,0 +1,46 @@
|
||||
To: [email protected], [email protected]
|
||||
Subject: July 12 snapshots.
|
||||
FCC: ~/Mail/outbox.txt
|
||||
X-Windows: Sometimes you fill a vacuum and it still sucks.
|
||||
--text follows this line--
|
||||
|
||||
Hey!
|
||||
|
||||
July 12 snapshots of class libraries, the compiler and the mono
|
||||
runtime are available.
|
||||
|
||||
New on this release:
|
||||
|
||||
* Runtime (module: mono)
|
||||
|
||||
The beginning of a simple interpreter that Paolo started
|
||||
workign on (can run really simple .NET programs).
|
||||
|
||||
Disassembler copes with more elements of the binary format and
|
||||
more tokens are decoded. Paolo is working now on moving some
|
||||
of these to the metadata library.
|
||||
|
||||
More tables are dumped.
|
||||
|
||||
* Class libraries (module: mcs/class)
|
||||
|
||||
Many new more classes are in from Joe, Vladimir, Jeff, Sean
|
||||
and yours truly.
|
||||
|
||||
Sean fixed the build process, and it is now possible to
|
||||
compile with a single command the assemblies. We will be
|
||||
revisiting this mechanism in the future to compile per-OS
|
||||
assemblies (ie, Unix, Windows, MacOS, etc).
|
||||
|
||||
* Compiler (module mcs/mcs)
|
||||
|
||||
Not much done this week, just a few fixes here and there, and
|
||||
more work to make it easy to compiler.
|
||||
|
||||
* Documentation (module: mono/doc)
|
||||
|
||||
All the changes to the web site are there for your browsing
|
||||
pleasure. We still need to integrate the status system in
|
||||
there.
|
||||
|
||||
Miguel.
|
||||
@@ -0,0 +1,43 @@
|
||||
To: [email protected]
|
||||
Subject: Sunday snapshot available.
|
||||
Gcc: mail.2001-07
|
||||
--text follows this line--
|
||||
|
||||
Hey guys,
|
||||
|
||||
I promise I will not be doing these so often once we have the CVS
|
||||
server up. In the meantime:
|
||||
|
||||
* MCS
|
||||
|
||||
Sean got the classes to compile in a single go. You
|
||||
will need CygWin (www.cygwin.org) to compile though
|
||||
(GNU make and stuff is required).
|
||||
|
||||
System.Xml.XmlReader contribution from Jason
|
||||
(WOOHHOO!!). It also contains a nice test-suite for
|
||||
his functions, and in his new code bit, his
|
||||
implementation is faster than Microsoft's
|
||||
|
||||
We now ship `jay' as part of the distribution to allow
|
||||
you to compile the compiler with the same `make'
|
||||
command. Small fixes to the parser as well were
|
||||
introduced.
|
||||
|
||||
* Mono 0.4
|
||||
|
||||
Paolo's interpreter supports call instructions and has
|
||||
the test suite program that he posted about.
|
||||
|
||||
|
||||
All documentation ships now in the mono-0.4.tar.gz
|
||||
|
||||
Notes:
|
||||
|
||||
As usual, MCS is targeted to be compiled on a Windows machine
|
||||
(you will need Cygwin).
|
||||
|
||||
Mono is targeted to be compiled on a Unix machine or a Windows
|
||||
machine running Cygwin.
|
||||
|
||||
Miguel.
|
||||
@@ -0,0 +1,156 @@
|
||||
|
||||
* Resources
|
||||
|
||||
There are a number of resources available for those of you who
|
||||
want to contribute to the Mono project. Here are a few links.
|
||||
|
||||
If you want to send suggestions for links, address them to <a
|
||||
mailto="[email protected]">[email protected]</a>.
|
||||
|
||||
** Microsoft .NET
|
||||
|
||||
The <a href="http://msdn.microsoft.com/net">Microsoft.NET site.</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>
|
||||
|
||||
** IRC
|
||||
|
||||
Various Mono contributors get together on channel #mono on
|
||||
irc.gnome.org
|
||||
|
||||
** Mono related sites.
|
||||
|
||||
Sergey's web page on Mono resources:
|
||||
|
||||
<a href="http://mono.eurosoft.od.ua">http://mono.eurosoft.od.ua</a>
|
||||
|
||||
Got Dot Net:
|
||||
|
||||
<a href="http://www.gotdotnet.com">Got Dot Net</a>
|
||||
|
||||
MonoMail:
|
||||
|
||||
<a href="http://sourceforge.net/projects/monomail/">http://sourceforge.net/projects/monomail/</a>
|
||||
|
||||
Zip classes:
|
||||
|
||||
Mike's port to .NET: <a
|
||||
href="http://www.icsharpcode.net/OpenSource/NZipLib/default.asp">NZipLib</a>
|
||||
|
||||
.NET Security:
|
||||
|
||||
A nice overview paper on the <a
|
||||
href="http://www.foundstone.com/pdf/dotnet-security-framework.pdf">.NET
|
||||
security architecture</a>.
|
||||
|
||||
** Presentations
|
||||
|
||||
Currently the <a href="Presentations/O-Reilly">O'Reilly</a>
|
||||
presentation on Mono is available. Arturo Espinosa has given
|
||||
a talk on Mono in Mexico and made <a
|
||||
href="http://construct.ximian.com/~arturo/Presentations/Mono.OLS/html">spanish
|
||||
slides</a>
|
||||
|
||||
** ECMA Documentation.
|
||||
|
||||
You can get the documentation for the ECMA specs from:
|
||||
|
||||
<ul>
|
||||
* <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>
|
||||
|
||||
|
||||
Older copies of the standard are available here:
|
||||
|
||||
<ul>
|
||||
* <a href="http://msdn.microsoft.com/net/ecma">At MSDN</a>
|
||||
* <a href="http://www.dotnetexperts.com">Dot Net Experts</a>
|
||||
* <a href="http://developer.intel.com/software/idap/ecma">Intel</a>
|
||||
* <a href="http://lightning.csse.monash.edu.au/.net/CLI">Monash University</a>
|
||||
</ul>
|
||||
|
||||
These contain specifications for the assembler, the metadata,
|
||||
byte codes supported by the CLI virtual machine, the C#
|
||||
language and the core class libraries.
|
||||
|
||||
For details on the .NET class libraries, you can
|
||||
visit the Microsoft's Developer Network:
|
||||
|
||||
<ul>
|
||||
* <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/cpref_start.asp">.NET Framework Class Library</a>
|
||||
</ul>
|
||||
|
||||
You can also get this information if you install the Beta2
|
||||
release of the .NET Framework.
|
||||
|
||||
** Discussion Groups.
|
||||
|
||||
<ul>
|
||||
|
||||
* <a href="http://www.oreillynet.com">O'Reilly
|
||||
Network</a> has a <a
|
||||
href="http://www.oreillynet.com/dotnet">section devoted to
|
||||
.NET</a>
|
||||
* <a
|
||||
href="http://msdn.microsoft.com/newsgroups">MSDN</a> also
|
||||
lists various newsgroups related to .NET</ul>
|
||||
</ul>
|
||||
|
||||
** Other .NET related projects
|
||||
|
||||
There are a number of related projects to Mono:
|
||||
|
||||
<ul>
|
||||
* <a
|
||||
href="http://www.icsharpcode.net/OpenSource/SD/default.asp">Sharp
|
||||
Develop:</a> an IDE for the C# language written in C#.
|
||||
|
||||
* <a
|
||||
href="http://janet-js.sourceforge.net/">Janet:</a>
|
||||
an implemention of ECMAScript (the standarized
|
||||
version of JavaScript) in C#
|
||||
|
||||
* <a
|
||||
href="http://xmarks.sourceforge.net/doc.html">XMarks DOC.NET:</a> For
|
||||
creating online documentation you can browse for your own classes.
|
||||
|
||||
* <a href="http://nunit.sourceforge.net">NUnit:</a> A
|
||||
testing framework for .NET classes.
|
||||
|
||||
* <a href="http://www.kaffe.org">Kaffe:</a> A popular
|
||||
Free Software JIT engine for Java.
|
||||
|
||||
* <a href="http://www.intel.com/research/mrl/orp">ORP:</a> A research
|
||||
JIT/VM/GC system from Intel.
|
||||
|
||||
* C# bindings for OpenGL and SDL are available here: <a
|
||||
href="http://csgl.sourceforge.net">http://csgl.sourceforge.net</a>
|
||||
|
||||
* <a
|
||||
href="http://www.southern-storm.com.au/portable_net.html">Portable.NET:</a>
|
||||
Another implementation of the CLI and C# compiler.
|
||||
|
||||
</ul>
|
||||
|
||||
** GNOME Documentation
|
||||
|
||||
Documnetation on GNOME, and the GNOME APIs is available from
|
||||
the <a href="http://developer.gnome.org">developer</a> site at
|
||||
GNOME:
|
||||
|
||||
<ul>
|
||||
* <a href="http://developer.gnome.org/doc/API/">GNOME
|
||||
API documentation</a>
|
||||
|
||||
* <a href="http://developer.gnome.org/doc/books">GNOME
|
||||
Online books</a>
|
||||
|
||||
* <A
|
||||
href="http://developer.gnome.org/arch/">Architecture Overview</a>
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,30 @@
|
||||
** MacOS Documentation
|
||||
|
||||
** Assembly Language Manuals online
|
||||
Intel
|
||||
MIPS
|
||||
SPARC
|
||||
|
||||
** Microsoft
|
||||
msdn.microsoft.com/net
|
||||
Research.microsoft.com
|
||||
|
||||
** Related Technologies
|
||||
|
||||
<ul>
|
||||
|
||||
* The CLI allows people to create Web Services using the SOAP
|
||||
protocol. SOAP is based on XML, XML schemas an the HTTP
|
||||
protocol.
|
||||
<ul>
|
||||
* XML specification.
|
||||
* XML Namespaces.
|
||||
* XML Schemas.
|
||||
* SOAP Specification.
|
||||
</ul>
|
||||
</ul>
|
||||
|
||||
** Compiler Information
|
||||
GCC
|
||||
GCC Sample front-end tutorial
|
||||
|
||||
@@ -0,0 +1,12 @@
|
||||
* Roadmap
|
||||
|
||||
We are working on the following three projects at Ximian:
|
||||
|
||||
The C# Compiler (mcs/mcs)
|
||||
|
||||
A .NET compatible Class Library (mcs/class)
|
||||
|
||||
The JIT/interpreter (mono)
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,167 @@
|
||||
* The Mono runtime
|
||||
|
||||
The Mono runtime implements a JIT engine for the CIL virtual
|
||||
machine (as well as a byte code interpreter, this is to
|
||||
quickly port it to new systems), the class loader, the garbage
|
||||
collector, threading system and metadata access libraries.
|
||||
|
||||
We currently have two runtimes:
|
||||
|
||||
<ul>
|
||||
* <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>
|
||||
|
||||
Currently both runtimes are missing garbage collection. We
|
||||
are planning on using the ORP GC engine and deploy it by
|
||||
middle January.
|
||||
|
||||
* COM and XPCOM
|
||||
|
||||
We plan on adding support for XPCOM on Unix and COM on Microsoft
|
||||
Windows later in our development process.
|
||||
|
||||
** Executing MSIL/CIL images
|
||||
|
||||
The code will load an executable and map the references to
|
||||
external assemblies to our own version of the assemblies on
|
||||
Linux.
|
||||
|
||||
Our roadmap looks like this, this has been updated as of
|
||||
<b>Dec 18, 2001</b>:
|
||||
|
||||
<ul>
|
||||
|
||||
* Milestone 1: <b>Done</b> Fully read and parse all CIL byte-codes
|
||||
and metadata tokens (ie, a disassembler).
|
||||
|
||||
* Milestone 2: <b>Done</b> Complete an interpreter for CIL byte
|
||||
codes. This interpreter can be used temporarly to
|
||||
run CIL byte code on a system where no JIT is
|
||||
available.
|
||||
|
||||
* Milestone 3: <b>Done</b>Define an <i>lburg</i>-like
|
||||
instruction selector for the JITer for Intel.
|
||||
|
||||
* Milestone 4: <b>Done</b> Implement JITer. This is where our
|
||||
current efforts are focused on, the JITer currently runs
|
||||
all of the code we have tested on it. The major limitation
|
||||
is that our class libraries are not complete, and hence not
|
||||
every application can be ran.
|
||||
|
||||
* Milestone 5: Port of the JITer to non IA32 systems.
|
||||
</ul>
|
||||
|
||||
A setup similar to the Kaffe JIT engine will be used to
|
||||
layout the code to support non-IA32 architectures. Our work
|
||||
will be focused on getting a IA32 version running first.
|
||||
|
||||
The JIT engine should work on Linux and Win32, although you
|
||||
will need to install the CygWin32 development tools to get a
|
||||
Unix-like compilation environment (mostly we use GNU make in
|
||||
a few of the makefiles).
|
||||
|
||||
** JIT Engine (<b>updated, March 26th, 2002</b>)
|
||||
|
||||
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.
|
||||
|
||||
There are a couple of books that deal with this technique: "A
|
||||
Retargetable C Compiler" and "Advanced Compiler Design and
|
||||
Implementation" are good references. You can also get a
|
||||
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>.
|
||||
|
||||
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>
|
||||
|
||||
|
||||
* <a href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/iburg.pdf&pub=ACM">Engineering efficient code generators using tree matching and dynamic programming.</a>
|
||||
|
||||
</ul>
|
||||
|
||||
** Future plans
|
||||
|
||||
We are evaluating the future directions for the JIT engine:
|
||||
both from our needs (optimizations like inlining, better register allocation,
|
||||
instruction scheduling, and porting to other CPUs).
|
||||
|
||||
We have not yet decided how we will evolve the JIT engine. We
|
||||
might just upgrade our current architecture, and provide optimizations as
|
||||
an extra layer.
|
||||
|
||||
** Garbage Collection
|
||||
|
||||
Currently we are using the Boehm conservative GC. Although our plans
|
||||
are to move to the Intel ORP GC engine, our plans on a next generation
|
||||
dual-JIT engine have to be taken into account.
|
||||
|
||||
We will be using the Intel ORP GC engine as it provides a precise
|
||||
garbage collector engine, similar to what is available on the
|
||||
.NET environment.
|
||||
|
||||
Although using a conservative garbage collector like Bohem's
|
||||
would work, all the type information is available at runtime,
|
||||
so we can actually implement a better collector than a
|
||||
conservative collector.
|
||||
|
||||
<ul>
|
||||
* Garbage collection list and FAQ:<br>
|
||||
<a href="http://www.iecc.com/gclist/">http://www.iecc.com/gclist/</a>
|
||||
|
||||
* "GC points in a Threaded Environment":<br>
|
||||
<a href="http://research.sun.com/techrep/1998/abstract-70.html">
|
||||
http://research.sun.com/techrep/1998/abstract-70.html</a>
|
||||
|
||||
* "A Generational Mostly-concurrent Garbage Collector":
|
||||
<a href="http://research.sun.com/techrep/2000/abstract-88.html">
|
||||
http://research.sun.com/techrep/2000/abstract-88.html</a>
|
||||
|
||||
* Details on The Microsoft .NET Garbage Collection Implementation:<br>
|
||||
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag00/html/GCI.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag00/html/GCI.asp</a>
|
||||
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag00/html/GCI2.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag00/html/GCI2.asp</a>
|
||||
</ul>
|
||||
|
||||
** IO and threading
|
||||
|
||||
The ECMA runtime and the .NET runtime assume an IO model and a
|
||||
threading model that is very similar to the Win32 API.
|
||||
|
||||
Dick Porter has been working on the Mono abstraction layer
|
||||
that allows our runtime to execute code that depend on this
|
||||
behaviour.
|
||||
|
||||
** Useful links
|
||||
|
||||
Paolo Molaro found a few interesting links:
|
||||
|
||||
<ul>
|
||||
* On compilation of stack-based languages:<br>
|
||||
<a href="http://www.complang.tuwien.ac.at/projects/rafts.html">
|
||||
http://www.complang.tuwien.ac.at/projects/rafts.html</a>
|
||||
|
||||
* A paper on fast JIT compilation of a stack-based language:<br>
|
||||
<a href="http://www.research.microsoft.com/~cwfraser/pldi99codegen.pdf">
|
||||
http://www.research.microsoft.com/~cwfraser/pldi99codegen.pdf</a>
|
||||
|
||||
* Vmgen generates much of the code for efficient virtual machine (VM)
|
||||
interpreters from simple descriptions of the VM instructions:<br>
|
||||
<a href="http://www.complang.tuwien.ac.at/anton/vmgen/">
|
||||
http://www.complang.tuwien.ac.at/anton/vmgen</a>
|
||||
</ul>
|
||||
|
||||
** PInvoke
|
||||
|
||||
PInvoke is the mechanism we are using to wrap Unix API calls
|
||||
as well as talking to system libraries.
|
||||
|
||||
Initially we used libffi, but it was fairly slow, so we have
|
||||
reused parts of the JIT work to create efficient PInvoke trampolines.
|
||||
@@ -0,0 +1,40 @@
|
||||
* Project Status
|
||||
|
||||
|
||||
Pieces of Mono that have been implemented:
|
||||
|
||||
<ul>
|
||||
* C# compiler: The C# compiler is mostly complete, a
|
||||
few features are still missing (for a list, check the
|
||||
<a href="c-sharp.html">C# compiler</a> web page.
|
||||
|
||||
* The Mono JIT engine (<b>mono</b>. The JIT engine is
|
||||
the real
|
||||
virtual machine that we support. It is
|
||||
functionaly currently, and we are improving its speed,
|
||||
and making it feature complete.
|
||||
|
||||
* A CIL bytecode interpreter (<b>mint</b>). This
|
||||
currently can be used to run most .NET programs
|
||||
(modulo the fact that our class libraries are not
|
||||
complete enough).
|
||||
|
||||
<b>mint</b> can currently run the Mono C# compiler and
|
||||
the compiler generates valid code.
|
||||
|
||||
We use <b>mint</b> as a reference implementation of
|
||||
the runtime environment and to quickly support
|
||||
non-Intel platforms.
|
||||
|
||||
* Metadata library: Can currently parse
|
||||
and load information from .NET modules (executables
|
||||
and DLL files).
|
||||
|
||||
* Disassembler: Can disassemble .NET modules. Still
|
||||
lacking exception handling as well as useful debugging
|
||||
tools (hex dumping, token dumping).
|
||||
|
||||
* Class Libraries: You can check the current status in the
|
||||
<a href="class-status.html">Class Status page</a>.
|
||||
</ul>
|
||||
|
||||
@@ -0,0 +1,46 @@
|
||||
* Testing
|
||||
|
||||
Testing is an important part of the Mono project: every one of its
|
||||
three major components has a test suite tailored for its needs. This
|
||||
is very helpful, because in the course of developing the software it
|
||||
is very common to introduce bugs in existing code. A test suite
|
||||
helps us fix the bugs as soon as they are introduced.
|
||||
|
||||
** Class Library Tests
|
||||
|
||||
All classes in Mono libraries should have comprehensive unit test
|
||||
suites to go with them. Unit testing is a software engineering
|
||||
methodology that makes it easier to build correct code. Every
|
||||
method in every class should have a set of tests to verify
|
||||
that they work correctly. Mono also needs a testing framework
|
||||
to make it easy to write and run lots of tests.
|
||||
|
||||
Try <a href="http://nunit.sourceforge.net">NUnit</a>
|
||||
|
||||
Why do unit testing? It becomes simple to run automated tests
|
||||
for the whole library. Unit tests are a safety net - you can
|
||||
change part of the code and verify that you haven't broken
|
||||
anything. Ideally, tests are written before the actual library
|
||||
code itself. And every time a bug is discovered, a test should
|
||||
be written to demonstrate the bug and its fix. Then, if
|
||||
you ever reintroduce the bug, you will know immediately. For
|
||||
more info, read <a
|
||||
href="http://junit.sourceforge.net/doc/testinfected/testing.htm">
|
||||
JUnit Test Infected: Programmers Love Writing Tests</a>.
|
||||
|
||||
|
||||
** Getting Started
|
||||
|
||||
We welcome all contributions to the Class Libary Test Suite.
|
||||
|
||||
There is information to help you get started in CVS at
|
||||
mcs/class/doc/NUnitGuidelines. Once you have written your test, please
|
||||
post it to <a href="mailing-lists.html">mono-list</a>.
|
||||
|
||||
Someone will make sure to add the file or apply the patch as
|
||||
appropriate. If you plan to be an on-going contributor and
|
||||
would like to get cvs account, email <a href="mailto:[email protected]">miguel</a>.
|
||||
|
||||
Normally, after you send a couple of well-written new files
|
||||
and/or patches to the list, you will be given cvs access.
|
||||
|
||||
@@ -0,0 +1,6 @@
|
||||
* Thanks
|
||||
|
||||
We would like to thank Tim O'Reilly, Brian Jepson and Nathan
|
||||
Torkington for their help.
|
||||
|
||||
Dave Winer for provided interesting comments and a to read.
|
||||
@@ -0,0 +1,67 @@
|
||||
* Tools
|
||||
|
||||
We need a number of tools to make people productive using a
|
||||
Mono-based solution. Some of these tools can be developed on
|
||||
Windows before Mono is fully finished.
|
||||
|
||||
All of these tools should be written using C#.
|
||||
|
||||
For the tools that are typically command line tools: Try to
|
||||
write these as components that could load their input from
|
||||
streams or collections of streams, and implement the command
|
||||
line tools as wrappers around those classes.
|
||||
|
||||
For example, we will be making the C# compiler a component
|
||||
that could be reused by applications that might have a use for
|
||||
the various bits of the compiler (either to embed the
|
||||
compiler, or reuse the code generator part of it).
|
||||
|
||||
This is important so that these components (compiler,
|
||||
assembler, linker, etc) can be integrated later into the
|
||||
visual development environment (hopefully with the help of the
|
||||
SharpDevelop hackers).
|
||||
|
||||
TODO=ilasm,IL Assembler
|
||||
** IL Assembler.
|
||||
|
||||
This assembler should basically take as input a file
|
||||
containing IL bytecodes as specified in the `Partition II' of
|
||||
the ECMA spec, and produce a binary file.
|
||||
|
||||
TODO=al,Assembly Linker
|
||||
** Assembly Linker.
|
||||
|
||||
This tool is used to construct assemblies, which are basically
|
||||
deployment units for CLI executables.
|
||||
|
||||
TODO=debugger,Debugger
|
||||
** Debugger
|
||||
|
||||
We will need a debugging API to debug CLI applications and
|
||||
then a debugger component that can be used in an IDE
|
||||
environment.
|
||||
|
||||
TODO=ide,Integrated Development Environment
|
||||
** Integrated Development Environment
|
||||
|
||||
There is already a project to create a C# development
|
||||
environment: <a
|
||||
href="http://www.icsharpcode.net/OpenSource/SD/default.asp">SharpDevelop</a>.
|
||||
People should work with the SharpDevelop hackers to produce a
|
||||
unified development environment.
|
||||
|
||||
Please work with the SharpDevelop hackers to build a good IDE.
|
||||
We will work on creating an embedable compiler component and
|
||||
an embeddable debugger component that can be used withing
|
||||
SharpDevelop
|
||||
|
||||
TODO=hbrowser,Help Browser
|
||||
** Help Browser
|
||||
|
||||
We need a good help browser that can be used to browse
|
||||
documentation. Ideally this help browser can accept as input
|
||||
XML Docbook input and an assorted set of file formats
|
||||
(Microsoft Help, Unix manual pages, Unix Info pages)
|
||||
|
||||
Look at the GNOME DevHelp for a good set of ideas on how to
|
||||
implement this.
|
||||
@@ -0,0 +1,2 @@
|
||||
*.src
|
||||
*.html
|
||||
@@ -0,0 +1,31 @@
|
||||
0,Home,index.html,index.src
|
||||
1,FAQ,faq.html,faq.src
|
||||
0,Mono,rationale.html,rationale.src
|
||||
1,Runtime,runtime.html,runtime.src
|
||||
1,Classes,class-library.html,class-library.src
|
||||
1,Gtk#,http://gtk-sharp.sourceforge.net
|
||||
1,Class Status,class-status.html,class-status.src,cm/cormissing.css,cm/cormissing.js
|
||||
2,corlib,class-status-corlib.html,class-status-corlib.src,cm/cormissing.css,cm/cormissing.js
|
||||
2,System,class-status-System.html,class-status-System.src,cm/cormissing.css,cm/cormissing.js
|
||||
2,System.Xml,class-status-System.Xml.html,class-status-System.Xml.src,cm/cormissing.css,cm/cormissing.js
|
||||
2,System.Data,class-status-System.Data.html,class-status-System.Data.src,cm/cormissing.css,cm/cormissing.js
|
||||
2,System.Web,class-status-System.Web.html,class-status-System.Web.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,C# Compiler,c-sharp.html,c-sharp.src
|
||||
1,Status,status.html,status.src
|
||||
0,Download,download.html,download.src
|
||||
1,CVS access,ccvs.html,ccvs.src
|
||||
1,AnonCVS access,anoncvs.html,anoncvs.src
|
||||
0,Contributing,contributing.html,contributing.src
|
||||
1,Documentation,documentation.html,documentation.src
|
||||
1,Class Docs,classlib-doc.html,classlib-doc.src
|
||||
1,Doc format,monodoc-xml.html,monodoc-xml.src
|
||||
1,Test Suite,testing.html,testing.src
|
||||
1,Tools,tools.html,tools.src
|
||||
1,Porting,porting.html,porting.src
|
||||
0,Resources,resources.html,resources.src
|
||||
1,Mailing Lists,mailing-lists.html,mailing-lists.src
|
||||
1,Ideas,ideas.html,ideas.src
|
||||
1,Passport,passport.html,passport.src
|
||||
1,Books,books.html,books.src
|
||||
1,Papers,papers.html,papers.src
|
||||
0,Contact,contact.html,contact.src
|
||||
@@ -0,0 +1 @@
|
||||
*.html
|
||||
|
After Width: | Height: | Size: 150 B |
@@ -0,0 +1,180 @@
|
||||
.y IMG
|
||||
{
|
||||
border: 0px;
|
||||
padding: 0px;
|
||||
margin: 0px;
|
||||
margin-right: 4px;
|
||||
vertical-align: middle;
|
||||
}
|
||||
|
||||
.y, .y_,
|
||||
.n, .n_,
|
||||
.c, .c_,
|
||||
.c, .c_,
|
||||
.d, .d_,
|
||||
.en, .en_,
|
||||
.i, .i_,
|
||||
.s, .s_,
|
||||
.e, .e_,
|
||||
.f, .f_,
|
||||
.m, .m_,
|
||||
.o, .o_,
|
||||
.p, .p_,
|
||||
.r, .r_,
|
||||
.x, .x_
|
||||
{
|
||||
FONT: 10px 'Verdana';
|
||||
margin-left: 20px;
|
||||
}
|
||||
|
||||
.y_ .n,
|
||||
.y_ .n_,
|
||||
.n_ .c,
|
||||
.n_ .c_,
|
||||
.n_ .s,
|
||||
.n_ .s_,
|
||||
.n_ .d,
|
||||
.n_ .d_,
|
||||
.n_ .en,
|
||||
.n_ .en_,
|
||||
.n_ .i,
|
||||
.n_ .i_,
|
||||
.c_ .c,
|
||||
.c_ .c_,
|
||||
.c_ .e,
|
||||
.c_ .e_,
|
||||
.c_ .f,
|
||||
.c_ .f_,
|
||||
.c_ .m,
|
||||
.c_ .m_,
|
||||
.c_ .o,
|
||||
.c_ .o_,
|
||||
.c_ .p,
|
||||
.c_ .p_,
|
||||
.c_ .r,
|
||||
.c_ .r_,
|
||||
.c_ .x,
|
||||
.c_ .x_,
|
||||
.c_ .i,
|
||||
.c_ .i_,
|
||||
.d_ .c,
|
||||
.d_ .c_,
|
||||
.d_ .e,
|
||||
.d_ .e_,
|
||||
.d_ .f,
|
||||
.d_ .f_,
|
||||
.d_ .m,
|
||||
.d_ .m_,
|
||||
.d_ .o,
|
||||
.d_ .o_,
|
||||
.d_ .p,
|
||||
.d_ .p_,
|
||||
.d_ .r,
|
||||
.d_ .r_,
|
||||
.d_ .x,
|
||||
.d_ .x_,
|
||||
.en_ .c,
|
||||
.en_ .c_,
|
||||
.en_ .e,
|
||||
.en_ .e_,
|
||||
.en_ .f,
|
||||
.en_ .f_,
|
||||
.en_ .m,
|
||||
.en_ .m_,
|
||||
.en_ .o,
|
||||
.en_ .o_,
|
||||
.en_ .p,
|
||||
.en_ .p_,
|
||||
.en_ .r,
|
||||
.en_ .r_,
|
||||
.en_ .x,
|
||||
.en_ .x_,
|
||||
.i_ .c,
|
||||
.i_ .c_,
|
||||
.i_ .e,
|
||||
.i_ .e_,
|
||||
.i_ .f,
|
||||
.i_ .f_,
|
||||
.i_ .m,
|
||||
.i_ .m_,
|
||||
.i_ .o,
|
||||
.i_ .o_,
|
||||
.i_ .p,
|
||||
.i_ .p_,
|
||||
.i_ .r,
|
||||
.i_ .r_,
|
||||
.i_ .x,
|
||||
.i_ .x_,
|
||||
.i_ .i,
|
||||
.i_ .i_,
|
||||
.s_ .c,
|
||||
.s_ .c_,
|
||||
.s_ .e,
|
||||
.s_ .e_,
|
||||
.s_ .f,
|
||||
.s_ .f_,
|
||||
.s_ .m,
|
||||
.s_ .m_,
|
||||
.s_ .o,
|
||||
.s_ .o_,
|
||||
.s_ .p,
|
||||
.s_ .p_,
|
||||
.s_ .r,
|
||||
.s_ .r_,
|
||||
.s_ .x,
|
||||
.s_ .x_,
|
||||
|
||||
.e_ .r,
|
||||
.e_ .r_,
|
||||
.e_ .o,
|
||||
.e_ .o_,
|
||||
.f_ .r,
|
||||
.f_ .r_,
|
||||
.f_ .o,
|
||||
.f_ .o_,
|
||||
.m_ .r,
|
||||
.m_ .r_,
|
||||
.m_ .o,
|
||||
.m_ .o_,
|
||||
.o_ .r,
|
||||
.o_ .r_,
|
||||
.o_ .o,
|
||||
.o_ .o_,
|
||||
.p_ .r,
|
||||
.p_ .r_,
|
||||
.p_ .o,
|
||||
.p_ .o_,
|
||||
.r_ .r,
|
||||
.r_ .r_,
|
||||
.r_ .o,
|
||||
.r_ .o_,
|
||||
.x_ .r,
|
||||
.x_ .r_,
|
||||
.x_ .o,
|
||||
.x_ .o_
|
||||
{
|
||||
display: none;
|
||||
}
|
||||
|
||||
.t
|
||||
{
|
||||
cursor: pointer;
|
||||
margin-right: 8px;
|
||||
}
|
||||
|
||||
.filter
|
||||
{
|
||||
cursor: pointer;
|
||||
vertical-align: middle;
|
||||
}
|
||||
|
||||
|
||||
.st
|
||||
{
|
||||
margin-left: 20px;
|
||||
}
|
||||
|
||||
.l
|
||||
{
|
||||
cursor: pointer;
|
||||
}
|
||||
@@ -0,0 +1,396 @@
|
||||
function toggle (elt)
|
||||
{
|
||||
if (elt == null)
|
||||
return;
|
||||
|
||||
var eltLink = elt.firstChild;
|
||||
if (eltLink != null && eltLink.className == 't') // toggle
|
||||
{
|
||||
var ich = elt.className.indexOf ('_');
|
||||
if (ich < 0)
|
||||
{
|
||||
eltLink.src = 'cm/tp.gif';
|
||||
elt.className += '_';
|
||||
}
|
||||
else
|
||||
{
|
||||
eltLink.src = 'cm/tm.gif';
|
||||
elt.className = elt.className.slice (0, ich);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
function setView (elt, fView)
|
||||
{
|
||||
var eltLink = elt.firstChild;
|
||||
if (eltLink != null && eltLink.className == 't') // toggle
|
||||
{
|
||||
var ich = elt.className.indexOf ('_');
|
||||
if (ich < 0 && !fView)
|
||||
{
|
||||
eltLink.src = 'cm/tp.gif';
|
||||
elt.className += '_';
|
||||
}
|
||||
else if (ich >= 0 && fView)
|
||||
{
|
||||
eltLink.src = 'cm/tm.gif';
|
||||
elt.className = elt.className.slice (0, ich);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
function trimSrc (strSrc)
|
||||
{
|
||||
return strSrc.slice (strSrc.lastIndexOf ('/') + 1, strSrc.lastIndexOf ('.'));
|
||||
}
|
||||
|
||||
function getChildrenByTagName (elt, strTag)
|
||||
{
|
||||
strTag = strTag.toLowerCase ();
|
||||
var rgChildren = new Array ();
|
||||
var eltChild = elt.firstChild;
|
||||
while (eltChild)
|
||||
{
|
||||
if (eltChild.tagName && eltChild.tagName.toLowerCase () == strTag)
|
||||
rgChildren.push (eltChild);
|
||||
eltChild = eltChild.nextSibling;
|
||||
}
|
||||
return rgChildren;
|
||||
}
|
||||
|
||||
function viewAll (elt, dictTypes)
|
||||
{
|
||||
var fView = false;
|
||||
var rgElts = getChildrenByTagName (elt, 'DIV');
|
||||
var cElts = rgElts.length;
|
||||
if (cElts == 0)
|
||||
{
|
||||
var rgImages = getChildrenByTagName (elt, 'IMG');
|
||||
var cImages = rgImages.length;
|
||||
for (var iImage = 0; iImage < cImages; iImage++)
|
||||
{
|
||||
var image = rgImages [iImage];
|
||||
var strImage = trimSrc (rgImages [iImage].src);
|
||||
if (dictTypes [strImage])
|
||||
{
|
||||
fView = true;
|
||||
break;
|
||||
}
|
||||
}
|
||||
}
|
||||
else
|
||||
{
|
||||
var iElt;
|
||||
for (iElt = 0; iElt < cElts; iElt ++)
|
||||
fView |= viewAll (rgElts [iElt], dictTypes);
|
||||
}
|
||||
elt.style.display = fView ? '' : 'none';
|
||||
return fView;
|
||||
}
|
||||
|
||||
function getView (elt)
|
||||
{
|
||||
var eltLink = elt.firstChild;
|
||||
if (eltLink != null && eltLink.className == 't') // toggle
|
||||
{
|
||||
var ich = elt.className.indexOf ('_');
|
||||
if (ich < 0)
|
||||
return true;
|
||||
}
|
||||
return false;
|
||||
}
|
||||
|
||||
function getParentDiv (elt)
|
||||
{
|
||||
if (elt)
|
||||
{
|
||||
do
|
||||
{
|
||||
elt = elt.parentNode;
|
||||
}
|
||||
while (elt && elt.tagName != 'DIV');
|
||||
}
|
||||
|
||||
return elt;
|
||||
}
|
||||
|
||||
function getName (elt)
|
||||
{
|
||||
var rgSpans = getChildrenByTagName (elt, 'SPAN');
|
||||
for (var iSpan = 0; iSpan < rgSpans.length; iSpan ++)
|
||||
{
|
||||
var span = rgSpans [iSpan];
|
||||
if (span.className == 'l') // label
|
||||
{
|
||||
if (span.innerText)
|
||||
return span.innerText;
|
||||
else
|
||||
return span.firstChild.nodeValue;
|
||||
}
|
||||
}
|
||||
return null;
|
||||
}
|
||||
|
||||
function clickHandler (evt)
|
||||
{
|
||||
var elt;
|
||||
if (document.layers)
|
||||
elt = evt.taget;
|
||||
else if (window.event && window.event.srcElement)
|
||||
{
|
||||
elt = window.event.srcElement;
|
||||
evt = window.event;
|
||||
}
|
||||
else if (evt && evt.stopPropagation)
|
||||
elt = evt.target;
|
||||
|
||||
if (!elt.className && elt.parentNode)
|
||||
elt = elt.parentNode;
|
||||
|
||||
if (elt.className == 'l') // label
|
||||
{
|
||||
var strClass;
|
||||
var strField;
|
||||
var strNamespace;
|
||||
var strAssembly;
|
||||
|
||||
elt = getParentDiv (elt);
|
||||
var strEltClass = elt.className;
|
||||
if (strEltClass.charAt (strEltClass.length - 1) == '_')
|
||||
strEltClass = strEltClass.slice (0, strEltClass.length - 1);
|
||||
|
||||
if (strEltClass == 'x') // constructor
|
||||
{
|
||||
strField = 'ctor';
|
||||
elt = getParentDiv (elt);
|
||||
}
|
||||
else
|
||||
if (strEltClass == 'm' || // method
|
||||
strEltClass == 'p' || // property
|
||||
strEltClass == 'e' || // event
|
||||
strEltClass == 'f') // field
|
||||
{
|
||||
strField = getName (elt).toLowerCase ();
|
||||
var match = strField.match ( /[\.A-Z0-9_]*/i );
|
||||
if (match)
|
||||
strField = match [0];
|
||||
elt = getParentDiv (elt);
|
||||
|
||||
}
|
||||
|
||||
var strEltClass = elt.className;
|
||||
if (strEltClass.charAt (strEltClass.length - 1) == '_')
|
||||
strEltClass = strEltClass.slice (0, strEltClass.length - 1);
|
||||
|
||||
if (strEltClass == 'c' || // class
|
||||
strEltClass == 's' || // struct
|
||||
strEltClass == 'i' || // struct
|
||||
strEltClass == 'd' || // delegate
|
||||
strEltClass == 'en') // enum
|
||||
{
|
||||
strClass = getName (elt);
|
||||
if (strEltClass == 'en')
|
||||
strField = null;
|
||||
elt = getParentDiv (elt);
|
||||
}
|
||||
|
||||
var strEltClass = elt.className;
|
||||
if (strEltClass.charAt (strEltClass.length - 1) == '_')
|
||||
strEltClass = strEltClass.slice (0, strEltClass.length - 1);
|
||||
|
||||
if (strEltClass == 'n')
|
||||
{
|
||||
strNamespace = getName (elt);
|
||||
elt = getParentDiv (elt);
|
||||
}
|
||||
|
||||
var strEltClass = elt.className;
|
||||
if (strEltClass.charAt (strEltClass.length - 1) == '_')
|
||||
strEltClass = strEltClass.slice (0, strEltClass.length - 1);
|
||||
|
||||
if (strEltClass == 'y')
|
||||
{
|
||||
strAssembly = getName (elt);
|
||||
}
|
||||
|
||||
if (evt.ctrlKey)
|
||||
{
|
||||
var strRoot = 'http://cvs.hispalinux.es/cgi-bin/cvsweb/mcs/class/';
|
||||
var strExtra = '?cvsroot=Mono';
|
||||
|
||||
if (strAssembly)
|
||||
{
|
||||
strRoot = strRoot + strAssembly + '/';
|
||||
if (strNamespace)
|
||||
{
|
||||
strRoot = strRoot + strNamespace + '/';
|
||||
if (strClass)
|
||||
{
|
||||
strRoot += strClass + '.cs';
|
||||
strExtra += '&rev=1';
|
||||
}
|
||||
}
|
||||
window.open (strRoot + strExtra, 'CVS');
|
||||
}
|
||||
}
|
||||
else if (strNamespace)
|
||||
{
|
||||
var re = /\./g ;
|
||||
strNamespace = strNamespace.toLowerCase ().replace (re, '');
|
||||
if (strClass)
|
||||
strNamespace += strClass.toLowerCase () + 'class';
|
||||
if (strField)
|
||||
strNamespace += strField;
|
||||
if (strClass || strField)
|
||||
strNamespace += 'topic';
|
||||
|
||||
window.open ('http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrf' + strNamespace + '.asp', 'MSDN');
|
||||
}
|
||||
}
|
||||
else
|
||||
{
|
||||
if (elt.parentNode && elt.parentNode.className == 't') // toggle
|
||||
elt = elt.parentNode;
|
||||
else if (elt.className != 't') // toggle
|
||||
return;
|
||||
|
||||
while (elt != null && elt.tagName != 'DIV')
|
||||
elt = elt.parentNode;
|
||||
|
||||
if (evt.shiftKey)
|
||||
{
|
||||
var rgElts = getChildrenByTagName (elt, 'DIV');
|
||||
var cElts = rgElts.length;
|
||||
if (cElts != 0)
|
||||
{
|
||||
var fView = false;
|
||||
var iElt;
|
||||
for (iElt = 0; iElt < cElts; iElt ++)
|
||||
{
|
||||
if (getView (rgElts [iElt]))
|
||||
{
|
||||
fView = true;
|
||||
break;
|
||||
}
|
||||
}
|
||||
for (iElt = 0; iElt < cElts; iElt ++)
|
||||
{
|
||||
setView (rgElts [iElt], !fView);
|
||||
}
|
||||
}
|
||||
}
|
||||
else if (evt.ctrlKey)
|
||||
{
|
||||
setView (elt, true);
|
||||
var eltParent = getParentDiv (elt);
|
||||
while (eltParent)
|
||||
{
|
||||
var rgSiblings = getChildrenByTagName (eltParent, 'DIV');
|
||||
var cSiblings = rgSiblings.length;
|
||||
for (var iSibling = 0; iSibling < cSiblings; iSibling++)
|
||||
{
|
||||
var eltSibling = rgSiblings [iSibling];
|
||||
if (eltSibling != elt)
|
||||
{
|
||||
setView (eltSibling, false);
|
||||
}
|
||||
}
|
||||
elt = eltParent;
|
||||
eltParent = getParentDiv (elt);
|
||||
}
|
||||
}
|
||||
else
|
||||
toggle (elt);
|
||||
}
|
||||
|
||||
return false;
|
||||
}
|
||||
|
||||
function filterTree ()
|
||||
{
|
||||
var eltMissing = document.getElementById ('missing');
|
||||
var eltTodo = document.getElementById ('todo');
|
||||
var eltExtra = document.getElementById ('extra');
|
||||
var eltErrors = document.getElementById ('errors');
|
||||
|
||||
var dictTypes = new Object ();
|
||||
if (eltMissing.checked)
|
||||
dictTypes ['sm'] = true;
|
||||
if (eltTodo.checked)
|
||||
dictTypes ['st'] = true;
|
||||
if (eltErrors.checked)
|
||||
dictTypes ['se'] = true;
|
||||
if (eltExtra.checked)
|
||||
dictTypes ['sx'] = true;
|
||||
dictTypes ['sc'] = true;
|
||||
|
||||
viewAll (document.getElementById ('ROOT'), dictTypes);
|
||||
}
|
||||
|
||||
function selectMissing ()
|
||||
{
|
||||
toggleFilter ('missing');
|
||||
}
|
||||
|
||||
function selectTodo ()
|
||||
{
|
||||
toggleFilter ('todo');
|
||||
}
|
||||
|
||||
function selectExtra ()
|
||||
{
|
||||
toggleFilter ('extra');
|
||||
}
|
||||
|
||||
function selectErrors ()
|
||||
{
|
||||
toggleFilter ('errors');
|
||||
}
|
||||
|
||||
function toggleFilter (strFilter)
|
||||
{
|
||||
var eltTodo = document.getElementById ('todo');
|
||||
var eltMissing = document.getElementById ('missing');
|
||||
var eltExtra = document.getElementById ('extra');
|
||||
var eltErrors = document.getElementById ('errors');
|
||||
|
||||
var eltToggle = document.getElementById (strFilter);
|
||||
if (window && window.event && window.event.shiftKey)
|
||||
{
|
||||
eltMissing.checked = eltTodo.checked = eltExtra.checked = eltErrors.checked = false;
|
||||
eltToggle.checked = true;
|
||||
}
|
||||
else
|
||||
if (!eltTodo.checked && !eltMissing.checked && !eltExtra.checked && !eltErrors.checked)
|
||||
{
|
||||
eltMissing.checked = eltTodo.checked = eltExtra.checked = eltErrors.checked = true;
|
||||
eltToggle.checked = false;
|
||||
}
|
||||
filterTree ();
|
||||
}
|
||||
|
||||
function onLoad ()
|
||||
{
|
||||
var eltMissing = document.getElementById ('missing');
|
||||
var eltTodo = document.getElementById ('todo');
|
||||
var eltExtra = document.getElementById ('extra');
|
||||
var eltErrors = document.getElementById ('errors');
|
||||
eltMissing.checked = eltTodo.checked = eltExtra.checked = eltErrors.checked = true;
|
||||
}
|
||||
|
||||
if (document.layers)
|
||||
{
|
||||
document.captureEvents (Event.MOUSEUP);
|
||||
document.onmouseup = clickHandler;
|
||||
}
|
||||
else if (document.attachEvent)
|
||||
{
|
||||
document.attachEvent('onclick', clickHandler);
|
||||
}
|
||||
else if (document.addEventListener)
|
||||
{
|
||||
document.addEventListener('click', clickHandler, false);
|
||||
}
|
||||
else
|
||||
document.onclick = clickHandler;
|
||||
|
||||
|
After Width: | Height: | Size: 137 B |
|
After Width: | Height: | Size: 861 B |
|
After Width: | Height: | Size: 111 B |
|
After Width: | Height: | Size: 90 B |
|
After Width: | Height: | Size: 90 B |
|
After Width: | Height: | Size: 101 B |
|
After Width: | Height: | Size: 65 B |
|
After Width: | Height: | Size: 111 B |
|
After Width: | Height: | Size: 73 B |
|
After Width: | Height: | Size: 127 B |
|
After Width: | Height: | Size: 70 B |
|
After Width: | Height: | Size: 73 B |
|
After Width: | Height: | Size: 76 B |
|
After Width: | Height: | Size: 101 B |
|
After Width: | Height: | Size: 73 B |
|
After Width: | Height: | Size: 49 B |
|
After Width: | Height: | Size: 64 B |
|
After Width: | Height: | Size: 67 B |
|
After Width: | Height: | Size: 92 B |
|
After Width: | Height: | Size: 4.8 KiB |
|
After Width: | Height: | Size: 3.0 KiB |
|
After Width: | Height: | Size: 49 B |
@@ -0,0 +1,28 @@
|
||||
#!/usr/bin/perl
|
||||
$q = 1;
|
||||
|
||||
while (<>){
|
||||
chop;
|
||||
if (/^\* (.*)$/){
|
||||
print "<h1>$1</h1>\n";
|
||||
} elsif (/^\*\* (.*)$/) {
|
||||
print "<h2>$1</h2>\n";
|
||||
} elsif (/^\*\*\* (.*)$/) {
|
||||
print "<h3>$1</h3>\n";
|
||||
} elsif (/^\*\*\*\* (.*)$/) {
|
||||
print "<h4>$1</h4>\n";
|
||||
} elsif (/^$/) {
|
||||
print "<p>\n";
|
||||
} elsif (/^\t\t\* (.*)$/) {
|
||||
print "<li>$1\n";
|
||||
} elsif (/^Q: (.*)$/){
|
||||
print "<p><a name=\"q$q\"></a><b>Question $q:</b> $1\n";
|
||||
$q++;
|
||||
} elsif (/^A: (.*)$/){
|
||||
print "$1\n";
|
||||
} elsif (/^TODO=(.*),$/){
|
||||
print "<a name=\"$1\">\n";
|
||||
} else {
|
||||
print "$_\n";
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,76 @@
|
||||
#!/usr/bin/perl
|
||||
$q = 1;
|
||||
|
||||
# Modified by Edwin Lima ([email protected]; [email protected])
|
||||
# Date: 08/21/01, The Netherlands
|
||||
# $f: Variable used as a flag to create the list of questions on top of the question-answers set. This
|
||||
# is the only way that I found to scan the questions which have a <CR><LF>, in such a way that I will not
|
||||
# scan the answer together at same time.
|
||||
# @aname: Buffer used to store the question-answers set to print them out just after the print of the
|
||||
# questions.
|
||||
# @href: Buffer used to store the anchors (only questions) to the questions-answers set on the bottom
|
||||
# of the page.
|
||||
# I opened explicitly the file for input (input.txt) but U can change this as it was originally.
|
||||
#
|
||||
#
|
||||
|
||||
#comment this line if you are not open the file explicitly
|
||||
#open(IN, "input.txt") || die "cannot open file input.txt" ;
|
||||
|
||||
print("<A name=TOP>") ;
|
||||
|
||||
#Uncomment line bellow to make it work as it was originally.
|
||||
while (<>){
|
||||
|
||||
#comment line bellow
|
||||
|
||||
#while (<IN>){
|
||||
chop;
|
||||
if (/^\* (.*)$/){
|
||||
push(@aname,"<h1>$1</h1>\n");
|
||||
# print $body;
|
||||
} elsif (/^\*\* (.*)$/) {
|
||||
push(@aname, "<h2>$1</h2>\n");
|
||||
push(@href, "<h2>$1</h2>\n");
|
||||
} elsif (/^\*\*\* (.*)$/) {
|
||||
push(@aname, "<h3>$1</h3>\n");
|
||||
|
||||
} elsif (/^$/) {
|
||||
push(@aname, "<p>\n");
|
||||
# push(@href, "<p>\n"); NOT NEEDED
|
||||
} elsif (/^\t\t\* (.*)$/) {
|
||||
push(@aname, "<li>$1\n");
|
||||
} elsif (/^Q: (.*)$/){
|
||||
push(@aname, "<p><a name=\"q$q\"></a><b>Question $q:</b> $1\n");
|
||||
push(@href,"<p><a href=\"#q$q\"><b>Question $q:</b></a> $1\n");
|
||||
$f=1;
|
||||
$q++;
|
||||
} elsif (/^A: (.*)$/){
|
||||
push(@aname,"<P>\n<A HREF=#TOP>Top</A>\n<P>");
|
||||
push(@aname,"$1\n");
|
||||
$f=0;
|
||||
} elsif (/^TODO=(.*),$/){
|
||||
push(@aname, "<a name=\"$1\">\n");
|
||||
#push(@href, "<a name=\"$1\">\n");
|
||||
} else {
|
||||
push(@aname,"$_\n");
|
||||
if ($f==1) {
|
||||
push(@href,"$_\n");
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
foreach $line (@href) #"\n\n";
|
||||
{
|
||||
print $line;
|
||||
}
|
||||
|
||||
foreach $line (@aname) #"\n\n";
|
||||
{
|
||||
print $line;
|
||||
}
|
||||
|
||||
|
||||
#comment this line if you are not open the file explicitly
|
||||
# close(IN) || die "cannot close file" ;
|
||||
|
||||
|
After Width: | Height: | Size: 4.8 KiB |
|
After Width: | Height: | Size: 4.5 KiB |
|
After Width: | Height: | Size: 3.0 KiB |
|
After Width: | Height: | Size: 4.4 KiB |
|
After Width: | Height: | Size: 49 B |
|
After Width: | Height: | Size: 157 B |
@@ -0,0 +1,90 @@
|
||||
CSCRIPT = $(SYSTEMROOT)/system32/cscript.exe
|
||||
|
||||
CORCOMPARE=../../../mcs/tools/corcompare
|
||||
|
||||
OBJECTS= \
|
||||
deploy/anoncvs.html \
|
||||
deploy/contributing.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.Data.html \
|
||||
deploy/class-status-System.Web.html \
|
||||
deploy/class-library.html \
|
||||
deploy/classlib-doc.html \
|
||||
deploy/contact.html \
|
||||
deploy/c-sharp.html \
|
||||
deploy/ccvs.html \
|
||||
deploy/documentation.html \
|
||||
deploy/download.html \
|
||||
deploy/faq.html \
|
||||
deploy/gcc-frontend.html \
|
||||
deploy/index.html \
|
||||
deploy/ideas.html \
|
||||
deploy/mailing-lists.html \
|
||||
deploy/monodoc-xml.html \
|
||||
deploy/passport.html \
|
||||
deploy/rationale.html \
|
||||
deploy/resources.html \
|
||||
deploy/roadmap.html \
|
||||
deploy/runtime.html \
|
||||
deploy/status.html \
|
||||
deploy/testing.html \
|
||||
deploy/porting.html \
|
||||
deploy/tools.html \
|
||||
deploy/books.html \
|
||||
deploy/papers.html
|
||||
|
||||
NON_HTML_SOURCES= \
|
||||
../mono-build.sh \
|
||||
../mono-build-w32.sh
|
||||
|
||||
|
||||
all: $(OBJECTS)
|
||||
perl process.pl commands template.html.in deploy
|
||||
|
||||
clean:
|
||||
rm -f $(OBJECTS) $(patsubst deploy/%.html,src/%.src, $(OBJECTS)) src/*.xml src/*.html.in ../class-status-* ../class-status
|
||||
|
||||
push:
|
||||
cp -f $(NON_HTML_SOURCES) deploy
|
||||
echo scp -P 2200 -r deploy/* [email protected]:/web/cvsmodules/mono
|
||||
(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh -p 2200' . [email protected]:/web/cvsmodules/mono )
|
||||
|
||||
push2:
|
||||
scp -r deploy/* primates:public_html/xxx
|
||||
|
||||
$(OBJECTS): $(patsubst deploy/%.html,src/%.src, $(OBJECTS))
|
||||
|
||||
#.PRECIOUS: $(patsubst deploy/%.html,src/%.src, $(OBJECTS))
|
||||
|
||||
|
||||
|
||||
.PRECIOUS: src/%.src
|
||||
src/%.src: ../% commands makefile template.html.in
|
||||
perl htmlify $< > $@
|
||||
|
||||
|
||||
|
||||
.PRECIOUS: ../class-status-%
|
||||
../class-status-%: src/%.html.in ../class-status.in
|
||||
cat ../class-status.in $< > $@
|
||||
|
||||
|
||||
.PRECIOUS: src/%.html.in
|
||||
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
|
||||
$(CORCOMPARE)/CorCompare.exe -x $@ $<
|
||||
|
||||
src/corlib.xml: ../../../mcs/class/lib/corlib_cmp.dll $(CORCOMPARE)/CorCompare.exe
|
||||
$(CORCOMPARE)/CorCompare.exe -f corlib -ms mscorlib -x $@ $<
|
||||
|
||||
|
||||
../class-status: ../class-status.in
|
||||
cp -f $< $@
|
||||
@@ -0,0 +1,89 @@
|
||||
#!/usr/bin/perl
|
||||
#
|
||||
# Author:
|
||||
# Sean MacIsaac
|
||||
#
|
||||
|
||||
use strict;
|
||||
|
||||
my $full_expand = 1;
|
||||
my @template;
|
||||
my $n;
|
||||
|
||||
if ($#ARGV != 2) {
|
||||
print "process.pl command_file template_file directory_prefix\n";
|
||||
exit ();
|
||||
}
|
||||
|
||||
my $menu = "";
|
||||
|
||||
open COMMANDS, $ARGV[0] || die "Can not open $ARGV[0]";
|
||||
while (<COMMANDS>) {
|
||||
chop;
|
||||
my @command = split /,/;
|
||||
if ($command[0] != -1) {
|
||||
$menu .= "\t\t";
|
||||
$menu .= "<tr><td valign=\"top\" class=\"navi" . $command[0];
|
||||
$menu .= "\"><a class=\"navi" . $command[0];
|
||||
$menu .= "\"";
|
||||
$menu .= "HREF=\"$command[2]\">$command[1]</A></td></tr>\n\n";
|
||||
}
|
||||
}
|
||||
close COMMANDS;
|
||||
|
||||
open TEMPLATE, $ARGV[1] || die "Can not open $ARGV[1]";
|
||||
while (<TEMPLATE>) {
|
||||
push @template, $_;
|
||||
}
|
||||
close TEMPLATE;
|
||||
|
||||
open COMMANDS, $ARGV[0] || die "Can not open $ARGV[0]";
|
||||
while (<COMMANDS>) {
|
||||
chop;
|
||||
my @command = split /,/;
|
||||
|
||||
if ($command[2] =~ /^http:/){
|
||||
} else {
|
||||
$n = $ARGV[2] . "/" . $command[2];
|
||||
open OUTPUT, ">" . $n || die "Can not create $n";
|
||||
|
||||
my $content = "";
|
||||
open INPUT, "src/$command[3]" || die "Can not open $command[3]";
|
||||
while (<INPUT>) {
|
||||
$content .= $_;
|
||||
}
|
||||
close INPUT;
|
||||
|
||||
my $line;
|
||||
my $temp;
|
||||
my $tit;
|
||||
my $title;
|
||||
my $css;
|
||||
my $script;
|
||||
|
||||
$tit = $command[1];
|
||||
$css = $command[4];
|
||||
$script = $command[5];
|
||||
|
||||
foreach $line (@template) {
|
||||
$temp = $line;
|
||||
$title = "$tit / Mono";
|
||||
$temp =~ s/#TITLE#/$title/;
|
||||
$temp =~ s/#CONTENT#/$content/;
|
||||
$temp =~ s/#MENU#/$menu/;
|
||||
if ($css) {
|
||||
$temp =~ s/#CSS#/<LINK rel="stylesheet" type="text\/css" href="$css">/;
|
||||
} else {
|
||||
$temp =~ s/#CSS#//;
|
||||
}
|
||||
|
||||
if ($script) {
|
||||
$temp =~ s/#SCRIPT#/<SCRIPT src="$script"><\/SCRIPT>/;
|
||||
} else {
|
||||
$temp =~ s/#SCRIPT#//;
|
||||
}
|
||||
print OUTPUT $temp;
|
||||
}
|
||||
}
|
||||
close OUTPUT;
|
||||
}
|
||||
@@ -0,0 +1 @@
|
||||
*.src
|
||||
@@ -0,0 +1,85 @@
|
||||
<html>
|
||||
<head>
|
||||
<title>#TITLE#</title>
|
||||
<style type="text/css">
|
||||
<!--
|
||||
body { font-family: "trebuchet ms", lucida, verdana, helvetica;
|
||||
background-image: url("images/bgsquares.gif");
|
||||
background-attachment: fixed; }
|
||||
body, td, table { font-family: "trebuchet ms", lucida, verdana, helvetica;
|
||||
font-size: 14px; }
|
||||
|
||||
.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}
|
||||
.footnote { font-size: 12px; color: #aaaaaa; }
|
||||
|
||||
a.navi0 { color: #ffffff; text-decoration: none}
|
||||
a.navi0:visited { color: #cccccc; }
|
||||
a.navi0:hover { color: #ee9900; text-decoration: underline; }
|
||||
|
||||
a.navi1 { color: #ffffff; text-decoration: none; margin-left: 7px;}
|
||||
a.navi1:visited { color: #cccccc; }
|
||||
a.navi1:hover { color: #ee9900; text-decoration: underline; }
|
||||
|
||||
a.navi2 { color: #ffffff; text-decoration: none; margin-left: 20px;}
|
||||
a.navi2:visited { color: #cccccc; }
|
||||
a.navi2:hover { color: #ee9900; text-decoration: underline; }
|
||||
|
||||
// -->
|
||||
</style>
|
||||
#CSS#
|
||||
#SCRIPT#
|
||||
</head>
|
||||
<body bgcolor="#555555" text="#000000">
|
||||
|
||||
<table cellpadding="0" cellspacing="0" border="0" width="100%">
|
||||
<tr>
|
||||
<td><img src="images/pixel.gif"></td><!-- left border -->
|
||||
<td colspan="4">
|
||||
<a href="http://www.go-mono.com"><img src="images/mono.gif" border="0"></a></td>
|
||||
<td><img src="images/pixel.gif"></td><!-- right border -->
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/pixel.gif" width="1" height="1"></td>
|
||||
<td colspan="3" bgcolor="black"><img src="images/pixel.gif" height="2"></td>
|
||||
<td bgcolor="black"><img src="images/pixel.gif" width="1"></td>
|
||||
<td><img src="images/pixel.gif"></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td width="100"><img src="images/pixel.gif"></td>
|
||||
<td valign="top">
|
||||
<table cellpadding="2" valign="top" cellspacing="0" border="0">
|
||||
#MENU#
|
||||
</table>
|
||||
</td>
|
||||
<td bgcolor="black" width="1"><img src="images/pixel.gif" width="1"></td>
|
||||
<td bgcolor="white" align="left" width="80%" valign="top">
|
||||
<table cellpadding="16">
|
||||
<tr><td>
|
||||
#CONTENT#
|
||||
</td></tr>
|
||||
</table>
|
||||
</td>
|
||||
<td bgcolor="black"><img src="images/pixel.gif" width="1"></td>
|
||||
<td width="100"><img src="images/pixel.gif"></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td colspan="2">
|
||||
<img src="images/pixel.gif"></td>
|
||||
<td colspan="2" bgcolor="black"><img src="images/pixel.gif" height="1"></td>
|
||||
<td bgcolor="black"><img src="images/pixel.gif" width="1"></td>
|
||||
<td><img src="images/pixel.gif"></td>
|
||||
</tr>
|
||||
|
||||
<td colspan="2"></td>
|
||||
<td colspan="2" align="center">
|
||||
<a class="footnote" href="mailto: [email protected]">[email protected]</a>
|
||||
</td>
|
||||
<td colspan="2"></td>
|
||||
</tr>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||