mirror of
https://github.com/BepInEx/mono.git
synced 2026-11-16 17:10:20 -10:00
Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
4a048a798c |
No files matched your search
@@ -1,255 +1,3 @@
|
||||
2003-11-26 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Add -fno-strict-aliasing to CFLAGS.
|
||||
|
||||
* configure.in: Applied patch from [email protected]. Avoid linking in
|
||||
librt if not neccesary.
|
||||
|
||||
2003-11-24 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Fix signbit check. Fixes #51315.
|
||||
|
||||
2003-11-20 Jackson Harper <[email protected]>
|
||||
|
||||
* data/machine.config: Add OutputCacheModule
|
||||
|
||||
2003-11-19 Jackson Harper <[email protected]>
|
||||
|
||||
* doc/web/team.xml: New email address and job description
|
||||
* doc/web/team/jackson.png: Picture of me debugging...seems appropriate
|
||||
|
||||
2003-11-14 Jackson Harper <[email protected]>
|
||||
|
||||
* Makefile.am: delete mscorlib.dll
|
||||
|
||||
2003-11-12 Jackson Harper <[email protected]>
|
||||
|
||||
* Makefile.am: corlib is now named mscorlib.dll
|
||||
|
||||
2003-11-12 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in acconfig.h: Add check for signbit, which is missing in
|
||||
FreeBSD 4.x.
|
||||
|
||||
2003-11-07 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Remove debugging junk accidently checked in.
|
||||
|
||||
* configure.in: Add new --with-nptl option to enable NPTL only
|
||||
features since auto-detection is not reliable.
|
||||
|
||||
* autogen.sh: Fix previous patch and silence noisy GNU which.
|
||||
|
||||
2003-11-07 Bernie Solomon <[email protected]>
|
||||
|
||||
* autogen.sh: tweak glibtool check so it works
|
||||
if which doesn't set return code properly
|
||||
|
||||
2003-11-07 Zoltan Varga <[email protected]>
|
||||
|
||||
* autogen.sh: Silence noisy GNU which.
|
||||
|
||||
* autogen.sh: Applied patch from Peter Teichman ([email protected]).
|
||||
Use 'glibtool' instead of 'libtool' on OSX.
|
||||
|
||||
2003-11-06 Zoltan Varga <zovarga@ws-zovarga2>
|
||||
|
||||
* mono/benchmark/pinvoke.cs: New benchmark for testing the performance
|
||||
of the managed/unmanaged boundary.
|
||||
|
||||
2003-11-06 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in acconfig.h: Add check for __thread keyword in gcc.
|
||||
|
||||
2003-10-29 Dick Porter <[email protected]>
|
||||
|
||||
* man/mono.1: Document MONO_EXTERNAL_ENCODINGS variable
|
||||
|
||||
2003-10-16 Miguel de Icaza <[email protected]>
|
||||
|
||||
* man/mono.1: Document new --trace options
|
||||
|
||||
2003-10-13 Bernie Solomon <[email protected]>
|
||||
|
||||
* configure.in: add hppa support (64bit only)
|
||||
make solaris build work with Forte compiler
|
||||
|
||||
2003-10-13 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Added check for pthread_attr_setstacksize.
|
||||
|
||||
* mono/tests/ChangeLog: New file.
|
||||
|
||||
2003-10-13 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am: Link the tests with the test driver program
|
||||
used for the mini tests.
|
||||
|
||||
2003-10-10 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c (mono_test_marshal_delegate): Added test for
|
||||
stdcall calling convention.
|
||||
|
||||
2003-10-09 Dick Porter <[email protected]>
|
||||
|
||||
* acconfig.h:
|
||||
* configure.in: Check for ICU availability
|
||||
|
||||
2003-10-09 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c: fix after merge of pinvoke2.cs
|
||||
|
||||
2003-10-07 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am mono/tests/libtest.c
|
||||
mono/tests/pinvoke18.cs: new test for bool marshalling.
|
||||
|
||||
2003-10-07 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/scripts/Makefile.am mono/scripts/*.in: fix
|
||||
managed .exe paths so they are found under cygwin.
|
||||
|
||||
2003-10-07 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke2.cs mono/tests/libtest.c: Fix array of structs
|
||||
test.
|
||||
|
||||
2003-10-06 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke2.cs mono/tests/pinvoke11.cs
|
||||
mono/tests/libtest.c: Add more pass by value struct
|
||||
tests for platforms with more complex calling conventions
|
||||
(Sparc V9, HPPA 64 bit).
|
||||
|
||||
2003-10-06 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke2.cs mono/tests/libtest.c: Add array of structs
|
||||
marshalling test.
|
||||
|
||||
2003-10-04 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c: remove warnings except
|
||||
"no previous prototype"
|
||||
|
||||
2003-10-03 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/libtest.c: (test_lpwstr_marshal) remove undefined
|
||||
behaviour of increment, (mono_test_marshal_char) = should be ==
|
||||
|
||||
2003-09-30 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/remoting1.cs: Added test for interface casts on
|
||||
TransparentProxies.
|
||||
|
||||
2003-09-24 Bernie Solomon <[email protected]>
|
||||
|
||||
* mono/tests/pinvoke*.cs, delegate4.cs, marshal10.cs, marshal4.cs
|
||||
marshal5.cs: remove .so from DllImport of libtest to aid portability.
|
||||
|
||||
2003-09-08 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Added check for valgrind headers.
|
||||
|
||||
2003-09-03 Zoltan Varga <[email protected]>
|
||||
|
||||
* Makefile.am: Use $(MAKE) in even more places. Patch by Bernie Solomon
|
||||
([email protected]).
|
||||
|
||||
2003-08-27 Zoltan Varga <[email protected]>
|
||||
|
||||
* Makefile.am: Use $(MAKE) instead of make. Patch by Bernie Solomon
|
||||
([email protected]).
|
||||
|
||||
2003-08-25 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono.pc.in: Added gthread-2.0.
|
||||
|
||||
2003-08-22 Zoltan Varga <[email protected]>
|
||||
|
||||
* configure.in: Added gthread-2.0 to GLIB_CFLAGS and GLIB_LIBS, so we
|
||||
can call g_thread_init ().
|
||||
|
||||
2003-08-21 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/threadpool.cs mono/tests/threadpool1.cs: Make increments
|
||||
of static variables atomic. Fixes bug #47683.
|
||||
|
||||
2003-08-21 Johannes Roith <[email protected]>
|
||||
|
||||
* mono/Makefile.am: small update. make sure, glib makes it in the build, add optional target for dependencies
|
||||
|
||||
2003-08-18 Johannes Roith <[email protected]>
|
||||
|
||||
* mono/Makefile.am: add windows build option
|
||||
* mono/monowiz.win32.nsi: add windows build script
|
||||
* mono/mono-win32-light.bmp: add bitmap
|
||||
|
||||
2003-08-16 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/checked.cs: Added mul.ovf tests.
|
||||
|
||||
2003-08-15 Duncan Mak <[email protected]>
|
||||
|
||||
* doc/mysql: Change references to ByteFX.Data.MySQLClient to the
|
||||
correct ByteFX.Data.MySqlClient (note the change in
|
||||
capitalization). Thanks to Tom Wagner <[email protected]> for
|
||||
spotting the error.
|
||||
|
||||
2003-08-15 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/bug-47295.cs: Regression test for bug #47295.
|
||||
|
||||
2003-08-11 Duncan Mak <[email protected]>
|
||||
|
||||
* runtime/Makefile.am (assemblies_DATA): Add Mono.Cairo.dll.
|
||||
|
||||
Sun Aug 3 21:12:13 BST 2003 Malte Hildingson <[email protected]>
|
||||
|
||||
* configure.in: added FPU test for ARM.
|
||||
|
||||
Thu Jul 31 16:19:07 CEST 2003 Paolo Molaro <[email protected]>
|
||||
|
||||
* configure.in, etc.: portability fixes and support for
|
||||
buidling outside the srcdir from Laurent Morichetti <[email protected]>.
|
||||
|
||||
2003-07-22 Duncan Mak <[email protected]>
|
||||
|
||||
* runtime/Makefile.am: Remove sqlsharp as we no longer distribute it.
|
||||
|
||||
2003-07-22 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/Makefile.am: Add missing test. Make tests interruptable
|
||||
by Ctrl-C. Add testinterp target to run the tests with the interpreter.
|
||||
Do not try to build vararg.cs under mcs.
|
||||
|
||||
* configure.in: Fix detection of GC_gcj_malloc.
|
||||
|
||||
2003-07-14 Jerome Laban <[email protected]>
|
||||
|
||||
* acconfig.h:
|
||||
* configure.in: Check for gethostbyname2_r availability.
|
||||
* data/machine.config: Added section system.net/settings. Added
|
||||
option for IPv6 availability.
|
||||
|
||||
2003-07-13 Zoltan Varga <[email protected]>
|
||||
|
||||
* mono/tests/cattr-object.cs: Make it run under both mono and MS.NET.
|
||||
|
||||
* mono/tests/struct.cs: Add test for unboxing trampolines.
|
||||
|
||||
* mono/tests/bug-27420.cs: new regression test.
|
||||
|
||||
* mono/tests/Makefile.am: skip vararg test since it does not compile
|
||||
under mono. Add testinterp target. Add new tests.
|
||||
|
||||
2003-07-10 Martin Willemoes Hansen
|
||||
|
||||
* doc/web/team.xml : Modified my tasks a bit.
|
||||
|
||||
2003-07-01 Paolo Molaro <[email protected]>
|
||||
|
||||
* acconfig.h, configure.in: added bundle support.
|
||||
|
||||
2003-06-10 Dick Porter <[email protected]>
|
||||
|
||||
* acconfig.h:
|
||||
|
||||
+1
-52
@@ -1,6 +1,6 @@
|
||||
AUTOMAKE_OPTIONS = foreign
|
||||
|
||||
SUBDIRS = @libgc_dir@ mono doc docs runtime scripts man data samples
|
||||
SUBDIRS = @libgc_dir@ mono doc docs runtime scripts man data
|
||||
|
||||
dnl EXTRA_SUBDIRS = libgc
|
||||
|
||||
@@ -9,54 +9,3 @@ EXTRA_DIST= mono.pc.in mono.spec.in
|
||||
pkgconfigdir = $(libdir)/pkgconfig
|
||||
pkgconfig_DATA= mono.pc
|
||||
DISTCLEANFILES= mono.pc
|
||||
|
||||
#
|
||||
# The following target is used to compile and install
|
||||
# mono and mcs without running into the out-of-sync
|
||||
# problems by doing the compilation in the right order.
|
||||
#
|
||||
|
||||
fullbuild: remove-binaries mcs-tree-safe-build xinstall-runtime mcs-rest install
|
||||
|
||||
mcs-tree-safe-build:
|
||||
(cd ../mcs/jay; $(MAKE))
|
||||
(cd ../mcs/mcs; $(MAKE) MCS=mcs)
|
||||
(cd ../mcs/class/corlib; $(MAKE) MCS=mcs)
|
||||
cp ../mcs/class/lib/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)
|
||||
|
||||
mcs-rest:
|
||||
(cd ../mcs/class; $(MAKE))
|
||||
|
||||
remove-binaries:
|
||||
rm ../mcs/class/lib/mscorlib.dll ../mcs/mcs/mcs.exe runtime/*dll runtime/*.exe >& /dev/null; echo
|
||||
|
||||
|
||||
win32getdeps:
|
||||
wget http://www.go-mono.com/archive/pkgconfig-0.11-20020310.zip
|
||||
wget http://www.go-mono.com/archive/glib-2.0.4-20020703.zip
|
||||
wget http://www.go-mono.com/archive/glib-dev-2.0.4-20020703.zip
|
||||
wget http://www.go-mono.com/archive/libiconv-1.7.zip
|
||||
wget http://www.go-mono.com/archive/libiconv-dev-1.7.zip
|
||||
wget http://www.go-mono.com/archive/libintl-0.10.40-20020101.zip
|
||||
wget http://www.jroith.de/nsis4cygwin.zip
|
||||
unzip -n -d / pkgconfig-0.11-20020310.zip
|
||||
unzip -n -d / glib-2.0.4-20020703.zip
|
||||
unzip -n -d / glib-dev-2.0.4-20020703.zip
|
||||
unzip -n -d / libiconv-1.7.zip
|
||||
unzip -n -d / libiconv-dev-1.7.zip
|
||||
unzip -n -d / libintl-0.10.40-20020101.zip
|
||||
unzip -n -d / nsis4cygwin.zip
|
||||
|
||||
win32setup:
|
||||
cp /usr/lib/libglib-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/iconv.dll @prefix@/lib
|
||||
cp /usr/lib/libgmodule-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/libgobject-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/libgthread-2.0-0.dll @prefix@/lib
|
||||
cp /usr/lib/libintl-1.dll @prefix@/lib
|
||||
makensis /DMILESTONE=@VERSION@ /DSOURCE_INSTALL_DIR=`cygpath -a -w @prefix@`\\* monowiz.win32.nsi
|
||||
@@ -1,28 +1,14 @@
|
||||
|
||||
This is Mono.
|
||||
|
||||
1. Installation
|
||||
2. Using Mono
|
||||
3. Directory Roadmap
|
||||
Installation:
|
||||
|
||||
1. Compilation and Installation
|
||||
===============================
|
||||
Read doc/download for installation instructions,
|
||||
or read the HTML version:
|
||||
|
||||
If you obtained this package as an officially released tarball,
|
||||
this is very simple, use configure and make:
|
||||
http://www.go-mono.com/download.html
|
||||
|
||||
./configure --prefix=/usr/local
|
||||
make
|
||||
make install
|
||||
|
||||
If you obtained this as a snapshot, you will need an existing
|
||||
Mono installation. To upgrade your installation do:
|
||||
|
||||
./autogen --prefix=/usr/local
|
||||
make fullbuild
|
||||
|
||||
2. Using Mono
|
||||
=============
|
||||
* Using Mono
|
||||
|
||||
Once you have installed the software, you can run a few programs:
|
||||
|
||||
@@ -43,8 +29,7 @@ This is Mono.
|
||||
See the man pages for mono(1), mint(1), monodis(1) and mcs(2)
|
||||
for further details.
|
||||
|
||||
3. Directory Roadmap
|
||||
====================
|
||||
* A directory roadmap:
|
||||
|
||||
doc/
|
||||
Contains documentation and the web site contents.
|
||||
|
||||
@@ -3,7 +3,6 @@
|
||||
#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
|
||||
@@ -20,13 +19,7 @@
|
||||
#undef HAVE_TIMEZONE
|
||||
#undef HAVE_TM_GMTOFF
|
||||
#undef MONO_SIZEOF_SUNPATH
|
||||
#undef MONO_ZERO_ARRAY_LENGTH
|
||||
#undef NEED_LINK_UNLINK
|
||||
#undef PTHREAD_POINTER_ID
|
||||
#undef HAVE_GC_H
|
||||
#undef HAVE_GC_GCJ_MALLOC
|
||||
#undef WITH_BUNDLE
|
||||
#undef HAVE_GETHOSTBYNAME2_R
|
||||
#undef HAVE_ICU
|
||||
#undef HAVE_KW_THREAD
|
||||
#undef HAVE_SIGNBIT
|
||||
+2
-9
@@ -30,15 +30,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 +91,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
|
||||
|
||||
|
||||
+20
-284
@@ -1,7 +1,7 @@
|
||||
AC_INIT(README)
|
||||
AC_CANONICAL_SYSTEM
|
||||
AM_CONFIG_HEADER(config.h)
|
||||
AM_INIT_AUTOMAKE(mono,0.29)
|
||||
AM_INIT_AUTOMAKE(mono,0.25)
|
||||
AM_MAINTAINER_MODE
|
||||
|
||||
dnl
|
||||
@@ -36,9 +36,7 @@ case "$host" in
|
||||
AC_DEFINE(PLATFORM_WIN32)
|
||||
CC="gcc -mno-cygwin"
|
||||
HOST_CC="gcc"
|
||||
# latest libgc already defines GC_WIN32_THREADS
|
||||
# CPPFLAGS="$CPPFLAGS -DGC_WIN32_THREADS -DWIN32_THREADS"
|
||||
CPPFLAGS="$CPPFLAGS -DWIN32_THREADS"
|
||||
CPPFLAGS="$CPPFLAGS -DGC_WIN32_THREADS -DWIN32_THREADS"
|
||||
libdl=
|
||||
libgc_threads=win32
|
||||
gc_default=boehm
|
||||
@@ -72,22 +70,12 @@ case "$host" in
|
||||
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
|
||||
libgc_threads=solaris
|
||||
;;
|
||||
*-*-darwin*)
|
||||
platform_win32=no
|
||||
@@ -114,12 +102,6 @@ AC_CHECK_TOOL(CC, gcc, gcc)
|
||||
AC_PROG_CC
|
||||
AM_PROG_CC_STDC
|
||||
AC_PROG_INSTALL
|
||||
dnl We should use AM_PROG_AS, but it's not available on automake/aclocal 1.4
|
||||
: ${CCAS='$(CC)'}
|
||||
# Set ASFLAGS if not already set.
|
||||
: ${CCASFLAGS='$(CFLAGS)'}
|
||||
AC_SUBST(CCAS)
|
||||
AC_SUBST(CCASFLAGS)
|
||||
|
||||
AC_CHECK_PROG(BISON, bison,yes,no)
|
||||
if test "x$BISON" = "xno";
|
||||
@@ -147,9 +129,6 @@ AM_PROG_LIBTOOL
|
||||
|
||||
AC_CHECK_HEADERS(sys/filio.h sys/sockio.h netdb.h utime.h semaphore.h sys/un.h)
|
||||
|
||||
# for mono/mini/tramp-x86.c
|
||||
AC_CHECK_HEADERS(valgrind/memcheck.h)
|
||||
|
||||
# for mono/metadata/debug-symfile.c
|
||||
AC_CHECK_HEADERS(elf.h)
|
||||
|
||||
@@ -159,21 +138,7 @@ AC_CHECK_HEADERS(wchar.h)
|
||||
# not 64 bit clean in cross-compile
|
||||
AC_CHECK_SIZEOF(void *, 4)
|
||||
|
||||
WARN=''
|
||||
if test x"$GCC" = xyes; then
|
||||
WARN='-Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings'
|
||||
# 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 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings'
|
||||
|
||||
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
|
||||
if test "x$PKG_CONFIG" = "xno"; then
|
||||
@@ -182,8 +147,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)
|
||||
|
||||
@@ -205,8 +170,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`
|
||||
|
||||
@@ -217,19 +182,6 @@ AC_SUBST(GMODULE_LIBS)
|
||||
|
||||
AC_ARG_WITH(gc, [ --with-gc=boehm,included,none],[gc=$with_gc],[gc=$gc_default])
|
||||
|
||||
# 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 Enable support for NPTL])
|
||||
|
||||
# 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=
|
||||
@@ -249,11 +201,7 @@ case "x$gc" in
|
||||
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_FUNCS(GC_gcj_malloc)
|
||||
;;
|
||||
|
||||
xincluded)
|
||||
@@ -381,21 +329,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 *****************************
|
||||
@@ -452,18 +385,6 @@ if test x$platform_win32 = xno; then
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
])
|
||||
|
||||
dnl **********************************
|
||||
dnl *** Check for gethostbyname2_r ***
|
||||
dnl **********************************
|
||||
AC_MSG_CHECKING(for gethostbyname2_r)
|
||||
AC_TRY_LINK([#include <netdb.h>], [
|
||||
gethostbyname2_r(NULL,0,NULL,NULL,0,NULL,NULL);
|
||||
], [
|
||||
# Yes, we have it...
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_GETHOSTBYNAME2_R)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for libnsl ***
|
||||
@@ -496,23 +417,6 @@ if test x$platform_win32 = xno; then
|
||||
AC_MSG_RESULT($cv_mono_sizeof_sunpath)
|
||||
AC_DEFINE_UNQUOTED(MONO_SIZEOF_SUNPATH, $cv_mono_sizeof_sunpath)
|
||||
|
||||
dnl *************************************
|
||||
dnl *** Checks for zero length arrays ***
|
||||
dnl *************************************
|
||||
AC_MSG_CHECKING(whether $CC supports zero length arrays)
|
||||
AC_TRY_COMPILE([
|
||||
struct s {
|
||||
int length;
|
||||
char data [0];
|
||||
};
|
||||
], [], [
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE_UNQUOTED(MONO_ZERO_ARRAY_LENGTH, 0)
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
AC_DEFINE_UNQUOTED(MONO_ZERO_ARRAY_LENGTH, 1)
|
||||
])
|
||||
|
||||
dnl *****************************
|
||||
dnl *** Checks for libxnet ***
|
||||
dnl *****************************
|
||||
@@ -539,7 +443,6 @@ if test x$platform_win32 = xno; then
|
||||
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>], [
|
||||
@@ -552,59 +455,11 @@ if test x$platform_win32 = xno; then
|
||||
AC_MSG_WARN(Using mono_mutex_t for recursive mutexes)
|
||||
AC_DEFINE(USE_MONO_MUTEX)
|
||||
])
|
||||
AC_CHECK_FUNCS(pthread_attr_setstacksize)
|
||||
|
||||
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" = "x"; then
|
||||
AC_MSG_RESULT(disabled)
|
||||
else
|
||||
AC_MSG_RESULT(yes)
|
||||
AC_DEFINE(HAVE_KW_THREAD)
|
||||
fi
|
||||
], [
|
||||
AC_MSG_RESULT(no)
|
||||
])
|
||||
|
||||
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)
|
||||
AC_CHECK_LIB(rt, sem_init, LIBS="$LIBS -lrt")
|
||||
|
||||
dnl ********************************
|
||||
dnl *** Checks for timezone stuff **
|
||||
@@ -631,40 +486,6 @@ if test x$platform_win32 = xno; then
|
||||
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)
|
||||
])
|
||||
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?))
|
||||
@@ -743,101 +564,22 @@ if test "x$try_shared_handles" != "xyes"; then
|
||||
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])
|
||||
else
|
||||
enable_icu="yes. Version: `$ICU_CONFIG --version`"
|
||||
AC_DEFINE(HAVE_ICU)
|
||||
ICU_CFLAGS=`$ICU_CONFIG --cppflags`
|
||||
ICU_LIBS=`$ICU_CONFIG --ldflags`
|
||||
fi
|
||||
AC_SUBST(ICU_CFLAGS)
|
||||
AC_SUBST(ICU_LIBS)
|
||||
|
||||
TARGET="unknown"
|
||||
ACCESS_UNALIGNED="yes"
|
||||
|
||||
JIT_SUPPORTED=no
|
||||
LIBC="libc.so.6"
|
||||
|
||||
case "$host" in
|
||||
# mips-sgi-irix5.* | mips-sgi-irix6.*)
|
||||
# TARGET=MIPS;
|
||||
# ACCESS_UNALIGNED="no"
|
||||
# ;;
|
||||
i*86-*-*)
|
||||
TARGET=X86;
|
||||
arch_target=x86;
|
||||
JIT_SUPPORTED=yes
|
||||
;;
|
||||
sparc*-*-*)
|
||||
TARGET=SPARC;
|
||||
arch_target=sparc;
|
||||
ACCESS_UNALIGNED="no"
|
||||
;;
|
||||
# alpha*-*-linux* | alpha*-*-osf*)
|
||||
# TARGET=ALPHA;
|
||||
# ACCESS_UNALIGNED="no"
|
||||
# ;;
|
||||
# ia64-*-linux* | ia64-*-hpux*)
|
||||
# TARGET=IA64;
|
||||
# arch_target=ia64;
|
||||
# JIT_SUPPORTED=no;
|
||||
# ACCESS_UNALIGNED="no";
|
||||
# case "$host_os" in
|
||||
# linux*) LIBC="libc.so.6.1";;
|
||||
# hpux*) LIBC="libc.so.1";;
|
||||
# esac
|
||||
# ;;
|
||||
# m68k-*-linux*)
|
||||
# TARGET=M68K
|
||||
# ;;
|
||||
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; JIT_SUPPORTED=yes;;
|
||||
sparc*-*-*) TARGET=SPARC; arch_target=sparc; ACCESS_UNALIGNED="no";;
|
||||
#alpha*-*-linux* | alpha*-*-osf*) TARGET=ALPHA; ACCESS_UNALIGNED="no";;
|
||||
#m68k-*-linux*) TARGET=M68K;;
|
||||
macppc-*-openbsd* | powerpc-*-linux* | powerpc-*-openbsd* | powerpc-*-sysv* | powerpc-*-darwin*) TARGET=POWERPC; arch_target=ppc; 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";;
|
||||
esac
|
||||
|
||||
if test ${TARGET} = ARM; then
|
||||
dnl ******************************************
|
||||
dnl *** Check to see what FPU is available ***
|
||||
dnl ******************************************
|
||||
AC_MSG_CHECKING(which FPU to use)
|
||||
|
||||
AC_TRY_COMPILE([], [
|
||||
__asm__ ("ldfd f0, [r0]");
|
||||
], fpu=FPA, [
|
||||
AC_TRY_COMPILE([], [
|
||||
__asm__ ("fldd d0, [r0]");
|
||||
], fpu=VFP, fpu=NONE)
|
||||
])
|
||||
|
||||
AC_MSG_RESULT($fpu)
|
||||
CPPFLAGS="$CPPFLAGS -DARM_FPU_$fpu"
|
||||
unset fpu
|
||||
fi
|
||||
|
||||
if test ${TARGET} = unknown; then
|
||||
CPPFLAGS="$CPPFLAGS -DNO_PORT"
|
||||
AC_MSG_WARN("mono has not been ported to $host: some things may not work.")
|
||||
@@ -852,15 +594,14 @@ AM_CONDITIONAL(MIPS_SGI, test ${TARGET}${ac_cv_prog_gcc} = MIPSno)
|
||||
AM_CONDITIONAL(SPARC, test x$TARGET = xSPARC)
|
||||
AM_CONDITIONAL(X86, test x$TARGET = xX86)
|
||||
AM_CONDITIONAL(ALPHA, test x$TARGET = xALPHA)
|
||||
AM_CONDITIONAL(IA64, test x$TARGET = xIA64)
|
||||
AM_CONDITIONAL(M68K, test x$TARGET = xM68K)
|
||||
AM_CONDITIONAL(POWERPC, test x$TARGET = xPOWERPC)
|
||||
AM_CONDITIONAL(ARM, test x$TARGET = xARM)
|
||||
AM_CONDITIONAL(S390, test x$TARGET = xS390)
|
||||
AM_CONDITIONAL(HPPA, test x$TARGET = xHPPA)
|
||||
|
||||
AM_CONDITIONAL(JIT_SUPPORTED, test x$JIT_SUPPORTED = xyes)
|
||||
|
||||
LIBC="libc.so.6"
|
||||
AC_SUBST(LIBC)
|
||||
|
||||
AC_SUBST(arch_target)
|
||||
@@ -881,7 +622,6 @@ mono/os/Makefile
|
||||
mono/os/win32/Makefile
|
||||
mono/os/unix/Makefile
|
||||
mono/arch/x86/Makefile
|
||||
mono/arch/hppa/Makefile
|
||||
mono/arch/ppc/Makefile
|
||||
mono/arch/sparc/Makefile
|
||||
mono/arch/s390/Makefile
|
||||
@@ -889,27 +629,23 @@ mono/arch/arm/Makefile
|
||||
mono/arch/alpha/Makefile
|
||||
mono/interpreter/Makefile
|
||||
mono/tests/Makefile
|
||||
mono/tests/tests-config
|
||||
mono/benchmark/Makefile
|
||||
mono/monoburg/Makefile
|
||||
mono/monograph/Makefile
|
||||
mono/io-layer/Makefile
|
||||
mono/handles/Makefile
|
||||
mono/mini/Makefile
|
||||
mono/profiler/Makefile
|
||||
runtime/Makefile
|
||||
scripts/Makefile
|
||||
man/Makefile
|
||||
doc/Makefile
|
||||
docs/Makefile
|
||||
data/Makefile
|
||||
samples/Makefile
|
||||
data/config
|
||||
mono.spec
|
||||
])
|
||||
|
||||
echo "
|
||||
|
||||
GC: $gc
|
||||
ICU: $enable_icu
|
||||
|
||||
"
|
||||
@@ -1,4 +0,0 @@
|
||||
Makefile.in
|
||||
Makefile
|
||||
config
|
||||
.cvsignore
|
||||
@@ -1,927 +0,0 @@
|
||||
<%
|
||||
//
|
||||
// DefaultWsdlHelpGenerator.aspx:
|
||||
//
|
||||
// Author:
|
||||
// Lluis Sanchez Gual ([email protected])
|
||||
//
|
||||
// (C) 2003 Ximian, Inc. http://www.ximian.com
|
||||
//
|
||||
%>
|
||||
|
||||
<%@ Import Namespace="System.Collections" %>
|
||||
<%@ Import Namespace="System.IO" %>
|
||||
<%@ Import Namespace="System.Xml.Serialization" %>
|
||||
<%@ Import Namespace="System.Xml" %>
|
||||
<%@ Import Namespace="System.Xml.Schema" %>
|
||||
<%@ Import Namespace="System.Web.Services.Description" %>
|
||||
<%@ Import Namespace="System" %>
|
||||
<%@ Import Namespace="System.Net" %>
|
||||
<%@ Import Namespace="System.Globalization" %>
|
||||
<%@ Import Namespace="System.Resources" %>
|
||||
<%@ Import Namespace="System.Diagnostics" %>
|
||||
<%@ Import Namespace="System.CodeDom" %>
|
||||
<%@ Import Namespace="System.CodeDom.Compiler" %>
|
||||
<%@ Import Namespace="Microsoft.CSharp" %>
|
||||
<%@ Import Namespace="Microsoft.VisualBasic" %>
|
||||
<%@ Import Namespace="System.Text.RegularExpressions" %>
|
||||
<%@ Assembly name="System.Web.Services" %>
|
||||
<%@ Page debug="true" %>
|
||||
|
||||
<html>
|
||||
<script language="C#" runat="server">
|
||||
|
||||
ServiceDescriptionCollection descriptions;
|
||||
XmlSchemas schemas;
|
||||
|
||||
string WebServiceName;
|
||||
string WebServiceDescription;
|
||||
string PageName;
|
||||
|
||||
string DefaultBinding;
|
||||
ArrayList ServiceProtocols;
|
||||
|
||||
string CurrentOperationName;
|
||||
string CurrentOperationBinding;
|
||||
string OperationDocumentation;
|
||||
string CurrentOperationFormat;
|
||||
bool CurrentOperationSupportsTest;
|
||||
ArrayList InParams;
|
||||
ArrayList OutParams;
|
||||
string CurrentOperationProtocols;
|
||||
int CodeTextColumns = 95;
|
||||
|
||||
void Page_Load(object sender, EventArgs e)
|
||||
{
|
||||
descriptions = (ServiceDescriptionCollection) Context.Items["wsdls"];
|
||||
schemas = (XmlSchemas) Context.Items["schemas"];
|
||||
|
||||
ServiceDescription desc = descriptions [0];
|
||||
if (schemas.Count == 0) schemas = desc.Types.Schemas;
|
||||
|
||||
Service service = desc.Services[0];
|
||||
WebServiceName = service.Name;
|
||||
DefaultBinding = desc.Bindings[0].Name;
|
||||
WebServiceDescription = service.Documentation;
|
||||
ServiceProtocols = FindServiceProtocols (null);
|
||||
|
||||
CurrentOperationName = Request.QueryString["op"];
|
||||
CurrentOperationBinding = Request.QueryString["bnd"];
|
||||
if (CurrentOperationName != null) BuildOperationInfo ();
|
||||
|
||||
PageName = HttpUtility.UrlEncode (Path.GetFileName(Request.Path), Encoding.UTF8);
|
||||
|
||||
ArrayList list = new ArrayList ();
|
||||
foreach (ServiceDescription sd in descriptions) {
|
||||
foreach (Binding bin in sd.Bindings)
|
||||
if (bin.Extensions.Find (typeof(SoapBinding)) != null) list.Add (bin);
|
||||
}
|
||||
|
||||
BindingsRepeater.DataSource = list;
|
||||
Page.DataBind();
|
||||
}
|
||||
|
||||
void BuildOperationInfo ()
|
||||
{
|
||||
InParams = new ArrayList ();
|
||||
OutParams = new ArrayList ();
|
||||
|
||||
Binding binding = FindBinding (CurrentOperationBinding);
|
||||
PortType portType = descriptions.GetPortType (binding.Type);
|
||||
Operation oper = FindOperation (portType, CurrentOperationName);
|
||||
|
||||
OperationDocumentation = oper.Documentation;
|
||||
if (OperationDocumentation == null || OperationDocumentation == "")
|
||||
OperationDocumentation = "No additional remarks";
|
||||
|
||||
foreach (OperationMessage opm in oper.Messages)
|
||||
{
|
||||
if (opm is OperationInput)
|
||||
BuildParameters (InParams, opm);
|
||||
else if (opm is OperationOutput)
|
||||
BuildParameters (OutParams, opm);
|
||||
}
|
||||
|
||||
// Protocols supported by the operation
|
||||
CurrentOperationProtocols = "";
|
||||
ArrayList prots = FindServiceProtocols (CurrentOperationName);
|
||||
for (int n=0; n<prots.Count; n++) {
|
||||
if (n != 0) CurrentOperationProtocols += ", ";
|
||||
CurrentOperationProtocols += (string) prots[n];
|
||||
}
|
||||
|
||||
CurrentOperationSupportsTest = prots.Contains ("HttpGet") || prots.Contains ("HttpPost");
|
||||
|
||||
// Operation format
|
||||
OperationBinding obin = FindOperation (binding, CurrentOperationName);
|
||||
if (obin != null)
|
||||
CurrentOperationFormat = GetOperationFormat (obin);
|
||||
|
||||
InputParamsRepeater.DataSource = InParams;
|
||||
InputFormParamsRepeater.DataSource = InParams;
|
||||
OutputParamsRepeater.DataSource = OutParams;
|
||||
}
|
||||
|
||||
void BuildParameters (ArrayList list, OperationMessage opm)
|
||||
{
|
||||
Message msg = descriptions.GetMessage (opm.Message);
|
||||
if (msg.Parts.Count > 0 && msg.Parts[0].Name == "parameters")
|
||||
{
|
||||
MessagePart part = msg.Parts[0];
|
||||
XmlSchemaComplexType ctype;
|
||||
if (part.Element == XmlQualifiedName.Empty)
|
||||
{
|
||||
ctype = (XmlSchemaComplexType) schemas.Find (part.Type, typeof(XmlSchemaComplexType));
|
||||
}
|
||||
else
|
||||
{
|
||||
XmlSchemaElement elem = (XmlSchemaElement) schemas.Find (part.Element, typeof(XmlSchemaElement));
|
||||
ctype = (XmlSchemaComplexType) elem.SchemaType;
|
||||
}
|
||||
XmlSchemaSequence seq = ctype.Particle as XmlSchemaSequence;
|
||||
if (seq == null) return;
|
||||
|
||||
foreach (XmlSchemaObject ob in seq.Items)
|
||||
{
|
||||
Parameter p = new Parameter();
|
||||
p.Description = "No additional remarks";
|
||||
|
||||
if (ob is XmlSchemaElement)
|
||||
{
|
||||
XmlSchemaElement selem = GetRefElement ((XmlSchemaElement)ob);
|
||||
p.Name = selem.Name;
|
||||
p.Type = selem.SchemaTypeName.Name;
|
||||
}
|
||||
else
|
||||
{
|
||||
p.Name = "Unknown";
|
||||
p.Type = "Unknown";
|
||||
}
|
||||
list.Add (p);
|
||||
}
|
||||
}
|
||||
else
|
||||
{
|
||||
foreach (MessagePart part in msg.Parts)
|
||||
{
|
||||
Parameter p = new Parameter ();
|
||||
p.Description = "No additional remarks";
|
||||
p.Name = part.Name;
|
||||
if (part.Element == XmlQualifiedName.Empty)
|
||||
p.Type = part.Type.Name;
|
||||
else
|
||||
{
|
||||
XmlSchemaElement elem = (XmlSchemaElement) schemas.Find (part.Element, typeof(XmlSchemaElement));
|
||||
p.Type = elem.SchemaTypeName.Name;
|
||||
}
|
||||
list.Add (p);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
string GetOperationFormat (OperationBinding obin)
|
||||
{
|
||||
string format = "";
|
||||
SoapOperationBinding sob = obin.Extensions.Find (typeof(SoapOperationBinding)) as SoapOperationBinding;
|
||||
if (sob != null) {
|
||||
format = sob.Style.ToString ();
|
||||
SoapBodyBinding sbb = obin.Input.Extensions.Find (typeof(SoapBodyBinding)) as SoapBodyBinding;
|
||||
if (sbb != null)
|
||||
format += " / " + sbb.Use;
|
||||
}
|
||||
return format;
|
||||
}
|
||||
|
||||
XmlSchemaElement GetRefElement (XmlSchemaElement elem)
|
||||
{
|
||||
if (!elem.RefName.IsEmpty)
|
||||
return (XmlSchemaElement) schemas.Find (elem.RefName, typeof(XmlSchemaElement));
|
||||
else
|
||||
return elem;
|
||||
}
|
||||
|
||||
ArrayList FindServiceProtocols(string operName)
|
||||
{
|
||||
ArrayList table = new ArrayList ();
|
||||
Service service = descriptions[0].Services[0];
|
||||
foreach (Port port in service.Ports)
|
||||
{
|
||||
string prot = null;
|
||||
Binding bin = descriptions.GetBinding (port.Binding);
|
||||
if (bin.Extensions.Find (typeof(SoapBinding)) != null)
|
||||
prot = "Soap";
|
||||
else
|
||||
{
|
||||
HttpBinding hb = (HttpBinding) bin.Extensions.Find (typeof(HttpBinding));
|
||||
if (hb != null && hb.Verb == "POST") prot = "HttpPost";
|
||||
else if (hb != null && hb.Verb == "GET") prot = "HttpGet";
|
||||
}
|
||||
|
||||
if (prot != null && operName != null)
|
||||
{
|
||||
if (FindOperation (bin, operName) == null)
|
||||
prot = null;
|
||||
}
|
||||
|
||||
if (prot != null && !table.Contains (prot))
|
||||
table.Add (prot);
|
||||
}
|
||||
return table;
|
||||
}
|
||||
|
||||
Binding FindBinding (string portName)
|
||||
{
|
||||
Service service = descriptions[0].Services[0];
|
||||
foreach (Port port in service.Ports)
|
||||
if (port.Name == portName)
|
||||
return descriptions.GetBinding (port.Binding);
|
||||
return null;
|
||||
}
|
||||
|
||||
Operation FindOperation (PortType portType, string name)
|
||||
{
|
||||
foreach (Operation oper in portType.Operations) {
|
||||
if (oper.Messages.Input.Name != null) {
|
||||
if (oper.Messages.Input.Name == name) return oper;
|
||||
}
|
||||
else
|
||||
if (oper.Name == name) return oper;
|
||||
}
|
||||
|
||||
return null;
|
||||
}
|
||||
|
||||
OperationBinding FindOperation (Binding binding, string name)
|
||||
{
|
||||
foreach (OperationBinding oper in binding.Operations) {
|
||||
if (oper.Input.Name != null) {
|
||||
if (oper.Input.Name == name) return oper;
|
||||
}
|
||||
else
|
||||
if (oper.Name == name) return oper;
|
||||
}
|
||||
|
||||
return null;
|
||||
}
|
||||
|
||||
string FormatBindingName (string name)
|
||||
{
|
||||
if (name == DefaultBinding) return "Methods";
|
||||
else return "Methods for binding<br>" + name;
|
||||
}
|
||||
|
||||
string GetOpName (object op)
|
||||
{
|
||||
OperationBinding ob = op as OperationBinding;
|
||||
if (ob == null) return "";
|
||||
if (ob.Input.Name != null) return ob.Input.Name;
|
||||
else return ob.Name;
|
||||
}
|
||||
|
||||
bool HasFormResult
|
||||
{
|
||||
get { return Request.QueryString ["ext"] == "testform"; }
|
||||
}
|
||||
|
||||
string GetTestResult ()
|
||||
{
|
||||
if (!HasFormResult) return null;
|
||||
|
||||
bool fill = false;
|
||||
string qs = "";
|
||||
for (int n=0; n<Request.QueryString.Count; n++)
|
||||
{
|
||||
if (fill) {
|
||||
if (qs != "") qs += "&";
|
||||
qs += Request.QueryString.GetKey(n) + "=" + Request.QueryString [n];
|
||||
}
|
||||
if (Request.QueryString.GetKey(n) == "ext") fill = true;
|
||||
}
|
||||
|
||||
string location = null;
|
||||
ServiceDescription desc = descriptions [0];
|
||||
Service service = desc.Services[0];
|
||||
foreach (Port port in service.Ports)
|
||||
if (port.Name == CurrentOperationBinding)
|
||||
{
|
||||
SoapAddressBinding sbi = (SoapAddressBinding) port.Extensions.Find (typeof(SoapAddressBinding));
|
||||
if (sbi != null)
|
||||
location = sbi.Location;
|
||||
}
|
||||
|
||||
if (location == null)
|
||||
return "Could not locate web service";
|
||||
|
||||
try
|
||||
{
|
||||
WebRequest req = WebRequest.Create (location + "/" + CurrentOperationName + "?" + qs);
|
||||
WebResponse resp = req.GetResponse();
|
||||
StreamReader sr = new StreamReader (resp.GetResponseStream());
|
||||
string s = sr.ReadToEnd ();
|
||||
sr.Close ();
|
||||
return "<div class='code-xml'>" + ColorizeXml(WrapText(s,CodeTextColumns)) + "</div>";
|
||||
}
|
||||
catch (Exception ex)
|
||||
{
|
||||
string res = "<b style='color:red'>" + ex.Message + "</b>";
|
||||
WebException wex = ex as WebException;
|
||||
if (wex != null)
|
||||
{
|
||||
WebResponse resp = wex.Response;
|
||||
if (resp != null) {
|
||||
StreamReader sr = new StreamReader (resp.GetResponseStream());
|
||||
string s = sr.ReadToEnd ();
|
||||
sr.Close ();
|
||||
res += "<div class='code-xml'>" + ColorizeXml(WrapText(s,CodeTextColumns)) + "</div>";
|
||||
}
|
||||
}
|
||||
return res;
|
||||
}
|
||||
}
|
||||
|
||||
//
|
||||
// Proxy code generation
|
||||
//
|
||||
|
||||
string GetProxyCode ()
|
||||
{
|
||||
CodeNamespace codeNamespace = new CodeNamespace();
|
||||
CodeCompileUnit codeUnit = new CodeCompileUnit();
|
||||
|
||||
codeUnit.Namespaces.Add (codeNamespace);
|
||||
|
||||
ServiceDescriptionImporter importer = new ServiceDescriptionImporter();
|
||||
|
||||
foreach (ServiceDescription sd in descriptions)
|
||||
importer.AddServiceDescription(sd, null, null);
|
||||
|
||||
foreach (XmlSchema sc in schemas)
|
||||
importer.Schemas.Add (sc);
|
||||
|
||||
importer.Import(codeNamespace, codeUnit);
|
||||
|
||||
string langId = Request.QueryString ["lang"];
|
||||
if (langId == null || langId == "") langId = "cs";
|
||||
CodeDomProvider provider = GetProvider (langId);
|
||||
ICodeGenerator generator = provider.CreateGenerator();
|
||||
CodeGeneratorOptions options = new CodeGeneratorOptions();
|
||||
|
||||
StringWriter sw = new StringWriter ();
|
||||
generator.GenerateCodeFromCompileUnit(codeUnit, sw, options);
|
||||
|
||||
return Colorize (WrapText (sw.ToString (), CodeTextColumns), langId);
|
||||
}
|
||||
|
||||
public string CurrentLanguage
|
||||
{
|
||||
get {
|
||||
string langId = Request.QueryString ["lang"];
|
||||
if (langId == null || langId == "") langId = "cs";
|
||||
return langId;
|
||||
}
|
||||
}
|
||||
|
||||
public string CurrentProxytName
|
||||
{
|
||||
get {
|
||||
string lan = CurrentLanguage == "cs" ? "C#" : "Visual Basic";
|
||||
return lan + " Client Proxy";
|
||||
}
|
||||
}
|
||||
|
||||
private CodeDomProvider GetProvider(string langId)
|
||||
{
|
||||
switch (langId.ToUpper())
|
||||
{
|
||||
case "CS": return new CSharpCodeProvider();
|
||||
case "VB": return new VBCodeProvider();
|
||||
default: return null;
|
||||
}
|
||||
}
|
||||
|
||||
//
|
||||
// Document generation
|
||||
//
|
||||
|
||||
string GenerateDocument ()
|
||||
{
|
||||
StringWriter sw = new StringWriter ();
|
||||
|
||||
if (CurrentDocType == "wsdl")
|
||||
descriptions [CurrentDocInd].Write (sw);
|
||||
else if (CurrentDocType == "schema")
|
||||
schemas [CurrentDocInd].Write (sw);
|
||||
|
||||
return Colorize (WrapText (sw.ToString (), CodeTextColumns), "xml");
|
||||
}
|
||||
|
||||
public string CurrentDocType
|
||||
{
|
||||
get { return Request.QueryString ["doctype"] != null ? Request.QueryString ["doctype"] : "wsdl"; }
|
||||
}
|
||||
|
||||
public int CurrentDocInd
|
||||
{
|
||||
get { return Request.QueryString ["docind"] != null ? int.Parse (Request.QueryString ["docind"]) : 0; }
|
||||
}
|
||||
|
||||
public string CurrentDocumentName
|
||||
{
|
||||
get {
|
||||
if (CurrentDocType == "wsdl")
|
||||
return "WSDL document for namespace \"" + descriptions [CurrentDocInd].TargetNamespace + "\"";
|
||||
else
|
||||
return "Xml Schema for namespace \"" + schemas [CurrentDocInd].TargetNamespace + "\"";
|
||||
}
|
||||
}
|
||||
|
||||
//
|
||||
// Pages and tabs
|
||||
//
|
||||
|
||||
bool firstTab = true;
|
||||
ArrayList disabledTabs = new ArrayList ();
|
||||
|
||||
string CurrentTab
|
||||
{
|
||||
get { return Request.QueryString["tab"] != null ? Request.QueryString["tab"] : "main" ; }
|
||||
}
|
||||
|
||||
string CurrentPage
|
||||
{
|
||||
get { return Request.QueryString["page"] != null ? Request.QueryString["page"] : "main" ; }
|
||||
}
|
||||
|
||||
void WriteTabs ()
|
||||
{
|
||||
if (CurrentOperationName != null)
|
||||
{
|
||||
WriteTab ("main","Overview");
|
||||
WriteTab ("test","Test Form");
|
||||
WriteTab ("msg","Message Layout");
|
||||
}
|
||||
}
|
||||
|
||||
void WriteTab (string id, string label)
|
||||
{
|
||||
if (!firstTab) Response.Write(" | ");
|
||||
firstTab = false;
|
||||
|
||||
string cname = CurrentTab == id ? "tabLabelOn" : "tabLabelOff";
|
||||
Response.Write ("<a href='" + PageName + "?" + GetPageContext(null) + GetDataContext() + "tab=" + id + "' style='text-decoration:none'>");
|
||||
Response.Write ("<span class='" + cname + "'>" + label + "</span>");
|
||||
Response.Write ("</a>");
|
||||
}
|
||||
|
||||
string GetTabContext (string pag, string tab)
|
||||
{
|
||||
if (tab == null) tab = CurrentTab;
|
||||
if (pag == null) pag = CurrentPage;
|
||||
if (pag != CurrentPage) tab = "main";
|
||||
return "page=" + pag + "&tab=" + tab + "&";
|
||||
}
|
||||
|
||||
string GetPageContext (string pag)
|
||||
{
|
||||
if (pag == null) pag = CurrentPage;
|
||||
return "page=" + pag + "&";
|
||||
}
|
||||
|
||||
class Tab
|
||||
{
|
||||
public string Id;
|
||||
public string Label;
|
||||
}
|
||||
|
||||
//
|
||||
// Syntax coloring
|
||||
//
|
||||
|
||||
static string keywords_cs =
|
||||
"(\\babstract\\b|\\bevent\\b|\\bnew\\b|\\bstruct\\b|\\bas\\b|\\bexplicit\\b|\\bnull\\b|\\bswitch\\b|\\bbase\\b|\\bextern\\b|" +
|
||||
"\\bobject\\b|\\bthis\\b|\\bbool\\b|\\bfalse\\b|\\boperator\\b|\\bthrow\\b|\\bbreak\\b|\\bfinally\\b|\\bout\\b|\\btrue\\b|" +
|
||||
"\\bbyte\\b|\\bfixed\\b|\\boverride\\b|\\btry\\b|\\bcase\\b|\\bfloat\\b|\\bparams\\b|\\btypeof\\b|\\bcatch\\b|\\bfor\\b|" +
|
||||
"\\bprivate\\b|\\buint\\b|\\bchar\\b|\\bforeach\\b|\\bprotected\\b|\\bulong\\b|\\bchecked\\b|\\bgoto\\b|\\bpublic\\b|" +
|
||||
"\\bunchecked\\b|\\bclass\\b|\\bif\\b|\\breadonly\\b|\\bunsafe\\b|\\bconst\\b|\\bimplicit\\b|\\bref\\b|\\bushort\\b|" +
|
||||
"\\bcontinue\\b|\\bin\\b|\\breturn\\b|\\busing\\b|\\bdecimal\\b|\\bint\\b|\\bsbyte\\b|\\bvirtual\\b|\\bdefault\\b|" +
|
||||
"\\binterface\\b|\\bsealed\\b|\\bvolatile\\b|\\bdelegate\\b|\\binternal\\b|\\bshort\\b|\\bvoid\\b|\\bdo\\b|\\bis\\b|" +
|
||||
"\\bsizeof\\b|\\bwhile\\b|\\bdouble\\b|\\block\\b|\\bstackalloc\\b|\\belse\\b|\\blong\\b|\\bstatic\\b|\\benum\\b|" +
|
||||
"\\bnamespace\\b|\\bstring\\b)";
|
||||
|
||||
static string keywords_vb =
|
||||
"(\\bAddHandler\\b|\\bAddressOf\\b|\\bAlias\\b|\\bAnd\\b|\\bAndAlso\\b|\\bAnsi\\b|\\bAs\\b|\\bAssembly\\b|" +
|
||||
"\\bAuto\\b|\\bBoolean\\b|\\bByRef\\b|\\bByte\\b|\\bByVal\\b|\\bCall\\b|\\bCase\\b|\\bCatch\\b|" +
|
||||
"\\bCBool\\b|\\bCByte\\b|\\bCChar\\b|\\bCDate\\b|\\bCDec\\b|\\bCDbl\\b|\\bChar\\b|\\bCInt\\b|" +
|
||||
"\\bClass\\b|\\bCLng\\b|\\bCObj\\b|\\bConst\\b|\\bCShort\\b|\\bCSng\\b|\\bCStr\\b|\\bCType\\b|" +
|
||||
"\\bDate\\b|\\bDecimal\\b|\\bDeclare\\b|\\bDefault\\b|\\bDelegate\\b|\\bDim\\b|\\bDirectCast\\b|\\bDo\\b|" +
|
||||
"\\bDouble\\b|\\bEach\\b|\\bElse\\b|\\bElseIf\\b|\\bEnd\\b|\\bEnum\\b|\\bErase\\b|\\bError\\b|" +
|
||||
"\\bEvent\\b|\\bExit\\b|\\bFalse\\b|\\bFinally\\b|\\bFor\\b|\\bFriend\\b|\\bFunction\\b|\\bGet\\b|" +
|
||||
"\\bGetType\\b|\\bGoSub\\b|\\bGoTo\\b|\\bHandles\\b|\\bIf\\b|\\bImplements\\b|\\bImports\\b|\\bIn\\b|" +
|
||||
"\\bInherits\\b|\\bInteger\\b|\\bInterface\\b|\\bIs\\b|\\bLet\\b|\\bLib\\b|\\bLike\\b|\\bLong\\b|" +
|
||||
"\\bLoop\\b|\\bMe\\b|\\bMod\\b|\\bModule\\b|\\bMustInherit\\b|\\bMustOverride\\b|\\bMyBase\\b|\\bMyClass\\b|" +
|
||||
"\\bNamespace\\b|\\bNew\\b|\\bNext\\b|\\bNot\\b|\\bNothing\\b|\\bNotInheritable\\b|\\bNotOverridable\\b|\\bObject\\b|" +
|
||||
"\\bOn\\b|\\bOption\\b|\\bOptional\\b|\\bOr\\b|\\bOrElse\\b|\\bOverloads\\b|\\bOverridable\\b|\\bOverrides\\b|" +
|
||||
"\\bParamArray\\b|\\bPreserve\\b|\\bPrivate\\b|\\bProperty\\b|\\bProtected\\b|\\bPublic\\b|\\bRaiseEvent\\b|\\bReadOnly\\b|" +
|
||||
"\\bReDim\\b|\\bREM\\b|\\bRemoveHandler\\b|\\bResume\\b|\\bReturn\\b|\\bSelect\\b|\\bSet\\b|\\bShadows\\b|" +
|
||||
"\\bShared\\b|\\bShort\\b|\\bSingle\\b|\\bStatic\\b|\\bStep\\b|\\bStop\\b|\\bString\\b|\\bStructure\\b|" +
|
||||
"\\bSub\\b|\\bSyncLock\\b|\\bThen\\b|\\bThrow\\b|\\bTo\\b|\\bTrue\\b|\\bTry\\b|\\bTypeOf\\b|" +
|
||||
"\\bUnicode\\b|\\bUntil\\b|\\bVariant\\b|\\bWhen\\b|\\bWhile\\b|\\bWith\\b|\\bWithEvents\\b|\\bWriteOnly\\b|\\bXor\\b)";
|
||||
|
||||
string Colorize (string text, string lang)
|
||||
{
|
||||
if (lang == "xml") return ColorizeXml (text);
|
||||
else if (lang == "cs") return ColorizeCs (text);
|
||||
else if (lang == "vb") return ColorizeVb (text);
|
||||
else return text;
|
||||
}
|
||||
|
||||
string ColorizeXml (string text)
|
||||
{
|
||||
text = text.Replace (" ", " ");
|
||||
Regex re = new Regex ("\r\n|\r|\n");
|
||||
text = re.Replace (text, "_br_");
|
||||
|
||||
re = new Regex ("<\\s*(\\/?)\\s*([\\s\\S]*?)\\s*(\\/?)\\s*>");
|
||||
text = re.Replace (text,"{blue:<$1}{maroon:$2}{blue:$3>}");
|
||||
|
||||
re = new Regex ("\\{(\\w*):([\\s\\S]*?)\\}");
|
||||
text = re.Replace (text,"<span style='color:$1'>$2</span>");
|
||||
|
||||
re = new Regex ("\"(.*?)\"");
|
||||
text = re.Replace (text,"\"<span style='color:purple'>$1</span>\"");
|
||||
|
||||
|
||||
text = text.Replace ("\t", " ");
|
||||
text = text.Replace ("_br_", "<br>");
|
||||
return text;
|
||||
}
|
||||
|
||||
string ColorizeCs (string text)
|
||||
{
|
||||
text = text.Replace (" ", " ");
|
||||
|
||||
text = text.Replace ("<", "<");
|
||||
text = text.Replace (">", ">");
|
||||
|
||||
Regex re = new Regex ("\"((((?!\").)|\\\")*?)\"");
|
||||
text = re.Replace (text,"<span style='color:purple'>\"$1\"</span>");
|
||||
|
||||
re = new Regex ("//(((.(?!\"</span>))|\"(((?!\").)*)\"</span>)*)(\r|\n|\r\n)");
|
||||
text = re.Replace (text,"<span style='color:green'>//$1</span><br/>");
|
||||
|
||||
re = new Regex (keywords_cs);
|
||||
text = re.Replace (text,"<span style='color:blue'>$1</span>");
|
||||
|
||||
text = text.Replace ("\t"," ");
|
||||
text = text.Replace ("\n","<br/>");
|
||||
|
||||
return text;
|
||||
}
|
||||
|
||||
string ColorizeVb (string text)
|
||||
{
|
||||
text = text.Replace (" ", " ");
|
||||
|
||||
/* Regex re = new Regex ("\"((((?!\").)|\\\")*?)\"");
|
||||
text = re.Replace (text,"<span style='color:purple'>\"$1\"</span>");
|
||||
|
||||
re = new Regex ("'(((.(?!\"\\<\\/span\\>))|\"(((?!\").)*)\"\\<\\/span\\>)*)(\r|\n|\r\n)");
|
||||
text = re.Replace (text,"<span style='color:green'>//$1</span><br/>");
|
||||
|
||||
re = new Regex (keywords_vb);
|
||||
text = re.Replace (text,"<span style='color:blue'>$1</span>");
|
||||
*/
|
||||
text = text.Replace ("\t"," ");
|
||||
text = text.Replace ("\n","<br/>");
|
||||
return text;
|
||||
}
|
||||
|
||||
//
|
||||
// Helper methods and classes
|
||||
//
|
||||
|
||||
string GetDataContext ()
|
||||
{
|
||||
return "op=" + CurrentOperationName + "&bnd=" + CurrentOperationBinding + "&";
|
||||
}
|
||||
|
||||
string GetOptionSel (string v1, string v2)
|
||||
{
|
||||
string op = "<option ";
|
||||
if (v1 == v2) op += "selected ";
|
||||
return op + "value='" + v1 + "'>";
|
||||
}
|
||||
|
||||
string WrapText (string text, int maxChars)
|
||||
{
|
||||
text = text.Replace(" />","/>");
|
||||
|
||||
string linspace = null;
|
||||
int lincount = 0;
|
||||
int breakpos = 0;
|
||||
int linstart = 0;
|
||||
bool inquotes = false;
|
||||
char lastc = ' ';
|
||||
string sublineIndent = "";
|
||||
System.Text.StringBuilder sb = new System.Text.StringBuilder ();
|
||||
for (int n=0; n<text.Length; n++)
|
||||
{
|
||||
char c = text [n];
|
||||
|
||||
if (c=='\r' || c=='\n' || n==text.Length-1)
|
||||
{
|
||||
sb.Append (linspace + sublineIndent + text.Substring (linstart, n-linstart+1));
|
||||
linspace = null;
|
||||
lincount = 0;
|
||||
linstart = n+1;
|
||||
breakpos = linstart;
|
||||
sublineIndent = "";
|
||||
lastc = c;
|
||||
continue;
|
||||
}
|
||||
|
||||
if (lastc==',' || lastc=='(')
|
||||
{
|
||||
if (!inquotes) breakpos = n;
|
||||
}
|
||||
|
||||
if (lincount > maxChars && breakpos >= linstart)
|
||||
{
|
||||
if (linspace != null)
|
||||
sb.Append (linspace + sublineIndent);
|
||||
sb.Append (text.Substring (linstart, breakpos-linstart));
|
||||
sb.Append ("\n");
|
||||
sublineIndent = " ";
|
||||
lincount = linspace.Length + sublineIndent.Length + (n-breakpos);
|
||||
linstart = breakpos;
|
||||
}
|
||||
|
||||
if (c==' ' || c=='\t')
|
||||
{
|
||||
if (!inquotes)
|
||||
breakpos = n;
|
||||
}
|
||||
else if (c=='"')
|
||||
{
|
||||
inquotes = !inquotes;
|
||||
}
|
||||
else
|
||||
if (linspace == null) {
|
||||
linspace = text.Substring (linstart, n-linstart);
|
||||
linstart = n;
|
||||
}
|
||||
|
||||
lincount++;
|
||||
lastc = c;
|
||||
}
|
||||
return sb.ToString ();
|
||||
}
|
||||
|
||||
class Parameter
|
||||
{
|
||||
string name;
|
||||
string type;
|
||||
string description;
|
||||
|
||||
public string Name { get { return name; } set { name = value; } }
|
||||
public string Type { get { return type; } set { type = value; } }
|
||||
public string Description { get { return description; } set { description = value; } }
|
||||
}
|
||||
|
||||
</script>
|
||||
|
||||
<head>
|
||||
<title><%=WebServiceName%> Web Service</title>
|
||||
<style type="text/css">
|
||||
BODY { font-family: Arial; margin-left: 20px; margin-top: 20px; font-size: x-small}
|
||||
TABLE { font-size: x-small }
|
||||
.title { color:dimgray; font-family: Arial; font-size:20pt; font-weight:900}
|
||||
.operationTitle { color:dimgray; font-family: Arial; font-size:15pt; font-weight:900}
|
||||
.method { font-size: x-small }
|
||||
.bindingLabel { font-size: x-small; font-weight:bold; color:darkgray; line-height:8pt; display:block; margin-bottom:3px }
|
||||
.label { font-size: small; font-weight:bold; color:darkgray }
|
||||
.paramTable { font-size: x-small }
|
||||
.paramTable TR { background-color: gainsboro }
|
||||
.paramFormTable { font-size: x-small; padding: 10px; background-color: gainsboro }
|
||||
.paramFormTable TR { background-color: gainsboro }
|
||||
.paramInput { border: solid 1px gray }
|
||||
.button {border: solid 1px gray }
|
||||
.smallSeparator { height:3px; overflow:hidden }
|
||||
.panel { background-color:whitesmoke; border: solid 1px silver; border-top: solid 1px silver }
|
||||
.codePanel { background-color: white; font-size:x-small; padding:7px; border:solid 1px silver}
|
||||
.code-xml { font-size:10pt; font-family:courier }
|
||||
.code-cs { font-size:10pt; font-family:courier }
|
||||
.code-vb { font-size:10pt; font-family:courier }
|
||||
.tabLabelOn { font-weight:bold }
|
||||
.tabLabelOff {color: darkgray }
|
||||
A:link { color: black; }
|
||||
A:visited { color: black; }
|
||||
A:active { color: black; }
|
||||
A:hover { color: blue }
|
||||
</style>
|
||||
|
||||
<script>
|
||||
function clearForm ()
|
||||
{
|
||||
document.getElementById("testFormResult").style.display="none";
|
||||
}
|
||||
</script>
|
||||
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<div class="title" style="margin-left:20px">
|
||||
<span class="label">Web Service</span><br>
|
||||
<%=WebServiceName%>
|
||||
</div>
|
||||
|
||||
<!--
|
||||
**********************************************************
|
||||
Left panel
|
||||
-->
|
||||
|
||||
<table border="0" width="100%" cellpadding="15px" cellspacing="15px">
|
||||
<tr valign="top"><td width="150px" class="panel">
|
||||
<div style="width:150px"></div>
|
||||
<a class="method" href='<%=PageName%>'>Overview</a><br>
|
||||
<div class="smallSeparator"></div>
|
||||
<a class="method" href='<%=PageName + "?" + GetPageContext("wsdl")%>'>Service Description</a>
|
||||
<div class="smallSeparator"></div>
|
||||
<a class="method" href='<%=PageName + "?" + GetPageContext("proxy")%>'>Client proxy</a>
|
||||
<br><br>
|
||||
<asp:repeater id="BindingsRepeater" runat=server>
|
||||
<itemtemplate name="itemtemplate">
|
||||
<span class="bindingLabel"><%#FormatBindingName(DataBinder.Eval(Container.DataItem, "Name").ToString())%></span>
|
||||
<asp:repeater id="OperationsRepeater" runat=server datasource='<%# ((Binding)Container.DataItem).Operations %>'>
|
||||
<itemtemplate>
|
||||
<a class="method" href="<%#PageName%>?<%#GetTabContext("op",null)%>op=<%#GetOpName(Container.DataItem)%>&bnd=<%#DataBinder.Eval(Container.DataItem, "Binding.Name")%>"><%#GetOpName(Container.DataItem)%></a>
|
||||
<div class="smallSeparator"></div>
|
||||
</itemtemplate>
|
||||
</asp:repeater>
|
||||
<br>
|
||||
</itemtemplate>
|
||||
</asp:repeater>
|
||||
|
||||
</td><td class="panel">
|
||||
|
||||
<% if (CurrentPage == "main") {%>
|
||||
|
||||
<!--
|
||||
**********************************************************
|
||||
Web service overview
|
||||
-->
|
||||
|
||||
<p class="label">Web Service Overview</p>
|
||||
<%#WebServiceDescription%>
|
||||
|
||||
<%} if (CurrentPage == "op") {%>
|
||||
|
||||
<!--
|
||||
**********************************************************
|
||||
Operation description
|
||||
-->
|
||||
|
||||
<span class="operationTitle"><%#CurrentOperationName%></span>
|
||||
<br><br>
|
||||
<% WriteTabs (); %>
|
||||
<br><br><br>
|
||||
|
||||
<% if (CurrentTab == "main") { %>
|
||||
<span class="label">Input Parameters</span>
|
||||
<div class="smallSeparator"></div>
|
||||
<% if (InParams.Count == 0) { %>
|
||||
No input parameters<br>
|
||||
<% } else { %>
|
||||
<table class="paramTable" cellspacing="1" cellpadding="5">
|
||||
<asp:repeater id="InputParamsRepeater" runat=server>
|
||||
<itemtemplate>
|
||||
<tr>
|
||||
<td width="150"><%#DataBinder.Eval(Container.DataItem, "Name")%></td>
|
||||
<td width="150"><%#DataBinder.Eval(Container.DataItem, "Type")%></td>
|
||||
</tr>
|
||||
</itemtemplate>
|
||||
</asp:repeater>
|
||||
</table>
|
||||
<% } %>
|
||||
<br>
|
||||
|
||||
<% if (OutParams.Count > 0) { %>
|
||||
<span class="label">Output Parameters</span>
|
||||
<div class="smallSeparator"></div>
|
||||
<table class="paramTable" cellspacing="1" cellpadding="5">
|
||||
<asp:repeater id="OutputParamsRepeater" runat=server>
|
||||
<itemtemplate>
|
||||
<tr>
|
||||
<td width="150"><%#DataBinder.Eval(Container.DataItem, "Name")%></td>
|
||||
<td width="150"><%#DataBinder.Eval(Container.DataItem, "Type")%></td>
|
||||
</tr>
|
||||
</itemtemplate>
|
||||
</asp:repeater>
|
||||
</table>
|
||||
<br>
|
||||
<% } %>
|
||||
|
||||
<span class="label">Remarks</span>
|
||||
<div class="smallSeparator"></div>
|
||||
<%#OperationDocumentation%>
|
||||
<br><br>
|
||||
<span class="label">Technical information</span>
|
||||
<div class="smallSeparator"></div>
|
||||
Format: <%#CurrentOperationFormat%>
|
||||
<br>Supported protocols: <%#CurrentOperationProtocols%>
|
||||
<% } %>
|
||||
|
||||
<% if (CurrentTab == "test") {
|
||||
if (CurrentOperationSupportsTest) {%>
|
||||
Enter values for the parameters and click the 'Invoke' button to test this method:<br><br>
|
||||
<form action="<%#PageName%>" method="GET">
|
||||
<input type="hidden" name="page" value="<%#CurrentPage%>">
|
||||
<input type="hidden" name="tab" value="<%#CurrentTab%>">
|
||||
<input type="hidden" name="op" value="<%#CurrentOperationName%>">
|
||||
<input type="hidden" name="bnd" value="<%#CurrentOperationBinding%>">
|
||||
<input type="hidden" name="ext" value="testform">
|
||||
<table class="paramFormTable" cellspacing="0" cellpadding="3">
|
||||
<asp:repeater id="InputFormParamsRepeater" runat=server>
|
||||
<itemtemplate>
|
||||
<tr>
|
||||
<td><%#DataBinder.Eval(Container.DataItem, "Name")%>: </td>
|
||||
<td width="150"><input class="paramInput" type="text" size="20" name="<%#DataBinder.Eval(Container.DataItem, "Name")%>"></td>
|
||||
</tr>
|
||||
</itemtemplate>
|
||||
</asp:repeater>
|
||||
<tr><td></td><td><input class="button" type="submit" value="Invoke"> <input class="button" type="button" onclick="clearForm()" value="Clear"></td></tr>
|
||||
</table>
|
||||
</form>
|
||||
<div id="testFormResult" style="display:<%# (HasFormResult?"block":"none") %>">
|
||||
The web service returned the following result:<br/><br/>
|
||||
<div class="codePanel"><%#GetTestResult()%></div>
|
||||
</div>
|
||||
<% } else {%>
|
||||
The test form is not available for this operation because it has parameters with a complex structure.
|
||||
<% } %>
|
||||
<% } %>
|
||||
<% if (CurrentTab == "msg") { %>
|
||||
TODO
|
||||
<% } %>
|
||||
<%}%>
|
||||
|
||||
<% if (CurrentPage == "proxy") {%>
|
||||
<!--
|
||||
**********************************************************
|
||||
Client Proxy
|
||||
-->
|
||||
<form action="<%#PageName%>" name="langForm" method="GET">
|
||||
Select the language for which you want to generate a proxy
|
||||
<input type="hidden" name="page" value="<%#CurrentPage%>">
|
||||
<SELECT name="lang" onchange="langForm.submit()">
|
||||
<%#GetOptionSel("cs",CurrentLanguage)%>C#</option>
|
||||
<%#GetOptionSel("vb",CurrentLanguage)%>Visual Basic</option>
|
||||
</SELECT>
|
||||
|
||||
</form>
|
||||
<br>
|
||||
<span class="label"><%#CurrentProxytName%></span>
|
||||
<a href="<%#PageName + "?code=" + CurrentLanguage%>">Download</a>
|
||||
<br><br>
|
||||
<div class="codePanel">
|
||||
<div class="code-<%#CurrentLanguage%>"><%#GetProxyCode ()%></div>
|
||||
</div>
|
||||
<%}%>
|
||||
|
||||
<% if (CurrentPage == "wsdl") {%>
|
||||
<!--
|
||||
**********************************************************
|
||||
Service description
|
||||
-->
|
||||
<% if (descriptions.Count > 1 || schemas.Count > 1) {%>
|
||||
The description of this web service is composed by several documents. Click on the document you want to see:
|
||||
|
||||
<ul>
|
||||
<%
|
||||
for (int n=0; n<descriptions.Count; n++)
|
||||
Response.Write ("<li><a href='" + PageName + "?" + GetPageContext(null) + "doctype=wsdl&docind=" + n + "'>WSDL document " + descriptions[n].TargetNamespace + "</a></li>");
|
||||
for (int n=0; n<schemas.Count; n++)
|
||||
Response.Write ("<li><a href='" + PageName + "?" + GetPageContext(null) + "doctype=schema&docind=" + n + "'>Xml Schema " + schemas[n].TargetNamespace + "</a></li>");
|
||||
%>
|
||||
</ul>
|
||||
|
||||
<%} else {%>
|
||||
<%}%>
|
||||
<br>
|
||||
<span class="label"><%#CurrentDocumentName%></span>
|
||||
<a href="<%=PageName + "?" + CurrentDocType + "=" + CurrentDocInd %>">Download</a>
|
||||
<br><br>
|
||||
<div class="codePanel">
|
||||
<div class="code-xml"><%#GenerateDocument ()%></div>
|
||||
</div>
|
||||
|
||||
<%}%>
|
||||
|
||||
<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br>
|
||||
</td>
|
||||
<td withd="20px"></td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
</body>
|
||||
</html>
|
||||
+7
-2
@@ -1,6 +1,11 @@
|
||||
monodir = $(sysconfdir)/mono
|
||||
|
||||
EXTRA_DIST = config.in machine.config DefaultWsdlHelpGenerator.aspx
|
||||
EXTRA_DIST = config.in machine.config
|
||||
|
||||
mono_DATA = config machine.config DefaultWsdlHelpGenerator.aspx
|
||||
mono_DATA = config machine.config
|
||||
|
||||
DISTCLEANFILES = config
|
||||
|
||||
config: config.in Makefile
|
||||
sed -e 's^\@LIBC\@^libc.so.6^g' < $(srcdir)/config.in > config.tmp \
|
||||
&& mv config.tmp config
|
||||
@@ -6,7 +6,6 @@
|
||||
<dllmap dll="odbc32.dll" target="libodbc.so" />
|
||||
<dllmap dll="libglib-2.0-0.dll" target="libglib-2.0.so" />
|
||||
<dllmap dll="libgobject-2.0-0.dll" target="libgobject-2.0.so" />
|
||||
<dllmap dll="libgthread-2.0-0.dll" target="libgthread-2.0.so" />
|
||||
<dllmap dll="libpango-1.0-0.dll" target="libpango-1.0.so" />
|
||||
<dllmap dll="libatk-1.0-0.dll" target="libatk-1.0.so" />
|
||||
<dllmap dll="libgdk-win32-2.0-0.dll" target="libgdk-x11-2.0.so" />
|
||||
@@ -16,5 +15,4 @@
|
||||
<dllmap dll="libglade-2.0-0.dll" target="libglade-2.0.so" />
|
||||
<dllmap dll="oci" target="clntsh" />
|
||||
<dllmap dll="gtkhtml-3.0" target="libgtkhtml-3.0.so.2" />
|
||||
<dllmap dll="db2cli" target="libdb2_36.so"/>
|
||||
</configuration>
|
||||
+6
-94
@@ -3,9 +3,9 @@
|
||||
<configuration>
|
||||
|
||||
<configSections>
|
||||
<section name="appSettings" type="System.Configuration.NameValueFileSectionHandler, System" />
|
||||
<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" />
|
||||
@@ -21,18 +21,8 @@
|
||||
type="System.Web.Configuration.GlobalizationConfigurationHandler, System.Web" />
|
||||
<section name="sessionState"
|
||||
type="System.Web.SessionState.SessionStateSectionHandler, System.Web" />
|
||||
<section name="webServices"
|
||||
type="System.Web.Services.Configuration.WebServicesConfigurationSectionHandler, System.Web.Services" />
|
||||
<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" />
|
||||
</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"
|
||||
@@ -42,7 +32,6 @@
|
||||
<section name="webRequestModules"
|
||||
type="System.Net.Configuration.WebRequestModuleHandler, System" />
|
||||
</sectionGroup>
|
||||
<section name="system.drawing" type="System.Configuration.NameValueSectionHandler" />
|
||||
</configSections>
|
||||
<system.net>
|
||||
<connectionManagement>
|
||||
@@ -61,23 +50,13 @@
|
||||
<add prefix="https" type="System.Net.HttpRequestCreator, System" />
|
||||
<add prefix="file" type="System.Net.FileWebRequestCreator, System" />
|
||||
</webRequestModules>
|
||||
<settings>
|
||||
<ipv6 enabled="false"/>
|
||||
</settings>
|
||||
</system.net>
|
||||
<system.web>
|
||||
<httpHandlers>
|
||||
<add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web" />
|
||||
<add verb="*" path="*.asmx" validate="false"
|
||||
type="System.Web.Services.Protocols.WebServiceHandlerFactory, System.Web.Services" />
|
||||
<add verb="*" path="*.ashx" type="System.Web.UI.SimpleHandlerFactory, System.Web" />
|
||||
<add verb="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>
|
||||
@@ -85,7 +64,6 @@
|
||||
<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="/">
|
||||
@@ -95,79 +73,16 @@
|
||||
</forms>
|
||||
</authentication>
|
||||
<machineKey validationKey="AutoGenerate" decryptionKey="AutoGenerate" validation="SHA1" />
|
||||
<globalization requestEncoding="utf-8"
|
||||
responseEncoding="utf-8"
|
||||
fileEncoding="utf-8"/>
|
||||
<!--
|
||||
<!-- Sample globalization settings
|
||||
<globalization requestEncoding="iso-8859-1"
|
||||
responseEncoding="iso-8859-1"
|
||||
fileEncoding="iso-8859-1"
|
||||
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" />
|
||||
</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" /> -->
|
||||
@@ -176,8 +91,5 @@
|
||||
<system.diagnostics>
|
||||
<trace autoflush="false" indentsize="4" />
|
||||
</system.diagnostics>
|
||||
<system.drawing>
|
||||
</system.drawing>
|
||||
</configuration>
|
||||
|
||||
|
||||
+3
-3
@@ -8,7 +8,7 @@ WEB_FILES= \
|
||||
tds-providers status testing thanks tools \
|
||||
porting anoncvs monodoc-xml winforms
|
||||
|
||||
OTHERS= pending resources-pending todo mono-build.sh mono-build-w32.sh print-stack
|
||||
OTHERS= pending resources-pending todo mono-build.sh mono-build-w32.sh
|
||||
|
||||
EXTRA_DIST = $(WEB_FILES) README $(OTHERS)
|
||||
|
||||
@@ -17,8 +17,8 @@ all-docs: $(WEB_FILES)
|
||||
runtime documentation download faq contributing \
|
||||
resources status > all-docs
|
||||
|
||||
class-status: class-status.in Makefile.am
|
||||
cat class-status.in > class-status
|
||||
class-status: class-status.in pending-classes Makefile.am
|
||||
cat class-status.in pending-classes > class-status
|
||||
|
||||
pending-classes:
|
||||
|
||||
|
||||
+99
-38
@@ -1,22 +1,82 @@
|
||||
* ADO.NET
|
||||
|
||||
** Data Access in Mono
|
||||
<p>Mono's ADO.NET Developers:
|
||||
|
||||
<ul>
|
||||
<li>Today, our goal is to be compatible with .NET 1.0 and .NET 1.1. We also would like
|
||||
to extend data access beyond what is included with .NET 1.0 and .NET 1.1,
|
||||
such as, including access to more databases, such as, PostgreSQL and MySQL,
|
||||
but also provide classes that help in creating data source-agnostic code, such as, Mono.Data.ProviderFactory.</li>
|
||||
<li>In the future, we would like to be compatible with .NET 1.2. This
|
||||
would include features like:
|
||||
<ul>
|
||||
<li><a href="http://longhorn.msdn.microsoft.com/lhsdk/ndp/daconworkingwithobjectspacesarchitecture.aspx">ObjectSpaces</a></li>
|
||||
<li>provide support for hosting Mono languages (C-Sharp, MonoBASIC, etc...)
|
||||
within a DBMS engine, such as, MySQL or PostgreSQL.</li>
|
||||
<li>implement .net 1.2 classes, such as, those found in System.Data.ProviderBase</li>
|
||||
<li>other stuff which can be brought up on the mono-list</li>
|
||||
</ul></li>
|
||||
</ul>
|
||||
<table border=1>
|
||||
|
||||
<tr>
|
||||
<td><b>Developer</b></td>
|
||||
<td><b>Email</b></td>
|
||||
<td><b>Contribution</b></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Rodrigo Moya</td>
|
||||
<td>rodrigo -AT-<br> ximian.comNOSPAM</td>
|
||||
<td>ADO.NET coordinator,<br> OLE DB provider,<br> and tests</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Daniel Morgan</td>
|
||||
<td>danmorg -AT-<br> sc.rr.comNOSPAM</td>
|
||||
<td>MySQL, PostgreSQL, <br>Oracle providers,<br> and tests</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Tim Coleman</td>
|
||||
<td>tim -AT- <br>timcoleman.comNOSPAM</td>
|
||||
<td>Microsoft SQL Server, <br>Sybase, <br>TDS providers,<br> Oracle,
|
||||
<br>and tests.<br>
|
||||
He has
|
||||
contributed <br>to other parts <br>of Mono too, <br>such as,
|
||||
<br>EnterpriseServices,
|
||||
XML, <br>and WebServices.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Brian Ritchie</td>
|
||||
<td>brianlritchie -AT-<br> hotmail.comNOSPAM</td>
|
||||
<td>ODBC provider <br>and the ProviderFactory <br>in Mono.Data</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Vladimir Vukicevic</td>
|
||||
<td>vladimir -AT-<br> pobox.comNOSPAM</td>
|
||||
<td>SQL Lite provider. <br> He has contributed to GTK# <br>and mPhoto too.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Christopher Bockner</td>
|
||||
<td>cleared -AT-<br> rogers.comNOSPAM</td>
|
||||
<td>IBM DB2 Universal <br>Database provider</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Ville Palo</td>
|
||||
<td>vi64pa -AT-<br> koti.soon.fiNOSPAM</td>
|
||||
<td>XML stuff <br>in System.Data <br>including DataSet <br>
|
||||
and XmlDataDocument, <br>and tests</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Gonzalo Paniagua Javier</td>
|
||||
<td>gonzalo -AT-<br> ximian.comNOSPAM</td>
|
||||
<td>Integration between <br>System.Web and <br>System.Data</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Gaurav Vaish</td>
|
||||
<td>gvaish -AT-<br> iitk.ac.inNOSPAM</td>
|
||||
<td>Web controls</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Phillip Jerkins</td>
|
||||
<td>Phillip.Jerkins -AT-<br> morgankeegan.comNOSPAM</td>
|
||||
<td>Named Instance support <br>in System.Data.SqlClient</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
** Bugs and Feature Requests
|
||||
|
||||
@@ -28,14 +88,14 @@
|
||||
and easy to create
|
||||
one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
|
||||
|
||||
<li>Any requests for new features or missing functionality
|
||||
can entered as a bug in Bugzilla too</li>
|
||||
<li>Any RFE (Request For Enhancement) for features missing or new functionality
|
||||
should be entered as a bug in Bugzilla too</li>
|
||||
|
||||
</ul>
|
||||
|
||||
** ADO.NET Data Providers
|
||||
|
||||
<p>Mono has many ADO.NET Data Providers to get you connected:
|
||||
<p>List of ADO.NET Data Providers working in Mono:
|
||||
|
||||
<ul>
|
||||
<li><a href="http://www.go-mono.com/ibmdb2.html">IBM DB2 Universal Database</a></li>
|
||||
@@ -87,38 +147,39 @@
|
||||
<p>Some tools that can be used for ADO.NET and other technologies (ASP.NET, XML, etc).
|
||||
|
||||
<ul>
|
||||
<li><p><b>SQL# command line query tool</b> is a command-line tool to
|
||||
enter and execute SQL statements or
|
||||
execute a batch of SQL commands from a file.
|
||||
<p>It can
|
||||
<li><b>SQL# CLI</b> - a SQL query tool with a command-line interface.
|
||||
It can be used to enter and execute SQL statements or
|
||||
execute a batch of SQL commands from a file. It can
|
||||
be used to test connection strings, connect to various ADO.NET
|
||||
providers, save output to text, html, or xml.
|
||||
<p>The SQL# CLI is distributed with the
|
||||
providers, save output to text, html, or xml. It is a work-in-progress.
|
||||
The SQL# CLI is distributed with the
|
||||
Mono runtime and class libraries as an executable assembly sqlsharp.exe.
|
||||
<p>The source to SQL# CLI can be found in the mcs source at
|
||||
The source to SQL# CLI can be found in the mcs source at
|
||||
mcs/tools/SqlSharp/SqlSharpCli.cs
|
||||
</li>
|
||||
|
||||
<li><p><b>SQL# For GTK#</b> - is a graphical SQL database query tool</b> allows a user
|
||||
to enter SQL commands in a top panel which is a text editor.
|
||||
<p>It has a toolbar and menu for various tasks, such as, executing
|
||||
<li><p><b>SQL# GUI - a graphical SQL query tool</b> allows a user
|
||||
to enter SQL commands in a top panel which is a text editor. It
|
||||
has a toolbar and menu for various tasks, such as, executing
|
||||
SQL commands one-at-a-time or in a batch. The results would appear
|
||||
in a bottom panel in a grid or could be saved to a file (xml, html, csv).
|
||||
<p>Also, the bottom panel would allow logging of SQL command executed.
|
||||
Here is a screenshot of <a href="http://go-mono.com/images/sqlsharp.png">SQL# For GTK#</a> which
|
||||
provides a GUI interface using the <a href="http://gtk-sharp.sourceforge.net">Gtk#</a> toolkit.
|
||||
<p>SQL# For GTK# can be found in mono cvs as sqlsharpgtk.</li>
|
||||
Also, the bottom panel would allow logging of SQL command executed.
|
||||
Currently, there is a <a href="http://go-mono.com/images/sqlsharp.png">SQL# For GTK#</a> which
|
||||
provides a GUI interface using the <a href="http://gtk-sharp.sourceforge.net">Gtk#</a> toolkit. SQL# For GTK#
|
||||
is a work-in-progress and can be found in the mcs source at
|
||||
mcs/tools/SqlSharp/gui/gtk-sharp</li>
|
||||
</ul>
|
||||
|
||||
<p>Tools we would like to have, but they have not been created yet:
|
||||
|
||||
<ul>
|
||||
<li>Mono has an <b>XML Schema Definition tool</b> (xsd.exe).</b>
|
||||
|
||||
<li><b>XML Schema Definition tool</b> <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/html/cpconxmlschemadefinitiontoolxsdexe.asp">xsd.exe</a> needs
|
||||
to be created. Maybe this TODO item should be at the System.XML web page instead.
|
||||
|
||||
<ul>
|
||||
<li>This tool
|
||||
would works like the xsd.exe tool included with
|
||||
the .NET Framework. The Xsd.exe tool has the
|
||||
would work like the xsd.exe tool included with
|
||||
the .NET Framework. The Xsd.exe tools has the
|
||||
following uses:
|
||||
<ul>
|
||||
<li><b>XDR to XSD</b> - used to generate an XML schema from an XDR (XML Data Reduced schema) file.
|
||||
@@ -269,7 +330,7 @@
|
||||
Mike Kestner or Rachel Hestilov would be the best people to ask for help on GTK#.
|
||||
|
||||
<p><b>Integration with QT#</b> has not been started. Any information on
|
||||
how this can be done is appreciated. Marcus would be the best
|
||||
how this can be done is appreciated. Adam Treat would be the best
|
||||
person to ask about QT#.
|
||||
|
||||
<p><b>Building System.Data</b>
|
||||
|
||||
+1
-4
@@ -2,7 +2,7 @@
|
||||
|
||||
Anonymous access to the Mono is available currently from three
|
||||
servers (anoncvs-spain-1.go-mono.com,
|
||||
anoncvs-spain-2.go-mono.com and us-anoncvs.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.
|
||||
@@ -43,9 +43,6 @@
|
||||
Special thanks to Jesus Climent, Rodrigo Moya, Juantomás
|
||||
García and Ismael Olea for making this happen.
|
||||
|
||||
Thanks to Matt Liotta of MontaraSoftware for hosting our
|
||||
US-based AnonCVS server.
|
||||
|
||||
<a name="#mirror">
|
||||
** Becoming an AnonCVS mirror
|
||||
|
||||
|
||||
+58
-50
@@ -7,79 +7,52 @@
|
||||
* Web Services (the SOAP-based rpc system).
|
||||
</ul>
|
||||
|
||||
Both are functional at this point, and applications like
|
||||
"IBuySpy" run with Mono.
|
||||
There is work underway for both systems. The Web Forms
|
||||
support is more advanced at this point, and various ".aspx"
|
||||
programs can be run using the Mono runtime, including IBuySpy.
|
||||
|
||||
ASP.NET works either embedded into
|
||||
our XSP server test server or the mod_mono Apache module.
|
||||
|
||||
We are now working on bug fixing and adding missing features
|
||||
We are now working bug fixing and adding missing features
|
||||
after making the whole pipeline compatible with MS.
|
||||
|
||||
Tim started work on the Web Services. After that, Lluis is in
|
||||
charge and has been working hard on them as part of our
|
||||
<a href="http://www.ximian.com/about_us/press_center/press_releases/index.html?pr=sourcegear">SourceGear</a> contract.
|
||||
|
||||
Web services are now supported and there are some samples in the
|
||||
XSP set of tests.
|
||||
Tim started work on the Web Services. Although we have a
|
||||
SoapFormatter as part of the remoting infrastructure already
|
||||
(contributed by Jesus), most people will be using the ASP.NET
|
||||
Web Services support. Work for the supporting class libraries
|
||||
just started recently.
|
||||
|
||||
** Hosting
|
||||
The major missing element is a complete XmlSerializer.
|
||||
|
||||
ASP.NET provides a hosting interface. Today we ship support
|
||||
for two different hosting mechanisms:
|
||||
<ul>
|
||||
* <a href="#xsp">XSP</a>: A light-weight C# web server.
|
||||
** HttpRuntime
|
||||
|
||||
* <a href="#mod_mono">mod_mono</a>: An apache module
|
||||
that can host the Mono runtime and the ASP.NET runtime
|
||||
</ul>
|
||||
Patrik has authored most of the HttpRuntime support (both on
|
||||
the System.Web and on the foundation).
|
||||
|
||||
<a name="xsp">
|
||||
** XSP
|
||||
|
||||
XSP is a simple web server written in C# that can be used to
|
||||
run your ASP.NET applications. The code is available from our
|
||||
<a href="download.html">download page</a> or from the <a
|
||||
href="anoncvs.html">Anonymous CVS</a> repository (module name:
|
||||
xsp)/.
|
||||
|
||||
This is where initial development of the .aspx/.ascx/.asax
|
||||
compiler to C# took place. That compiler is now integrated in
|
||||
System.Web classes mostly under System.Web.Compilation
|
||||
namespace. We added a new web server that works with mono and
|
||||
MS runtime and is being used to debug our classes. It resides
|
||||
in xsp/server.
|
||||
This is where initial development of the .aspx/.ascx/.asax compiler
|
||||
to C# took place. That compiler is now integrated in System.Web classes
|
||||
mostly under System.Web.Compilation namespace.
|
||||
|
||||
A couple of classes of this new server can be reused/extended
|
||||
to make an apache module/cgi using mono (MonoWorkerRequest and
|
||||
MonoApplicationHost). This server also uses a couple of
|
||||
plugins distributed with Mono to support gzip HTTP transfers.
|
||||
We added a new web server that works with mono and MS runtime and is
|
||||
being used to debug our classes. It resides in xsp/server. A couple of
|
||||
classes of this new server can be reused/extended to make an apache
|
||||
module/cgi using mono (MonoWorkerRequest and MonoApplicationHost).
|
||||
|
||||
There is also a set of .aspx pages to test the server along with
|
||||
a few user controls under xsp/test.
|
||||
|
||||
You can check it out from CVS and run 'make install' to test it.
|
||||
|
||||
<a name="mod_mono">
|
||||
* mod_mono
|
||||
|
||||
This Apache module is available from our <a
|
||||
href="download.html">download page</a>. The <a href="anoncvs.html">
|
||||
cvs</a> module name is mod_mono. It works with both 1.3 and 2.0
|
||||
versions of the <a href="http://httpd.apache.org">apache server</a>.
|
||||
|
||||
It allows apache to serve ASP.NET pages.
|
||||
|
||||
Work is underway to improve it.
|
||||
|
||||
** Controls
|
||||
|
||||
A lot of work has been put in the various classes that
|
||||
implement the controls (UI.HtmlControls and UI.WebControls).
|
||||
They have been coded mostly in the dark, and without being
|
||||
implement the controls (UI.HtmlControls and UI.WebControls),
|
||||
but they have been coded mostly in the dark, and without being
|
||||
able to test them in real life: Gaurav and Leen worked very
|
||||
hard on this namespace. After that, we keep fixing bugs on
|
||||
them.
|
||||
hard on this namespace.
|
||||
|
||||
We can now render all HtmlControls and all WebControls.
|
||||
|
||||
@@ -90,6 +63,41 @@
|
||||
We want to encourage developers to create open source controls
|
||||
that can be used both on Mono's ASP.NET and Microsoft's ASP.NET.
|
||||
|
||||
* Web Forms: The pieces (historical)
|
||||
|
||||
There are a couple of components to the puzzle:
|
||||
|
||||
<ul>
|
||||
* .aspx page parser (converts .aspx to C# code).
|
||||
|
||||
* System.Web.HttpRuntime support.
|
||||
|
||||
* Web controls (System.Web.UI.HtmlControls and
|
||||
System.Web.UI.WebControls).
|
||||
|
||||
* Underlying infrastructure for the controls (System.Web.UI).
|
||||
|
||||
* HttpRuntime.ProcessRequest is the core of the ASP.NET
|
||||
implementation.
|
||||
</ul>
|
||||
|
||||
|
||||
Gonzalo has been working on an ASP.NET parser that takes .aspx
|
||||
files and generated the code required to run them (the code lives in
|
||||
module `xsp' along with a little web server for testing).
|
||||
|
||||
Most of the runtime support was written by Patrik Torstensson
|
||||
(now at Intel). This was interesting, because in order to implement
|
||||
some of its features, Patrik had to go into the runtime/JIT engine and
|
||||
he spent a few weeks doing work there.
|
||||
|
||||
The classes for running ASP.NET are being actively written.
|
||||
Gaurav, Leen and Patrik worked in the core of the classes
|
||||
required to run ASP.NET web application as well as a small
|
||||
embeddable web server.
|
||||
|
||||
Duncan got our System.Web assembly to compile.
|
||||
|
||||
** How to Help
|
||||
|
||||
Testing and fixing HtmlControls, WebControls and validators is an
|
||||
|
||||
@@ -1,38 +0,0 @@
|
||||
|
||||
You can read the aggregates news from the Mono developers in
|
||||
<a href="http://www.go-mono.com/monologue">Monologue</a>. You
|
||||
can also download our aggregator from the <a
|
||||
href="anoncvs.html">AnonCVS</a> server.
|
||||
|
||||
Various Mono contributors maintain blogs, some are listed here:
|
||||
|
||||
<a href="http://codeblogs.ximian.com/blogs/benm/index.rdf"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://codeblogs.ximian.com/blogs/benm/">Ben Maurer</a>
|
||||
<br>
|
||||
<a href="http://ada.fciencias.unam.mx/~olopez/jscript/cesar.rss2"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://ada.fciencias.unam.mx/~olopez/jscript/">Cesar Nataren</a>
|
||||
<br>
|
||||
<a href="http://www.jacksonh.net/jackson/blog/jackson.rss2"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://www.jacksonh.net/jackson/blog/">Jackson Harper</a>
|
||||
<br>
|
||||
<a href="http://primates.ximian.com/~lluis/blog/index.rdf"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://primates.ximian.com/~lluis/blog/">Lluis Sánchez</a>
|
||||
<br>
|
||||
<a href="http://primates.ximian.com/~martin/blog/rss.xml"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://primates.ximian.com/~martin/blog/">Martin Baulig</a>
|
||||
<br>
|
||||
<a href="http://primates.ximian.com/~miguel/miguel2.rss"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://primates.ximian.com/~miguel/activity-log.php">Miguel de Icaza</a>
|
||||
<br>
|
||||
<a href="http://primates.ximian.com/~mkestner/blog/index.rdf"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://primates.ximian.com/~mkestner/blog/">Mike Kestner</a>
|
||||
<br>
|
||||
<a href="http://pages.infinit.net/ctech/poupou.rss"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://pages.infinit.net/ctech/poupou.html">Sebastien Pouliot</a>
|
||||
<br>
|
||||
<a href="http://primates.ximian.com/~gonzalo/mono/blog/index.xml"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://primates.ximian.com/~gonzalo/mono/blog/">Gonzalo Paniagua</a>
|
||||
<br>
|
||||
<a href="http://codeblogs.ximian.com/blogs/ndrochak/index.rdf"><img align="center" src="images/xml.gif"></a>
|
||||
<a href="http://codeblogs.ximian.com/blogs/ndrochak/">Nick Drochak</a>
|
||||
|
||||
@@ -8,12 +8,6 @@
|
||||
|
||||
A Programmer's Introduction to C# - Second Edition: Eric Gunnerson
|
||||
|
||||
* .NET Framework
|
||||
|
||||
Avery good techincal book about .NET is Don Box's <a
|
||||
href="http://service.bfast.com/bfast/click?bfmid=2181&sourceid=39391960&isbn=0201734117">Essential
|
||||
.NET</a>
|
||||
|
||||
* Remoting
|
||||
|
||||
<a href="http://www.dotnetremoting.cc/book/AdvancedDotNetRemoting.asp">
|
||||
|
||||
@@ -1,69 +0,0 @@
|
||||
* Bug reporting
|
||||
|
||||
To report bugs you need to create a <a
|
||||
href="http://bugzilla.ximian.com/createaccount.cgi">Bugzilla
|
||||
Account</a>.
|
||||
|
||||
Here are some convenient shortcuts to browse or add bug reports.
|
||||
|
||||
<ul>
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&newqueryname=&form_name=query&order=bugs.priority%2C%20bugs.bug_id">[Query]</> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FClass%20Libraries">[Add]</a> Class Libraries
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FAssembler&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FAssembler">[Add]</a> IL Assembler.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FMCS&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FMCS">[Add]</a> C# Compiler.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FRuntime">[Add]</a> Runtime
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FDoctools&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FDoctools">[Add]</a> Documentation system.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=gtk%23&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=gtk%23">[Add]</a> Gtk#
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FDebugger&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">[Query]</a> <a href="http://bugzilla.ximian.com/enter_bug.cgi?product=Mono%2FDebugger">[Add]</a> Debugger.
|
||||
|
||||
* <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&product=Mono%2FMCS&product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=%27Importance%27&form_name=query">[Query]</a> All core components.
|
||||
</ul>
|
||||
|
||||
<a name="goodbugreport"/>
|
||||
** How to make good bug reports
|
||||
|
||||
<ol>
|
||||
* Submit a test case, the smaller it is, the better
|
||||
|
||||
* Use <a href="http://bugzilla.ximian.com">
|
||||
http://bugzilla.ximian.com</a> to report the bug.
|
||||
|
||||
<p>In <b>addition</b> to bugzilla, posting to the list is
|
||||
fine if the bug merits larger exposure or design
|
||||
discussions to solve; posting to the list twice or more
|
||||
is just a way to annoy people and make them waste time,
|
||||
specially when you start a new thread about it.
|
||||
|
||||
* If the test involves libraries or assemblies that are
|
||||
not part of mono, add info about where to download all
|
||||
the dependencies, and how to compile/install them.
|
||||
|
||||
* If compiling the test case requires more than:
|
||||
<pre> mcs test.cs </pre>
|
||||
provide the <b>full command line</b> you used to compile
|
||||
the test.
|
||||
|
||||
* If running the test requires more than:
|
||||
<pre> mono test.exe </pre>
|
||||
provide the <b>full command line</b> needed to replicate
|
||||
the bug.
|
||||
|
||||
* Provide info about the version of the software you're
|
||||
using (both mono and the operating system or relevant
|
||||
libraries).
|
||||
|
||||
* Provide the output you expect the test case to produce.
|
||||
|
||||
* Provide the actual output <b>you</b> get from the test case.
|
||||
</ol>
|
||||
|
||||
A good bug report complies with at least 6 items from the list.
|
||||
If your bug report complies with 3 or less items, it is very
|
||||
poor and it means it will take much more time to fix (when it's
|
||||
not ignored).
|
||||
|
||||
@@ -1,12 +1,7 @@
|
||||
* CVS Access
|
||||
|
||||
Here we describe how one obtains commit access to the Mono CVS
|
||||
repository and the responsibilities that come with that access
|
||||
privilege.
|
||||
|
||||
These only apply to the Mono CVS repository, and not to the <a
|
||||
href="http://forge.novell.com/modules/xfmod/community/?monocomm">Mono
|
||||
Community</a> repositories at Novell Forge.
|
||||
Here we describe how one obtains commit access to the CVS repository
|
||||
and the responsibilities that come with that access privilege.
|
||||
|
||||
** What is CVS?
|
||||
|
||||
@@ -28,13 +23,9 @@
|
||||
mailing lists and/or bugzilla for review.
|
||||
|
||||
If you are not a developer, but want to access the latest sources,
|
||||
please see the <a href="anoncvs.html">AnonCVS</a>
|
||||
instructions. If you are not a direct contributor to Mono,
|
||||
but want to host your .NET or Mono-based project, you can use
|
||||
<a href="forge.html">Novell Forge</a>.
|
||||
please see the <a href="anoncvs.html">AnonCVS</a> instructions.
|
||||
|
||||
|
||||
If you feel you are ready for a CVS account send an e-mail to
|
||||
If you feel you are ready for a CVS account send an e-mail to
|
||||
<a href="mailto:[email protected]">miguel</a> with your public OpenSSH
|
||||
key for this purpose. Please specify if the key was generated with SSH
|
||||
version 1 or version 2. Detailed instructions are below.
|
||||
|
||||
+11
-1
@@ -5,26 +5,36 @@
|
||||
Here is the status of the different assemblies:
|
||||
<ul>
|
||||
<li><a href="http://www.go-mono.com/class-status-corlib.html">corlib</a>: The core library.
|
||||
<li><a href="http://www.go-mono.com/class-status-System.html">System</a>: Extra modules
|
||||
<li><a href="http://www.go-mono.com/class-status-System.html">System</a>.
|
||||
<li><a href="http://www.go-mono.com/class-status-System.Xml.html">System.Xml</a>.
|
||||
|
||||
<li><a
|
||||
href="http://www.go-mono.com/class-status-System.Data.html">System.Data</a>:
|
||||
Database access functionality (also check the <a href="ado-net.html">Mono ADO.NET status</a> pages).
|
||||
|
||||
<li><a href="http://www.go-mono.com/class-status-System.Drawing.html">System.Drawing</a>.
|
||||
|
||||
<li><a
|
||||
href="http://www.go-mono.com/class-status-System.Web.html">System.Web</a>:
|
||||
ASP.NET classes, also check the <a href="asp-net.html">Mono ASP.NET status pages</a>
|
||||
|
||||
<li><a href="http://www.go-mono.com/class-status-System.Web.Services.html">System.Web.Services</a>.
|
||||
|
||||
<li><a
|
||||
href="http://www.go-mono.com/class-status-Microsoft.VisualBasic.html">Microsoft.VisualBasic</a>:
|
||||
Support runtime for Visual Basic applications
|
||||
|
||||
<li><a
|
||||
href="http://www.go-mono.com/class-status-System.Windows.Forms.html">Windows.Forms</a>:
|
||||
there is also a <a
|
||||
href="http://lists.ximian.com/mailman/listinfo/mono-winforms-list">mailing
|
||||
list available</a>
|
||||
|
||||
<li><a href="http://www.go-mono.com/class-status-System.EnterpriseServices.html">EnterpriseServices</a>.
|
||||
|
||||
<li><a
|
||||
href="http://www.go-mono.com/class-status-System.Runtime.Serialization.Formatters.Soap.html">System.Runtime.Serialization.Formatters.Soap</a>.
|
||||
|
||||
<li><a
|
||||
href="http://www.go-mono.com/class-status-System.Security.html">System.Security</a>:
|
||||
Xml Signature Security classes, also check the <a href="crypto.html">Cryptography status pages</a>
|
||||
|
||||
+4
-9
@@ -17,7 +17,6 @@
|
||||
|
||||
<ul>
|
||||
<li><a href="#monodoc">monodoc - A graphical documentation viewer.</a></li>
|
||||
|
||||
<li>xmllint: a tool used to validate a proper XML document.
|
||||
</ul>
|
||||
|
||||
@@ -28,15 +27,11 @@
|
||||
|
||||
*** <a name="monodoc">MonoDoc</a>
|
||||
|
||||
The MonoDoc system offers both a GUI client as well as a <a
|
||||
href="http://www.go-mono.com:8080">Web-based interface</a> to
|
||||
the documentation.
|
||||
A graphical documentation viewer written in Gtk#. In the
|
||||
future we will have an ASP.NET front-end to present the
|
||||
documentation on the web as well.
|
||||
|
||||
The GUI edition uses <a
|
||||
href="http://gtk-sharp.sf.net">Gtk#</a> and the Web edition
|
||||
uses Mono's ASP.NET implementation.
|
||||
|
||||
<img src="images/Screenshot-Monodoc.png">
|
||||
** Status and Roadmap
|
||||
|
||||
** Get Involved
|
||||
|
||||
|
||||
+1
-4
@@ -128,10 +128,7 @@
|
||||
|
||||
You can review the list of current bugs by going <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FClass+Libraries&product=Mono%2FMCS&product=Mono%2FRuntime&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&order=%27Importance%27&form_name=query">here</a>
|
||||
|
||||
Check our <a href="bugs.html">Bugs</a> that contains links to
|
||||
easily add a bug report, or to query the existing bugs.
|
||||
|
||||
<a name="goodbugreport"/>
|
||||
<a name="goodbugreport"/>
|
||||
** How to make good bug reports
|
||||
|
||||
A mail from Paolo to mono-devel-list contained this check list:
|
||||
|
||||
+60
-77
@@ -24,6 +24,11 @@
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* The current implementation of <code>CryptoStream</code> is
|
||||
very limited and contain known bugs (<a
|
||||
href="http://bugzilla.ximian.com/show_bug.cgi?id=40689">
|
||||
40689</a>). The class need to be re-designed.
|
||||
|
||||
* RNGCryptoServiceProvider is currently only working on Linux.
|
||||
The current implementation reside in Mono's runtime and use
|
||||
the <code>/dev/[u]random</code> device (which do not exists
|
||||
@@ -67,8 +72,8 @@
|
||||
(using the Mono.Security.ASN1 class).
|
||||
|
||||
* Software Publisher Certificates (SPC) used by Authenticode
|
||||
(tm) to sign assemblies are supported and <b>minimally</b>
|
||||
validated.
|
||||
(tm) to sign assemblies are supported (extraction from PE
|
||||
files) but <b>not yet</b> validated.
|
||||
|
||||
* Unit tests are generated from a set of existing certificates
|
||||
(about a dozen) each having different properties. Another
|
||||
@@ -77,6 +82,14 @@
|
||||
size and time consideration, i.e. a 7.5Mb C# source file).
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* Authenticode(tm) support is incomplete. We can extract the
|
||||
certificates from PE files but cannot validate the signature
|
||||
nor the certificate chain (and we're still missing some trust
|
||||
anchors). See Tools section for more information.
|
||||
</ul>
|
||||
|
||||
**** Notes
|
||||
<ul>
|
||||
* Except for their structure <b>there are no validation of the
|
||||
@@ -96,8 +109,8 @@
|
||||
continue to evolve to support the security tools.
|
||||
|
||||
* Microsoft implementation of <code>X509Certificate</code> is
|
||||
done by using CryptoAPI (unmanaged code). Based on the
|
||||
exceptions thrown, Authenticode(tm) support is done via COM.
|
||||
done by using CryptoAPI (unmanaged code). From the exceptions
|
||||
thrown Authenticode(tm) support is done via COM.
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
@@ -111,16 +124,20 @@
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* All classes are present but some Transforms are only stubbed.
|
||||
|
||||
* We now have a fully managed C14N implementation.
|
||||
* All classes are present but some (most Transforms) are only
|
||||
stubbed.
|
||||
|
||||
* Most classes have their unit tests.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* Complete all Transform derived classes.
|
||||
* All the transforms needs to be done. But this requires far
|
||||
more XML knowledge than crypto. Note: Most tests runs because
|
||||
the feeded XML is pre-c14n (by hand in the code) before
|
||||
signing (not because the transforms works). In the short
|
||||
term <code>libxml2</code> could be used to provide C14N, but
|
||||
in the long term a fully managed class would be much better.
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
@@ -148,10 +165,6 @@
|
||||
* Additional algorithms: MD2, ARCFOUR (required for SSL)
|
||||
* Convertion helpers
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.Protocol.Tls
|
||||
<ul>
|
||||
* An 100% managed TLS implementation from Carlos Guzman Alvarez.
|
||||
</ul>
|
||||
*** Namespace: Mono.Security.X509
|
||||
<ul>
|
||||
* X.509 structures (certificate, CRL...) building and decoding.
|
||||
@@ -164,6 +177,8 @@
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* Some part of the work has not yet been commited (still cleaning up).
|
||||
|
||||
* A big part of this assembly is also included inside Mono's
|
||||
corlib. The classes are duplicated in this assembly so the
|
||||
functionalities can be used without a dependency on Mono's
|
||||
@@ -202,8 +217,7 @@
|
||||
algorithms shouldn't be used in new design (MD4 is broken,
|
||||
MD2 and MD5 aren't considered safe for some usage). They are
|
||||
included to preserve interoperability with older applications
|
||||
(e.g. some old, but still valid, X.509 certificates use MD2,
|
||||
MD4 is required for NTLM authentication ...).
|
||||
(e.g. some old, but still valid, X.509 certificates use MD2).
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
@@ -242,36 +256,26 @@
|
||||
<a href="http://www.oasis-open.org/committees/wss/">OASIS</a> or
|
||||
other committees.
|
||||
|
||||
*** Namespace: Microsoft.Web.Services.Security
|
||||
<b>[*] There are some licensing issues to consider before starting to
|
||||
implement WS-Security. All contributors must sign an agreement with
|
||||
Microsoft before commiting anything related to WS-Security into CVS.
|
||||
</b>
|
||||
|
||||
*** Namespace: Microsoft.Web.Services.Security [*]
|
||||
*** Namespace: Microsoft.Web.Services.Timestamp [*]
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* Most WSE 1.0 classes are implemented.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
<ul>
|
||||
* Some classes from System.Security assembly need to be
|
||||
duplicated (and somewhat fixed) in WSE for XMLDSIG.
|
||||
|
||||
* There are still missing classes and <b>many</b> missing
|
||||
unit tests.
|
||||
</ul>
|
||||
|
||||
|
||||
*** Namespace: Microsoft.Web.Services.Timestamp
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* This seems complete for WSE 1.0 but some new classes were
|
||||
introduced in WSE 2.0.
|
||||
* Nothing (yet) commited in CVS <b>[*]</b>.
|
||||
</ul>
|
||||
|
||||
*** Namespace: Microsoft.Web.Services.Security.X509
|
||||
|
||||
**** Status
|
||||
<ul>
|
||||
* X509Certificate support is complete for both WSE 1.0 and 2.0.
|
||||
* Nothing (yet) commited in CVS. However the classes in this
|
||||
namespace are outside WS-Security scope. So development, for
|
||||
those classes, could be done without signing any agreements.
|
||||
</ul>
|
||||
|
||||
**** TODO
|
||||
@@ -281,14 +285,6 @@
|
||||
keypairs. This could also be used to store the SPC roots.
|
||||
</ul>
|
||||
|
||||
*** Notes
|
||||
<ul>
|
||||
* Microsoft has <a href="http://microsoft.com/downloads/details.aspx?FamilyId=21FB9B9A-C5F6-4C95-87B7-FC7AB49B3EDD&displaylang=en">released</a>
|
||||
a technical preview of WSE 2. <b>Note that WSDK (the technical
|
||||
preview of WSE) had A LOT of changes before it's initial
|
||||
release!</b>
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
** Tools
|
||||
|
||||
@@ -299,7 +295,7 @@
|
||||
|
||||
**** Status
|
||||
|
||||
The following tools are complete (or mostly complete):
|
||||
The following tools are complete (mostly complete):
|
||||
<ul>
|
||||
* <code>secutil</code> is a tool to extract certificates and
|
||||
strongnames from assemblies in a format that can be easily
|
||||
@@ -310,26 +306,14 @@
|
||||
(SPC) file - which is a long name for a simple PKCS#7 file.
|
||||
|
||||
* <code>makecert</code> to create X.509 test certificates that
|
||||
can be used (once transformed in SPC) to sign assemblies. It's
|
||||
now possible to generate SSL certificates for web servers.
|
||||
|
||||
* <code>sn</code> is a clone of the <code>sn</code> to manage
|
||||
strongnames. Current version can create, convert, sign and
|
||||
verify strongnames signatures. Some configuration options
|
||||
are still missing.
|
||||
|
||||
* <code>signcode</code> and <code>chktrust</code> for signing
|
||||
and validating Authenticode(tm) signatures on assemblies (or
|
||||
any PE file) are now working (signature and timestamps) but
|
||||
some options aren't yet supported.
|
||||
can be used (once transformed in SPC) to sign assemblies.
|
||||
</ul>
|
||||
|
||||
Somewhat usable, somewhat incomplete:
|
||||
<ul>
|
||||
* <code>certview</code> is a certificate viewer for
|
||||
<code>System.Windows.Forms</code> (right now only working on
|
||||
Windows), while <code>gcertview</code> is the same viewer
|
||||
implemented for GTK# (working on both Windows and Linux).
|
||||
* <code>sn</code> is a clone of the <code>sn</code> to manage
|
||||
strongnames. Current version is limited to creating new keypairs
|
||||
and converting values.
|
||||
|
||||
* <code>monosn</code> is a clone of the <code>sn</code> to manage
|
||||
strongnames. This tools is part of the runtime (not the class
|
||||
@@ -340,6 +324,11 @@
|
||||
**** TODO
|
||||
The following tools are still missing or largely incomplete:
|
||||
<ul>
|
||||
|
||||
* <code>signcode</code> and <code>chktrust</code> (in progress)
|
||||
for signing and validating Authenticode(tm) signatures on
|
||||
assemblies (or any PE file).
|
||||
|
||||
* Other tools like a, GUI-based, certificate manager...
|
||||
</ul>
|
||||
|
||||
@@ -348,40 +337,34 @@
|
||||
tools are of limited use until supported by the runtime.
|
||||
|
||||
<hr>
|
||||
** References
|
||||
** Other stuff
|
||||
|
||||
<ul>
|
||||
* RSA Laboratories' <a href="http://www.rsasecurity.com/rsalabs/faq/index.html">
|
||||
Frequently Asked Questions</a> About Today's Cryptography, Version 4.1
|
||||
|
||||
* Public-Key Cryptography Standards (<a href="http://www.rsasecurity.com/rsalabs/pkcs/index.html">
|
||||
PKCS</a>)
|
||||
|
||||
* National Institute of Standards and Technology - Federal
|
||||
Information Processing Standards <a href="http://csrc.nist.gov/publications/fips/index.html">
|
||||
NIST FIPS</a>
|
||||
* SSL/TLS for secure communication (a prototype is under way).
|
||||
Some work is already visible in Mono.Security assembly (e.g.
|
||||
RC4, RSAManaged ...).
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
|
||||
<hr>
|
||||
** How to Help
|
||||
|
||||
<ul>
|
||||
* Complete any of the TODO (and feel good about it ;-).
|
||||
|
||||
* Analyse the current coverage of the unit tests on the
|
||||
cryptographic classes and complete the unit tests. <b><code>
|
||||
monocov</code> does a great job at this! Now we just need to
|
||||
complete the missing unit tests.</b>
|
||||
cryptographic classes and complete the unit tests.
|
||||
|
||||
* Optimization can also be done on most algorithms as crypto
|
||||
is never fast enough. Some have been done using the
|
||||
Community Edition of BoundChecker (a free VisualStudio
|
||||
addon) - recommanded! Just be sure to test every optimization
|
||||
(using the unit tests) carefully - it's so fast to break an
|
||||
(using the unit test) carefully - it's so fast to break an
|
||||
algorithm ;-).
|
||||
|
||||
* Write some documentation on the cryptographic classes for
|
||||
<b>monodoc</b> as I'm not a very good writer (at least in English).
|
||||
the <a href="http://go-mono.com/tutorial/html/en/index.html">Mono
|
||||
Handbook</a> as I'm not a very good writer (at least in English).
|
||||
</ul>
|
||||
|
||||
Contact Sebastien Pouliot (<a href="mailto:[email protected]">home</a>
|
||||
@@ -389,4 +372,4 @@
|
||||
informations about the status of the cryptographic classes.
|
||||
|
||||
<hr>
|
||||
Last reviewed: October 26, 2003 (post mono 0.28)
|
||||
Last reviewed: June 11, 2003 (post mono 0.24)
|
||||
+2
-6
@@ -25,11 +25,7 @@
|
||||
libraries as well as the class libraries produced by
|
||||
the project).
|
||||
|
||||
* Tutorials on Mono and the specifics of running it
|
||||
(The <a href="http://www.monohispano.org">Mono
|
||||
Hispano</a> team has produced lots of <a
|
||||
href="http://www.monohispano.org/tutoriales.php">tutorials
|
||||
in spanish</a>
|
||||
* Tutorials on Mono and the specifics of running it.
|
||||
|
||||
* A guide to Mono as compared to the Microsoft.NET
|
||||
Framework SDK
|
||||
@@ -203,7 +199,7 @@
|
||||
</pre>
|
||||
|
||||
Use this to create lists. Lists contains <item>
|
||||
elements which have to contain <term> containers.
|
||||
elements
|
||||
|
||||
<pre>
|
||||
<list type="table"> </lits>
|
||||
|
||||
+29
-258
@@ -13,213 +13,6 @@
|
||||
section</a>, the <a
|
||||
href="http://www.go-mono.org/faq.html">FAQ</a>.
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
<td>
|
||||
<b>Release 0.28</b><br>
|
||||
<a href="archive/mono-0.28.html">Release notes</a><br>
|
||||
Oct 1st, 2003
|
||||
</td>
|
||||
<td>
|
||||
<table cellspacing="1" cellpadding="3">
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source Code</b>
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/mcs-0.28.tar.gz">Mono Class Libraries and C# Compiler.</a>
|
||||
<li><a href="archive/mono-0.28.tar.gz">Mono Runtime</a>
|
||||
<li><a href="archive/xsp-0.6.tar.gz">XSP web server (0.6)</a>
|
||||
<li><a href="archive/mod_mono-0.5.tar.gz">Apache Mono module (mod_mono)</a>
|
||||
<li><a href="archive/monodoc-0.7.tar.gz">MonoDoc 0.7</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source RPMs</b><br>
|
||||
(No RPMS for XSP).
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.28-1.ximian.6.1.src.rpm">mono-0.28-1.src.rpm (RH9)</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.28-1.ximian.5.1.src.rpm">mono-0.28-1.src.rpm (RH8)</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 9.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.28-1.ximian.6.1.i386.rpm">mono-0.28-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-devel-0.28-1.ximian.6.1.i386.rpm">mono-devel-0.28-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-debuginfo-0.28-1.ximian.6.1.i386.rpm">mono-debuginfo-0.28-1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/mono-wine-20030318-1.ximian.6.4.i386.rpm">mono-wine-20030318-1.ximian.6.4.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-wine-debuginfo-20030318-1.ximian.6.4.i386.rpm">mono-wine-debuginfo-20030318-1.ximian.6.4.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 8.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-80-i386/mono-0.28-1.ximian.5.1.i386.rpm">mono-0.28-1.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-devel-0.28-1.ximian.5.1.i386.rpm">mono-devel-0.28-1.ximian.5.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-80-i386/mono-wine-20030318-1.ximian.5.3.i386.rpm">mono-wine-20030318-1.ximian.5.3.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/mandrake-36.gif"><b>Mandrake 9.1/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/mandrake-91-i586/mono-0.28-1.ximian.6.1.i586.rpm">mono-0.28-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/mono-devel-0.28-1.ximian.6.1.i586.rpm">mono-devel-0.28-1.ximian.6.1.i586.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<b>Linux s390</b>
|
||||
<ul>
|
||||
<li><a href="archive/s390/libgc-6.1-1.s390.rpm">libgc-6.1-1.s390.rpm</a>
|
||||
<li><a href="archive/s390/libgc-devel-6.1-1.s390.rpm">libgc-devel-6.1-1.s390.rpm</a>
|
||||
<li><a href="archive/s390/mono-0.28-1.s390.rpm">mono-0.28-1.s390.rpm</a>
|
||||
<li><a href="archive/s390/mono-devel-0.28-1.s390.rpm">mono-devel-0.28-1.s390.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/suse-36.gif"><b>SuSE 8.2</b>
|
||||
<ul>
|
||||
<li><a href="archive/suse-82-i586/mono-0.28-1.ximian.7.1.i586.rpm">mono-0.28-1.ximian.7.1.i586.rpm</a>
|
||||
<li><a href="archive/suse-82-i586/mono-devel-0.28-1.ximian.7.1.i586.rpm">mono-devel-0.28-1.ximian.7.1.i586.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/windows-36.gif"><b>Windows installer</b>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.28-win32-1.exe">mono-0.28-win32-1.exe</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</table>
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
<td>
|
||||
<b>Release 0.26</b><br>
|
||||
<a href="archive/mono-0.26.html">Release notes</a><br>
|
||||
Aug 14, 2003
|
||||
</td>
|
||||
<td>
|
||||
<table cellspacing="1" cellpadding="3">
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source Code</b>
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/mcs-0.26.tar.gz">Mono Class Libraries and C# Compiler.</a>
|
||||
<li><a href="archive/mono-0.26.tar.gz">Mono Runtime</a>
|
||||
<li><a href="archive/xsp-0.5.tar.gz">XSP web server (0.5)</a>
|
||||
<li><a href="archive/mod_mono-0.4.tar.gz">Apache Mono module (mod_mono)</a>
|
||||
<li><a href="archive/monodoc-0.6.tar.gz">MonoDoc 0.6</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr bgcolor="#BBBBBB">
|
||||
<td>
|
||||
<b>Source RPMs</b><br>
|
||||
(No RPMS for XSP).
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.26-1.ximian.6.1.src.rpm">mono-0.26-1.src.rpm (RH9)</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.26-1.ximian.5.1.src.rpm">mono-0.26-1.src.rpm (RH8)</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 9.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.26-1.ximian.6.1.i386.rpm">mono-0.26-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-devel-0.26-1.ximian.6.1.i386.rpm">mono-devel-0.26-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-debuginfo-0.26-1.ximian.6.1.i386.rpm">mono-debuginfo-0.26-1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/libpixregion-0.1.0-1.ximian.6.1.i386.rpm">libpixregion-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libpixregion-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">libpixregion-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libic-0.1.0-1.ximian.6.1.i386.rpm">libic-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libic-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">libic-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xc-0.1.0-1.ximian.6.1.i386.rpm">xc-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xc-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">xc-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xr-0.1.0-1.ximian.6.1.i386.rpm">xr-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xr-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">xr-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/monodoc-0.6-1.ximian.6.1.i386.rpm">monodoc-0.6-1.ximian.6.1.i386.rpm</a> (To be used only with CVS gtk-sharp)
|
||||
<li><a href="archive/redhat-90-i386/monodoc-debuginfo-0.5-1.ximian.6.1.i386.rpm">monodoc-debuginfo-0.5-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-wine-20030318-1.ximian.6.3.i386.rpm">mono-wine-20030318-1.ximian.6.3.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-wine-debuginfo-20030318-1.ximian.6.2.i386.rpm">mono-wine-debuginfo-20030318-1.ximian.6.3.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 8.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-80-i386/mono-0.26-2.ximian.5.1.i386.rpm">mono-0.26-2.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-devel-0.26-2.ximian.5.1.i386.rpm">mono-devel-0.26-2.ximian.5.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-80-i386/monodoc-0.5-1.ximian.5.1.i386.rpm">monodoc-0.5-1.ximian.5.1.i386.rpm</a> (To be used only with CVS gtk-sharp)
|
||||
<li><a href="archive/redhat-80-i386/mono-wine-20030318-1.ximian.5.3.i386.rpm">mono-wine-20030318-1.ximian.5.3.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/debian-36.gif"><b>Debian</b>
|
||||
<ul>
|
||||
<li><a href="http://www.debianplanet.com/mono/">Debian Packages here.</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/mandrake-36.gif"><b>Mandrake 9.1/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/mandrake-91-i586/mono-0.26-1.ximian.6.1.i586.rpm">mono-0.26-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/mono-devel-0.26-1.ximian.6.1.i586.rpm">mono-devel-0.26-1.ximian.6.1.i586.rpm</a>
|
||||
<!-- <li><a href="archive/mandrake-91-i586/monodoc-0.5-1.ximian.6.1.i586.rpm">monodoc-0.5-1.ximian.6.1.i586.rpm</a> -->
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/suse-36.gif"><b>SuSE 8.2</b>
|
||||
<ul>
|
||||
<li><a href="archive/suse-82-i586/mono-0.26-2.ximian.7.1.i586.rpm">mono-0.26-2.ximian.7.1.i586.rpm</a>
|
||||
<li><a href="archive/suse-82-i586/mono-devel-0.26-2.ximian.7.1.i586.rpm">mono-devel-0.26-2.ximian.7.1.i586.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/windows-36.gif"><b>Windows installer</b>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.26-win32-2.exe">mono-0.26-win32-2.exe</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</table>
|
||||
<table>
|
||||
<tbody>
|
||||
<tr bgcolor="#DDDDDD">
|
||||
@@ -239,8 +32,8 @@
|
||||
<li><a href="archive/mcs-0.25.tar.gz">Mono Class Libraries and C# Compiler.</a>
|
||||
<li><a href="archive/mono-0.25.tar.gz">Mono Runtime</a>
|
||||
<li><a href="archive/xsp-0.4.tar.gz">XSP web server (0.4)</a>
|
||||
<li><a href="archive/monodoc-0.5.tar.gz">MonoDoc 0.5</a>
|
||||
<li><a href="archive/gtk-sharp-0.11.tar.gz">Gtk# 0.11</a>
|
||||
<li><a href="archive/monodoc-0.4.tar.gz">MonoDoc 0.5</a>
|
||||
<li><a href="archive/gtk-sharp-0.10.tar.gz">Gtk# 0.10</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
@@ -251,7 +44,7 @@
|
||||
</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><a href="archive/mono-0.25-1.ximian.5.src.rpm">mono-0.25-1.src.rpm</a>
|
||||
<li><a href="archive/mono-0.25-1.src.rpm">mono-0.25-1.src.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
@@ -263,39 +56,23 @@
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 9.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.25-1.ximian.6.1.i386.rpm">mono-0.25-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-devel-0.25-1.ximian.6.1.i386.rpm">mono-devel-0.25-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-debuginfo-0.25-1.ximian.6.1.i386.rpm">mono-debuginfo-0.25-1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/libpixregion-0.1.0-1.ximian.6.1.i386.rpm">libpixregion-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libpixregion-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">libpixregion-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libic-0.1.0-1.ximian.6.1.i386.rpm">libic-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/libic-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">libic-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xc-0.1.0-1.ximian.6.1.i386.rpm">xc-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xc-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">xc-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xr-0.1.0-1.ximian.6.1.i386.rpm">xr-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/xr-debuginfo-0.1.0-1.ximian.6.1.i386.rpm">xr-debuginfo-0.1.0-1.ximian.6.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-0.10-1.ximian.6.1.i386.rpm">gtk-sharp-0.10-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-gapi-0.10-1.ximian.6.1.i386.rpm">gtk-sharp-gapi-0.10-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-debuginfo-0.10-1.ximian.6.1.i386.rpm">gtk-sharp-debuginfo-0.10-1.ximian.6.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/monodoc-0.5-1.ximian.6.1.i386.rpm">monodoc-0.5-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/monodoc-debuginfo-0.5-1.ximian.6.1.i386.rpm">monodoc-debuginfo-0.5-1.ximian.6.1.i386.rpm</a>
|
||||
<li><a href="archive/mono-wine-20030318-1.ximian.6.2.i386.rpm">mono-wine-20030318-1.ximian.6.2.i386.rpm</a>
|
||||
<li><a href="archive/mono-wine-debuginfo-20030318-1.ximian.6.2.i386.rpm">mono-wine-debuginfo-20030318-1.ximian.6.2.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-0.25-1.i386.rpm">mono-0.25-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-devel-0.25-1.i386.rpm">mono-devel-0.25-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/mono-debuginfo-0.25-1.i386.rpm">mono-debuginfo-0.25-1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-0.9-1.i386.rpm">gtk-sharp-0.9-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/gtk-sharp-debuginfo-0.9-1.i386.rpm">gtk-sharp-debuginfo-0.9-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-90-i386/monodoc-0.4-1.i386.rpm">monodoc-0.4-1.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 8.0/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-80-i386/mono-0.25-1.ximian.5.1.i386.rpm">mono-0.25-1.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-devel-0.25-1.ximian.5.1.i386.rpm">mono-devel-0.25-1.ximian.5.1.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-80-i386/gtk-sharp-0.10-1.ximian.5.1.i386.rpm">gtk-sharp-0.10-1.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/gtk-sharp-gapi-0.10-1.ximian.5.1.i386.rpm">gtk-sharp-gapi-0.10-1.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/monodoc-0.5-1.ximian.5.1.i386.rpm">monodoc-0.5-1.ximian.5.1.i386.rpm</a>
|
||||
<li><a href="archive/mono-wine-20030318-1.ximian.5.2.i386.rpm">mono-wine-20030318-1.ximian.5.2.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-0.25-2.i386.rpm">mono-0.25-2.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/mono-devel-0.25-2.i386.rpm">mono-devel-0.25-2.i386.rpm</a>
|
||||
<br>
|
||||
<li><a href="archive/redhat-80-i386/gtk-sharp-0.9-1.i386.rpm">gtk-sharp-0.9-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-80-i386/monodoc-0.4-1.i386.rpm">monodoc-0.4-1.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
@@ -319,34 +96,28 @@
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/redhat-36.gif"><b>Red Hat 7.3/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/redhat-73-i386/mono-0.25-1.ximian.4.1.i386.rpm">mono-0.25-1.ximian.4.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/mono-devel-0.25-1.ximian.4.1.i386.rpm">mono-devel-0.25-1.ximian.4.1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/mono-0.25-1.i386.rpm">mono-0.25-1.i386.rpm</a>
|
||||
<li><a href="archive/redhat-73-i386/mono-devel-0.25-1.i386.rpm">mono-devel-0.25-1.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/mandrake-36.gif"><b>Mandrake 9.1/x86</b>
|
||||
<img src="images/mandrake-36.gif"><b>Mandrake 8.2/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/mandrake-91-i586/mono-0.25-1.ximian.6.1.i586.rpm">mono-0.25-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/mono-devel-0.25-1.ximian.6.1.i586.rpm">mono-devel-0.25-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/gtk-sharp-0.10-1.ximian.6.1.i586.rpm">gtk-sharp-0.10-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/gtk-sharp-gapi-0.10-1.ximian.6.1.i586.rpm">gtk-sharp-gapi-0.10-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-91-i586/monodoc-0.5-1.ximian.6.1.i586.rpm">monodoc-0.5-1.ximian.6.1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-82-i386/mono-0.25-1.i586.rpm">mono-0.25-1.i586.rpm</a>
|
||||
<li><a href="archive/mandrake-82-i386/mono-devel-0.25-1.i586.rpm">mono-devel-0.25-1.i586.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<!--
|
||||
We don't have SuSE packages right now
|
||||
-->
|
||||
<!-- <tr> -->
|
||||
<!-- <td bgcolor="#999999"> -->
|
||||
<!-- <img src="images/suse-36.gif"><b>SuSE 8.2/x86</b> -->
|
||||
<!-- <ul> -->
|
||||
<!-- <li><a href="archive/suse-80-i386/mono-0.25-1.i386.rpm">mono-0.25-1.i386.rpm</a> -->
|
||||
<!-- <li><a href="archive/suse-80-i386/mono-devel-0.25-1.i386.rpm">mono-devel-0.25-1.i386.rpm</a> -->
|
||||
<!-- </ul> -->
|
||||
<!-- </td> -->
|
||||
<!-- </tr> -->
|
||||
<tr>
|
||||
<td bgcolor="#999999">
|
||||
<img src="images/suse-36.gif"><b>SuSE 8.2/x86</b>
|
||||
<ul>
|
||||
<li><a href="archive/suse-80-i386/mono-0.25-1.i386.rpm">mono-0.25-1.i386.rpm</a>
|
||||
<li><a href="archive/suse-80-i386/mono-devel-0.25-1.i386.rpm">mono-devel-0.25-1.i386.rpm</a>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
-43
@@ -1,43 +0,0 @@
|
||||
* Drawing
|
||||
|
||||
Mono provides two mechanism to draw. The first exposes the
|
||||
Microsoft System.Drawing API and the second exposes the <a
|
||||
href="http://www.cairographics.org">Cairo</a> API.
|
||||
|
||||
* System.Drawing
|
||||
|
||||
The System.Drawing implementation in Mono is designed to be
|
||||
compatible with the Microsoft API. The imaging model is very
|
||||
similar to the PDF 1.4 composition-based imaging model.
|
||||
|
||||
Our implementation is a C# wrapper around the GDI+ C API (also
|
||||
called the "GDI+ Flat API").
|
||||
|
||||
<center>
|
||||
<img src="images/system-drawing.png">
|
||||
</center>
|
||||
|
||||
In Windows Mono uses the GDI+ library that is included
|
||||
with the operating system, while in Unix we provide an
|
||||
implementation of this API which uses Cairo to do the heavy
|
||||
lifting.
|
||||
|
||||
The implementation of GDI+ lives in mcs/class/System.Drawing
|
||||
in the gdiplus directory and requires <a
|
||||
href="http://www.cairographics.org">Cairo</a> to be installed
|
||||
to get the package built.
|
||||
|
||||
The C# code that implement System.Drawing is the same for
|
||||
Windows and Unix builds.
|
||||
|
||||
Since this is an implementation of an existing Microsoft API
|
||||
no architectural changes go here.
|
||||
|
||||
* Mono.Cairo
|
||||
|
||||
The Mono.Cairo.dll assembly exposes the Cairo API to managed
|
||||
applications. The mapping is a pretty straightforward one,
|
||||
and the programming model is very close to the C API.
|
||||
|
||||
This API is still unstable due to the nature of the underlying
|
||||
API being used and will be revisited as Cairo evolves.
|
||||
+1
-16
@@ -68,20 +68,9 @@
|
||||
not interfere with code in other domains. This is useful if
|
||||
you want to host different applications in your program.
|
||||
|
||||
Now, it is necessary to transfer control to Mono, and setup
|
||||
the threading infrastructure, you do this like this:
|
||||
Then you can load an assembly containing code into the domain:
|
||||
|
||||
<pre>
|
||||
void *user_data = NULL;
|
||||
|
||||
mono_runtime_exec_managed_code (domain, main_thread_handler, user_data);
|
||||
</pre>
|
||||
|
||||
Where your main_thread_handler can load your assembly and execute it:
|
||||
|
||||
<pre>
|
||||
static void main_thread_handler (gpointer user_data)
|
||||
{
|
||||
MonoAssembly *assembly;
|
||||
|
||||
assembly = mono_domain_assembly_open (domain, "file.dll");
|
||||
@@ -120,10 +109,6 @@
|
||||
layer, so in each file where you use pthread.h you should
|
||||
include the <gc/gc.h> file.
|
||||
|
||||
If you can not do this for any reasons, just remember that you
|
||||
can not store pointers to Mono Objects on the stack, you can
|
||||
store them safely in the heap, or in global variables though
|
||||
|
||||
* Exposing C code to the CIL universe
|
||||
|
||||
The Mono runtime provides two mechanisms to expose C code to
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<a href="#basics">Basics</a><br>
|
||||
<a href="#novell">The Novell Role in the Mono project</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>
|
||||
@@ -39,55 +39,14 @@ A: The Mono Project is an open development initiative sponsored by
|
||||
implement various technologies developed by Microsoft that have now
|
||||
been submitted to the ECMA for standardization.
|
||||
|
||||
The Mono project has also sparked a lot of interest in developing
|
||||
C#-based components, libraries and frameworks. Today Mono is not
|
||||
limited to implement the .NET Framework, but also contains other
|
||||
components. Some of the components of the Mono platform were
|
||||
developed by the Mono team, and some others we have incorporated
|
||||
from other open source efforts, the most important ones:
|
||||
|
||||
<ul>
|
||||
<li><a
|
||||
href="http://remoting-corba.sourceforge.net/">Remoting.CORBA</a>: A
|
||||
CORBA implementation for Mono.
|
||||
|
||||
<li>Ginzu: An implementation on top of Remoting for the <a
|
||||
href="http://www.zeroc.com">ICE</a> stack
|
||||
|
||||
<li><a href="http://gtk-sharp.sf.net">Gtk#</a>: Bindings for
|
||||
the popular Gtk+ GUI toolkit for Unix and Windows systems.
|
||||
Other bindings are available: Diacanvas-Sharp and MrProject.
|
||||
|
||||
<li><a
|
||||
href="http://www.icsharpcode.net/OpenSource/SharpZipLib/Default.aspx">#ZipLib</a>:
|
||||
A library to manipulate various kinds of compressed files and
|
||||
archives (Zip and tar).
|
||||
|
||||
<li>GlGen (available from the Mono CVS): Bindings for OpenGL.
|
||||
|
||||
<li>Mono.LDAP: LDAP access for .NET apps.
|
||||
|
||||
<li>Mono.Data: We ship support for Postgress, MySql, Sybase,
|
||||
DB2, SqlLite, Tds (SQL server protocol) and Oracle databases.
|
||||
|
||||
<li>Mono.Cairo: Bindings for the <a
|
||||
href="http://www.cairographics.org">Cairo</a> rendering
|
||||
engine (Our System.Drawing is implemented on top of this).
|
||||
|
||||
<li>Mono.Posix: Bindings for building POSIX applications using
|
||||
C#.
|
||||
|
||||
<li>Mono.Http: Support for creating custom, embedded HTTP
|
||||
servers and common HTTP handlers for your applications.
|
||||
</ul>
|
||||
|
||||
Q: What is the difference between Mono and the .NET Initiative?
|
||||
|
||||
A: The ".NET Initiative" is a somewhat nebulous company-wide effort by
|
||||
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 or software-as-a-service.
|
||||
Initiative, such as Passport, software-as-a-service, or
|
||||
corporate re-branding.
|
||||
|
||||
Q: What technologies are included in Mono?
|
||||
|
||||
@@ -100,9 +59,7 @@ A: Mono contains a number of components useful for building new
|
||||
compiler, and a garbage collecting runtime.
|
||||
|
||||
* A class library that can work with any language
|
||||
which works on the CLR. Both .NET compatible class
|
||||
libraries as well as Mono-provided class libraries
|
||||
are included.
|
||||
which works on the CLR.
|
||||
|
||||
* A compiler for the C# language. In the future we
|
||||
might work on other compilers that target the Common
|
||||
@@ -146,26 +103,38 @@ Q: Will you offer an ECMA-compliant set of class libraries?
|
||||
|
||||
A: Eventually we will. Our current focus is on inter-operating
|
||||
with the Microsoft SDK, but we will also offer an ECMA compliant
|
||||
subset of the libraries.
|
||||
set of libraries.
|
||||
|
||||
Q: What does the name "Mono" mean?
|
||||
|
||||
A: Mono is the word for `monkey' in Spanish. We like monkeys.
|
||||
A: Mono is the word for `monkey' in Spanish. We like monkeys.
|
||||
|
||||
Q: Does Mono work today?
|
||||
Q: Is Mono usable?
|
||||
|
||||
A: The execution engine works on various platforms, we support
|
||||
Just-in-Time and Ahead-of-Time compilations on Intel x86 machines
|
||||
(and soon PowerPC).
|
||||
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 mature enough to run various real
|
||||
applications: our C# compiler, ASP.NET, and Gtk#-based
|
||||
applications.
|
||||
The class libraries are mature enough to run some real applications
|
||||
(the compiler for instance, and every day more and more applications
|
||||
are natively developed with Mono).
|
||||
|
||||
Q: When will you ship Mono?
|
||||
Q: When will you ship it?
|
||||
|
||||
A: Please see the <a href="mono-roadmap.html">Mono Roadmap</a> for
|
||||
more details on the release plans.
|
||||
A: Different parts of Mono will achieve usability at different stages,
|
||||
once we are comfortable with the compiler, we will release "Mono Core",
|
||||
which contains everything needed to develop applications with the base
|
||||
class libraries, this will happen soon and in the meantime you can
|
||||
download daily snapshots of our work. Also the full ASP.NET support is
|
||||
close to completion.
|
||||
|
||||
Other higher level class libraries (ASP.NET, ADO.NET, WinForms) will
|
||||
be released when they become stable.
|
||||
|
||||
Q: What major components will you include in Mono?
|
||||
|
||||
A: Hopefully everything that Microsoft ships on their Framework
|
||||
(ADO.NET, ASP.NET, WinForms), and we encourage third party developers to
|
||||
create reusable components that work on both Mono and Windows.
|
||||
|
||||
Q: How can I contribute?
|
||||
|
||||
@@ -187,26 +156,26 @@ Q: Miguel said once that Mono was being implemented in COBOL. Is that true?.
|
||||
A: No. It was a joke.
|
||||
|
||||
|
||||
<a name="novell"></a>
|
||||
<a name="ximian"></a>
|
||||
|
||||
** The Novell Role in the Mono Project
|
||||
** The Ximian Role in the Mono Project
|
||||
|
||||
Q: Why is Novell working on .NET?
|
||||
Q: Why is Ximian working on .NET?
|
||||
|
||||
A: Novell is interested in providing the best tools for programmers to
|
||||
develop applications for Free Operating Systems.
|
||||
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 Novell be able to take on a project of this size?
|
||||
Q: Will Ximian be able to take on a project of this size?
|
||||
|
||||
A: Of course not. Novell is a supporter of the Mono project, but the only way
|
||||
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 Novell be working on?
|
||||
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
|
||||
@@ -214,30 +183,25 @@ A: We will devote most of our resources to work on the pieces which are
|
||||
the real world, it will achieve a critical mass of developers to
|
||||
improve it further.
|
||||
|
||||
Q: Will Novell offer Mono commercially?
|
||||
Q: Will Ximian offer Mono commercially?
|
||||
|
||||
A: When Mono is ready to be shipped Ximian will offer a commercial
|
||||
support and services for Mono. Mono components are also
|
||||
available to be licensed commercially. For licensing details,
|
||||
contact <a
|
||||
href="mailto:[email protected]">[email protected]</a>
|
||||
support and services for Mono.
|
||||
|
||||
Q: Does Novell provide consulting services around Mono?
|
||||
Q: Does Ximian provide consulting services around Mono?
|
||||
|
||||
A: Yes, Novell does provide consulting services around Mono to
|
||||
A: Yes, Ximian does provide consulting services around Mono to
|
||||
make it suitable to your needs. Porting the runtime engine,
|
||||
customizing it, working on specific classes or tuning the code
|
||||
for your particular needs.
|
||||
|
||||
Please contact <a
|
||||
href="mailto:[email protected]">[email protected]</a>
|
||||
for consulting services information.
|
||||
|
||||
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,
|
||||
see the <a href="mono-roadmap.html">Mono Roadmap</a> for details
|
||||
require only a subset of the technologies, those will ship first.
|
||||
|
||||
More advanced features will take more time to develop. A support
|
||||
time line will be available in June 2002.
|
||||
|
||||
<a name="gnome"></a>
|
||||
** Mono and GNOME
|
||||
@@ -251,10 +215,6 @@ A: In a number of ways. This project was born out of the need of
|
||||
implement Winforms and the Drawing2D API and are considering
|
||||
GObject support.
|
||||
|
||||
Mono team members work actively on the <a
|
||||
href="http://gtk-sharp.sf.net">Gtk#</a> project: a binding of the
|
||||
GNOME class libraries for .NET and Mono.
|
||||
|
||||
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
|
||||
@@ -283,8 +243,7 @@ A: Yes, we will provide a set of classes for implementing and using
|
||||
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, we also use other
|
||||
third-party open source libraries like Cairo and ICU.
|
||||
the GNOME team like the `glib' library.
|
||||
|
||||
Q: But will I be able to build GNOME applications?
|
||||
|
||||
@@ -292,58 +251,50 @@ A: Yes, we will enable people to write GNOME applications using Mono.
|
||||
|
||||
Q: Do you have C# bindings for GNOME?.
|
||||
|
||||
A: Yes, the <a href="http://gtk-sharp.sf.net">Gtk# project</a>
|
||||
provides bindings for Gtk+, Gdk, Atk, libgnome, libgnomecanvas, and
|
||||
libgnomeui. Other libraries under the GNOME framework will be
|
||||
added on an as-needed (and as-requested) basis.
|
||||
A: Yes, we currently bind libgnome, libgnomecanvas, and libgnomeui --
|
||||
although I dare say I have no idea how functional the bindings are
|
||||
outside of what I tested in the sample app. I imagine other libraries
|
||||
under the GNOME framework will be added on an as-needed (and as-requested)
|
||||
basis...although a truly good bonobo binding will have to wait on the CORBA
|
||||
remoting support which has been started recently.
|
||||
|
||||
<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. Today you can use Gtk# or #WT to develop GUI
|
||||
applications, and support for Windows.Forms is underway.
|
||||
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# API.
|
||||
|
||||
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), it integrates natively with the Gnome
|
||||
desktop. System.Windows.Forms is an API defined by Microsoft to
|
||||
build GUI applications.
|
||||
|
||||
Windows.Forms is currently being implemented on top of a modified
|
||||
version of Wine that can be used as a library: WineLib.
|
||||
CIL-enabled languages). System.Windows.Forms is an API defined
|
||||
by Microsoft to build GUI applications.
|
||||
|
||||
Q: Why not implement System.Windows.Forms on top of Gtk# or Qt#?
|
||||
|
||||
A: Compatibility.
|
||||
A: There are several reasons for this.
|
||||
|
||||
Although it is possible to run simple Windows.Forms applications
|
||||
with the Gtk#-based backend of Windows.Forms, it is very unlikely
|
||||
that the implementation will ever implement everything needed for
|
||||
full compatibility with Windows.Forms.
|
||||
|
||||
The reason is that Windows.Forms is not a complete toolkit, and to
|
||||
work around this problem some of the underlying Win32 foundation is
|
||||
exposed to the programmer in the form of exposing the Windows
|
||||
message handler (WndProc). Any control can override this method.
|
||||
Also developers often P/Invoke into Win32 to get to functionality
|
||||
that was not wrapped.
|
||||
|
||||
To achieve full compatibility, we would have to emulate this, and
|
||||
it would take too long.
|
||||
|
||||
For more details see the <a href="winforms.html">winforms page</a>
|
||||
|
||||
Q: Wine applications do not look like native applications, what are
|
||||
you going to do about this?
|
||||
|
||||
A: We have already a few patches into our version of Windows.Forms
|
||||
that makes Wine use the colors and font settings from your desktop,
|
||||
improving the integration a lot. In the future, we will continue
|
||||
to improve this interoperability scenario.
|
||||
First of all, Gtk+ and Qt are standard toolkits on Linux, and their
|
||||
proponents want to use their favorite toolkits when writing
|
||||
applications.
|
||||
|
||||
Related to this is the idea that System.Windows.Forms is
|
||||
brain-dead in certain areas, such as internationalization.
|
||||
System.Windows.Forms uses explicit sizes for all controls, as opposed
|
||||
to Gtk+ and Qt which use a box/packing model, which can better deal with
|
||||
the different string lengths different languages will have.
|
||||
|
||||
Next is compatibility. It is not possible to implement
|
||||
System.Windows.Forms on top of Gtk+/Qt and have 100% compatibility,
|
||||
because System.Windows.Forms exposes some Win32-isms, such as the
|
||||
Win32 message loop. In order to maintain compatibility, Wine must be used,
|
||||
and this is being done; see the
|
||||
<a href="/winforms.html">System.Windows.Forms effort page</a>.
|
||||
|
||||
Additionally, Wine apps don't currently fit in -- visually -- with
|
||||
Gtk+ or Qt apps.
|
||||
|
||||
Q: Will I be able to run my smart clients on systems powered by Mono?
|
||||
|
||||
@@ -363,7 +314,9 @@ A: Gtk# is becoming very usable and you can create applications and
|
||||
|
||||
Q: How can I compile my HelloWorld.cs which uses Gtk#?.
|
||||
|
||||
A: Try: mcs -r:gtk-sharp HelloWorld.cs
|
||||
A: Try: mcs --unsafe -o HelloWorld.exe -r glib-sharp -r pango-sharp -r
|
||||
atk-sharp -r gdk-sharp -r gtk-sharp -r gdk-imaging-sharp
|
||||
HelloWorld.cs
|
||||
|
||||
Q: Is there any way how to connect DataAdapter to some GTK# controls?
|
||||
|
||||
@@ -378,14 +331,9 @@ A: There is a sample file called `DbClient' in gtk-sharp/samples that you
|
||||
|
||||
Q: Do you have an estimate for when Windows.Forms will be released?
|
||||
|
||||
A: The plan currently is aimed at Q3/2004.
|
||||
|
||||
|
||||
Q: Do you have a comparission chart about the various toolkit
|
||||
offerings?
|
||||
|
||||
A: A document explaining this is available at: <a
|
||||
href="http://primates.ximian.com/~miguel/toolkits.html">http://primates.ximian.com/~miguel/toolkits.html</a>.
|
||||
A: We do not know, volunteers are working on this, but there is no set
|
||||
date yet. The current approach is using the Wine Library to implement
|
||||
it.
|
||||
|
||||
<a name="msft"></a>
|
||||
** Mono and Microsoft
|
||||
@@ -403,7 +351,7 @@ A: There is no high level communication between Ximian and Microsoft
|
||||
Ximian was also invited to participate in the ECMA committee
|
||||
meetings for C# and the CLI.
|
||||
|
||||
Q: Are Microsoft or Corel paying Ximian to do this?
|
||||
Q: Is Microsoft or Corel paying Ximian to do this?
|
||||
|
||||
A: No.
|
||||
|
||||
@@ -442,6 +390,13 @@ A: No. MS Passport is unrelated to running .NET compatible applications
|
||||
produced with the Mono tools. The only thing you will need is a
|
||||
just-in-time compiler (JIT).
|
||||
|
||||
Q: What is a 100% .NET application?
|
||||
|
||||
A: A `100% .NET application' is one that only uses the APIs defined
|
||||
under the System namespace and does not use PInvoke. These
|
||||
applications would in theory run unmodified on Windows, Linux,
|
||||
HP-UX, Solaris, MacOS X and others.
|
||||
|
||||
Q: If Microsoft will release a port of their .NET platform under the
|
||||
`Shared Source' license, why should I bother with anything else?
|
||||
|
||||
@@ -479,6 +434,12 @@ A: No, it will not. Microsoft Office is a Windows application. To
|
||||
learn more about running Windows applications on Intel Unix systems
|
||||
refer to <a href="http://www.winehq.com">the Wine Project</a>.
|
||||
|
||||
Q: Will I be able to compile a Microsoft VB.NET application and execute
|
||||
the resultant MSIL file under MONO on Linux without converting to C#
|
||||
and recompiling?
|
||||
|
||||
A: Once we have a complete VisualBasic runtime, yes.
|
||||
|
||||
Q: Can mono run the WebMatrix?
|
||||
|
||||
A: No. That requires System.Windows.Forms support which is not
|
||||
@@ -529,33 +490,12 @@ A: Mono requires Unicode versions of Win32 APIs to run,
|
||||
Win32 libs. This is achieved by inserting -lunimono before
|
||||
-lkerner32/user32 in the linker's specs file.
|
||||
|
||||
Q: Why support Windows, when you can run the real thing?
|
||||
|
||||
A: There are various reasons:
|
||||
|
||||
<ul>
|
||||
<li> About half the contributors to Mono are Windows developers.
|
||||
They have many different for contributing to the effort, and
|
||||
we find it very important to let those developers run the runtime on Windows without forcing
|
||||
them to use a new operating system.
|
||||
|
||||
<li> Supporting Windows helps us identify the portable portions
|
||||
of Mono from the non-portable versions of it, helping Mono
|
||||
become more portable in the future.
|
||||
|
||||
<li> Mono does not heavily modify the windows registry, update system DLLs,
|
||||
install DLLs to the Windows/System32 path. Another words, I knew Mono would
|
||||
not cause any legacy enterprise applications to stop working - and it
|
||||
hasn't. However, our CIO er is againt it because of the changes that would
|
||||
be made to Windows 2000, such as, affecting security.
|
||||
</ul>
|
||||
|
||||
<a name="compatibility"></a>
|
||||
** Compatibility
|
||||
|
||||
Q: Can Mono run applications developed with the Microsoft.NET framework?
|
||||
Q: Can Mono run applications developed with the Microsoft.NET fraemwork?
|
||||
|
||||
A: Yes, Mono can run applications developed with the Microsoft .NET Framework
|
||||
A: Yes, Mono can run applications developed with the Microsft .NET Framework
|
||||
on Unix. There are a few caveats to keep in mind: Mono has not
|
||||
been completed yet, so a few API calls might be missing; And in
|
||||
some cases the Mono behavior *might* be incorrect.
|
||||
@@ -589,71 +529,6 @@ A: Sometimes they will. But sometimes a .NET application might invoke
|
||||
Win32 API calls, or assume certain patterns that are not correct
|
||||
for cross-platform applications.
|
||||
|
||||
Q: What is a 100% .NET application?
|
||||
|
||||
A: A `100% .NET application' is one that only uses the APIs defined
|
||||
under the System namespace and does not use P/Invoke. These
|
||||
applications would in theory run unmodified on Windows, Linux,
|
||||
HP-UX, Solaris, MacOS X and others.
|
||||
|
||||
Note that this requirement also holds for all assemblies used by the
|
||||
application. If one of them is Windows-specific, then the entire program
|
||||
is not a 100% .NET application.
|
||||
|
||||
Furthermore, a 100% .NET application must not contain non-standard data
|
||||
streams in the assembly. For example, Visual Studio .NET will insert a
|
||||
<tt>#-</tt> stream into assemblies built under the "Debug" target.
|
||||
This stream contains debugging information for use by Visual Studio .NET;
|
||||
however, this stream can not be interpreted by Mono (unless you're willing
|
||||
to donate support).
|
||||
|
||||
Thus, it is recommended that all Visual Studio .NET-compiled code be
|
||||
compiled under the Release target before it is executed under Mono.
|
||||
|
||||
Q: Can I execute my Visual Studio .NET program (Visual Basic .NET, Visual C#,
|
||||
Managed Extensions for C++, etc.) under Mono?
|
||||
|
||||
A: Yes, with some reservations.
|
||||
|
||||
The .NET program must either be a 100% .NET application, or (somehow) have
|
||||
all dependent assemblies available on all desired platforms. (How to do so
|
||||
is outside the bounds of this FAQ.)
|
||||
|
||||
Mono must also have an implementation for the .NET assemblies used. For
|
||||
example the System.EnterpriseServices namespace is part of .NET, but it
|
||||
has not been implemented in Mono. Thus, any applications using this
|
||||
namespace will not run under Mono.
|
||||
|
||||
With regards to languages, C# applications tend to be most portable.
|
||||
|
||||
Visual Basic .NET applications are portable, but Mono's
|
||||
Microsoft.VisualBasic.dll implementation is incomplete. It is recommended
|
||||
to either avoid using this assembly in your own code, only use the
|
||||
portions that Mono has implemented, or to help implement the missing
|
||||
features. Additionally, you can set 'Option Strict On', which
|
||||
eliminates the implicit calls to the unimplemented
|
||||
Microsoft.VisualBasic.CompilerServices.ObjectType class.
|
||||
(Thanks to Jörg Rosenkranz.)
|
||||
|
||||
Managed Extensions for C++ is least likely to operate under Mono. Mono
|
||||
does not support mixed mode assemblies (that is, assemblies containing both
|
||||
managed and unmanaged code, which Managed C++ can produce). You need a
|
||||
fully-managed assembly to run under Mono, and getting the Visual C++ .NET
|
||||
compiler to generate such an executable can be difficult. You need to use
|
||||
only the .NET-framework assemblies, not the C libraries (you can't use
|
||||
<b>printf</b>(3) for example.), and you need to use
|
||||
the linker options <tt>/nodefaultlib /entry:main mscoree.lib</tt> in
|
||||
addition to the <tt>/clr</tt> compiler flag. You can still use certain
|
||||
compiler intrinsic functions (such as <b>memcpy</b>(3)) and the STL.
|
||||
You should also see <a
|
||||
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vcmex/html/vcgrfconvertingmanagedextensionsforcprojectsfrommixed-modetopureil.asp"
|
||||
>Converting Managed Extensions for C++ Projects from Mixed Mode to Pure
|
||||
Intermediate Language</a> at MSDN.
|
||||
Finally, you can use PEVERIFY.EXE from the .NET SDK to determine if the
|
||||
assembly is fully managed.
|
||||
|
||||
Thanks to Serge Chaban for the linker flags to use.
|
||||
|
||||
<a name="pnpproject"></a>
|
||||
** Mono and Portable.NET
|
||||
|
||||
@@ -805,8 +680,10 @@ A: MonoDoc is a graphical documentation browser for the Mono class
|
||||
Q: I am having trouble compiling a new version of Mono from CVS, it
|
||||
complains about my runtime being out of sync.
|
||||
|
||||
A: To upgrade your class libraries and compiler, see the
|
||||
INSTALL.txt in the MCS directory.
|
||||
A: Jonathan Pryor has provided the following answer:
|
||||
|
||||
To upgrade your class libraries and compiler, see the See
|
||||
README.building in the MCS directory.
|
||||
|
||||
The single biggest source of confusion seems to be the "Your
|
||||
runtime is out of sync" messages. Realize that this is *normal*
|
||||
@@ -822,18 +699,6 @@ A: To upgrade your class libraries and compiler, see the
|
||||
Once this is done, you can continue building your entire
|
||||
environment.
|
||||
|
||||
For instance you just need to:
|
||||
1.- Upgrade your Mono runtime (you might better do it with the
|
||||
mono-build.sh script available in the <a
|
||||
href="http://www.go-mono.com">download</a> page.
|
||||
2.- Get the latest mono-lite tarball from the daily snapshots
|
||||
<a href="http://www.go-mono.com/daily/">page</a>, unzip and
|
||||
untar and copy all the dll files to your install path lib
|
||||
directory (typically pointed by the $MONO_PATH variable).
|
||||
Copy all the exe files to the install path bin directory.
|
||||
3.- Then checkout or update your mcs CVS copy. Then follow
|
||||
the steps described in mcs/INSTALL.txt.
|
||||
|
||||
Q: Will it be possible to use the CLI features without using byte codes
|
||||
or the JIT?
|
||||
|
||||
@@ -850,9 +715,6 @@ A: With any luck, Free Software enthusiasts will contribute tools to
|
||||
initially using the Microsoft implementation of the CLI and then
|
||||
executed later with Mono.
|
||||
|
||||
We are recommending people to use and contribute to existing
|
||||
projects like SharpDevelop, Anjuta and Eclipse.
|
||||
|
||||
Q: What kind of rules make the Common Intermediate Language useful for
|
||||
JITers?
|
||||
|
||||
@@ -880,14 +742,32 @@ A: In Mono, xsp is just the name of the C# code generator for ASP.NET
|
||||
Pages" technology so as they are very different things, they don't
|
||||
conflict.
|
||||
|
||||
Q: What about using something like Jabber instead of the System.Messaging
|
||||
namespace?.
|
||||
|
||||
A: In short, MSMQ is not something like Jabber, but asynchronous messaging
|
||||
through queues. Useful queues do more than serialize messages, they are
|
||||
also platform bridges.
|
||||
|
||||
Q: Are you supporting XMLDocument and relatives?.
|
||||
|
||||
A: Currently, we aren't implementing them yet. It would require updates to
|
||||
most of the XmlNode derivatives so it's not a trivial task. We are
|
||||
currently focusing on getting XPath support working.
|
||||
|
||||
Q: Is there any plan to develop an aspx server for Mono?.
|
||||
|
||||
A: The XSP reference server is available and you can also use mod_mono
|
||||
with Apache.
|
||||
A: The web server turned out to be very simple compared to the rest of the
|
||||
work. Gonzalo has got the page generator mostly done (a module called
|
||||
xsp, who has nothing to do with the XSP term used in the Apache Project).
|
||||
Patrik has done a lot of the work to get the ProcessRequest to work.
|
||||
You can try to help in the final touches to the System.Web classes and
|
||||
writing regression tests for the widgets we have.
|
||||
|
||||
Q: Is there any way I can develop the class libraries using Linux yet?
|
||||
|
||||
A: Yes. Mono has been self hosting since May 2002.
|
||||
A: Yes. Some class libraries can be developed on Linux. Search for
|
||||
Paolo's post (he lists which classes can be compiled fine now).
|
||||
|
||||
Q: Is there any way I can install a known working copy of mono in /usr,
|
||||
and an experimental copy somewhere else, and have both copies use
|
||||
@@ -907,27 +787,37 @@ Q: Would it be too terrible to have another corlib signed as mscorlib?
|
||||
A: We rename corlib to mscorlib also when saving the PE files, in fact,
|
||||
the runtime can execute program created by mono just fine.
|
||||
|
||||
Q: Is there a relatively straightforward way to repeat the steps taken
|
||||
by Paolo to get Mono completely self-hosted on Linux?
|
||||
|
||||
A: To build the compiler and class libraries in Linux, run:
|
||||
<ul><li>make -f makefile.gnu. To install them, run: </li>
|
||||
<li>make -f makefile.gnu install prefix=/opt/mono</li>
|
||||
</ul>
|
||||
|
||||
If you want to produce and distribute a monocharge tarball, run:
|
||||
make -f makefile.gnu dist
|
||||
Of course you have to run these in the top level mcs directory.
|
||||
|
||||
Q: Is it possible to build a C# file to some sort of intermediate format which
|
||||
can linked into a final module, like the traditional .c -> .o -> .so path?
|
||||
|
||||
A: You can use:
|
||||
A: You could do: mcs /target:module file1.cs, mcs /target:module file2.cs,
|
||||
mcs /target:exe file1.dll file2.dll /out:mybin.exe
|
||||
|
||||
mcs /target:library file1.cs, mcs /target:library file2.cs,
|
||||
mcs /target:exe file1.dll file2.dll /out:mybin.exe
|
||||
Q: Is there any plans for implementing remoting in the near future?, When will
|
||||
work in System.Runtime.Remoting.dll start?
|
||||
|
||||
Q: Is there any plans for implementing remoting in the near future?
|
||||
A: The remoting infrastructure is in place. Some of the channels and
|
||||
formatters are not.
|
||||
|
||||
A: The remoting infrastructure is in place. We have implementations
|
||||
of the TcpChannel, HttpChannel and the Soap and Binary Formatters.
|
||||
They are compatible with .NET.
|
||||
|
||||
However, some classes from the library may have a different binary
|
||||
representation, because they may have a different internal data
|
||||
structure, so for example you won't be able to exchange a Hastable
|
||||
object between Mono and MS.NET. It should not be a problem if you
|
||||
are using primitive types, arrays or your own classes. In any case,
|
||||
could you post a test case?
|
||||
Q: I'm wondering if there are any plans to start using nant to build the
|
||||
class lib + test lib. i think that every project need/should use an
|
||||
automated build process and nant + a couple of tools enables this. is
|
||||
the problem that the compiler can't run nant yet?
|
||||
|
||||
A: Maybe well be doing some sort of automated build process + testing when
|
||||
the summer finish.
|
||||
|
||||
Q: My C code uses the __stdcall which is not availble on Linux, how can I
|
||||
make the code portable Windows/Unix across platforms?
|
||||
@@ -942,7 +832,7 @@ A: Replace the __stdcall attribute with the STDCALL macro, and include this
|
||||
Q: I want to be able to execute Mono binaries, without having to use the "mono"
|
||||
command. How can I do this?
|
||||
|
||||
A: From Carlos Perelló:
|
||||
A: From Carlos Perelló:
|
||||
|
||||
<i>I think that the best solution is the binfmt feature with the
|
||||
wrapper that exists with Debian packages at:
|
||||
@@ -958,23 +848,6 @@ A: From Carlos Perelló:
|
||||
This way you just execute: ./my-cool-mono-application.exe and it works
|
||||
without the need of any wrapper.</i>
|
||||
|
||||
Q: I see funny characters when I run programs, what is the problem?
|
||||
|
||||
A: (From Peter Williams and Gonzalo Paniagua):
|
||||
|
||||
This is Red Hat 9 (probably) using UTF8 on its console; the bytes are
|
||||
the UTF8 endianness markers. You can do:
|
||||
|
||||
LC_ALL=C mono myexe.exe
|
||||
|
||||
And they wont show up.
|
||||
|
||||
Alternatively, you can do:
|
||||
|
||||
$ echo -e "\033%G"
|
||||
|
||||
to enable UTF-8 on the console.
|
||||
|
||||
<a name="asp">
|
||||
** Mono and ASP.NET
|
||||
|
||||
@@ -1011,7 +884,7 @@ A: Modules developed for Apache 2 are not compatible with Apache 1.3
|
||||
|
||||
Q: Can I run Apache 1 and Apache 2 on the same machine?
|
||||
|
||||
You can always keep a copy of Apache 2 running in parallel with your Apache
|
||||
You can always keep a copy of Apache 2 running in paralell with your Apache
|
||||
1.3 (either different port or using a reverse proxy).
|
||||
|
||||
You can also bind the two servers to different IP addresses on the
|
||||
@@ -1077,11 +950,37 @@ A: Yes, Java could target the CLI, Microsoft's J# compiler does that.
|
||||
|
||||
Q: Is it possible to write a JVM byte code to CIL converter?
|
||||
|
||||
A: Yes, this is what <a href="http://weblog.ikvm.net">IKVM</a> does.
|
||||
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>
|
||||
|
||||
See also the <a href="http://weblog.ikvm.net/">IKVM project</a>
|
||||
|
||||
Q: Could mono become a hybrid CIL/java platform?
|
||||
|
||||
A: This can be obtained easily with IKVM.
|
||||
A: No. It is quite far from the philosophy of the project. The idea of Mono
|
||||
is, to have only _one_ VM, on which all can run. And if there existing a
|
||||
binary-converter from Java-.class to IL and if there existing something
|
||||
like J-Sharp on Mono, you can write programs in Java, which than can run
|
||||
on Mono. You do not need two bindings (like your example: GTK-Sharp _and_
|
||||
Java-Gnome). You need only _one_ of it (GTK-Sharp). Thats the idea of Mono.
|
||||
An other point is, that there are no people, who use Open Source-JVMs. They
|
||||
all prefer Suns original. But for Unix there don't exist a .NET-Framework.
|
||||
So it is possible, that in the future Mono is the standard .NET for Unixes.
|
||||
|
||||
Q: Do you plan to implement a Javascript compiler?
|
||||
|
||||
@@ -1122,7 +1021,7 @@ 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
|
||||
making incompatible changes to the technologies.
|
||||
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
|
||||
@@ -1132,11 +1031,6 @@ A: Embracing a good technology is good. Extending technologies in
|
||||
developed either by members of the Mono community, or other
|
||||
groups.
|
||||
|
||||
In some cases, we have found the bits from Microsoft to be
|
||||
incomplete, but we avoid breaking the API, instead we expose the
|
||||
missing functionality in new assemblies (See Mono.Security and
|
||||
System.Security).
|
||||
|
||||
Q: Is there any way I can develop the class libraries using Linux yet?
|
||||
|
||||
A: Yes. Mono has been selfhosting since March 2002.
|
||||
@@ -1168,14 +1062,11 @@ A: Our main intention at Ximian is to be able to develop GNOME
|
||||
|
||||
Q: What operating systems/CPUs do you support
|
||||
|
||||
A: Mono currently runs on Linux, Windows, Solaris, FreeBSD, HP-UX and
|
||||
MacOS X.
|
||||
|
||||
A: Mono currently runs on Linux, Windows, Solaris and FreeBSD.
|
||||
There is a JIT engine available for x86 processors that can
|
||||
generate code and optimizations tailored for a particular CPU.
|
||||
|
||||
Interpreters exist for the SPARC v8, SPARC v9, Itanium, HP-PA,
|
||||
PowerPC and StrongARM CPUs.
|
||||
Interpreters exist for the SPARC, PowerPC and StrongARM CPUs.
|
||||
|
||||
Q: Does Mono run on Windows?
|
||||
|
||||
@@ -1198,6 +1089,17 @@ A: It will depend only if you are using a particular assembly (for
|
||||
in Mono for implementing a `Hello World Enterprise P2P Web
|
||||
Service', you will not need any GNOME components.
|
||||
|
||||
Q: Is anyone working on porting Mono to IA-64?
|
||||
|
||||
A: Nobody is working on such port.
|
||||
|
||||
Q: If I were about to start a Mono port to IA-64,would the same lburg code
|
||||
generator work for IA-64 also? or anything else need to be used for code
|
||||
generation(as the processor architecture is totally different from IA32)
|
||||
|
||||
A: The lburg approach can be use for any processor architecture. But you might
|
||||
think in another better approach.
|
||||
|
||||
Q: Do you plan to port Rhino to C#?.
|
||||
|
||||
A: Eto Demerzal has started a Rhino port to C#.
|
||||
@@ -1217,17 +1119,34 @@ 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.
|
||||
|
||||
We are using some pieces of ORP (Their code generation interface)
|
||||
and we use it as a source of inspiration for optimizations. Paolo
|
||||
and Dietmar consider ORP as being one of the best JIT engines out
|
||||
there (and their research work and papers are very useful if you are
|
||||
interested in JIT technology).
|
||||
|
||||
Q: What about using GNU Lightning?
|
||||
|
||||
A: We are not using GNU Lightning. Our JIT is using an instruction
|
||||
selector based on tree-pattern matching, and a code generation
|
||||
interface that is very tied to the current architecture.
|
||||
|
||||
Q: Will I be able to use Microsoft SQL Server 2000 or will I need to switch
|
||||
to a specific Open Source Database. Will I need to recode?
|
||||
|
||||
A: There is no need to rewrite your code as long as you keep using
|
||||
Microsoft SQL Server. If you want to use an open source database,
|
||||
you might need to make changes to your code.
|
||||
A: There should not be any need to recode.
|
||||
|
||||
Q: What do I need to watch out for when programming in VB.NET so that I'm
|
||||
sure to be able to run those apps on Linux?
|
||||
|
||||
A: Not making any P/Invoke or DLL calls should and not using anything in
|
||||
A: Not making any PInvoke or DLL calls should and not using anything in
|
||||
the Microsoft.* namespaces should suffice. Also do not use any
|
||||
Methods/Classes marked as "This type/method supports the .NET Framework
|
||||
infrastructure and is not intended to be used directly from your code."
|
||||
@@ -1236,7 +1155,7 @@ A: Not making any P/Invoke or DLL calls should and not using anything in
|
||||
Q: Will built-in reporting be supported for crystal reports? This is a
|
||||
heavily used part of our system.
|
||||
|
||||
A: . Crystal Reports are propriety. Someone may try to emulate
|
||||
A: Probably not. Crystal Reports are propriety. Someone may try to emulate
|
||||
the behavior, but no-one has yet volunteered.
|
||||
|
||||
Q: Who about writing to the registry? As I understand it, Linux does not have
|
||||
@@ -1252,22 +1171,19 @@ A: Try to avoid it. Although there would be a emulation for registry in
|
||||
Q: System.Data.SqlClient with FreeTDS, will you port parts of these to C# and
|
||||
use them?
|
||||
|
||||
A: This has been done.
|
||||
A: if their license is compatible with mono's, yes, we'd think about porting
|
||||
them. If not, we'll continue with the plan of using FreeTDS.
|
||||
|
||||
<a name="gcc"></a>
|
||||
** Mono and GCC
|
||||
|
||||
Q: Are you working on a GCC front-end to C#? A GCC back-end that will
|
||||
generate CIL images?
|
||||
generate CIL images? What about making a front-end to GCC that
|
||||
takes CIL images and generates native code?
|
||||
|
||||
A: We would love to see a GCC modification that would generate CIL
|
||||
images, but there is nothing at this point.
|
||||
|
||||
Q: What about making a front-end to GCC that takes CIL images and
|
||||
generates native code?
|
||||
|
||||
A: There is no active work on this area, but Mono already provides
|
||||
pre-compilation services (Ahead-of-Time compilation).
|
||||
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?
|
||||
@@ -1275,6 +1191,12 @@ Q: But would this work around the GPL in the GCC compiler and allow
|
||||
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
|
||||
|
||||
@@ -1283,9 +1205,11 @@ 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'.
|
||||
|
||||
Mono's JIT engine has been recently re-architected, and it provides
|
||||
many new features, and layers suitable for optimization. It is
|
||||
relatively easy to add new optimizations to Mono.
|
||||
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
|
||||
@@ -1379,7 +1303,7 @@ A: First some background information.
|
||||
|
||||
The Mono strategy for dealing with these technologies is as
|
||||
follows: (1) work around the patent by using a different
|
||||
implementation technique that retains the API, but changes the
|
||||
implementation techinque that retains the API, but changes the
|
||||
mechanism; if that is not possible, we would (2) remove the pieces
|
||||
of code that were covered by those patents, and also (3) find prior
|
||||
art that would render the patent useless.
|
||||
@@ -1396,17 +1320,6 @@ A: First some background information.
|
||||
components, and things that we have developed (like Gtk#) or Apache
|
||||
integration.
|
||||
|
||||
Q: Is Mono only an implementation of the .NET Framework?
|
||||
|
||||
A: Mono implements both the .NET Framework, as well as plenty of class
|
||||
libraries that are either Unix specific, <a
|
||||
href="http://www.gnome.org">Gnome</a> specific, or that are not
|
||||
part of the .NET Framework but people find useful.
|
||||
|
||||
The following map shows the relationship between the components:
|
||||
|
||||
<img src="http://primates.ximian.com/~miguel/tmp/map.png">
|
||||
|
||||
<a name="etc"></a>
|
||||
** Miscellaneous Questions
|
||||
|
||||
@@ -1435,12 +1348,17 @@ Q: Will Ximian offer certifications on Mono or related technologies?.
|
||||
|
||||
A: It's possible. But there is no plan about this. So the short answer is no.
|
||||
|
||||
Q: Are there any Boehm's GC binaries?
|
||||
|
||||
A: Yes. You can find RPMs <a href="http://java.thn.htu.se/~toor/">here</a>, though
|
||||
if your distribution provides the correct packages, you should use those.
|
||||
The suggested version of the Boehm GC is 6.1.
|
||||
|
||||
Q: How can I report a bug?
|
||||
|
||||
A: The best thing is to track down the bug and provide a simple test
|
||||
to reproduce the bug. You can then add the bug to our bug tracking
|
||||
system. You can use our <a href="bugs.html">Bug Form</a> to enter
|
||||
bugs for the appropriate component.
|
||||
A: The best thing is to track down the bug and provide a simple test to
|
||||
reproduce the bug. You can then add the bug to the
|
||||
<a href="http://bugzilla.ximian.com/enter_bug.cgi">bugtracking system</a>.
|
||||
|
||||
Please provide information about what version of mono you're using
|
||||
and any relevant details to be able to reproduce the bug. Note that
|
||||
@@ -1491,18 +1409,10 @@ Q: Is it possible to use Visual C++ with Mono?.
|
||||
A: It's possible to run VC++ generated apps under Mono, but we do not
|
||||
provide a Manager C++ compiler ourselves.
|
||||
|
||||
Q: Does Mono support generics?.
|
||||
|
||||
A: Mono doesn't support generics currently but a lot of work is being
|
||||
done towards it.
|
||||
|
||||
<a name="problems"></a>
|
||||
** Mono Common Problems
|
||||
|
||||
If you are having problems compiling or running Mono software
|
||||
or if you think that you found a bug, etc. Please visit the
|
||||
<a href="http://monoevo.sf.net/mono-common-problems.html">Mono Common Problems</a> document and try there.
|
||||
<a href="http://geneura.ugr.es/~jaime/deploy/mono-common-problems.html">Mono Common Problems</a> document and try there.
|
||||
|
||||
** Credits
|
||||
|
||||
The FAQ contains material contributed by Miguel de Icaza, Jaime Anguiano, Lluis Sánchez.
|
||||
+80
-37
@@ -19,18 +19,19 @@
|
||||
<li>Bugs with Mono or the data provider should be reported
|
||||
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
|
||||
do not have Bugzilla user account, it is free
|
||||
and easy to create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
|
||||
and easy to
|
||||
create one <a href="http://bugzilla.ximian.com/createaccount.cgi">here</a>.</li>
|
||||
|
||||
</ul>
|
||||
|
||||
** Current Status
|
||||
|
||||
<ul>
|
||||
<li>Current stable version: 1.0</li>
|
||||
|
||||
<li>Current developement version: 1.5</li>
|
||||
|
||||
<li>The new data provider/driver is written in C# and provides a high-performance native
|
||||
<ul>
|
||||
<li>Currently, it is able to connect to Firebird and Interbase databases
|
||||
and execute commands</li>
|
||||
|
||||
<li>The new data
|
||||
provider/driver is written in C# and provides a high-performance native
|
||||
implementation of the GDS32/API functions. This means that .Net developers
|
||||
will be able to access Firebird databases without the need of Firebird
|
||||
client install</li>
|
||||
@@ -38,31 +39,74 @@
|
||||
<li>In support of the new module, a new mailing list
|
||||
<a href="http://lists.sourceforge.net/lists/listinfo/firebird-net-provider">firebird-net-provider</a> has
|
||||
been created. Please use this list for any
|
||||
questions that you may have about the provider</li>
|
||||
questions that you may have about the provider</li>
|
||||
|
||||
<li>Stuff that works:
|
||||
<ul>
|
||||
<li>Currently implemented classes:
|
||||
<ul>
|
||||
<li>Connection and Connection Pooling</li>
|
||||
<li>Command</li>
|
||||
<li>Transaction</li>
|
||||
<li>CommandBuilder</li>
|
||||
<li>DataAdapter</li>
|
||||
<li>DataReader</li>
|
||||
<li>Error</li>
|
||||
<li>ErrorCollection</li>
|
||||
<li>Exception</li>
|
||||
<li>Parameter</li>
|
||||
<li>ParameterCollection</li>
|
||||
<li>Transaction</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
** New features & enhancements in 1.5 version
|
||||
|
||||
** Action Plan
|
||||
|
||||
<ul>
|
||||
<li>Better fit to ADO.NET</li>
|
||||
|
||||
<li>New GDS implementation</li>
|
||||
|
||||
<li>Implicit transaction support</li>
|
||||
|
||||
<li>Array datatype support</li>
|
||||
|
||||
<li>Firebird services API support</li>
|
||||
|
||||
<li>Firebird events API support</li>
|
||||
|
||||
<li>Stored procedure calls using Sql Server style</li>
|
||||
|
||||
<li>Support for retrieve database schema information ( FbConnection.GetDbSchema )</li>
|
||||
|
||||
<li>Improved Commandbuilder implementation</li>
|
||||
</ul>
|
||||
|
||||
<li>Bug fixing</li>
|
||||
<li>Improving API reference documentation</li>
|
||||
<li>Full testing with Firebird 1.5</li>
|
||||
<li>Test with Mono ( http://www.go-mono.com )
|
||||
<ul>
|
||||
<li>Status : Started</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>Support for array datatype
|
||||
<ul>
|
||||
<li>Status : Started</li>
|
||||
<li>Comments: See Interbase API reference documentation</li>
|
||||
<li>Add new file FbArray.cs for array fields management</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>Support for Stored Procs calls that have returns values
|
||||
<ul>
|
||||
<li>Status : Pending.</li>
|
||||
<li>Comments: Modify the isc_dsql_prepare method of GDS implementation for
|
||||
allow to return the output parameters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>Implementation of FbClientPermission and FbClientPermissionAttribute
|
||||
<ul>
|
||||
<li>Status : Pending</li>
|
||||
<li>Comments: See if these are really needed for Firebird</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>Improve Logger implementation
|
||||
<ul>
|
||||
<li>Status: Pending</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
** Testing
|
||||
|
||||
<ul>
|
||||
@@ -95,13 +139,12 @@
|
||||
{
|
||||
public static void Main(string[] args)
|
||||
{
|
||||
string connectionString =
|
||||
"Database=C:\\PROGRAM FILES\\FIREBIRD\\EXAMPLES\\EMPLOYEE.GDB;" +
|
||||
"User=SYSDBA;" +
|
||||
"Password=masterkey;" +
|
||||
"Dialect=3;" +
|
||||
"Server=localhost";
|
||||
|
||||
string connectionString =
|
||||
"Database=C:\\PROGRAM FILES\\FIREBIRD\\EXAMPLES\\EMPLOYEE.GDB;" +
|
||||
"User=SYSDBA;" +
|
||||
"Password=masterkey;" +
|
||||
"Dialect=3;" +
|
||||
"Server=localhost";
|
||||
IDbConnection dbcon = new FbConnection(connectionString);
|
||||
dbcon.Open();
|
||||
IDbCommand dbcmd = dbcon.CreateCommand();
|
||||
@@ -109,7 +152,7 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
object dataValue = reader.GetValue(0);
|
||||
object dataValue = myReader.GetValue(0);
|
||||
string sValue = dataValue.ToString();
|
||||
Console.WriteLine("Value: " + sValue);
|
||||
}
|
||||
|
||||
@@ -1,72 +0,0 @@
|
||||
* Novell Forge
|
||||
|
||||
Novell Forge (<a
|
||||
href="http://forge.novell.com/">http://forge.novell.com/</a>)
|
||||
is a website managed by Novell to promote the development of
|
||||
open source applications and solutions. Novell Forge features
|
||||
communities, akin to foundries on SourceForge.net, which exist
|
||||
for the purpose of facilitating collaboration and information
|
||||
exchange about certain technologies or solutions. At Miguel's
|
||||
request, we have created a Mono community on Novell Forge that
|
||||
is administered by Miguel. This community, located at
|
||||
http://forge.novell.com/modules/xfmod/community/?monocomm,
|
||||
provides a resource for interaction and collaboration on Mono
|
||||
and associated solutions. Each community has the ability to
|
||||
provide forums, mailing lists, FAQs, news, documentation,
|
||||
surveys, sample code, and links to related applications. The
|
||||
Mono community has been created for anyone interested in Mono
|
||||
to use, and the exact set of features offered at the community
|
||||
is determined by Miguel.
|
||||
|
||||
Any individual or group that wishes to provide Mono-based solutions in
|
||||
an open source fashion is encouraged to host their solution on the
|
||||
Novell Forge website, free of charge. Once the project is hosted on
|
||||
Novell Forge, you can send Miguel an e-mail requesting that your project
|
||||
be associated with the Mono project. This promotes a symbiotic
|
||||
relationship where the growth of Mono applications helps to improve
|
||||
Mono, and the growth of Mono likewise helps to increase the visibility
|
||||
and usefulness of your applications.
|
||||
|
||||
* Creating an Account
|
||||
|
||||
A Novell Forge account is required in order to create a project on
|
||||
Novell Forge as well as for certain levels of participation within a
|
||||
community like the Mono community. In order to create an account, do
|
||||
the following:
|
||||
|
||||
<ul>
|
||||
|
||||
<li>Go to http://forge.novell.com/ and click on the "Register" link.
|
||||
|
||||
<li>You will be redirected to the Novell Login page. This one resource
|
||||
is used by all of Novell's websites that require authentication, so if
|
||||
you already have a Novell login you may use that login here. Otherwise,
|
||||
simply create a login account.
|
||||
|
||||
<li>You will be redirected back to the Novell Forge page. Click on the
|
||||
"create my Novell Forge account" link, near the top left of the page.
|
||||
|
||||
<li>A form should be filled in with the correct information for you.
|
||||
If you like, choose an avatar and then submit the form.
|
||||
|
||||
<li>Confirm the creation of your account.
|
||||
</ul>
|
||||
|
||||
|
||||
You should be good to go at this point. Now, to create a project,
|
||||
simply choose the "Start New Project" link from the left menu and follow
|
||||
the steps.
|
||||
|
||||
Novell Forge offers a limited set of context-sensitive help links and a
|
||||
full help section. If you have trouble, go to the help section at
|
||||
http://forge.novell.com/modules/xfmod/help/about.php.
|
||||
|
||||
|
||||
* Important Links:
|
||||
|
||||
Novell Forge - <a href="http://forge.novell.com/">http://forge.novell.com/</a>
|
||||
|
||||
Mono Community - <a href="http://forge.novell.com/modules/xfmod/community/?monocomm">http://forge.novell.com/modules/xfmod/community/?monocomm</a>
|
||||
|
||||
Novell Forge Help - <a href="http://forge.novell.com/modules/xfmod/help/about.php">http://forge.novell.com/modules/xfmod/help/about.php</a>
|
||||
|
||||
@@ -15,13 +15,25 @@
|
||||
<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).
|
||||
@@ -33,6 +45,7 @@
|
||||
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
|
||||
@@ -45,10 +58,23 @@
|
||||
|
||||
This list of projects ideas is outdated
|
||||
|
||||
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=Bonobo,Bonobo for Mono
|
||||
* Once <a href="http://remoting-corba.sourceforge.net/">CORBA</a> 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
|
||||
|
||||
@@ -12,14 +12,15 @@
|
||||
Common Language Infrastructure (also referred as the CLR) and a
|
||||
set of <a href="class-library.html">class libraries</a>. The
|
||||
runtime can be <a href="embedded-api.html">embedded</a> into your
|
||||
application. It implements of both <a href="ado-net.html">ADO.NET</a>
|
||||
and <a href="asp-net.html">ASP.NET</a>.
|
||||
application.
|
||||
|
||||
Mono has implementations of both <a href="ado-net">ADO.NET</a>
|
||||
and <a href="asp-net">ASP.NET</a> as part of its distribution.
|
||||
|
||||
You can read our <a href="rationale.html">rationale</a> for
|
||||
this project. If you have questions about the project, please
|
||||
read our list of <a href="faq.html">Frequently Asked
|
||||
Questions</a> or <a href="mailto:[email protected]">contact
|
||||
us.</a> The project <a href="mono-roadmap.html">roadmap</a>.
|
||||
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
|
||||
@@ -33,9 +34,16 @@
|
||||
href="http://www.gotmono.com/cgi-bin/yabb/YaBB.pl">forum</a> at <a
|
||||
href="http://www.gotmono.com">GotMono</a>.
|
||||
|
||||
Wikis: <a href="http://www.nullenvoid.com/gtksharp/wiki">Gtk# Wiki</a>
|
||||
and <a href="http://www.nullenvoid.com/mono/wiki">Mono
|
||||
Wiki</a>
|
||||
You can contact the team at: <a
|
||||
href="mailto:mono-list@ximian.com">mono[email protected]</a>
|
||||
|
||||
In order to follow the process of the project and to learn more
|
||||
about the team members we have created the <a
|
||||
href="http://monoevo.sf.net/mwn/index.html">Mono Weekly News letter</a>.
|
||||
Which archives can be found <a
|
||||
href="http://monoevo.sf.net/mwn/archives.html">here</a>.
|
||||
We have a <a href="http://www.nullenvoid.com/gtksharp/wiki">Gtk# Wiki</a>
|
||||
and a <a href="http://www.nullenvoid.com/mono/wiki">Mono Wiki</a>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
@@ -68,12 +76,14 @@
|
||||
</td>
|
||||
<td>
|
||||
Working:<br>
|
||||
Linux/x86, Linux/PPC, S390, StrongARM, SPARC, HPPA, SPARC v9 <br>
|
||||
Linux/x86, Linux/PPC, S390, StrongARM<br>
|
||||
In progress:<br>
|
||||
SPARC.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><b><a href="asp-net.html">ASP.NET</a></b></td>
|
||||
<td>Webforms and WebServices working<br></td>
|
||||
<td>Webforms working<br></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
@@ -141,454 +151,10 @@
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@item Nov 25th: Gtk# 0.14, System.DirectoryServices
|
||||
@item Jun 23rd, 2003: DiaCanvas#, Turkish presentation
|
||||
|
||||
Gtk# 0.14 has been released, and it is available from <a
|
||||
href="http://gtk-sharp.sf.net">the Gtk# web site</a>.
|
||||
http://enver.casdb.com/sunumlar/mono/
|
||||
|
||||
Sunil has checked in the implementation of
|
||||
System.DirectoryServices as well as the Novell.Directory.Ldap
|
||||
code into Mono CVS.
|
||||
|
||||
@item Nov 14th: Gtk# 0.13 released.
|
||||
|
||||
Mike Kestner has <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-November/016943.html">announced</a>
|
||||
the release of the <a href="http://gtk-sharp.sf.net">Gtk#</a>
|
||||
GUI toolkit for .NET and Mono.
|
||||
|
||||
@item Nov 13th: Managed LDAP binding for Mono and .NET
|
||||
|
||||
Sunil Kumar at Novell has <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-November/016907.html">announced</a>
|
||||
the availability of a fully managed implementation of LDAP for
|
||||
Mono and the .NET Framework.
|
||||
|
||||
You can obtain the library from <a
|
||||
href="http://forge.novell.com">Novell Forge's</a> <a
|
||||
href="http://forge.novell.com/modules/xfmod/cvs/cvsbrowse.php/ldapcsharp/CsharpLDAP">CSharpLDAP</a>
|
||||
module.
|
||||
|
||||
@item Nov 4th: Mono Roadmap announced.
|
||||
|
||||
The <a href="mono-roadmap.html">Mono Roadmap</a> and <a
|
||||
href="mono-hacking-roadmap.html">Mono Hackers Roadmap</a> have
|
||||
been released.
|
||||
|
||||
@item Oct 28th: Mono Get Together at the PDC. GTK# 0.12 Released.
|
||||
|
||||
We will be getting together at the West Tower Lobby on Tuesday
|
||||
28th at 6pm to talk about the Mono project. You have 24 hours to
|
||||
notify all of your friends, open source buddies and free software
|
||||
folks.
|
||||
|
||||
We will bring Mono t-shirts.
|
||||
|
||||
Mike Kestner released <a href="http://gtk-sharp.sourceforge.net">Gtk#</a> 0.12 today. GTK# source tar balls
|
||||
and RPMs are available. A windows installer was contributed by Johannes Roith.
|
||||
|
||||
@item Oct 26th: Last Minute Mono BOF
|
||||
|
||||
The first in a series of undercover Mono BOFs at the PDC will take
|
||||
place tonight at 7pm on the Academy meeting, in room 411. Come join us
|
||||
to plot the evolution.
|
||||
|
||||
|
||||
@item Oct 25th: GTK# 0.11+ Windows Installer available
|
||||
|
||||
Johannes created a <a href="http://java.thn.htu.se/~toor/gtk-sharp/gtk-sharp-0.11-cvs.exe">Windows Installer for GTK# 0.11+</a> and works
|
||||
with Mono 0.28 for Windows.
|
||||
|
||||
@item Oct 21st: Mono Community at Novell Forge
|
||||
|
||||
Mono Developers that are looking for a public repository for
|
||||
hosting their projects can now use <a
|
||||
href="http://forge.novell.com">Novell Forge's</a> which hosts
|
||||
a <a
|
||||
href="http://forge.novell.com/modules/xfmod/community/?monocomm">Mono
|
||||
Community</a>.
|
||||
|
||||
Novell Forge offers mailing lists, cvs repository, bug
|
||||
tracking and mailing list services and all the other services
|
||||
you expect. Mono will continue to be hosted in our own CVS
|
||||
repository, and using our <a href="anoncvs.html">anonymous CVS
|
||||
servers</a>
|
||||
|
||||
@item Oct 13th: SPARC V9, HPPA, Internationalization, GdiPlus
|
||||
|
||||
Dick Porter has checked in our rewrite of the international
|
||||
substrate in Mono that uses the <a
|
||||
href="http://oss.software.ibm.com/icu/">International
|
||||
Components for Unicode</a> library from IBM. This means that
|
||||
we got CultureInfo support through the whole code base now.
|
||||
|
||||
Alexandre Pigolkine has checked-in the new implementation of
|
||||
System.Drawing. We have now dropped the old implementation
|
||||
with multiple-backends that we had, and replaced it with an
|
||||
implementation that P/Invokes into GDI+. A GDI+
|
||||
implementation on top of <a
|
||||
href="http://www.cairographics.org">Cairo</a> is used on Unix
|
||||
systems. This step vastly simplifies the development and
|
||||
maintenance of System.Drawing.
|
||||
|
||||
There are plenty of updates to Mono as well, we encourage you
|
||||
to read the <a
|
||||
href="http://www.go-mono.com/monologue">Monologue</a> to keep
|
||||
an eye on recent developments.
|
||||
|
||||
Bernie Solomon just <a
|
||||
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-October/002460.html">checked
|
||||
in</a> 64-bit support for SPARC v9 and HPPA into the Mono
|
||||
runtime. This also improves the SPARC-32 support.
|
||||
|
||||
@item Oct 6th: Linux s390 Mono packages available.
|
||||
|
||||
Neale Ferguson has contributed Mono packages for the
|
||||
Linux/s390. You can get them from the <a
|
||||
href="download.html">download</a> page.
|
||||
|
||||
@item Oct 5th: Monologue aggregates Mono Blogs
|
||||
|
||||
You can now read an aggregated view of the <a
|
||||
href="blogs.html">blogs</a> maintained by Mono developers in
|
||||
<a href="http://www.go-mono.com/monologue">Monologue</a>.
|
||||
Monologue is available as an HTML page or as an <a
|
||||
href="monologue/index.rss">RSS feed</a>.
|
||||
|
||||
@item Oct 2nd: Windows packages, MonoDoc 0.7
|
||||
|
||||
Windows packages for Mono 0.28 are now available from our <a
|
||||
href="download.html">download</a> page.
|
||||
|
||||
A new version of MonoDoc has been released. The new version
|
||||
is available <a href="archive/monodoc-0.7.tar.gz">here</a>
|
||||
|
||||
@item Oct 1st: Mono 0.28 has been released.
|
||||
|
||||
Check out the <a
|
||||
href="http://www.go-mono.com/archive/mono-0.28.html">Release
|
||||
notes</a> for details on Mono 0.28. This release marks the
|
||||
completion of the SourceGear project to add web services
|
||||
functionality to Mono and improve its reliability.
|
||||
|
||||
@item Sep 30th: Mono Kick Start book available
|
||||
|
||||
The Mono Kick Start book is now <a
|
||||
href="http://www.amazon.com/exec/obidos/tg/detail/-/0672325799/qid=1064937318/sr=8-1/ref=sr_8_1/103-9624440-8714218?v=glance&s=books&n=507846">available</a>
|
||||
in English. Originally available only in <a
|
||||
href="http://www.amazon.de/exec/obidos/ASIN/3827264928/qid=1050051051/sr=2-1/ref=sr_2_3_1/028-2755135-1623712">German</a>.
|
||||
The book technical review was done by <a
|
||||
href="http://www.maurer-it.com/">Dietmar Maurer</a> JIT
|
||||
architect at the Mono team.
|
||||
|
||||
@item Sep 26th, 2003: DiaCanvas# 0.1 released, Gtk# 0.11 released.
|
||||
|
||||
Mike Kestner has <a
|
||||
href="http://lists.ximian.com/archives/public/gtk-sharp-list/2003-September/002475.html">released</a>
|
||||
a new version of <a href="http://gtk-sharp.sf.net">Gtk#</a>.
|
||||
|
||||
Martin has also
|
||||
<a href="http://mwh.sysrq.dk/programs/announcements/diacanvas-sharp-0.1.0.html">released</a>
|
||||
his binding to <a href="http://diacanvas.sf.net">DiaCanvas</a> for C#.
|
||||
|
||||
@item Sep 16th, 2003: WineLib, Authenticode, Generics, Xslt updates, Wsdl compiler, WSE.
|
||||
|
||||
<b>WineLib:</b> Vladimir has added new libraries to the Wine
|
||||
process, which we will soon bring into our packages: the
|
||||
various Windows common dialogs can now be used (screenshots:
|
||||
<a href="images/colordlg.png">here</a>, <a
|
||||
href="images/fontdlg.png">here</a>, <a
|
||||
href="images/filedlg.png">here</a> and <a
|
||||
href="images/finddlg.png">here</a>.
|
||||
|
||||
Johannes has patches to have Wine track the Gtk theme,
|
||||
screenshot <a href="http://www.sport-huettn.de/jroith/swfsample.png">here</a>
|
||||
|
||||
<b>Security:</b> New authenticode support from Sebastien has
|
||||
been checked into CVS.
|
||||
|
||||
<b>Xslt:</b> Plenty of conformance updates to the managed
|
||||
implementation of Xslt, as well as breaking the libxslt speed
|
||||
barrier. Our managed implementation is now faster than the
|
||||
C-based libxslt that we used before.
|
||||
|
||||
<b>Generics:</b> Work continues on generics support, feel free
|
||||
to try it out. The compiler is currently on a separate
|
||||
directory until we stability it (gmcs) and you need to compile
|
||||
the class libraries with the `generics' profile to try it
|
||||
out. Sample generic programs are included in the CVS module.
|
||||
|
||||
<b>Wsdl:</b> We now have Wsdl support in Mono: a wsdl compiler
|
||||
command line tool, and support on ASP.NET to generate the wsdl
|
||||
file from an .asmx file.
|
||||
|
||||
<b>AOT:</b> Many robustness updates to the ahead-of-time
|
||||
compiler and a new locking and threading system that avoids
|
||||
having "big locks" around the mono kernel, and moves to a
|
||||
fine-grained locking system. The design includes a lattice to
|
||||
avoid deadlocks.
|
||||
|
||||
<b>Dogfooding:</b> We are now running Mono's ASP.NET on
|
||||
go-mono.com to find problems. It is currently hosting our
|
||||
Monodoc documentation. The <a
|
||||
href="http://www.go-mono.com/docs/index.html">Apache module
|
||||
version</a> and the <a href="http://www.go-mono.com:8080/">XSP
|
||||
version</a>.
|
||||
|
||||
<b>WSE:</b> The Web Services Enhancements season has begun.
|
||||
The Microsoft.Web.Services namespace and classes are now
|
||||
checked into CVS.
|
||||
|
||||
@item Sep 1st, 2003: Ice for Mono; XmlSerializer generators; Monodoc progress.
|
||||
|
||||
<b>Ice:</b> Vladimir has checked into CVS (Module ginzu) an
|
||||
implementation of <a href="http://www.zeroc.com">ZeroC's</a>
|
||||
<a href="http://www.zeroc.com/ice.html">ICE</a> protocol. It
|
||||
is implemented using Remoting. If you were looking for an
|
||||
efficient binary protocol to use with Remoting, this is it.
|
||||
|
||||
ICE is simpler to use than CORBA, and was created by people
|
||||
who were deeply involved in CORBA and wanted to fix its
|
||||
problems (you can see a <a
|
||||
href="http://www.zeroc.com/iceVsCorba.html">list of
|
||||
differences</a>).
|
||||
|
||||
<b>XmlSerializer</b>: Lluis has checked in a new technology
|
||||
for use in our XmlSerializer: the XmlSerializer code
|
||||
generator. Currently our XmlSerializer generates a
|
||||
description of instructions for serializing data, these
|
||||
instructions are later interpreted while using it: Reflection
|
||||
is used to pull all the data. The code generator is the first
|
||||
step into turning the Serializer from an intepreter into a
|
||||
compiler and improving the performance of it.
|
||||
|
||||
Currently was used internally to implement the WSDL
|
||||
serializer, in the future it will just be part of the standard
|
||||
serialization process.
|
||||
|
||||
<b>MonoDoc:</b> New providers! Thanks to <a
|
||||
href="http://www.jaggersoft.com/">Jon Jagger</a> for providing
|
||||
us with his master XML files for the C# specification we now
|
||||
have integrated the C# spec into Monodoc. Another provider is
|
||||
the Error provider: now we include all the C# compiler errors
|
||||
in the help system.
|
||||
|
||||
Alp has contributed various user interface improvement, and
|
||||
updated our list widget for key navigation; Ben made the
|
||||
matches window more useful and Joshua has helped us clean up
|
||||
the ECMA provider even more.
|
||||
|
||||
@item Aug 14th, 2003: Mono 0.26 has been released
|
||||
|
||||
A new version of Mono is available, the new features include:
|
||||
<a href="http://www.cairographics.org/">Cairo support</a>, <a
|
||||
href="http://remoting-corba.sf.net">Remoting.Corba</a>
|
||||
support, as well as a managed XSLT implementation.
|
||||
|
||||
Existing features have been improved vastly: better
|
||||
Windows.Forms, runtime, faster compiler, web services, better
|
||||
compliance to the spec and more.
|
||||
|
||||
Check out the <a
|
||||
href="http://www.go-mono.com/archive/mono-0.26.html">Release
|
||||
notes</a> for details.
|
||||
|
||||
@item Aug 9th, 2003: Python for .NET Preview 2 available; Mono Documentation site up.
|
||||
|
||||
Brian Lloyd has <a
|
||||
href="http://lists.ximian.com/archives/public/mono-list/2003-August/015313.html">announced</a>
|
||||
the availability of his Python binding to .NET. This works
|
||||
with .NET and Mono. For more information about it, see
|
||||
Brian's site at <a href="
|
||||
http://zope.org/Members/Brian/PythonNet/">http://zope.org/Members/Brian/PythonNet/</a>
|
||||
|
||||
We have uploaded the current Mono Documentation (core
|
||||
libraries and Gtk#) to <a
|
||||
href="http://mono.ximian.com:8080"/>http://mono.ximian.com:8080</a>.
|
||||
The site is running the ASP.NET edition of <a
|
||||
href="archive/monodoc-0.6.tar.gz">MonoDoc 0.6</a> on XSP.
|
||||
|
||||
@item Aug 6th, 2003: Winforms samples
|
||||
|
||||
Timothy Parez is coordinating the effort to create sample
|
||||
programs that exercise the various Windows.Forms controls. We
|
||||
are using this as graphical regression test suite for the Mono
|
||||
implementation.
|
||||
|
||||
The screenshots of the various widgets, together with the
|
||||
source code is available on the <a
|
||||
href="http://www.nullenvoid.com/mono/wiki/index.php/WineSamples">WineSamples</a>
|
||||
page on the <a
|
||||
href="http://www.nullenvoid.com/mono/wiki/">Mono Wiki</a>.
|
||||
|
||||
A new cvs module called `winforms' has been created that
|
||||
contains the source code for the samples. To run the samples,
|
||||
you can install the WineLib packages available from our <a
|
||||
href="download.html">download page</a>.
|
||||
|
||||
@item Aug 5th, 2003: New Apache Module architecture: 1.3 and 2.x supported
|
||||
|
||||
Gonzalo rearchitected our Apache module for hosting Mono and
|
||||
ASP.NET. The previous incarnation hosted a Mono runtime on
|
||||
each Apache process, which lead to a slow setup for webforms.
|
||||
The new setup uses a shared mono process for all the incoming
|
||||
requests. Daniel later improved up the new architecture and
|
||||
added dual support, so now in addition to Apache 2.x, we
|
||||
support Apache 1.3 with the same codebase.
|
||||
|
||||
The new code is available on CVS, on module `mod_mono', and
|
||||
now requires an XSP installation to be available.
|
||||
|
||||
@item Aug 4th, 2003: Ximian acquired by Novell.
|
||||
|
||||
Today <a href="http://www.novell.com">Novell</a> acquired <a
|
||||
href="http://www.ximian.com">Ximian</a>. The press release is
|
||||
available <a
|
||||
href="http://www.ximian.com./about_us/press_center/press_releases/index.html?pr=novell">here</a>.
|
||||
|
||||
Mono and Gnome form an integral part of the Novell strategy.
|
||||
|
||||
@item Jul 30th, 2003: Remoting.CORBA, Managed XSLT.
|
||||
|
||||
Today Lluis announced that Mono CVS contains all the fixes to
|
||||
run <a
|
||||
href="http://remoting-corba.sourceforge.net/">Remoting.CORBA</a>:
|
||||
both client and server channels work; We are interested in people
|
||||
testing it with other ORBs.
|
||||
|
||||
Ben checked-in today his managed implementation of Xslt that
|
||||
we mentioned on Jul 19th; This uncovered various limitations
|
||||
on the XPath implementation, which Piers has swifly removed.
|
||||
Monodoc, NUnit and our Corcompare work with it. Since this is
|
||||
implementation is not completed yet, we still support the
|
||||
libxslt-based version by default. For more details on how to
|
||||
try the new XSLT implementation, see <a
|
||||
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001681.html">Ben's
|
||||
post</a>
|
||||
|
||||
@item Jul 27th, 2003: Wine packages and Daily Snapshots
|
||||
|
||||
MonoWine packages (used to run System.Windows.Forms) software
|
||||
are now available from our (<a
|
||||
href="download.html">download</a> page). You can track the
|
||||
progress on our <a
|
||||
href="http://www.nullenvoid.com/mono/wiki/index.php/WineSamples">Wiki
|
||||
page.</a>
|
||||
|
||||
We're now building daily snapshots of Mono. They come in
|
||||
three distinct flavors:
|
||||
|
||||
<ul>
|
||||
* mono snapshot tarballs - These are 'release-style' tarballs and
|
||||
contain everything necessary to setup a new
|
||||
installation from scratch. This includes the Mono
|
||||
runtime and all the assemblies we distribute.
|
||||
|
||||
* monocharge tarballs - These tarballs contain only
|
||||
the assemblies built on that day.
|
||||
|
||||
* monolite tarballs - These tarballs contain a copy of
|
||||
'corlib.dll', 'mcs.exe', 'System.dll', 'System.Xml.dll' and
|
||||
'Mono.CSharp.Debugger.dll'. They can be used to
|
||||
re-bootstrap an out-of-sync installation.
|
||||
</ul>
|
||||
|
||||
The daily builds are availble here: <a href="http://go-mono.com/daily">http://go-mono.com/daily</a>
|
||||
|
||||
If you find that the builds are broken, please notify Duncan.
|
||||
|
||||
@item Jul 19th, 2003: Recent developments
|
||||
|
||||
Since Mono has matured, we have limited the news on the site
|
||||
to major accomplishments that are finished, but this week, it
|
||||
is worth devoting some time to talk about some of the
|
||||
work-in-progress projects that are progressing.
|
||||
|
||||
Jackson has added support to the IL assembler for generics as
|
||||
well as to the PEAPI library, and it has assembled its first
|
||||
generic program. Support for handling images with generics
|
||||
has been on our file format reader for a while, but the JIT
|
||||
engine is still incomplete.
|
||||
|
||||
On the XSLT world, Atsushi and Ben continue to make big
|
||||
improvements. Ben recently got the prototype managed XSLT
|
||||
implementation to run its first stylesheet. Although
|
||||
currently Mono uses libxslt to implement the System.Xml.Xsl
|
||||
namespace, to have a fully .NET compliant implementation we
|
||||
will need a managed version, and this is the beginning of it.
|
||||
|
||||
Lluis recently posted an update on the <a
|
||||
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001550.html">state
|
||||
of WSDL</a> in Mono. Now that the web services runtime is
|
||||
ready, the WSDL compiler becomes more important as a
|
||||
development tool.
|
||||
|
||||
Atsushi continues his work on the DTD validating reader in
|
||||
System.Xml, as well as improving our XML Schema support.
|
||||
|
||||
@item Jul 14th, 2003: New build system; IPV6 support.
|
||||
|
||||
Peter Williams has contributed a new build system that
|
||||
addresses many of the annoyance we had with our previous build
|
||||
system. He has worked on this for a few weeks, and Gonzalo
|
||||
helped test it and get it into CVS. We no longer have the
|
||||
historical dual build system: make for Unix and nant for
|
||||
Windows.
|
||||
|
||||
This system also offers the opportunity to compile our class
|
||||
libraries with different profiles (.NET 1.0, .NET 1.1 and the
|
||||
various ECMA subsets).
|
||||
|
||||
Peter explains the new build system <a
|
||||
href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001506.html">here</a>
|
||||
|
||||
Jerome's IPV6 code has been checked into CVS; With Peter's new
|
||||
build system, we will be able to expose it (as part of the
|
||||
NET_1_1 build).
|
||||
|
||||
@item Jul 9th, 2003: ASP.NET web services, coverage tools.
|
||||
|
||||
Web Services keep advancing: now we also support server-side
|
||||
authoring of Web Services as well as web service clients
|
||||
(which shipped in Mono 0.25). This works using our ASP.NET
|
||||
runtime, so it works with either XSP or the Apache module. The
|
||||
new Web Services work from Lluis added the missing bits:
|
||||
<ul>
|
||||
<li> .asmx files.
|
||||
<li> Method calls with complex parameters (whatever XmlSerializer can currently serialize, which is a quite a lot).
|
||||
<li> ref and out parameters.
|
||||
<li> Soap headers (In, Out and InOut).
|
||||
<li> Soap extensions, both global (configured in web.config) and particular to methods (configured using attributes).
|
||||
</ul>
|
||||
|
||||
For more details, see Lluis <a href="http://lists.ximian.com/archives/public/mono-devel-list/2003-July/001449.html">post</a>
|
||||
|
||||
GUI-wise: Work on <a href="http://xr.xwin.org">Xr</a> to
|
||||
implement System.Drawing continues. This will provide a full
|
||||
GDI+ implementation for Mono, and this will be hooked up into
|
||||
Gtk# and System.Windows.Forms.
|
||||
|
||||
MonoDoc keeps moving along, with a new web-based version
|
||||
coming up next, and we are also exploring a collaborative
|
||||
extension to allow people to contribute documentation through
|
||||
their web browsers.
|
||||
|
||||
Zoltan's Coverage analysis tool has been checked into CVS.
|
||||
With this tool it is now possible to find which class library
|
||||
code paths are missing regression tests. The module is
|
||||
`monocov'. Details are <a
|
||||
href="http://www.nexus.hu/vargaz/">here</a>. A fresh Gtk#
|
||||
version is available now.
|
||||
|
||||
Jean's remoting-based Soap implenentation is also maturing.
|
||||
|
||||
@item Jun 26th: Mono 0.25 has been released.
|
||||
|
||||
We have released Mono 0.25. A list of the new features is
|
||||
available <a href="archive/mono-0.25.html">here</a>.
|
||||
|
||||
Packages for Windows, and various Linux distributions are
|
||||
available on our <a href="download.html">download</a> page.
|
||||
|
||||
@item Jun 17th, 2003: Web Services client; Profiling hooks
|
||||
|
||||
@@ -636,7 +202,7 @@
|
||||
that SourceGear Corporation will use Mono\x{2122} Project
|
||||
technology to offer cross-platform versions of its
|
||||
products. In addition, the companies have entered into a
|
||||
development partnership under which Ximian will provide
|
||||
development partnership under which Ximian® will provide
|
||||
custom Mono development to enable delivery of SourceGear
|
||||
products later this year. As a result, SourceGear will offer
|
||||
both UNIX and Linux clients for its SourceGear Vault source
|
||||
@@ -1526,6 +1092,4 @@
|
||||
|
||||
<h2>Older News</h2>
|
||||
|
||||
Click <a href="oldnews.html">here</a> to see the olds news.
|
||||
|
||||
|
||||
Click <a href="oldnews.html">here</a> to see the olds news.
|
||||
+1
-29
@@ -13,34 +13,6 @@
|
||||
Notice that the program will need to be compiled with the -g
|
||||
flag and that running with --debug will slow down the execution.
|
||||
|
||||
* Debugging with GDB
|
||||
|
||||
If you use GDB to debug your mono process, you can use the function
|
||||
print_method_from_ip(void *address) to obtain the name of a method
|
||||
given an address.
|
||||
|
||||
For example:
|
||||
|
||||
<pre>
|
||||
(gdb) where
|
||||
#0 ves_icall_System_String_GetHashCode (me=0x80795d0) at string-icalls.c:861
|
||||
#1 0x0817f490 in ?? ()
|
||||
#2 0x0817f42a in ?? ()
|
||||
#3 0x0817f266 in ?? ()
|
||||
#4 0x0817f1a5 in ?? ()
|
||||
</pre>
|
||||
|
||||
You can now use:
|
||||
|
||||
<pre>
|
||||
(gdb) p print_method_from_ip (0x0817f490)
|
||||
IP 0x817f490 at offset 0x28 of method (wrapper managed-to-native) System.String:GetHashCode () (0x817f468 0x817f4a4)
|
||||
$1 = void
|
||||
(gdb) p print_method_from_ip (0x0817f42a)
|
||||
IP 0x817f42a at offset 0x52 of method System.Collections.Hashtable:GetHash (object) (0x817f3d8 0x817f43b)
|
||||
$2 = void
|
||||
</pre>
|
||||
|
||||
* Mono Debugger
|
||||
|
||||
The Mono debugger is written in C# and can debug both managed
|
||||
@@ -66,4 +38,4 @@ $2 = void
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
+16
-20
@@ -9,7 +9,6 @@
|
||||
* <a href="#Oberon">Oberon</a>
|
||||
* <a href="#Forth">Forth</a>
|
||||
* <a href="#mbas">Mono Basic</a> (Mono's VB.NET compiler)
|
||||
* <a href="#dotlist">dotLisp</a>
|
||||
</ul>
|
||||
|
||||
Languages which are known to run, but we have not done a
|
||||
@@ -85,9 +84,9 @@
|
||||
** Component Pascal
|
||||
|
||||
The Component Pascal compiler: <a
|
||||
href="http://www.citi.qut.edu.au/research/plas/projects/cp_files/cpnet.html">Home
|
||||
href="http://www2.fit.qut.edu.au/CompSci/PLAS/ComponentPascal">Home
|
||||
Page</a>, you can <a
|
||||
href="http://www.citi.qut.edu.au/research/plas/projects/cp_files/cpdownload.html">
|
||||
href="http://www2.fit.qut.edu.au/CompSci/PLAS/ComponentPascal/gpcp1.1.4-netRTM.zip">
|
||||
download it</a>
|
||||
|
||||
<a name="Forth">
|
||||
@@ -111,22 +110,10 @@
|
||||
<a href="mailto:[email protected]">Brian Lloyd</a> is
|
||||
working on linking the Python runtime with the .NET runtime.
|
||||
More information on the PS.NET project can be found <a
|
||||
href="http://www.zope.org/Members/Brian/PythonNet">here</a>.
|
||||
href="http://www.zope.org/Members/Brian/PythonNet/index_html">here</a>.
|
||||
An FAQ document is available <a
|
||||
href="http://www.zope.org/Members/Brian/PythonNet/FAQ.html">here</a>.
|
||||
|
||||
<a name="dotlisp">
|
||||
** dotLisp
|
||||
|
||||
DotLisp is available from: <a
|
||||
href="http://sourceforge.net/projects/dotlisp/">http://sourceforge.net/projects/dotlisp/</a>
|
||||
|
||||
<a name="JavaScript">
|
||||
* Java Script
|
||||
|
||||
Cesar is working on Mono's implementation of JScript, the code
|
||||
is available on CVS on module `mcs'.
|
||||
|
||||
* Missing languages
|
||||
|
||||
Here is a list of a few languages that we would like to see
|
||||
@@ -135,6 +122,19 @@
|
||||
implementing or adapting a compiler for any of these
|
||||
languages:
|
||||
|
||||
<a name="JavaScript">
|
||||
* Java Script
|
||||
|
||||
The Mozilla project has an implementation of JavaScript
|
||||
written in Java called <a
|
||||
href="http://www.mozilla.org/rhino/">Rhino</a>.
|
||||
|
||||
You could port this code from Java to C#.
|
||||
|
||||
Note that since JavaScript allows for evaluation at runtime,
|
||||
the compiler has to be built as a class that can be invoked at
|
||||
runtime.
|
||||
|
||||
<a name="c">
|
||||
* C
|
||||
|
||||
@@ -152,10 +152,6 @@
|
||||
<a name="Java">
|
||||
* Java
|
||||
|
||||
Java bytecode can run directly on Mono using the <a
|
||||
href="http://www.ikvm.net">IKVM</a> java virtual machine for
|
||||
.NET.
|
||||
|
||||
We have a <a href="java.html">separate page</a> for Java.
|
||||
|
||||
|
||||
@@ -1,91 +0,0 @@
|
||||
<html>
|
||||
<head>
|
||||
<title>Mono 1.0 assemblies</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Assemblies</h1>
|
||||
<pre>
|
||||
Stable:
|
||||
Commons.RelaxNG
|
||||
Cscompmgd
|
||||
Mono.Data
|
||||
Mono.Data.Tds
|
||||
Mono.Posix
|
||||
Mono.Security
|
||||
Mono.Security.Win32
|
||||
System.Web
|
||||
System.Configuration.Install
|
||||
System.Data
|
||||
System.Data.OracleClient
|
||||
System.DirectoryServices
|
||||
System
|
||||
System.Drawing
|
||||
System.Runtime.Remoting
|
||||
System.Security
|
||||
System.Web.Services
|
||||
System.XML
|
||||
|
||||
Unstable:
|
||||
Accessibility
|
||||
Mono.Cairo
|
||||
Mono.CSharp.Debugger
|
||||
Mono.Data.DB2Client
|
||||
Mono.Data.SqlLite
|
||||
Mono.Data.SybaseClient
|
||||
Mono.GetOptions
|
||||
System.Web.Mobile
|
||||
System.Design
|
||||
System.Drawing.Design
|
||||
System.Windows.Forms
|
||||
Formatters.Soap
|
||||
Mono.Data.TdsClient (older Sybase and MS SQL)
|
||||
|
||||
Missing:
|
||||
System.EnterpriseServices
|
||||
System.Management
|
||||
System.Messaging
|
||||
System.ServiceProcess
|
||||
System.Web.RegularExpressions
|
||||
|
||||
Third party assemblies.
|
||||
ByteFX.Data
|
||||
Npgsql
|
||||
PEAPI
|
||||
SharpZipLib.
|
||||
|
||||
Java integration with IKVM.NET
|
||||
|
||||
</pre>
|
||||
|
||||
<h1>Languages</h1>
|
||||
|
||||
<pre>
|
||||
Stable:
|
||||
C#
|
||||
|
||||
Unstable:
|
||||
VB.NET
|
||||
|
||||
Not ready:
|
||||
JScript
|
||||
</pre>
|
||||
|
||||
<h1>Virtual Machine</h1>
|
||||
|
||||
<pre>
|
||||
JIT, 32 bits:
|
||||
PPC
|
||||
x86
|
||||
|
||||
Interpreter, 32 bits:
|
||||
s390
|
||||
HPPA
|
||||
StrongARM
|
||||
SPARC v8
|
||||
|
||||
Interpreter, 64 bits:
|
||||
ia64
|
||||
SPARC v9
|
||||
</body>
|
||||
</html>
|
||||
@@ -1,271 +0,0 @@
|
||||
<html>
|
||||
<head><title>Mono Hacking Roadmap</title>
|
||||
<style type="text/css">
|
||||
h1 {
|
||||
color: #efefef;
|
||||
font-size: 18pt;
|
||||
font-family: "Trebuchet MS";
|
||||
border: 0;
|
||||
margin: 0;
|
||||
padding: 1em;
|
||||
background: #666666;
|
||||
}
|
||||
|
||||
h2, h3, h4, h5, h6 {
|
||||
font-family: Verdana,sans-serif;
|
||||
font-weight: bold;
|
||||
margin: 9pt;
|
||||
}
|
||||
|
||||
h2, h3 {
|
||||
font-size: 18px;
|
||||
}
|
||||
|
||||
h2 {
|
||||
padding: 3px;
|
||||
color: #000000;
|
||||
}
|
||||
|
||||
h3 {
|
||||
font-size: 13px;
|
||||
border-bottom: 2px solid #dddddd;
|
||||
}
|
||||
|
||||
h4 {
|
||||
border-bottom: 2px solid #dddddd;
|
||||
}
|
||||
|
||||
body, table {
|
||||
background-color: #ffffff;
|
||||
font-family: Verdana, sans-serif; font-size: 12px;
|
||||
color: black;
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
border: 0;
|
||||
margin-left: 20%;
|
||||
margin-right: 20%;
|
||||
}
|
||||
|
||||
p {
|
||||
margin-left: 2em;
|
||||
margin-right: 2em;
|
||||
}
|
||||
|
||||
ul li {
|
||||
margin-left: 2em;
|
||||
}
|
||||
|
||||
img {
|
||||
border: 0;
|
||||
vertical-align: top;
|
||||
}
|
||||
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
<center>
|
||||
<h1>
|
||||
Mono Hacking Roadmap
|
||||
<br>
|
||||
|
||||
<font size=1>Miguel de Icaza (<a href="mailto:[email protected]">[email protected]</a>)</font>
|
||||
|
||||
</h1>
|
||||
<p>
|
||||
</center>
|
||||
|
||||
<h3>Introductory notes</h3>
|
||||
|
||||
<p>The intention of this document and the <a
|
||||
href="http://www.go-mono.com/mono-roadmap.html">Mono
|
||||
Roadmap</a> is to be a basis for discussion. I want to build
|
||||
on these two documents, and update as we get more insight into
|
||||
the release process and the technologies we want to ship.
|
||||
|
||||
<h3>Background</h3>
|
||||
|
||||
<p>At the 2003 PDC Microsoft introduced many new technologies,
|
||||
which many of us are very excited about. To me, it underlined
|
||||
the importance of having a roadmap for users of Mono
|
||||
technologies. That way they know precisely what to expect
|
||||
from us when. We have been working on Mono for more than two
|
||||
years, and it is important that we release a stable product to
|
||||
the public.
|
||||
|
||||
<p>We have various degrees of maturity and feature
|
||||
completeness in our code base, and I do not believe that we
|
||||
should aim to be full implementation .NET 1.0 or .NET 1.1 in
|
||||
our 1.0 release, that would just push the release at least for
|
||||
another year . The <a
|
||||
href="http://www.go-mono.com/mono-roadmap.html">Mono
|
||||
Roadmap</a> emphasizes this assumption.
|
||||
|
||||
<p>The 1.0 release is critical for the adoption of Mono on the
|
||||
Linux environment, even if it is not as complete as the
|
||||
Framework, lets get something stable, and fun to people to
|
||||
use.
|
||||
|
||||
<h3>Mono 1.0: missing functionality.</h3>
|
||||
|
||||
<p>For the 1.0 release, there are a number of features that we
|
||||
will have to complete, in no particular order:
|
||||
|
||||
<ul>
|
||||
<li>We need to fix corcompare and our cor-compare
|
||||
pages to support both 1.0 and 1.1 API API compares.
|
||||
|
||||
We might want to move this outside of the Mono site,
|
||||
to reduce the complexity of the HTML hackage, and use
|
||||
ASP.NET to implement this. Bonus points if we use
|
||||
Piers' nice dynamic tree to load the CorCompare data
|
||||
dynamically.
|
||||
|
||||
<li>Global Assembly Cache: Needed to support the
|
||||
parallel installation of .NET 1.0 and 1.1 assemblies,
|
||||
and to fix the various Assembly loading routines.
|
||||
|
||||
<li>PowerPC port.
|
||||
|
||||
<li>ECMA profile: We will like take care of this one
|
||||
at Novell.
|
||||
|
||||
<li>Assembly signing: I do not know what is the state
|
||||
of this feature currently in Mono, maybe Sebastien and
|
||||
Zoltan could give us an update here.
|
||||
|
||||
<li>ASP.NET caching: Non-existant at this point, this
|
||||
needs to be implemented.
|
||||
|
||||
<li>Stability of ASP.NET and Mod_Mono. They are both
|
||||
functional, but they fail under load. Much debugging
|
||||
and testing must go into these components. As we use
|
||||
more of it, we have found more little problems surface
|
||||
on it.
|
||||
|
||||
<li>Codebase audit: Duncan did an audit of Corlib, but
|
||||
we must do an audit of all the assemblies that we we
|
||||
are going to ship, just to get an idea of the major
|
||||
areas missing.
|
||||
</ul>
|
||||
|
||||
<p>The team at Novell will focus on these areas. We of course
|
||||
welcomes the contribution of the rest of the Mono team and
|
||||
encourage the developers to focus on 1.0, to have a solid
|
||||
release, and a solid foundation that can lead to 1.2
|
||||
|
||||
<p>We will use Bugzilla milestones to track these issues.
|
||||
|
||||
<h3>Synchronized releases</h3>
|
||||
|
||||
<p>It would be great if we can ship Mono 1.0 with Gtk# 1.0 and
|
||||
a preview of Monodoc with the early documentation.
|
||||
|
||||
<h3>Alpha components.</h3>
|
||||
|
||||
<p>Various Mono developers are working on areas that will not
|
||||
make it into the 1.0 timeframe: JScript, WSE, VB.NET,
|
||||
Windows.Forms, Generics. We should continue to work on
|
||||
those components, as they will come shortly after, and they
|
||||
are probably more fun to develop than stabilizing the core.
|
||||
|
||||
<h3>New components: Whidbey and Longhorn features</h3>
|
||||
|
||||
<p>Everyone is probably very excited about the new features in
|
||||
the Whidbey release of .NET, and most importantly the Longhorn
|
||||
features. I am sure that many of us will not resist the urge
|
||||
to put some of the new assemblies on CVS.
|
||||
|
||||
<p>We will likely add a profile for those of you that want to
|
||||
work on this, and can not wait to get your hands in the code,
|
||||
although keep in mind that your contributions wont reach the
|
||||
general audience until we successfully ship 1.0.
|
||||
|
||||
<p>The things to keep in mind while adding code which is not
|
||||
in .NET 1.0 and .NET 1.1:
|
||||
|
||||
<ul>
|
||||
<li>Make sure you surround new classes and methods
|
||||
with the appropriate define: NET_1_2 for things
|
||||
available on the .NET 1.2 SDK (Whidbey) and NET_3
|
||||
define for things only available on the Longhorn API.
|
||||
We need this so that these methods do not appear on
|
||||
the 1.0 and 1.1 builds.
|
||||
|
||||
<li>If you add generic types or methods, also surround
|
||||
the method with GENERICS for now, since our compiler
|
||||
can not currently build this code yet. This is
|
||||
redundant with the NET_1_2 define but important.
|
||||
|
||||
<li>For every assembly you update, make sure that you
|
||||
also add the relevant AssemblyInfo versioning
|
||||
information. If possible, when you add methods from
|
||||
.NET 1.2 to the build, also update the AssemblyInfo.cs
|
||||
for the library.
|
||||
</ul>
|
||||
|
||||
<p>There are three areas of new hot features:
|
||||
|
||||
<ul>
|
||||
<li>Class library improvements (Whidbey, Mono 1.2
|
||||
time frames).
|
||||
|
||||
<li>Indigo: They will release this in 2005 or 2006 and
|
||||
wont make it into the 2004 Whidbey .NET 1.2 release.
|
||||
|
||||
<li>Avalon: Definitely a Longhorn-bound feature.
|
||||
</ul>
|
||||
|
||||
<p>Most code that will reach the users in the short time frame
|
||||
(next year) will be related to the Whidbey improvements, so I
|
||||
encourage developers to work on those pieces, as they are the
|
||||
ones that will help Mono the most.
|
||||
|
||||
<h3>ASP.NET 2.0 plans</h3>
|
||||
|
||||
<p>Gonzalo will continue to coordinate this effort; At this
|
||||
time ASP.NET 2.0 features will not make it into Mono 1.0.
|
||||
|
||||
<h3>Avalon plans</h3>
|
||||
|
||||
<p>On the surface Avalaon seems like it uses something like
|
||||
GdiPlus/Cairo for rendering. That was my initial feeling, but
|
||||
it turns out that they had to rewrite everything to have a
|
||||
performing rendering engine, and implement some very advanced
|
||||
rendering features that include compositing with video
|
||||
streams, also their brushes seem to be fairly powerful.
|
||||
|
||||
<p>XAML, a new markup language that binds tags to .NET classes
|
||||
was also presented, but this is the least interesting part. A
|
||||
tiny compiler translates the XAML source files into C# code.
|
||||
The whole process is just like Glade, and should be easy to
|
||||
do.
|
||||
|
||||
<p>The really elaborate parts are the rendering engine, and the
|
||||
composition model for widgets. It is a complete new toolkit,
|
||||
and if we want to implement this one, we will have to have a
|
||||
new toolkit on Unix, incompatible with everything else, maybe
|
||||
stressing the importance of working with other open source
|
||||
projects in defining a cross-toolkit theming strategy to
|
||||
address this particular problem.
|
||||
|
||||
<p>A Mini-Avalon is easy to do, but a complete one will
|
||||
require much interaction with other groups: the Cairo folks
|
||||
are probably the most qualified to assist us.
|
||||
|
||||
<h3>Indigo Plans</h3>
|
||||
|
||||
<p>Indigo is still an early product (<a
|
||||
href="http://msdn.microsoft.com/Longhorn/understanding/pillars/Indigo/default.aspx?pull=/library/en-us/dnlong/html/indigofaq1.asp">FAQ</a>),
|
||||
but it could benefit from continued development of our WSE1
|
||||
and WSE2 components, later to bring some of the code to it.
|
||||
|
||||
<p>Again, since people are visibly excited about this
|
||||
technology, we will lay down in the next few days a framework
|
||||
to contribute to it.
|
||||
|
||||
|
||||
<p>
|
||||
<i>Last Updated: Nov 1st, 2003</i>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -1,394 +0,0 @@
|
||||
<html>
|
||||
<head><title>Mono Roadmap</title>
|
||||
<style type="text/css">
|
||||
h1 {
|
||||
color: #efefef;
|
||||
font-size: 18pt;
|
||||
font-family: "Trebuchet MS";
|
||||
border: 0;
|
||||
margin: 0;
|
||||
padding: 1em;
|
||||
background: #666666;
|
||||
}
|
||||
|
||||
h2, h3, h4, h5, h6 {
|
||||
font-family: Verdana,sans-serif;
|
||||
font-weight: bold;
|
||||
margin: 9pt;
|
||||
}
|
||||
|
||||
h2, h3 {
|
||||
font-size: 18px;
|
||||
}
|
||||
|
||||
h2 {
|
||||
padding: 3px;
|
||||
color: #000000;
|
||||
}
|
||||
|
||||
h3 {
|
||||
font-size: 13px;
|
||||
border-bottom: 2px solid #dddddd;
|
||||
}
|
||||
|
||||
h4 {
|
||||
border-bottom: 2px solid #dddddd;
|
||||
}
|
||||
|
||||
body, table {
|
||||
background-color: #ffffff;
|
||||
font-family: Verdana, sans-serif; font-size: 12px;
|
||||
color: black;
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
border: 0;
|
||||
margin-left: 20%;
|
||||
margin-right: 20%;
|
||||
}
|
||||
|
||||
p {
|
||||
margin-left: 2em;
|
||||
margin-right: 2em;
|
||||
}
|
||||
|
||||
ul li {
|
||||
margin-left: 2em;
|
||||
}
|
||||
|
||||
img {
|
||||
border: 0;
|
||||
vertical-align: top;
|
||||
}
|
||||
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<center>
|
||||
<h1>
|
||||
Mono Project Roadmap
|
||||
<br>
|
||||
<font size=1>Miguel de Icaza ([email protected])</font>
|
||||
</h1>
|
||||
<p>
|
||||
</center>
|
||||
|
||||
<h3>Introduction</h3>
|
||||
|
||||
<p>This document describes the high-level roadmap for <a
|
||||
href="http://www.go-mono.com">Mono</a>.
|
||||
|
||||
<p>The Mono project started in 2001 as an effort to implement
|
||||
the .NET Framework to Unix. To bring both the new programming
|
||||
model based on the Common Language Infrastructure and C# as
|
||||
well as helping people migrate their existing knowledge and
|
||||
applications to Unix. Mono today supports a wide variety of
|
||||
operating systems, CPUs and a large chunk of the functionality
|
||||
available in the .NET Framework.
|
||||
|
||||
<p>At the October 2003 PDC conference a number of new
|
||||
technologies were announced. From the Mono release schedule
|
||||
perspective, we should think about these technologies from
|
||||
their release time standpoint, and the features that must be
|
||||
supported.
|
||||
|
||||
<p>This document outlines the roadmap for the Mono project
|
||||
from my perspective: what we can effectively deliver on the
|
||||
dates outlined. Since Mono is a large open source project,
|
||||
things might change and new features can be incorporated
|
||||
into the plan if external sources devote enough attention to
|
||||
those problems.
|
||||
|
||||
<p>This is the timeline:
|
||||
<p>
|
||||
<center>
|
||||
<img src="roadmap.png">
|
||||
</center>
|
||||
|
||||
<h3>Background</h3>
|
||||
|
||||
<p>So far Microsoft has published two versions of the .NET
|
||||
Framework: 1.0 and 1.1, the later with incremental updates to
|
||||
the changes in 1.0
|
||||
|
||||
<p>The Mono project has been tracking some of the
|
||||
improvements available in those two releases, some of the
|
||||
highlights of our work so far are:
|
||||
|
||||
<ul>
|
||||
<li> Core: mscorlib, System, System.Security and
|
||||
System.XML assemblies.
|
||||
|
||||
<li> ADO.NET: System.Data and various other database
|
||||
providers.
|
||||
|
||||
<li> ASP.NET: WebForms and Web Services are
|
||||
supported. Work on WSE1/WSE2 has also started.
|
||||
|
||||
<li> Compilers: C#, VB.NET and various command line tools
|
||||
that are part of the SDK.
|
||||
|
||||
<li> Open Source, Unix and Gnome specific libraries.
|
||||
</ul>
|
||||
|
||||
<p>Other components like Windows.Forms, Directory.Services,
|
||||
Enterprise Services and JScript are being developed but are not
|
||||
as mature as the other components but are under development by
|
||||
various people.
|
||||
|
||||
<p>Some other smaller and less used components do not have yet
|
||||
a Mono equivalent (System.Management, System.Drawing.Design).
|
||||
|
||||
<h3>Mono release strategy</h3>
|
||||
|
||||
<p>The levels of maturity of Mono fluctuate depending on the
|
||||
development effort we have put into it, and the use we have
|
||||
given to them. For example, the virtual machine and the C#
|
||||
compiler very mature, while less commonly used functionality
|
||||
in Mono like Windows.Forms or VB.NET are still under heavy
|
||||
development.
|
||||
|
||||
<p>Our strategy is to release the mature components as Mono
|
||||
1.0, and have upcoming versions of Mono add extra
|
||||
functionality.
|
||||
|
||||
<h3>Mono 1.0 goals</h3>
|
||||
|
||||
<p>The Mono 1.0 release would include the following
|
||||
components:
|
||||
|
||||
<ul>
|
||||
<li>C# compiler.
|
||||
|
||||
<li>VM, with JIT and pre-compiler.
|
||||
|
||||
<li>IL assembler, disassembler.
|
||||
|
||||
<li>Development and security tools.
|
||||
|
||||
<li>Core libraries: mscorlib, System, System.XML.
|
||||
|
||||
<li>System.Data and Mono database providers.
|
||||
|
||||
<li>System.Web: Web applications platform and Apache
|
||||
integration module.
|
||||
|
||||
<li>System.Web.Services: client and server support.
|
||||
|
||||
<li>System.Drawing.
|
||||
|
||||
<li>System.DirectoryServices
|
||||
|
||||
<li>JIT support: x86 and PPC architectures
|
||||
(interpreter available for other architectures).
|
||||
|
||||
<li>ECMA profiles: special build options to build
|
||||
Mono as an implementation of the various ECMA profiles
|
||||
will be available.
|
||||
|
||||
<li>Java integration through IKVM.
|
||||
|
||||
<li>Embedding interface for the runtime.
|
||||
</ul>
|
||||
|
||||
<p>Packaging:
|
||||
|
||||
<ul>
|
||||
<li>mono: will contain the above features implementing
|
||||
the .NET 1.1 API.
|
||||
|
||||
<li>mono-1.0-compat: Will include a build of the
|
||||
libraries with the .NET 1.0 API, this is a
|
||||
compatibility build for people running .NET 1.0
|
||||
applications.
|
||||
|
||||
<li>mono-unstable: Will contain a snapshot of the
|
||||
other technologies under development for developer's
|
||||
convenience, but will be unsupported at this time.
|
||||
These include the Generics edition of the C#
|
||||
compiler.
|
||||
|
||||
<li>mono-ecma: A build that only includes the ECMA
|
||||
components.
|
||||
</ul>
|
||||
|
||||
<p>Release target: Q2/2004.
|
||||
|
||||
<p>Bug fix releases would be done on a monthly basis.
|
||||
|
||||
<p>For a detailed list, see the <a
|
||||
href="mono-1.0.html">mono-1.0 feature list.</a>
|
||||
|
||||
<h3>Microsoft's Whidbey</h3>
|
||||
|
||||
<p>To understand post 1.0 editions of Mono, it is important to
|
||||
put it into perspective with the Microsoft Whidbey product, to
|
||||
be released in 2004.
|
||||
|
||||
<p>The new features in the Whidbey release of the .NET Framework
|
||||
include:
|
||||
|
||||
<ul>
|
||||
<li><b>Generic types</b><br>
|
||||
These introduce changes to the compiler, runtime and
|
||||
class libraries.
|
||||
|
||||
<li><b>ASP.NET 2</b><br>
|
||||
Many tools to simplify web application development:
|
||||
Master pages, new controls for common operations,
|
||||
personalization and themes.
|
||||
|
||||
<li><b>Remoting</b><br>
|
||||
New security channels and version-resistant remoting
|
||||
(good news in the interop department).
|
||||
|
||||
<li><b>XML</b><br>
|
||||
XQuery debuts on this release as well as an improved
|
||||
XmlDocument system based on XPath: XPathDocument.
|
||||
|
||||
<li><b>Networking</b><br>
|
||||
FTP client, Ssl streams.
|
||||
|
||||
<li><b>Console and Serial ports:</b></br>
|
||||
Console terminal input/output is available as well as
|
||||
serial port handling.
|
||||
|
||||
<li><b>Windows.Forms</b><br>
|
||||
Layout containers finally appeared on Windows.Forms as
|
||||
well as various new controls.
|
||||
|
||||
<li><b>ObjectSpaces</b><br>
|
||||
An API for simpler data-base access.
|
||||
</ul>
|
||||
|
||||
<h3>Mono 1.2</h3>
|
||||
|
||||
<p>The Mono team is developing in parallel some features that
|
||||
wont make it to the 1.0 release in stable form. These will be
|
||||
the foundation for the 1.2 release. The focus of this release
|
||||
is to track the core API for the .NET Framework 1.2, but
|
||||
again, only a subset of the total framework will be
|
||||
available.
|
||||
|
||||
<p>Mostly, Mono 1.2 consists of components that were not
|
||||
stable enough for Mono 1.0, but that would be mature at this
|
||||
point, plus the incorporation of some new features from
|
||||
Whidbey. In addition to the Mono 1.0 components, this release
|
||||
will add:
|
||||
|
||||
<ul>
|
||||
<li>Generic types support: C# compiler, execution
|
||||
system and core class libraries.
|
||||
|
||||
<li>ASP.NET 2.0 improvements.
|
||||
|
||||
<li>Remoting improvements from Whidbey.
|
||||
|
||||
<li>System.XML: simpler improvements from Whidbey,
|
||||
lacking the large additions (XQuery for example).
|
||||
|
||||
<li>Console and Serial ports support.
|
||||
|
||||
<li>New compilers: VB.NET and JScript support.
|
||||
|
||||
<li>WSE1/WSE2 implementations.
|
||||
|
||||
<li>System.Windows.Forms officially debuts with .NET
|
||||
1.0 API; 1.2 API available as an unstable addition.
|
||||
</ul>
|
||||
|
||||
<p>This release will by default provide .NET 1.2 APIs, but
|
||||
compatibility libraries for 1.0 and 1.1 will be distributed in
|
||||
the mono-compat package. The unstable components of Mono will
|
||||
be distributed on the `mono-unstable' package, the libraries
|
||||
in this release will be unsupported.
|
||||
|
||||
<p>Release target: Q4/2004.
|
||||
|
||||
<h3>Mono 1.4</h3>
|
||||
|
||||
<p>A refresh update on the Mono 1.2 release containing the
|
||||
missing components from the previous release and complete any
|
||||
under performing pieces. Updates to System.Xml, ASP.NET and
|
||||
Windows.Forms to match the .NET 1.2 API.
|
||||
|
||||
<p>Release target: Q2/2005.
|
||||
|
||||
<h3>Peer projects</h3>
|
||||
|
||||
<p>Other projects like the debugger, the documentation
|
||||
browser, Java integration through IKVM and Gtk# will remain on
|
||||
their own schedules. This page will be updated to contain
|
||||
that information when it becomes available.
|
||||
|
||||
<h3>Unscheduled activities</h3>
|
||||
|
||||
<p>A missing component of Mono is the Code Access Security
|
||||
(CAS). This functionality is not needed in today's Mono as
|
||||
currently Mono is being used to run fully trusted
|
||||
applications, and we are not using it on embedded scenarios
|
||||
where assemblies would have different trust levels.
|
||||
|
||||
<p>This is an important component, but requires three major
|
||||
pieces of work:
|
||||
|
||||
<ul>
|
||||
<li>Runtime support for implementing the security
|
||||
demands.
|
||||
|
||||
<li>A guidelines document outlining what and where
|
||||
must have security demands in place.
|
||||
|
||||
<li>A full audit of our class libraries: method by
|
||||
method
|
||||
</ul>
|
||||
|
||||
<p>All of these are major pieces of work, and we currently
|
||||
have no plans to implement any of those. A volunteer effort might be
|
||||
able to help with the runtime requirements and the document,
|
||||
but until those are done, we are unlikely to start doing any
|
||||
work on the actual class library audit and instrumentation.
|
||||
|
||||
<h3>Mono and WinFX: 2006</h3>
|
||||
|
||||
<p>WinFX is the name given to the new set of libraries that
|
||||
makes up .NET in the Longhorn operating system: the existing
|
||||
.NET set of class libraries, plus the new functionality
|
||||
available in the OS.
|
||||
|
||||
<p>WinFX adds things like storage facilities (WinFS), a
|
||||
new versatile communications stack (Indigo) and a new
|
||||
eye-candy packed GUI programming system (Avalon).
|
||||
|
||||
<p>Although WinFS, Avalon and Indigo are very exciting
|
||||
components, at this time it is too early to tell when those
|
||||
components will be available for Mono. Open source developers
|
||||
will very likely start work on these, but since they are still
|
||||
far from being officially released, they are not in the radar
|
||||
at this point.
|
||||
|
||||
<h3>Unsupported technologies</h3>
|
||||
|
||||
<p>Some technologies are very hard to implement or are being
|
||||
phased out by components in the Longhorn time frame. In some
|
||||
cases, we feel that they are not crucial to the future of the
|
||||
open source desktop.
|
||||
|
||||
<p>System.EnterpriseServices and System.Management come to
|
||||
mind, and we are unlikely to put any resources into the task.
|
||||
We would gladly host the code if someone cares to implement
|
||||
it, but they would likely remain unsupported features of Mono.
|
||||
|
||||
<h3>Mono Developer Strategy</h3>
|
||||
|
||||
<p>Mono Developers should read the <a
|
||||
href="mono-hacking-roadmap.html">Mono Hacking Roadmap</a>
|
||||
|
||||
<h3>Comments</h3>
|
||||
|
||||
<p>Feel free to send your comments or questions the roadmap to
|
||||
<a href="mailto:[email protected]">[email protected]</a>
|
||||
|
||||
|
||||
<p>
|
||||
<i>Last Updated: Nov 1st, 2003</i>
|
||||
-194
@@ -1,194 +0,0 @@
|
||||
* Mono hacking TODO list
|
||||
|
||||
From time to time people that want to contribute to Mono ask
|
||||
on the mailing list what they can help with. The generic
|
||||
answer is always:
|
||||
<ul>
|
||||
* Write documentation.
|
||||
* Write regression tests.
|
||||
* Complete the implementations of the class libraries.
|
||||
* Help fix the bugs filed in our bugzilla database.
|
||||
</ul>
|
||||
|
||||
The proposed tasks are very important for the Mono project and
|
||||
are suitable for people that can dedicate even just an hour
|
||||
per week to contribute. But some people may need something
|
||||
more focused to work on, such as students that want to do a
|
||||
thesis on their contribution to Mono. For such people (and
|
||||
also for professors who want ideas for thesis regarding JIT or
|
||||
VM technologies), here is a list of tasks that need attention.
|
||||
|
||||
The estimated time to complete any of the tasks is between 1
|
||||
week to several months to accomodate for different hacking
|
||||
possibilities.
|
||||
|
||||
Note on the time estimates: they are very rough estimates, a
|
||||
smart and dedicated hacker can complete the tasks in half of
|
||||
the minimum time, a part-time hacker that also has a social
|
||||
life can take more than double the max time, but there's
|
||||
nothing to worry as long as progress is being done.
|
||||
|
||||
If some people (or group of people) want to take on a task,
|
||||
they should write to the mono-devel mailing list and in the
|
||||
relative bugzilla bug report. Discussions about how to
|
||||
implement a feature or additional information on the task
|
||||
should be mailed to the list or in the bugzilla report as well
|
||||
so that people can keep informed on the progress or have the
|
||||
information needed to start contributing.
|
||||
|
||||
Mono is an excellent platform for research on JITs, virtual
|
||||
machines and specifically the CLR because it provides an
|
||||
advanced free software implementation that can be used as a
|
||||
basis for more optimizations, new approaches to problems and
|
||||
new features.
|
||||
|
||||
There are different areas of interest where high-level
|
||||
contributions can be made:
|
||||
|
||||
<ul>
|
||||
* <b>JIT compiler</b>: tasks can be: adding more optimizations, reducing
|
||||
compile time, porting to different architectures.
|
||||
|
||||
* <b>AOT compiler</b>: optimizing the compiler output and the AOT loader,
|
||||
better support for multiple application domains.
|
||||
|
||||
* <b>VM runtime</b>: optimizing the runtime data structures, experimenting with
|
||||
different garbage collectors, integration with different component models.
|
||||
|
||||
* <b>Class library</b>: many opportunities in the implementation of regular
|
||||
expressions, Xml related technologies (XPath, XLST, etc).
|
||||
|
||||
* <b>Compilers</b>: writing compilers, interpreters and runtimes for langauges
|
||||
so that they run on the CLR (using Reflection.Emit support, for example).
|
||||
</ul>
|
||||
|
||||
Happy hacking!
|
||||
|
||||
<table border=1 cellspacing="0" cellpadding="0">
|
||||
<tr>
|
||||
<th>Area<th>Description<th>Difficulty<th>Time estimate<th>Bugzilla ID
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Runtime (mono/metadata)
|
||||
<td>Optimize method vtable. Currently all the methods in a class
|
||||
are added to the method vtable, including static and non-virtual methods.
|
||||
This makes vtables bigger and the instructions to access them are longer,
|
||||
increasing also code size. Some code in metadata/icall.c and maybe also some
|
||||
remoting code may depend on the current layout: such code should be fixed as well.
|
||||
<td>Medium
|
||||
<td>1-2 weeks
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>System assembly (mcs/class/System/)
|
||||
<td>Implement the IL-based regular expression engine. Instead of
|
||||
intepreting the regular expression pattern, a method is created at runtime using
|
||||
Reflection.Emit. This makes for faster pattern matching because there is no
|
||||
intepreter overhead and the matching code is jitted to fast native code.
|
||||
Bonus points if the compiled regular expression is compatible with the ones generated
|
||||
by the MS runtime.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>2-4 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Implement common subexpression elimination.
|
||||
Global and local common subexpression elimination needs to be implemented
|
||||
to achieve better performance. The local case is easier and may take just one month.
|
||||
It should be implemented in the context of the SSA framework (mini/ssa.c).
|
||||
<td>Hard (thesis subject)
|
||||
<td>2-4 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Optimize AOT compiler output.
|
||||
Currently the code generated by the AOT compiler may be significantly slower than
|
||||
jitted code. This is mostly because the AOT code supports multiple application domains
|
||||
and some values that are constant at JIT-time are not constant at AOT-time. It may be
|
||||
needed to write a simple dynamic linker and/or binary object writer. Bonus poinst if
|
||||
it supports ELF, PE/COFF and mach-O binary formats. A possible idea for improvements
|
||||
is also the use of appdomain ID-indexed tables to get at the appdomain specific data.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>3-6 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Implement generics support.
|
||||
We need to add support for the additional instructions and change existing ones to
|
||||
support the generics requirements.
|
||||
<td>Medium-hard
|
||||
<td>2-3 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>JIT (mono/mini/)
|
||||
<td>Port the JIT to additional architectures.
|
||||
Currently ports are in the works for ppc, arm, sparc, s390. None of the ports
|
||||
are as feature-complete as the x86 one, yet, so help is needed in getting them
|
||||
up to speed. Ports to more architectures are welcome as well.
|
||||
<td>Medium-hard
|
||||
<td>3-6 months per arch
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Runtime and JIT (mono/metadata and mono/mini/)
|
||||
<td>Add support for COM and/or XPCOM and/or ORBit.
|
||||
We need a way to seamlessy use existing component technologies inside the mono runtime.
|
||||
The COM support needs to match the MS runtime behaviour and is targeted at windows systems.
|
||||
XPCOM and ORBit support are important on Unix platforms. Bonus points for developing
|
||||
the runtime support so that different component systems can be used at the same time.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>3-4 months for each
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Runtime and JIT (mono/metadata and mono/mini/)
|
||||
<td>Implement support for Code Access Security.
|
||||
Support needs to be added to the JIT and the runtime to ensure
|
||||
code that executes privileged operations is permitted to do so.
|
||||
The task includes loading the security information from metadata,
|
||||
collecting evidence, inserting calls to the permission objects,
|
||||
stack walking to collect security info.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>4-5 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Runtime and JIT (mono/metadata and mono/mini/)
|
||||
<td>Implement support for a generational GC.
|
||||
We're currently using a conservative non-moving GC.
|
||||
Support for a generational and moving GC requires changes to the JIT
|
||||
(to record locations in frames as well as registers that may contain
|
||||
pointers to GC-allocated memory) and to the runtime code (when
|
||||
objects are manipulated directly we should make sure they are pinned
|
||||
and reachable by the GC also in the C unmanaged code). Code from an existing
|
||||
precise GC such as the ORP one could be reused or a new GC may be developed
|
||||
(increasing the estimated development time).
|
||||
<td>Hard (thesis subject)
|
||||
<td>6-8 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Compilers for dynamic languages
|
||||
<td>Write a IL compiler and runtime support for dynamic languages like
|
||||
Python, Perl, Ruby, PHP.
|
||||
<td>Medium-hard (thesis subject)
|
||||
<td>6-12 months
|
||||
<td>not assigned
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
@@ -43,7 +43,7 @@
|
||||
in the Microsoft .NET Environment</a> is an article
|
||||
by Mr. Venu who is a MySQL AB developer.</li>
|
||||
|
||||
<p>Testing for Mono's Mono.Data.MySql and ByteFX's ByteFX.Data.MySqlClient is below.
|
||||
<p>Testing for Mono's Mono.Data.MySql and ByteFX's ByteFX.Data.MySQLClient is below.
|
||||
|
||||
** Current Status
|
||||
|
||||
@@ -51,7 +51,7 @@
|
||||
|
||||
<ul>
|
||||
|
||||
<li>ByteFX.Data.MySqlClient
|
||||
<li>ByteFX.Data.MySQLClient
|
||||
<ul>
|
||||
<li>Build and Runs on Microsoft .NET and Mono</li>
|
||||
<li>Works with SQL# (command-line and GTK# GUI versions)</li>
|
||||
@@ -109,7 +109,7 @@
|
||||
The current plan for the MySQL data providers:
|
||||
|
||||
<ul>
|
||||
<li>ByteFX.Data.MySqlClient
|
||||
<li>ByteFX.Data.MySQLClient
|
||||
<ul>
|
||||
<li>Testing and fixes</li>
|
||||
<li>Implement missing features</li>
|
||||
@@ -163,7 +163,7 @@
|
||||
<pre>
|
||||
using System;
|
||||
using System.Data;
|
||||
using ByteFX.Data.MySqlClient;
|
||||
using ByteFX.Data.MySQLClient;
|
||||
|
||||
public class Test
|
||||
{
|
||||
@@ -175,7 +175,7 @@
|
||||
"User ID=myuserid;" +
|
||||
"Password=mypassword;";
|
||||
IDbConnection dbcon;
|
||||
dbcon = new MySqlConnection(connectionString);
|
||||
dbcon = new MySQLConnection(connectionString);
|
||||
dbcon.Open();
|
||||
IDbCommand dbcmd = dbcon.CreateCommand();
|
||||
// requires a table to be created named employee
|
||||
@@ -283,8 +283,8 @@ mono TestExample.exe
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["firstname"];
|
||||
string LastName = (string) reader["lastname"];
|
||||
string FirstName = reader["firstname"];
|
||||
string LastName = reader["lastname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
@@ -175,8 +175,8 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["firstname"];
|
||||
string LastName = (string) reader["lastname"];
|
||||
string FirstName = reader["firstname"];
|
||||
string LastName = reader["lastname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
@@ -109,8 +109,8 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["firstname"];
|
||||
string LastName = (string) reader["lastname"];
|
||||
string FirstName = reader["firstname"];
|
||||
string LastName = reader["lastname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
+14
-11
@@ -10,7 +10,7 @@
|
||||
|
||||
<li>Works with Oracle 8i</li>
|
||||
|
||||
<li>May work with Oracle 9i</li>
|
||||
<li>Untested, but should work with Oracle 9i</li>
|
||||
|
||||
<li>Uses the Oracle CLI (Call Level Interface) which is a C library (API) for the Oracle Client
|
||||
software</li>
|
||||
@@ -19,6 +19,8 @@
|
||||
|
||||
<li>Created by Daniel Morgan and Tim Coleman</li>
|
||||
|
||||
<li>Does not support trusted connections</li>
|
||||
|
||||
<li>Bugs with Mono or the data provider should be reported
|
||||
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
|
||||
do not have Bugzilla user account, it is free
|
||||
@@ -62,12 +64,14 @@
|
||||
|
||||
<li>Handling of various data types need to be added.</li>
|
||||
|
||||
<li>Data Adapter exists, and a DataSet can be filled using it.</li>
|
||||
<li>Data Adapter exists, and a DataSet can be filled using it. The
|
||||
Data Adapter is abstract enough that it should work as expected.</li>
|
||||
|
||||
<li>Lots of missing functionality and bugs.</li>
|
||||
|
||||
<li>Works with SQL# command-line and GTK# versions in cvs. Only works with
|
||||
simple character data though.</li>
|
||||
simple character data though. SQL# For GTK# can only show the results to
|
||||
the TextView because the Data Adapter is not yet available</li>
|
||||
|
||||
</ul>
|
||||
|
||||
@@ -79,8 +83,7 @@
|
||||
<li>transactions (WORKING)</li>
|
||||
<li>Stored Procedures, Functions, and Packages support</li>
|
||||
<li>Be able to fill a DataTable in a DataSet via a data adapter (IN PROGRESS)</li>
|
||||
<li>Support for Oracle 8i (WORKING</li>
|
||||
<li>Support for Oracle 9i (UNKNOWN)</li>
|
||||
<li>Support for Oracle 8i and 9i (UNKNOWN)</li>
|
||||
<li>Support LOBs</li>
|
||||
<li>Support all the data types</li>
|
||||
<li>Implement Connection pooling</li>
|
||||
@@ -93,7 +96,7 @@
|
||||
<ul>
|
||||
<li>Have a working mono and mcs</li>
|
||||
|
||||
<li>Have access to an Oracle 8i or 9i database or download it from
|
||||
<li>Have access to an Oracle 8i database or download it from
|
||||
<a href="http://www.oracle.com/">Oracle</a>. If you are connecting
|
||||
remotely to an Oracle database, you need the Oracle client software.
|
||||
Registration to the <a href="http://technet.oracle.com/">Oracle Technology Network</a> is free. If installing on Linux,
|
||||
@@ -126,16 +129,16 @@
|
||||
"Data Source=testdb;" +
|
||||
"User ID=scott;" +
|
||||
"Password=tiger;";
|
||||
OracleConnection dbcon = null;
|
||||
IDbConnection dbcon;
|
||||
dbcon = new OracleConnection (connectionString);
|
||||
dbcon.Open ();
|
||||
OracleCommand dbcmd = dbcon.CreateCommand ();
|
||||
IDbCommand dbcmd = dbcon.CreateCommand ();
|
||||
string sql = "SELECT ename, job FROM scott.emp";
|
||||
dbcmd.CommandText = sql;
|
||||
OracleDataReader reader = dbcmd.ExecuteReader ();
|
||||
IDataReader reader = dbcmd.ExecuteReader ();
|
||||
while (reader.Read ()) {
|
||||
string employeeName = (string) reader["ename"];
|
||||
string job = (string) reader["job"];
|
||||
string employeeName = reader["ename"];
|
||||
string job = reader["job"];
|
||||
Console.WriteLine ("Employee Name: {0} Job: {1}",
|
||||
employeeName, job);
|
||||
}
|
||||
|
||||
@@ -94,8 +94,3 @@
|
||||
href="http://citeseer.nj.nec.com/seligmann95incremental.html">
|
||||
Incremental Collection of Mature Objects: Richard Hudson, Eliot Moss</a>
|
||||
|
||||
* Threads
|
||||
|
||||
<a
|
||||
href="http://research.microsoft.com/~birrell/papers/ThreadsCSharp.pdf">
|
||||
Programming with Threads in C#: Andrew Birrell</a>
|
||||
@@ -8,7 +8,7 @@
|
||||
|
||||
Currently you can read our plans for <a
|
||||
href="ado-net.html">ADO.NET</a>, <a
|
||||
href="asp-net.html">ASP.NET</a>, <a href="java.html">Java</a> and
|
||||
href="asp-net">ASP.NET</a>, <a href="java.html">Java</a> and
|
||||
<a href="winforms.html">WinForms</a>.
|
||||
|
||||
|
||||
|
||||
+7
-33
@@ -1,30 +1,12 @@
|
||||
* PostgreSQL and Mono
|
||||
* PostgreSQL Data Provider
|
||||
|
||||
When it comes to Mono and PostgreSQL, there are many ways
|
||||
you can handle your data. You have many Mono Data Providers which can be used
|
||||
to access data from a application written for Mono.
|
||||
Then there is the future goal of having the ability to host Mono within PostgreSQL to
|
||||
have the applications run on the server which makes things much faster.
|
||||
|
||||
* Hosting Mono in PostgreSQL
|
||||
|
||||
There is a project to <a href="http://gborg.postgresql.org/project/plmono/projdisplay.php">host Mono within PostgreSQL</a>.
|
||||
|
||||
plMono is a PostgreSQL language using the embedded Mono runtime. It provides support for writing functions in C#, or any other language that supports .NET.
|
||||
|
||||
* Data Providers
|
||||
|
||||
There are many ADO.NET data providers for <a href="http://www.postgresql.org/">PostgreSQL</a>:
|
||||
|
||||
There are two providers created specifically for PostgreSQL included with Mono:
|
||||
There are two ADO.NET data providers for <a href="http://www.postgresql.org/">PostgreSQL</a> in Mono:
|
||||
|
||||
<ul>
|
||||
|
||||
<li><a href="http://gborg.postgresql.org/project/npgsql/projdisplay.php">Npgsql</a>
|
||||
<ul>
|
||||
<li>included with Mono</li>
|
||||
|
||||
<li>a .NET Managed Data Provider for PostgreSQL</li>
|
||||
<li>a .NET Managed Data Provider for PostgreSQL
|
||||
|
||||
<li>Written in 100% C#</li>
|
||||
|
||||
@@ -43,8 +25,6 @@
|
||||
|
||||
<li>Mono.Data.PostgreSQL (deprecated)
|
||||
<ul>
|
||||
<li>included with Mono</li>
|
||||
|
||||
<li>Deprecated in favor of Npgsql</li>
|
||||
|
||||
<li>Exists in namespace Mono.Data.PostgreSql and assembly Mono.Data.PostgreSql</li>
|
||||
@@ -57,12 +37,6 @@
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li><a href="http://sourceforge.net/projects/mysqlnet/">ByteFX.Data</a> has a provider for PostgreSQL too, but I do not know how well it works with Mono.</li>
|
||||
|
||||
<li>There is another .NET data provider for PostgreSQL named <a href="http://sourceforge.net/projects/pgsqlclient/">PgSqlClient</a>, but I do not know if it works with Mono.</li>
|
||||
|
||||
<li>If none of the above providers meet your needs. There is the ODBC and OLEDB providers included with Mono.</li>
|
||||
|
||||
<li>Bugs with Mono or the data provider should be reported
|
||||
in Mono's Bugzilla <a href="http://bugzilla.ximian.com/">here</a>. If you
|
||||
do not have Bugzilla user account, it is free
|
||||
@@ -476,8 +450,8 @@ mono PostgresTest.exe
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["firstname"];
|
||||
string LastName = (string) reader["lastname"];
|
||||
string FirstName = reader["firstname"];
|
||||
string LastName = reader["lastname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
@@ -560,8 +534,8 @@ mono TestExample.exe
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["firstname"];
|
||||
string LastName = (string) reader["lastname"];
|
||||
string FirstName = reader["firstname"];
|
||||
string LastName = reader["lastname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
@@ -10,6 +10,8 @@
|
||||
|
||||
** EOG component
|
||||
|
||||
** XmlStorageSystem component
|
||||
|
||||
* Gtk# related projects
|
||||
|
||||
Gnome Canvas Bindings.
|
||||
|
||||
+4
-4
@@ -11,8 +11,8 @@
|
||||
|
||||
The <a href="http://msdn.microsoft.com/net">Microsoft.NET site.</a>
|
||||
|
||||
The Microsoft .NET Framework can be downloaded <a
|
||||
href="http://msdn.microsoft.com/library/default.asp?url=/downloads/list/netdevframework.asp">here</a>
|
||||
The Microsoft .NET Framework 1.0 can be downloaded <a
|
||||
href="http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true">here</a>
|
||||
|
||||
New methods that are not documented in 1.0, are documented <a
|
||||
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/framewrkaddend.asp">here</a>
|
||||
@@ -87,8 +87,8 @@
|
||||
You can get the documentation for the ECMA specs from:
|
||||
|
||||
<ul>
|
||||
* <a href="http://www.ecma-international.org/publications/standards/ECMA-334.HTM">C# Language Specification</a>
|
||||
* <a href="http://www.ecma-international.org/publications/standards/ECMA-335.HTM">Common Language Infrastructure</a>
|
||||
* <a href="http://www.ecma.ch/ecma1/STAND/ecma-334.htm">C# Language Specification</a>
|
||||
* <a href="http://www.ecma.ch/ecma1/STAND/ecma-335.htm">Common Language Infrastructure</a>
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
+19
-59
@@ -9,8 +9,9 @@
|
||||
We currently have two runtimes:
|
||||
|
||||
<ul>
|
||||
* <b>mono:</b> Our Just-in-Time and Ahead-of-Time code
|
||||
generator for maximum performance.
|
||||
* <b>mono:</b> The Just In Time compiler implemented
|
||||
using a BURS instruction selector. We only support
|
||||
x86 machines in the JIT engine at this point.
|
||||
|
||||
* <b>mint:</b> The Mono interpreter. This is an
|
||||
easy-to-port runtime engine.
|
||||
@@ -19,7 +20,7 @@
|
||||
We are using the Boehm conservative garbage collector.
|
||||
|
||||
The Mono runtime can be used as a stand-alone process, or it
|
||||
can be <a href="embedded-api.html">embedded into applications</a> (see
|
||||
can be <a href="embedded-api">embedded into applications</a> (see
|
||||
the documentation in mono/samples/embed for more details).
|
||||
|
||||
Embedding the Mono runtime allows applications to be extended
|
||||
@@ -30,52 +31,12 @@
|
||||
href="http://primates.ximian.com/~lupus/slides/jit/">slides
|
||||
here</a>
|
||||
|
||||
** Current JIT Engine: technical details (<b>updated, June 28th, 2003</b>)
|
||||
** Current JIT Engine: technical details (<b>updated, July 8th, 2002</b>)
|
||||
|
||||
We have re-written our JIT compiler. We wanted to support a
|
||||
number of features that were missing:
|
||||
|
||||
<ul>
|
||||
* Ahead-of-time compilation.
|
||||
|
||||
The idea is to allow developers to pre-compile their code
|
||||
to native code to reduce startup time, and the working
|
||||
set that is used at runtime in the just-in-time compiler.
|
||||
|
||||
Although in Mono this has not been a visible problem, we
|
||||
wanted to pro-actively address this problem.
|
||||
|
||||
When an assembly (a Mono/.NET executable) is installed in
|
||||
the system, it would then be possible to pre-compile the
|
||||
code, and have the JIT compiler tune the generated code
|
||||
to the particular CPU on which the software is
|
||||
installed.
|
||||
|
||||
This is done in the Microsoft.NET world with a tool
|
||||
called ngen.exe
|
||||
|
||||
* Have a good platform for doing code optimizations.
|
||||
|
||||
The design called for a good architecture that would
|
||||
enable various levels of optimizations: some
|
||||
optimizations are better performed on high-level
|
||||
intermediate representations, some on medium-level and
|
||||
some at low-level representations.
|
||||
|
||||
Also it should be possible to conditionally turn these on
|
||||
or off. Some optimizations are too expensive to be used
|
||||
in just-in-time compilation scenarios, but these
|
||||
expensive optimizations can be turned on for
|
||||
ahead-of-time compilations or when using profile-guided
|
||||
optimizations on a subset of the executed methods.
|
||||
|
||||
* Reduce the effort required to port the Mono code
|
||||
generator to new architectures.
|
||||
|
||||
For Mono to gain wide adoption in the Unix world, it is
|
||||
necessary that the JIT engine works in most of today's
|
||||
commercial hardware platforms.
|
||||
</ul>
|
||||
The JIT engine uses a code-generator generator approach for
|
||||
compilation. Given the properties of CIL byte codes, we can
|
||||
take full advantage of a real instruction selector for our
|
||||
code generator.
|
||||
|
||||
The JIT engine implements a number of optimizations:
|
||||
|
||||
@@ -86,7 +47,7 @@
|
||||
|
||||
* Inlining.
|
||||
|
||||
* Constant folding, copy propagation, dead code elimination.
|
||||
* Constant folding.
|
||||
|
||||
Although compilers typically do
|
||||
constant folding, the combination of inlining with
|
||||
@@ -95,9 +56,6 @@
|
||||
* Linear scan register allocation. In the past,
|
||||
register allocation was our achilles heel, but now
|
||||
we have left this problem behind.
|
||||
|
||||
* SSA-based framework. Various optimizations are
|
||||
implemented on top of this framework
|
||||
</ul>
|
||||
|
||||
There are a couple of books that deal with this technique: "A
|
||||
@@ -106,13 +64,7 @@
|
||||
technical description of <a
|
||||
href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/iburg.pdf&pub=ACM">lbrug</a>.
|
||||
|
||||
The new JIT engines uses three intermediate representations:
|
||||
the source is the CIL which is transformed into a forest of
|
||||
trees; This is fed into a BURS instruction selector that
|
||||
generates the final low-level intermediate representation.
|
||||
|
||||
The instruction selector is documented in the following
|
||||
papers:
|
||||
A few papers that describe the instruction selector:
|
||||
|
||||
<ul>
|
||||
* <a href="http://research.microsoft.com/copyright/accept.asp?path=http://www.research.microsoft.com/~drh/pubs/interface.pdf&pub=wiley">A code generation interface for ANSI C</a>
|
||||
@@ -122,6 +74,14 @@
|
||||
|
||||
</ul>
|
||||
|
||||
** New JIT engine.
|
||||
|
||||
We are working on a new JIT engine. The new JIT engine
|
||||
focuses on portability and in two intermediate representations
|
||||
that simplify the development of optimizations. This together
|
||||
with the Ahead-of-Time compilation will allow developers to
|
||||
deploy applications that match the speed of natively compiled code.
|
||||
|
||||
** Garbage Collection
|
||||
|
||||
We are using the Boehm conservative GC. We might consider
|
||||
|
||||
+4
-37
@@ -135,27 +135,14 @@
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
** Type Reflector
|
||||
** SkyNET
|
||||
|
||||
Type Reflector is a tool included in Mono to inspect your assemblies.
|
||||
SkyNET is written in C# and uses GTK# for displaying a star chart.
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/type-reflector.png">
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
** Object Browser
|
||||
|
||||
Radek Doulik's Object Browser (in Mono CVS) is a useful tool
|
||||
to inspect existing assemblies and their source code:
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="images/Screenshot-ObjectBrowserDemo.png">
|
||||
<img src="http://go-mono.com/images/skynet.png">
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
@@ -164,14 +151,6 @@
|
||||
|
||||
Windows.Forms running with Wine on Linux:
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
<a href="http://go-mono.com/images/monomdi.jpg"><img src="http://go-mono.com/images/monomdi-thumb.jpg"></a>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
@@ -179,7 +158,7 @@
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
|
||||
** Mono running on the iPaq
|
||||
|
||||
<table border=1>
|
||||
@@ -215,15 +194,3 @@
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
** SkyNET
|
||||
|
||||
SkyNET is written in C# and uses GTK# for displaying a star chart.
|
||||
|
||||
<table border=1>
|
||||
<tr>
|
||||
<td>
|
||||
<img src="http://go-mono.com/images/skynet.png">
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
+2
-2
@@ -172,8 +172,8 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["fname"];
|
||||
string LastName = (string) reader["lname"];
|
||||
string FirstName = reader["fname"];
|
||||
string LastName = reader["lname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
+3
-3
@@ -82,7 +82,7 @@
|
||||
{
|
||||
string connectionString = "URI=file:SqliteTest.db";
|
||||
IDbConnection dbcon;
|
||||
dbcon = new SqliteConnection(connectionString);
|
||||
dbcon = new MySQLConnection(connectionString);
|
||||
dbcon.Open();
|
||||
IDbCommand dbcmd = dbcon.CreateCommand();
|
||||
// requires a table to be created named employee
|
||||
@@ -97,8 +97,8 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader[0];
|
||||
string LastName = (string) reader[1];
|
||||
string FirstName = reader[0];
|
||||
string LastName = reader[1];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
+2
-2
@@ -110,8 +110,8 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["fname"];
|
||||
string LastName = (string) reader["lname"];
|
||||
string FirstName = reader["fname"];
|
||||
string LastName = reader["lname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
+2
-2
@@ -115,8 +115,8 @@
|
||||
dbcmd.CommandText = sql;
|
||||
IDataReader reader = dbcmd.ExecuteReader();
|
||||
while(reader.Read()) {
|
||||
string FirstName = (string) reader["fname"];
|
||||
string LastName = (string) reader["lname"];
|
||||
string FirstName = reader["fname"];
|
||||
string LastName = reader["lname"];
|
||||
Console.WriteLine("Name: " +
|
||||
FirstName + " " + LastName);
|
||||
}
|
||||
|
||||
+1
-8
@@ -1,12 +1,10 @@
|
||||
0,Home,index.html,index.src
|
||||
1,Roadmap,mono-roadmap.html
|
||||
1,FAQ,faq.html,faq.src
|
||||
1,News archive,http://monoevo.sf.net/mwn/archives.html
|
||||
1,Screenshots,screenshots.html,screenshots.src
|
||||
1,Team,team.html,team.src
|
||||
1,Other sites,other.html,other.src
|
||||
1,Old News,oldnews.html,oldnews.src
|
||||
1,Bug Reporting,bugs.html,bugs.src
|
||||
0,Mono,rationale.html,rationale.src
|
||||
1,Runtime,runtime.html,runtime.src
|
||||
2,Embedding,embedded-api.html,embedded-api.src
|
||||
@@ -19,13 +17,11 @@
|
||||
0,Download,download.html,download.src
|
||||
1,CVS access,ccvs.html,ccvs.src
|
||||
1,AnonCVS access,anoncvs.html,anoncvs.src
|
||||
1,Forge,forge.html,forge.src
|
||||
0,Contributing,contributing.html,contributing.src
|
||||
1,Hackers,hackers.html,hackers.src
|
||||
1,Documentation,documentation.html,documentation.src
|
||||
1,Class Docs,classlib-doc.html,classlib-doc.src
|
||||
1,Test Suite,testing.html,testing.src
|
||||
1,Mono TODO,mono-todo.html,mono-todo.src
|
||||
1,Tools,tools.html,tools.src
|
||||
1,Porting,porting.html,porting.src
|
||||
2,PowerPC,ppc.html,ppc.src
|
||||
@@ -33,7 +29,6 @@
|
||||
0,Resources,resources.html,resources.src
|
||||
1,Beginning,mono-beginning.html,mono-beginning.src
|
||||
1,Mailing Lists,mailing-lists.html,mailing-lists.src
|
||||
1,Blogs,http://www.go-mono.com/monologue
|
||||
1,Ideas,ideas.html,ideas.src
|
||||
1,Passport,passport.html,passport.src
|
||||
1,Books,books.html,books.src
|
||||
@@ -42,7 +37,6 @@
|
||||
1,Debugging,jit-debug.html,jit-debug.src
|
||||
0,Plans,plans.html,plans.src
|
||||
1,ADO.NET,ado-net.html,ado-net.src
|
||||
1,Drawing,drawing.html,drawing.src
|
||||
2,ProviderFactory,provider-factory.html,provider-factory.src
|
||||
2,Firebird Interbase,firebird.html,firebird.src
|
||||
2,IBM DB2,ibmdb2.html,ibmdb2.src
|
||||
@@ -55,7 +49,6 @@
|
||||
2,SQL Lite,sqlite.html,sqlite.src
|
||||
2,Sybase,sybase.html,sybase.src
|
||||
2,TDS Generic,tdsclient.html,tdsclient.src
|
||||
2,TDS Providers,tds-providers.html,tds-providers.src
|
||||
1,Crypto,crypto.html,crypto.src
|
||||
1,Java,java.html,java.src
|
||||
1,Windows.Forms,winforms.html,winforms.src
|
||||
@@ -69,7 +62,7 @@
|
||||
1,Web.Services,class-status-System.Web.Services.html,class-status-System.Web.Services.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Microsoft.VisualBasic,class-status-Microsoft.VisualBasic.html,class-status-Microsoft.VisualBasic.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Windows.Forms,class-status-System.Windows.Forms.html,class-status-System.Windows.Forms.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,DirectoryServices,class-status-System.DirectoryServices.html,class-status-System.DirectoryServices.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,EnterpriseServices,class-status-System.EnterpriseServices.html,class-status-System.EnterpriseServices.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Formatters.Soap,class-status-System.Runtime.Serialization.Formatters.Soap.html,class-status-System.Runtime.Serialization.Formatters.Soap.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,Cscompmgd,class-status-Cscompmgd.html,class-status-Cscompmgd.src,cm/cormissing.css,cm/cormissing.js
|
||||
1,System.Security,class-status-System.Security.html,class-status-System.Security.src,cm/cormissing.css,cm/cormissing.js
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
*.xml
|
||||
+37
-68
@@ -9,23 +9,29 @@ CORCOMPARE=../../../mcs/tools/corcompare
|
||||
|
||||
OBJECTS= \
|
||||
deploy/ado-net.html \
|
||||
deploy/provider-factory.html \
|
||||
deploy/mysql.html \
|
||||
deploy/odbc.html \
|
||||
deploy/oledb.html \
|
||||
deploy/oracle.html \
|
||||
deploy/postgresql.html \
|
||||
deploy/sqlclient.html \
|
||||
deploy/sqlite.html \
|
||||
deploy/sybase.html \
|
||||
deploy/tdsclient.html \
|
||||
deploy/anoncvs.html \
|
||||
deploy/asp-net.html \
|
||||
deploy/blogs.html \
|
||||
deploy/books.html \
|
||||
deploy/bugs.html \
|
||||
deploy/contributing.html \
|
||||
deploy/contact.html \
|
||||
deploy/c-sharp.html \
|
||||
deploy/ccvs.html \
|
||||
deploy/documentation.html \
|
||||
deploy/download.html \
|
||||
deploy/drawing.html \
|
||||
deploy/crypto.html \
|
||||
deploy/embedded-api.html \
|
||||
deploy/faq.html \
|
||||
deploy/firebird.html \
|
||||
deploy/forge.html \
|
||||
deploy/gcc-frontend.html \
|
||||
deploy/gtk-sharp.html \
|
||||
deploy/hackers.html \
|
||||
@@ -40,51 +46,39 @@ OBJECTS= \
|
||||
deploy/mbas.html \
|
||||
deploy/mono-beginning.html \
|
||||
deploy/mono-contribution-howto.html \
|
||||
deploy/mono-todo.html \
|
||||
deploy/monodoc-xml.html \
|
||||
deploy/mysql.html \
|
||||
deploy/odbc.html \
|
||||
deploy/oledb.html \
|
||||
deploy/oracle.html \
|
||||
deploy/other.html \
|
||||
deploy/papers.html \
|
||||
deploy/passport.html \
|
||||
deploy/plans.html \
|
||||
deploy/porting.html \
|
||||
deploy/postgresql.html \
|
||||
deploy/ppc.html \
|
||||
deploy/provider-factory.html \
|
||||
deploy/rationale.html \
|
||||
deploy/resources.html \
|
||||
deploy/roadmap.html \
|
||||
deploy/runtime.html \
|
||||
deploy/screenshots.html \
|
||||
deploy/sqlclient.html \
|
||||
deploy/sqlite.html \
|
||||
deploy/status.html \
|
||||
deploy/sybase.html \
|
||||
deploy/tdsclient.html \
|
||||
deploy/tds-providers.html \
|
||||
deploy/team.html \
|
||||
deploy/testing.html \
|
||||
deploy/tools.html \
|
||||
deploy/winforms.html \
|
||||
deploy/class-library.html \
|
||||
deploy/classlib-doc.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.Security.html \
|
||||
deploy/class-status-System.Web.html \
|
||||
deploy/class-status-System.Web.Services.html \
|
||||
deploy/class-status-System.Drawing.html \
|
||||
deploy/class-status.html \
|
||||
deploy/class-status-corlib.html \
|
||||
deploy/class-status-System.html \
|
||||
deploy/class-status-System.Xml.html \
|
||||
deploy/class-status-System.Drawing.html \
|
||||
deploy/class-status-System.Data.html \
|
||||
deploy/class-status-System.Web.html \
|
||||
deploy/class-status-System.Web.Services.html \
|
||||
deploy/class-status-Microsoft.VisualBasic.html \
|
||||
deploy/class-status-System.EnterpriseServices.html \
|
||||
deploy/class-status-System.Runtime.Serialization.Formatters.Soap.html \
|
||||
deploy/class-status-System.Security.html \
|
||||
deploy/class-status-System.Windows.Forms.html \
|
||||
deploy/class-status-System.DirectoryServices.html \
|
||||
deploy/class-status-Cscompmgd.html \
|
||||
deploy/class-status-System.Runtime.Serialization.Formatters.Soap.html
|
||||
|
||||
HTML_SOURCES = ../mono-roadmap.html
|
||||
deploy/class-library.html \
|
||||
deploy/classlib-doc.html
|
||||
|
||||
#2,Configuration.Install,class-status-System.Configuration.Install.html,class-status-System.Configuration.Install.src,cm/cormissing.css,cm/cormissing.js
|
||||
#2,Runtime.Remoting,class-status-System.Runtime.Remoting.html,class-status-System.Runtime.Remoting.src,cm/cormissing.css,cm/cormissing.js
|
||||
@@ -98,8 +92,7 @@ NON_HTML_SOURCES= \
|
||||
|
||||
all: $(OBJECTS) deploy/index.rss ../team
|
||||
perl process.pl commands template.html.in deploy
|
||||
cp $(HTML_SOURCES) deploy
|
||||
test -d deploy/team || mkdir deploy/team
|
||||
-mkdir deploy/team
|
||||
cp team/*png deploy/team
|
||||
|
||||
tutorial: mono-beginning.html.stamp mono-beginning.pdf
|
||||
@@ -128,15 +121,12 @@ render-team-page.exe: render-team-page.cs
|
||||
$(CSC) render-team-page.cs
|
||||
|
||||
clean:
|
||||
rm -f $(OBJECTS) $(patsubst deploy/%.html,src/%.src, $(OBJECTS)) src/*.xml src/*.html.in ../class-status-* ../class-status infos/*
|
||||
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
|
||||
cp ../mono-roadmap.html deploy
|
||||
#echo scp -P 2200 -r deploy/* [email protected]:/web/cvsmodules/mono
|
||||
#(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . [email protected]:/web/cvsmodules/mono )
|
||||
(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . [email protected]:/web/cvsmodules/mono )
|
||||
|
||||
echo scp -P 2200 -r deploy/* [email protected]:/web/cvsmodules/mono
|
||||
(cd deploy; rsync --verbose --recursive --checksum --update --rsh='ssh' . [email protected]:/web/cvsmodules/mono )
|
||||
|
||||
push2:
|
||||
scp -r deploy/* primates:public_html/xxx
|
||||
@@ -150,7 +140,7 @@ transform.exe: transform.cs
|
||||
|
||||
|
||||
.PRECIOUS: src/%.src
|
||||
src/%.src: ../% commands template.html.in makefile
|
||||
src/%.src: ../% commands template.html.in #makefile
|
||||
perl htmlify $< > $@
|
||||
|
||||
.PRECIOUS: ../class-status-%
|
||||
@@ -159,41 +149,20 @@ src/%.src: ../% commands template.html.in makefile
|
||||
|
||||
|
||||
.PRECIOUS: src/%.html.in
|
||||
src/%.html.in: src/%.xml transform.exe $(CORCOMPARE)/mono-api.xsl
|
||||
$(RUN_MONO) ./transform.exe $< $(CORCOMPARE)/mono-api.xsl > $@ || (rm -f $@ && exit 1)
|
||||
src/%.html.in: src/%.xml transform.exe $(CORCOMPARE)/cormissing.xsl
|
||||
$(RUN_MONO) ./transform.exe $< $(CORCOMPARE)/cormissing.xsl > $@
|
||||
|
||||
|
||||
.PRECIOUS: infos/%.xml
|
||||
infos/%.xml: ../../../mcs/class/lib/%.dll $(CORCOMPARE)/mono-api-info.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $< > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
.PRECIOUS: src/%.xml
|
||||
src/%.xml: infos/%.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/$(notdir $<) $< > $@ || (rm -f $@ && exit 1)
|
||||
src/%.xml: ../../../mcs/class/lib/%.dll $(CORCOMPARE)/CorCompare.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/CorCompare.exe -x $@ $<
|
||||
|
||||
# corlib, corlib...
|
||||
infos/mscorlib.xml: ../../../mcs/class/lib/mscorlib.dll $(CORCOMPARE)/mono-api-info.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $(notdir $(basename $<)) > $@ || (rm -f $@ && exit 1)
|
||||
src/corlib.xml: ../../../mcs/class/lib/corlib_cmp.dll $(CORCOMPARE)/CorCompare.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/CorCompare.exe -f corlib -ms mscorlib -x $@ $<
|
||||
|
||||
src/corlib.xml: infos/mscorlib.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/mscorlib.xml $< > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
# System
|
||||
infos/System.xml: ../../../mcs/class/lib/System.dll $(CORCOMPARE)/mono-api-info.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $(notdir $(basename $<)) > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
src/System.xml: infos/System.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/System.xml $< > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
# System.Xml
|
||||
infos/System.Xml.xml: ../../../mcs/class/lib/System.Xml.dll $(CORCOMPARE)/mono-api-info.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-info.exe $(notdir $(basename $<)) > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
src/System.Xml.xml: infos/System.Xml.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/System.Xml.xml $< > $@ || (rm -f $@ && exit 1)
|
||||
|
||||
src/System.DirectoryServices.xml: infos/System.DirectoryServices.xml $(CORCOMPARE)/mono-api-diff.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/mono-api-diff.exe masterinfos/System.DirectoryServices.xml $< > $@ || (rm -f $@ && exit 1)
|
||||
src/System.Security.xml: ../../../mcs/class/lib/System.Security_cmp.dll $(CORCOMPARE)/CorCompare.exe
|
||||
$(RUN_MONO) $(CORCOMPARE)/CorCompare.exe -f System.Security -ms System.Security -x $@ $<
|
||||
|
||||
../class-status: ../class-status.in
|
||||
cp -f $< $@
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
*.xml
|
||||
+2
-12
@@ -6,21 +6,18 @@
|
||||
using System;
|
||||
using System.IO;
|
||||
using System.Xml;
|
||||
using System.Text;
|
||||
using RSS;
|
||||
|
||||
class X {
|
||||
static RSS.RSS rss;
|
||||
static Channel c;
|
||||
static int item_count;
|
||||
static int line;
|
||||
|
||||
|
||||
static void PopulateRSS (StreamReader input)
|
||||
{
|
||||
string s;
|
||||
|
||||
while ((s = input.ReadLine ()) != null){
|
||||
line++;
|
||||
if (s.StartsWith ("@item "))
|
||||
break;
|
||||
}
|
||||
@@ -52,11 +49,9 @@ class X {
|
||||
i = c.NewItem ();
|
||||
i.Title = title;
|
||||
i.Link = link;
|
||||
i.PubDate = s.Substring (6, s.IndexOf (":") - 6) + ", 2003";
|
||||
} else {
|
||||
description += "\n" + (s == "\n" ? "<p>" : s);
|
||||
}
|
||||
line++;
|
||||
} while ((s = input.ReadLine ()) != null);
|
||||
|
||||
if (i != null){
|
||||
@@ -81,12 +76,7 @@ class X {
|
||||
|
||||
using (FileStream fs = new FileStream (input, FileMode.Open)){
|
||||
using (StreamReader input_stream = new StreamReader (fs)){
|
||||
try {
|
||||
PopulateRSS (input_stream);
|
||||
} catch {
|
||||
Console.WriteLine ("{0} failure while loading: {1}", line, input);
|
||||
throw;
|
||||
}
|
||||
PopulateRSS (input_stream);
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
+1
-16
@@ -13,7 +13,7 @@ namespace RSS {
|
||||
public class Item {
|
||||
XmlDocument doc;
|
||||
XmlNode item;
|
||||
XmlText title, link, description, pubdate;
|
||||
XmlText title, link, description;
|
||||
|
||||
public Item (XmlDocument doc, XmlNode item)
|
||||
{
|
||||
@@ -76,21 +76,6 @@ namespace RSS {
|
||||
description.Value = value;
|
||||
}
|
||||
}
|
||||
|
||||
public string PubDate {
|
||||
get {
|
||||
if (pubdate == null)
|
||||
return null;
|
||||
|
||||
return pubdate.Value;
|
||||
}
|
||||
|
||||
set {
|
||||
if (pubdate == null)
|
||||
pubdate = MakeTextElement ("pubDate");
|
||||
pubdate.Value = value;
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
public class Channel {
|
||||
|
||||
+14
-127
@@ -312,7 +312,7 @@
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<location>Honolulu, Hawai`i</location>
|
||||
<location>Kansas City</location>
|
||||
|
||||
<tasks>
|
||||
|
||||
@@ -454,9 +454,9 @@
|
||||
|
||||
<task>NUnit1 -> NUnit2 conversion</task>
|
||||
|
||||
<task>Mono Handbook, Documentation</task>
|
||||
<task>Stubbing</task>
|
||||
|
||||
<task>DiaCanvas#</task>
|
||||
<task>Mono Handbook work</task>
|
||||
|
||||
<task>Various fixes</task>
|
||||
|
||||
@@ -648,7 +648,7 @@
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>jackson@ximian.com</e-mail>
|
||||
<e-mail>jackson@latitudegeo.com</e-mail>
|
||||
|
||||
<image>jackson.png</image>
|
||||
|
||||
@@ -658,12 +658,12 @@
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>Misc Bug fixes</task>
|
||||
|
||||
<task>Cscompmgd</task>
|
||||
|
||||
<task>IL Assembler</task>
|
||||
|
||||
<task>System.Web</task>
|
||||
|
||||
<task>Bug Fix0r</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
@@ -678,7 +678,7 @@
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>ndrochak AT ieee.org</e-mail>
|
||||
<e-mail>ndrochak AT gol.com</e-mail>
|
||||
|
||||
<image>nickd.png</image>
|
||||
|
||||
@@ -858,13 +858,13 @@
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>jonpryor.png</image>
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Richmond, Virginia</location>
|
||||
<location>Blacksburg, Virginia</location>
|
||||
|
||||
<organization>Cadmus Professional Communications</organization>
|
||||
<organization>Virginia Tech</organization>
|
||||
|
||||
<description>Mono Hacker</description>
|
||||
<description>Graduate Student</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
@@ -1432,120 +1432,7 @@
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>Documentation.</task>
|
||||
|
||||
<task>Monodoc.</task>
|
||||
|
||||
<task>Gtk#</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>Peter</first-name>
|
||||
|
||||
<last-name>Williams</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>peterw.png</image>
|
||||
|
||||
<location>Cambridge, MA</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>Makefile Magician</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>MCS build system </task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>Todd</first-name>
|
||||
|
||||
<last-name>Berman</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>tberman.png</image>
|
||||
|
||||
<location>Toronto, ON, CA</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description></description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>WSE2</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>Carlos</first-name>
|
||||
|
||||
<last-name>Guzmán Álvarez</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>none.png</image>
|
||||
|
||||
<location>Vigo, Spain</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>Contributor</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>TLS protocol</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
</contributor>
|
||||
|
||||
<contributor>
|
||||
|
||||
<name>
|
||||
|
||||
<first-name>Jordi</first-name>
|
||||
|
||||
<last-name>Mas i Hernàndez</last-name>
|
||||
|
||||
</name>
|
||||
|
||||
<e-mail>[email protected]</e-mail>
|
||||
|
||||
<image>jordi.png</image>
|
||||
|
||||
<location>Barcelona, Spain</location>
|
||||
|
||||
<organization></organization>
|
||||
|
||||
<description>Developer</description>
|
||||
|
||||
<tasks>
|
||||
|
||||
<task>Windows.Forms implementation</task>
|
||||
<task>Gtk# Documentation.</task>
|
||||
|
||||
</tasks>
|
||||
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 4.5 KiB After Width: | Height: | Size: 4.3 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.3 KiB |
@@ -15,7 +15,6 @@
|
||||
.navi0 { font-size: 14px; font-weight: bold; background: #444444; }
|
||||
.navi1 { font-size: 14px; font-weight: bold; left-margin: 10pt}
|
||||
.navi2 { font-size: 10px; font-weight: bold; left-margin: 20pt}
|
||||
.topmenu { font-size: 14px; font-weight: bold; }
|
||||
.footnote { font-size: 12px; color: #aaaaaa; }
|
||||
|
||||
a.navi0 { color: #ffffff; text-decoration: none}
|
||||
@@ -30,14 +29,6 @@
|
||||
a.navi2:visited { color: #cccccc; }
|
||||
a.navi2:hover { color: #ee9900; text-decoration: underline; }
|
||||
|
||||
a.topmenu { color: #ffffff; text-decoration: none; margin-left: 7px;}
|
||||
a.topmenu:visited { color: #cccccc; }
|
||||
a.topmenu:hover { color: #ee9900; text-decoration: underline; }
|
||||
|
||||
h1 {
|
||||
border-bottom: 2px solid #dddddd;
|
||||
}
|
||||
|
||||
// -->
|
||||
</style>
|
||||
#CSS#
|
||||
@@ -47,28 +38,11 @@
|
||||
|
||||
<table cellpadding="0" cellspacing="0" border="0" width="100%">
|
||||
<tr>
|
||||
<td><img src="images/pixel.gif" alt=""></td><!-- left border
|
||||
-->
|
||||
<td colspan="4">
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
<a href="http://www.go-mono.com"><img
|
||||
src="images/mono-new.gif" alt="mono-logo" border="0"></a>
|
||||
</td>
|
||||
<td>
|
||||
<a class="topmenu" href="download.html">Downloads</a> |
|
||||
<a class="topmenu" href="http://go-mono.com/daily">Daily snapshots</a> |
|
||||
<a class="topmenu" href="screenshots.html">Screenshots</a> |
|
||||
<a class="topmenu" href="http://www.go-mono.com:8080">Documentation</a> |
|
||||
<a class="topmenu" href="bugs.html">Bugs</a> |
|
||||
<a class="topmenu" href="blogs.html">Blogs</a>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
<td><img src="images/pixel.gif" alt=""></td><!-- right border
|
||||
-->
|
||||
<td><img src="images/pixel.gif" alt=""></td><!-- left border -->
|
||||
<td colspan="4">
|
||||
<a href="http://www.go-mono.com"><img src="images/mono-new.gif"
|
||||
alt="mono-logo" border="0"></a></td>
|
||||
<td><img src="images/pixel.gif" alt=""></td><!-- right border -->
|
||||
</tr>
|
||||
<tr>
|
||||
<td><img src="images/pixel.gif" width="1" height="1" alt=""></td>
|
||||
|
||||
+81
-10
@@ -27,13 +27,12 @@
|
||||
|
||||
* Win32/Wine edition.
|
||||
|
||||
To get the Windows.Forms support working, you need a Mono
|
||||
installation from CVS, and you need to install Wine plus the
|
||||
<a href="http://www.openlinksw.com">OpenLink patch</a>, and
|
||||
Currently (May 21st, 2003) to get the Windows.Forms support
|
||||
working, you need a Mono installation from CVS, and you need
|
||||
to install Wine plus the <a
|
||||
href="http://www.openlinksw.com">OpenLink patch</a>, and
|
||||
define the environment variable "SWF" (export SWF=1 from your
|
||||
shell). For more information, see the <a
|
||||
href="http://www.nullenvoid.com/mono/wiki/index.php/MonoWinePackages">Mono
|
||||
Wine Packages</a> page in the Mono Wiki.
|
||||
shell).
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
@@ -48,7 +47,7 @@
|
||||
calls to Win32 and we will then just run the result on Unix.
|
||||
|
||||
In terms of integrating visually with the desktop, we are
|
||||
hoping to contribute to the Wine project a mechanism to make
|
||||
hoping to contribute to the Wine project an mechanism to make
|
||||
it use the Gtk+ themes on X11 and Cocoa on MacOS to render the
|
||||
widgets, and get the native look and feel on each of these
|
||||
platforms.
|
||||
@@ -90,7 +89,79 @@
|
||||
|
||||
* System.Drawing
|
||||
|
||||
For details, see the <a
|
||||
href="drawing.html">System.Drawing implementation notes</a>
|
||||
section of the web site.
|
||||
Using existing libraries to implement some of the
|
||||
functionality required:
|
||||
|
||||
<ul>
|
||||
* gdk-pixbuf is a generic image loader that loads an image
|
||||
and leaves it into an RGB buffer. It hides all the details
|
||||
about what image file format is being loaded.
|
||||
|
||||
* Libart is a general framework for rendering RGB/RGBA
|
||||
buffers into RGB buffers and rendering postscript-like paths into
|
||||
RGB/RGBA buffers.
|
||||
</ul>
|
||||
|
||||
We want to use gdk-pixbuf as the image loader for the image
|
||||
classes, and then we need operations to render that into the
|
||||
windowing system (Gtk+, MacOS, etc). But notice how there is
|
||||
very little dependnecies in Gdk-pixbuf on gtk, and libart has
|
||||
none.
|
||||
|
||||
They are pretty independent from a windowing system
|
||||
(gdk-pixbuf comes with some "helper" routines for rendering
|
||||
data into a pixmap and to load pixmaps into RGB buffers).
|
||||
|
||||
A few things to keep in mind:
|
||||
|
||||
<ul>
|
||||
|
||||
* gdk-pixbuf can be used to load images for Gtk+,
|
||||
MacOS X and Windows, it should be pretty portable,
|
||||
although we might need in the future to back-port
|
||||
some new features from Gtk head.
|
||||
|
||||
* Libart is probably only going to be used with X11,
|
||||
as the MacOS X provides the same features in Quartz,
|
||||
and Win32 *probably* has that in GDI+. If not, we
|
||||
should use libart in Win32 as well (or for older
|
||||
Windows systems).
|
||||
</ul>
|
||||
|
||||
* Directory Layout
|
||||
|
||||
<pre>
|
||||
System.Drawing (assembly directory)
|
||||
System.Drawing.Blah
|
||||
Common code for "Blah"
|
||||
Stubs for "Blah" to ease ports.
|
||||
|
||||
Gtk
|
||||
System.Drawing.Blah.
|
||||
Gtk ports of "System.Drawing.Blah"
|
||||
MacOS
|
||||
System.Drawing.Blah
|
||||
MacOS ports of "System.Drawing.Blah"
|
||||
WineLIB
|
||||
System.Drawing.Blah
|
||||
Win32 ports of "System.Drawing.Blah"
|
||||
</pre>
|
||||
|
||||
Notice that there is a proof of concept Gtk-backend for
|
||||
Windows.Forms, but nobody is working on it, and for the
|
||||
reasons stated before it is not a long term strategy.
|
||||
|
||||
* Open questions:
|
||||
|
||||
I believe that the graphics contexts that are used to render
|
||||
can accept either libart-like rendering operations and
|
||||
X11-like rendering operations. This complicates matters, but
|
||||
I am not sure. Someone needs to investigate this.
|
||||
|
||||
* Historical
|
||||
|
||||
Although the original plans were to use Gtk on X and Cocoa on
|
||||
MacOS X, it would be very hard to emulate the event model in
|
||||
which some Winforms applications depend, and it would be very
|
||||
hard to implement the Wndproc method.
|
||||
|
||||
+1
-2
@@ -1,4 +1,3 @@
|
||||
EXTRA_DIST = gc-issues jit-thoughts object-layout unmanaged-calls \
|
||||
exceptions jit-trampolines stack-alignment embedded-api \
|
||||
assembly-bundle
|
||||
exceptions jit-trampolines stack-alignment embedded-api
|
||||
|
||||
@@ -1,42 +0,0 @@
|
||||
|
||||
HOWTO bundle assemblies inside the mono runtime.
|
||||
|
||||
Bundling assemblies inside the mono runtime may be useful for a number
|
||||
of reasons:
|
||||
* creating a standalone complete runtime that can be more easily
|
||||
distributed
|
||||
* having an application run against a known set of assemblies
|
||||
that has been tested
|
||||
|
||||
Of course, there are drawbacks, too: if there has been fixes to the assemblies,
|
||||
replacing them means recompiling the runtime as well and if there are other mono apps,
|
||||
unless they use the same mono binary, there will be less opportunities for
|
||||
the operating system to optimize memory usage. So use this feature only
|
||||
when really needed.
|
||||
|
||||
To bundle a set of assemblies, you need to create a file that lists the assembly
|
||||
names and the relative files. Empty lines and lines starting with # are ignored:
|
||||
|
||||
== cut cut ==
|
||||
# Sample bundle template
|
||||
mscorlib: /path/to/mscorlib/assembly.dll
|
||||
myapp: /path/to/myapp.exe
|
||||
== cut cut ==
|
||||
|
||||
Next you need to build the mono runtime using a special configure option:
|
||||
|
||||
./configure --with-bundle=/path/to/bundle/template
|
||||
|
||||
The path to the template should be an absolute path.
|
||||
|
||||
The script metadata/make-bundle.pl will take the specifie assemblies and embed
|
||||
them inside the runtime where the loading routines can find them before
|
||||
searching for them on disk.
|
||||
|
||||
There are still two issues to solve:
|
||||
* config files: sometimes they are needed but they are not yet bundled
|
||||
inside the library ()
|
||||
* building with the included libgc makes it not possible to build a mono
|
||||
binary statically linked to libmono: this needs to be fixed to make bundles
|
||||
really useful
|
||||
|
||||
+2
-1
@@ -1,4 +1,5 @@
|
||||
man_MANS = mcs.1 mono.1 monostyle.1 mono-config.5 sqlsharp.1 oldmono.1 ilasm.1 \
|
||||
cert2spc.1 cilc.1 genxs.1
|
||||
cert2spc.1 cilc.1
|
||||
|
||||
EXTRA_DIST = $(man_MANS)
|
||||
|
||||
@@ -1,37 +0,0 @@
|
||||
.\"
|
||||
.\" chktrust manual page.
|
||||
.\" Copyright 2003 Motus Technologies
|
||||
.\" Author:
|
||||
.\" Sebastien Pouliot ([email protected])
|
||||
.\"
|
||||
.TH Mono "chktrust"
|
||||
.SH NAME
|
||||
chktrust \- Check the trust of a PE executable.
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B chktrust [options] filename
|
||||
.SH DESCRIPTION
|
||||
Verify if an PE executable (CLR assembly, Win32 EXE or DLL) has a valid
|
||||
Authenticode(r) signature that can be traced back to a trusted certificate
|
||||
authority (CA).
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
.I "-q", "-quiet"
|
||||
Limited display on console.
|
||||
.TP
|
||||
.I "-v", "-verbose"
|
||||
More details displayed on the console.
|
||||
.TP
|
||||
.I "-help", "-h", "-?", "/?"
|
||||
Display help about this tool.
|
||||
.SH AUTHOR
|
||||
Written by Sebastien Pouliot
|
||||
.SH COPYRIGHT
|
||||
Copyright (C) 2003 Motus Technologies.
|
||||
Released under BSD license.
|
||||
.SH MAILING LISTS
|
||||
Visit http://mail.ximian.com/mailman/mono-list for details.
|
||||
.SH WEB SITE
|
||||
Visit: http://www.go-mono.com for details
|
||||
.SH SEE ALSO
|
||||
.BR signcode(1), makecert(1)
|
||||
-294
@@ -1,294 +0,0 @@
|
||||
.\"
|
||||
.\" genxs manual page.
|
||||
.\" (C) Lluis Sanchez Gual ([email protected])
|
||||
.\"
|
||||
.TH genxs 1
|
||||
.SH NAME
|
||||
genxs \- Mono's Xml Serializer Generator
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B genxs
|
||||
configurationFile [destinationFolder]
|
||||
.SH DESCRIPTION
|
||||
.I genxs
|
||||
is a tool for generating custom XML serialization writers and readers for
|
||||
classes.
|
||||
.PP
|
||||
.I configurationFile
|
||||
is configuration file which specifies several
|
||||
information, such as the class for which to generate the reader and writer, the
|
||||
name and namespace of the classes to generate, and a collection of hooks to
|
||||
apply. By using hooks it is possible to customize the
|
||||
behavior of the serializer without needing to modify the generated file, so you
|
||||
can safely regenerate it if the source class is modified.
|
||||
.PP
|
||||
.I destinationFolder
|
||||
specifies the folder where the files will be generated.
|
||||
.PP
|
||||
.B NOTE:
|
||||
This tool only runs in the Mono runtime, since it uses some internal
|
||||
classes not available in other runtimes.
|
||||
.SH CONFIGURATION FILE FORMAT
|
||||
The configuration file is an xml document based on the following grammar
|
||||
("?" means optional, "*" 0 or more):
|
||||
.PP
|
||||
.nf
|
||||
<configuration>
|
||||
<serializer class="name" assembly="name"> *
|
||||
<reader>name</reader> ?
|
||||
<writer>name</writer> ?
|
||||
<namespace>name</namespace> ?
|
||||
<outFileName>name</outFileName> ?
|
||||
<readerHooks> ?
|
||||
<hook ...> *
|
||||
</readerHooks>
|
||||
<writerHooks> ?
|
||||
<hook ...> *
|
||||
</writerHooks>
|
||||
</serializer>
|
||||
</configuration>
|
||||
.fi
|
||||
.PP
|
||||
A configuration file can have multiple "serializer" elements, each of which
|
||||
specifies the class for which to generate a serializer together with several
|
||||
generation options. The source class is specified in the following attributes:
|
||||
.PP
|
||||
.IP " *" 5
|
||||
.I class
|
||||
: name of the class (including namespace).
|
||||
.IP " *" 5
|
||||
.I assembly
|
||||
: assembly name. It can include the complete path.
|
||||
.PP
|
||||
Generation options are specified in child elements:
|
||||
.PP
|
||||
.IP " *" 5
|
||||
.I reader
|
||||
: name of the reader class.
|
||||
.IP " *" 5
|
||||
.I writer
|
||||
: name of the writer class.
|
||||
.IP " *" 5
|
||||
.I namespace
|
||||
: namespace of the reader and writer classes.
|
||||
.IP " *" 5
|
||||
.I outFileName
|
||||
: name of the generated file.
|
||||
.IP " *" 5
|
||||
.I readerHooks
|
||||
: a list of hooks to apply to the reader.
|
||||
.IP " *" 5
|
||||
.I writerHooks
|
||||
: a list of hooks to apply to the writer.
|
||||
.SH SPECIFYING HOOKS
|
||||
Using hooks you can customize the behavior of readers and writers.
|
||||
A hook specification follows this grammar:
|
||||
.PP
|
||||
.nf
|
||||
<hook type="name">
|
||||
<select> ?
|
||||
<typeName>name</typeName> ?
|
||||
<typeAttribute>name</typeAttribute> *
|
||||
<typeMember>name</typeMember> ?
|
||||
</select>
|
||||
<replace>source code</replace> ?
|
||||
<insertBefore>source code</insertBefore> ?
|
||||
<insertAfter>source code</insertAfter> ?
|
||||
</hook>
|
||||
.fi
|
||||
.PP
|
||||
The "type" attribute specifies the context in which the hook is applied. It can
|
||||
be one of the following:
|
||||
.PP
|
||||
.IP " *" 5
|
||||
.I attributes
|
||||
: hook is applied where attributes are serialized/deserialized.
|
||||
.IP " *" 5
|
||||
.I elements
|
||||
: hook is applied where elements are serialized/deserialized.
|
||||
.IP " *" 5
|
||||
.I unknownAttribute
|
||||
: hook is applied where unknown attributes are processed.
|
||||
.IP " *" 5
|
||||
.I unknownElement
|
||||
: hook is applied where unknown elements are processed.
|
||||
.IP " *" 5
|
||||
.I member
|
||||
: hook is applied where a member is serialized/deserialized.
|
||||
.IP " *" 5
|
||||
.I type
|
||||
: hook is applied for the whole type.
|
||||
.PP
|
||||
The "select" element specifies the classes and members to which the hook has
|
||||
to be added. It can contain the following elements:
|
||||
.PP
|
||||
.IP " *" 5
|
||||
.I typeName
|
||||
: the class with that name will be selected (must include namespace)
|
||||
.IP " *" 5
|
||||
.I typeAttribute
|
||||
: all classes which have that attribute applied will be selected (specify the
|
||||
full attribute class name, including namespace). Several attribute names can be
|
||||
specified.
|
||||
.IP " *" 5
|
||||
.I typeMember
|
||||
: name of the class member for which the hook must be added.
|
||||
.PP
|
||||
The hook source code can be specified using any of the following elements:
|
||||
.PP
|
||||
.IP " *" 5
|
||||
.I replace
|
||||
: the provided source code will replace all serialization/deserialization
|
||||
operations in the hook context.
|
||||
.IP " *" 5
|
||||
.I insertBefore
|
||||
: the source code will be added before the hook context.
|
||||
.IP " *" 5
|
||||
.I insertAfter
|
||||
: the source code will be added after the hook context.
|
||||
.PP
|
||||
When writing the code for a hook you can use some special variables that are
|
||||
defined during the code generation process. The variables are the following:
|
||||
.PP
|
||||
.IP " *" 5
|
||||
.I $TYPE:
|
||||
name of the class being generated, without namespace.
|
||||
.IP " *" 5
|
||||
.I $FULLTYPE:
|
||||
full name of the class being generated, including namespace.
|
||||
.IP " *" 5
|
||||
.I $OBJECT:
|
||||
the object being serialized or deserialized. When using a replace
|
||||
reader hook of type "type", the hook code must assign the deserialized object
|
||||
to this variable.
|
||||
.IP " *" 5
|
||||
-I $ELEMENT:
|
||||
name of the element of the object being serialized/deserialized.
|
||||
.IP " *" 5
|
||||
.I $NAMESPACE:
|
||||
namespace of the element of the object being serialized/deserialized.
|
||||
.IP " *" 5
|
||||
.I $MEMBER:
|
||||
name of the member being serialized/deserialized. Only valid in the "member"
|
||||
context.
|
||||
.SH HOOK EXAMPLES
|
||||
The following example adds a call to a Validate method after the deserialization
|
||||
of any object:
|
||||
.PP
|
||||
.nf
|
||||
<hook type="type">
|
||||
<insertAfter>
|
||||
System.Xml.Schema.XmlSchema.Validate$TYPE ($OBJECT);
|
||||
</insertAfter>
|
||||
</hook>
|
||||
.fi
|
||||
.PP
|
||||
This example specifies the code to be used to deserialize the XmlSchema class:
|
||||
.PP
|
||||
.nf
|
||||
<hook type="type">
|
||||
<select>
|
||||
<typeName>System.Xml.Schema.XmlSchema</typeName>
|
||||
</select>
|
||||
<replace>
|
||||
$OBJECT = System.Xml.Schema.XmlSchema.Read (Reader, null);
|
||||
</replace>
|
||||
</hook>
|
||||
.fi
|
||||
.PP
|
||||
That one specifies the code to be used to read XmlSchema instances:
|
||||
.PP
|
||||
.nf
|
||||
<hook type="type">
|
||||
<select>
|
||||
<typeName>System.Xml.Schema.XmlSchema</typeName>
|
||||
</select>
|
||||
<replace>$OBJECT.Write (Writer);</replace>
|
||||
</hook>
|
||||
.fi
|
||||
.PP
|
||||
With this two hooks the serializer will print some information when serializing
|
||||
the class "MyClass":
|
||||
.PP
|
||||
.nf
|
||||
<hook type="type">
|
||||
<select>
|
||||
<typeName>MyNamespace.MyClass</typeName>
|
||||
</select>
|
||||
<insertBefore>Console.WriteLine ("Serializing MyClass");</replace>
|
||||
<insertAfter>Console.WriteLine ("MyClass serialized");</insertAfter>
|
||||
</hook>
|
||||
<hook type="member">
|
||||
<select>
|
||||
<typeName>MyNamespace.MyClass</typeName>
|
||||
</select>
|
||||
<insertAfter>
|
||||
Console.WriteLine ("Serialized member $MEMBER");
|
||||
</insertAfter>
|
||||
</hook>
|
||||
.fi
|
||||
.PP
|
||||
This hook writes an additional element for all types that have the custom
|
||||
attribute "MyAttribute":
|
||||
.PP
|
||||
.nf
|
||||
<hook type="elements">
|
||||
<select>
|
||||
<typeAttribute>MyNamespace.MyAttribute</typeAttribute>
|
||||
</select>
|
||||
<insertAfter>
|
||||
Writer.WriteStartElement ("privateData");
|
||||
Writer.WriteString ($OBJECT.PrivateData);
|
||||
Writer.WriteEndElement ();
|
||||
</insertAfter>
|
||||
</hook>
|
||||
.fi
|
||||
.SH CONFIGURATION FILE EXAMPLE
|
||||
This is the configuration file used to generate the serializer for ServiceDescription:
|
||||
.PP
|
||||
.nf
|
||||
<configuration>
|
||||
<serializer class="System.Web.Services.Description.ServiceDescription" assembly="System.Web.Services">
|
||||
<reader>ServiceDescriptionReaderBase</reader>
|
||||
<writer>ServiceDescriptionWriterBase</writer>
|
||||
<namespace>System.Web.Services.Description</namespace>
|
||||
<outFileName>ServiceDescriptionSerializerBase.cs</outFileName>
|
||||
<readerHooks>
|
||||
<hook type="unknownElement">
|
||||
<select>
|
||||
<typeAttribute>System.Web.Services.Configuration.XmlFormatExtensionPointAttribute</typeAttribute>
|
||||
</select>
|
||||
<replace>ServiceDescription.ReadExtension (Reader, $OBJECT);</replace>
|
||||
</hook>
|
||||
<hook type="type">
|
||||
<select>
|
||||
<typeName>System.Xml.Schema.XmlSchema</typeName>
|
||||
</select>
|
||||
<replace>$OBJECT = System.Xml.Schema.XmlSchema.Read (Reader, null);</replace>
|
||||
</hook>
|
||||
</readerHooks>
|
||||
<writerHooks>
|
||||
<hook type="elements">
|
||||
<select>
|
||||
<typeAttribute>System.Web.Services.Configuration.XmlFormatExtensionPointAttribute</typeAttribute>
|
||||
</select>
|
||||
<insertBefore>ServiceDescription.WriteExtensions (Writer, $OBJECT);</insertBefore>
|
||||
</hook>
|
||||
<hook type="type">
|
||||
<select>
|
||||
<typeName>System.Xml.Schema.XmlSchema</typeName>
|
||||
</select>
|
||||
<replace>$OBJECT.Write (Writer);</replace>
|
||||
</hook>
|
||||
</writerHooks>
|
||||
</serializer>
|
||||
</configuration>
|
||||
.fi
|
||||
.SH AUTHORS
|
||||
Lluis Sanchez Gual ([email protected])
|
||||
.PP
|
||||
.SH LICENSE
|
||||
GenXS is released under the terms of the GNU GPL.
|
||||
.PP
|
||||
.SH SEE ALSO
|
||||
mono(1), mcs(1)
|
||||
@@ -1,88 +0,0 @@
|
||||
.\"
|
||||
.\" makecert manual page.
|
||||
.\" Copyright 2003 Motus Technologies
|
||||
.\" Author:
|
||||
.\" Sebastien Pouliot ([email protected])
|
||||
.\"
|
||||
.TH Mono "MakeCert"
|
||||
.SH NAME
|
||||
MakeCert \- Create X.509 certificates for test purposes
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B MakeCert [options] certificate
|
||||
.SH DESCRIPTION
|
||||
Create an X.509 certificate using the provided informations. This
|
||||
is useful for testing Authenticode signatures, SSL and S/MIME
|
||||
technologies.
|
||||
.SH PARAMETERS
|
||||
.TP
|
||||
.I "-# num"
|
||||
Certificate serial number
|
||||
.TP
|
||||
.I "-n dn"
|
||||
Subject Distinguished Name
|
||||
.TP
|
||||
.I "-in dn"
|
||||
Issuert Distinguished Name
|
||||
.TP
|
||||
.I "-r"
|
||||
Create a self-signed (root) certificate
|
||||
.TP
|
||||
.I "-sv pkvfile"
|
||||
Private key file (.PVK) for the subject (created if missing)
|
||||
.TP
|
||||
.I "-iv pvkfile"
|
||||
Private key file (.PVK) for the issuer
|
||||
.TP
|
||||
.I "-ic certfile"
|
||||
Extract the issuer's name from the specified certificate
|
||||
.TP
|
||||
.I "-?"
|
||||
Help (display this help message)
|
||||
.TP
|
||||
.I "-!"
|
||||
Extended help (for advanced options)
|
||||
.TP
|
||||
.I "-a hash"
|
||||
Select hash algorithm. Only MD5 and SHA1 are supported.
|
||||
.TP
|
||||
.I "-b date"
|
||||
The date since when the certificate is valid (notBefore).
|
||||
.TP
|
||||
.I "-cy [authority|end]"
|
||||
Basic constraints. Select Authority or End-Entity certificate.
|
||||
.TP
|
||||
.I "-e date"
|
||||
The date until when the certificate is valid (notAfter).
|
||||
.TP
|
||||
.I "-eku oid[,oid]"
|
||||
Add some extended key usage OID to the certificate.
|
||||
.TP
|
||||
.I "-h number"
|
||||
Add a path length restriction to the certificate chain.
|
||||
.TP
|
||||
.I "-ic cert"
|
||||
Take the issuer's name from the specified certificate.
|
||||
.TP
|
||||
.I "-in name"
|
||||
Take the issuer's name from the specified parameter.
|
||||
.TP
|
||||
.I "-iv pvkfile"
|
||||
Sign the certificate using the private key inside the PVK file.
|
||||
.TP
|
||||
.I "-m number"
|
||||
Certificate validity period (in months).
|
||||
.TP
|
||||
.I "-sv pvkfile"
|
||||
Create a new PVK file if non-existant, otherwise use the PVK file as the subject public key.
|
||||
.SH AUTHOR
|
||||
Written by Sebastien Pouliot
|
||||
.SH COPYRIGHT
|
||||
Copyright (C) 2003 Motus Technologies.
|
||||
Released under BSD license.
|
||||
.SH MAILING LISTS
|
||||
Visit http://mail.ximian.com/mailman/mono-list for details.
|
||||
.SH WEB SITE
|
||||
Visit: http://www.go-mono.com for details
|
||||
.SH SEE ALSO
|
||||
.BR signcode(1)
|
||||
-18
@@ -1,18 +0,0 @@
|
||||
<?xml version="1.0"?>
|
||||
<manpages>
|
||||
<manpage name="Mono" page="mono.1" />
|
||||
<manpage name="Mint" page="mono.1" />
|
||||
<manpage name="Mcs" page="mcs.1" />
|
||||
<manpage name="Ilasm" page="ilasm.1" />
|
||||
<manpage name="Monodis" page="mono.1" />
|
||||
<manpage name="Cilc" page="cilc.1" />
|
||||
<manpage name="Sql#" page="sqlsharp.1" />
|
||||
<manpage name="SecUtil" page="secutil.1" />
|
||||
<manpage name="MonoStyle" page="monostyle.1" />
|
||||
<manpage name="genxs" page="genxs.1" />
|
||||
<manpage name="cert2spc" page="cert2spc.1" />
|
||||
<manpage name="makecert" page="makecert.1" />
|
||||
<manpage name="chktrust" page="chktrust.1" />
|
||||
<manpage name="signcode" page="signcode.1" />
|
||||
<manpage name="sn" page="sn.1" />
|
||||
</manpages>
|
||||
@@ -1,4 +0,0 @@
|
||||
<?xml version="1.0"?>
|
||||
<monodoc>
|
||||
<source provider="man" basefile="tree" path="manpages"/>
|
||||
</monodoc>
|
||||
@@ -195,9 +195,7 @@ for details on how to use this file.
|
||||
.SH NOTES
|
||||
During compilation the MCS compiler defines the __MonoCS__ symbol,
|
||||
this can be used by pre-processor instructions to compile Mono C#
|
||||
compiler specific code. Please note that this symbol is only to test
|
||||
for the compiler, and is not useful to distinguish compilation or
|
||||
deployment platforms.
|
||||
compiler specific code.
|
||||
.SH AUTHORS
|
||||
The Mono C# Compiler was written by Miguel de Icaza, Ravi Pratap and
|
||||
Martin Baulig at Ximian.
|
||||
|
||||
+10
-73
@@ -115,9 +115,8 @@ Instructs the runtime to collect profiling information about execution
|
||||
times and memory allocation, and dump it at the end of the execution.
|
||||
If a profiler is not specified, the default profiler is used. profiler_args
|
||||
is a profiler-specific string of options for the profiler itself.
|
||||
.PP
|
||||
The default profiler accepts -time and -alloc to options to disable
|
||||
the time profiling or the memory allocation profilng.
|
||||
|
||||
|
||||
.SH JIT MAINTAINER OPTIONS
|
||||
The maintainer options are only used by those developing the runtime
|
||||
itself, and not typically of interest to runtime users or developers.
|
||||
@@ -168,45 +167,10 @@ breakpoint on the application's main method.
|
||||
Inserts a breakpoint on exceptions. This allows you to debug your
|
||||
application with a native debugger when an exception is thrown.
|
||||
.TP
|
||||
.I "--trace[=expression]"
|
||||
Shows method names as they are invoked. By default all methods are
|
||||
traced.
|
||||
.TP
|
||||
The trace can be customized to include or exclude methods, classes or
|
||||
assemblies. A trace expression is a comma separated list of targets,
|
||||
each target can be prefixed with a minus sign to turn off a particular
|
||||
target. The words `program' and `all' have special meaning.
|
||||
`program' refers to the main program being executed, and `all' means
|
||||
all the method calls.
|
||||
.TP
|
||||
Assemblies are specified by their name, for example, to trace all
|
||||
calls in the System assembly, use:
|
||||
.nf
|
||||
mono --trace=System app.exe
|
||||
.fi
|
||||
Classes are specified with the T: prefix. For example, to trace all
|
||||
calls to the System.String class, use:
|
||||
.nf
|
||||
mono --trace=T:System.String app.exe
|
||||
.fi
|
||||
And individual methods are referenced with the M: prefix, and the
|
||||
standar method notation:
|
||||
.nf
|
||||
mono --trace=M:System.Console.WriteLine app.exe
|
||||
.fi
|
||||
As previously noted, various rules can be specified at once:
|
||||
.nf
|
||||
mono --trace=T:System.String,T:System.Random app.exe
|
||||
.fi
|
||||
You can exclude pieces, the next example traces calls to
|
||||
System.String except for the System.String:Concat method.
|
||||
.nf
|
||||
mono --trace=T:System.String,-M:System.String:Concat
|
||||
.fi
|
||||
Finally, namespaces can be specified using the N: prefix:
|
||||
.nf
|
||||
mono --trace=N:System.Xml
|
||||
.fi
|
||||
.I "--trace"
|
||||
Shows method names as they are invoked.
|
||||
|
||||
|
||||
.SH ENVIRONMENT VARIABLES
|
||||
.TP
|
||||
.I "GC_DONT_GC"
|
||||
@@ -219,10 +183,9 @@ Directories are separated by the platform path separator (colons on unix). Examp
|
||||
.B /home/username/lib:/usr/local/mono/lib
|
||||
.TP
|
||||
.I "MONO_DISABLE_SHM"
|
||||
If this variable is set, it disables the shared memory part of the
|
||||
Windows I/O Emulation layer, and handles (files, events, mutexes,
|
||||
pipes) will not be shared across processes. Process creation is also
|
||||
disabled. This option is only available on Unix.
|
||||
If this variable is set, it disables the Windows I/O Emulation layer,
|
||||
and handles (files, events, mutexes, pipes) will not be shared across
|
||||
processes. This option is only available on Unix.
|
||||
.TP
|
||||
.I "MONO_CFG_DIR"
|
||||
If set, this variable overrides the default system configuration directory
|
||||
@@ -232,30 +195,6 @@ If set, this variable overrides the default system configuration directory
|
||||
If set, this variable overrides the default runtime configuration file
|
||||
($PREFIX/etc/mono/config). The --config command line options overrides the
|
||||
environment variable.
|
||||
.TP
|
||||
.I "MONO_DEBUG"
|
||||
If set, enables some features of the runtime useful for debugging.
|
||||
Currently it only makes the runtime display the stack traces for all the
|
||||
threads running and exit. It may not exit cleanly. Use at your own risk.
|
||||
.TP
|
||||
.I "MONO_EXTERNAL_ENCODINGS"
|
||||
If set, contains a colon-separated list of text encodings to try when
|
||||
turning externally-generated text (e.g. command-line arguments or
|
||||
filenames) into unicode. The encoding names come from the list
|
||||
provided by iconv, and the special case "default_locale" which refers
|
||||
to the current locale's default encoding.
|
||||
.TP
|
||||
When reading externally-generated text strings UTF-8 is tried first,
|
||||
and then this list is tried in order with the first successful
|
||||
conversion ending the search. When writing external text (e.g. new
|
||||
filenames or arguments to new processes) the first item in this list
|
||||
is used, or UTF-8 if the environment variable is not set.
|
||||
.TP
|
||||
.I "MONO_SHARED_DIR"
|
||||
If set its the directory where the ".wapi" handle state is stored.
|
||||
This is the directory where the Windows I/O Emulation layer stores its
|
||||
shared state data (files, events, mutexes, pipes). By default Mono
|
||||
will store the ".wapi" directory in the users's home directory.
|
||||
.SH FILES
|
||||
On Unix assemblies are loaded from the installation lib directory. If you set
|
||||
`prefix' to /usr, the assemblies will be located in /usr/lib. On
|
||||
@@ -271,8 +210,6 @@ Visit http://mail.ximian.com/mailman/mono-list for details.
|
||||
.SH WEB SITE
|
||||
Visit: http://www.go-mono.com for details
|
||||
.SH SEE ALSO
|
||||
.BR mcs(1), mint(1), monodis(1), mono-config(5).
|
||||
.PP
|
||||
For ASP.NET-related documentation, see the xsp(1) manual page
|
||||
.BR mcs(1), mint(1), monodis(1), mono-config(5)
|
||||
|
||||
|
||||
@@ -1,81 +0,0 @@
|
||||
.\"
|
||||
.\" signcode manual page.
|
||||
.\" Copyright 2003 Motus Technologies
|
||||
.\" Author:
|
||||
.\" Sebastien Pouliot ([email protected])
|
||||
.\"
|
||||
.TH Mono "signcode"
|
||||
.SH NAME
|
||||
signcode \- Digitally sign an PE executable using an X.509 certificate.
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B signcode [options] filename
|
||||
.SH DESCRIPTION
|
||||
Digitally sign an PE executable (CLR assembly, Win32 EXE or DLL) using an
|
||||
X.509 certificate and it's associated private key. The signature is compatible
|
||||
with Authenticode(r) and can be validated with chktrust.
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
.I "-spc spcfile"
|
||||
The Software Publisher File (spc) that contains the X.509 certificate chain
|
||||
used to digitally sign the PE executable.
|
||||
.TP
|
||||
.I "-v pvkfile"
|
||||
The Private Key File (pvk) that contains the private key used to digitally
|
||||
sign the PE executable. This private key must match the public key inside the
|
||||
publisher X.509 certificate.
|
||||
.TP
|
||||
.I "-a md5 | sha1"
|
||||
The hash algorithm used in the digital signature of the PE executable. The
|
||||
default algorithm is MD5.
|
||||
.TP
|
||||
.I "-$ individual | commercial"
|
||||
Add information about the publisher, i.e. if the signature is generated by an
|
||||
individual or a commercial entity.
|
||||
.TP
|
||||
.I "-n description"
|
||||
Add a textual description of the signed file.
|
||||
.TP
|
||||
.I "-i url"
|
||||
Add a URL associated to the publisher or the signed file.
|
||||
.TP
|
||||
.I "-t url"
|
||||
URL to a timestamp service to countersign the PE executable. Countersignature
|
||||
is required if you want the PE executable signature to be valid after the
|
||||
publisher certificate expires. The countersignature proves that the publisher
|
||||
had a valid (non-expired) certificate when the PE executable was signed.
|
||||
.TP
|
||||
.I "-tr #"
|
||||
Number of retries to get a timestamp for the countersignature.
|
||||
.TP
|
||||
.I "-td #"
|
||||
Delay (in seconds) between the retries to get a timestamp for the countersignature.
|
||||
.TP
|
||||
.I "-k name"
|
||||
CryptoAPI key container name (when not using -v).
|
||||
.TP
|
||||
.I "-p name"
|
||||
CryptoAPI provider name (when not using -v).
|
||||
.TP
|
||||
.I "-y #"
|
||||
CryptoAPI provider type (when not using -v or -p).
|
||||
.TP
|
||||
.I "-ky signature | exchange | #"
|
||||
CryptoAPI key type (when not using -v).
|
||||
.TP
|
||||
.I "-r localMachine | currentUser"
|
||||
CryptoAPI key location (when not using -v).
|
||||
.TP
|
||||
.I "-help", "-h", "-?", "/?"
|
||||
Display help about this tool.
|
||||
.SH AUTHOR
|
||||
Written by Sebastien Pouliot
|
||||
.SH COPYRIGHT
|
||||
Copyright (C) 2003 Motus Technologies.
|
||||
Released under BSD license.
|
||||
.SH MAILING LISTS
|
||||
Visit http://mail.ximian.com/mailman/mono-list for details.
|
||||
.SH WEB SITE
|
||||
Visit: http://www.go-mono.com for details
|
||||
.SH SEE ALSO
|
||||
.BR chktrust(1), makecert(1), cert2spc(1)
|
||||
@@ -1,117 +0,0 @@
|
||||
.\"
|
||||
.\" sn manual page.
|
||||
.\" Copyright 2003 Motus Technologies
|
||||
.\" Author:
|
||||
.\" Sebastien Pouliot ([email protected])
|
||||
.\"
|
||||
.TH Mono "sn"
|
||||
.SH NAME
|
||||
sn \- Digitally sign/verify/compare strongname on CLR assemblies.
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
.B sn [-q | -quiet] [options] [parameters]
|
||||
.SH DESCRIPTION
|
||||
Digitally sign, verify or compare, CLR assemblies using strongnames.
|
||||
.SH CONFIGURATION OPTIONS
|
||||
.TP
|
||||
.I "-c provider"
|
||||
Change the default CSP (Crypto Service Provider).
|
||||
.TP
|
||||
.I "-m [y|n]"
|
||||
Use a machine [y] key container or a user [n] key container.
|
||||
.TP
|
||||
.I "-Vl"
|
||||
List the verification options.
|
||||
.TP
|
||||
.I "-Vr assembly [userlist]"
|
||||
Exempt the specified assembly from verification for the specified user list.
|
||||
.TP
|
||||
.I "-Vu assembly"
|
||||
Remove the exemption entry for the specified assembly.
|
||||
.TP
|
||||
.I "-Vx"
|
||||
Remove all exemptions entries.
|
||||
.SH CSP RELATED OPTIONS
|
||||
.TP
|
||||
.I "-d container"
|
||||
Delete the keypair present in the specified key container.
|
||||
.TP
|
||||
.I "-i keypair.snk container"
|
||||
Import the specified strongname file into the specified container.
|
||||
.TP
|
||||
.I "-pc container publickey"
|
||||
Export the public key from the specified CSP container to the specified file.
|
||||
.SH CONVERTION OPTIONS
|
||||
.TP
|
||||
.I "-e assembly output.pub"
|
||||
Export the assembly public key to the specified output file.
|
||||
.TP
|
||||
.I "-p keypair.snk output.pub"
|
||||
Export the public key from the specified strongname key file (SNK) to the
|
||||
specified output file.
|
||||
.TP
|
||||
.I "-o input output.txt"
|
||||
Convert the input file to a CSV file (using decimal).
|
||||
.TP
|
||||
.I "-oh input output.txt"
|
||||
Convert the input file to a CSV file (using hexadecimal).
|
||||
.SH STRONGNAME SIGNING OPTIONS
|
||||
.TP
|
||||
.I "-D assembly1 assembly2"
|
||||
Compare if assembly1 and assembly are the same exception for their signature.
|
||||
This is done by comparing the hash of the metadata of both assembly.
|
||||
.TP
|
||||
.I "-k keypair.snk"
|
||||
Create a new strongname keypair in the specified file.
|
||||
.TP
|
||||
.I "-R assembly keypair.snk"
|
||||
Resign the specified assembly using the specified strongname keypair file
|
||||
(SNK).
|
||||
.TP
|
||||
.I "-Rc assembly container"
|
||||
Resign the specified assembly using the specified strongname container.
|
||||
.TP
|
||||
.I "-t file"
|
||||
Show the public key from the specified file.
|
||||
.TP
|
||||
.I "-tp file"
|
||||
Show the public key and the public key token from the specified file.
|
||||
.TP
|
||||
.I "-T assembly"
|
||||
Show the public key from the specified assembly.
|
||||
.TP
|
||||
.I "-Tp assembly"
|
||||
Show the public key and the public key token from the specified assembly.
|
||||
.TP
|
||||
.I "-V assembly"
|
||||
Verify the specified assembly signature.
|
||||
.TP
|
||||
.I "-Vf assembly"
|
||||
Verify the specified assembly signature (even if disabled).
|
||||
.SH HELP OPTIONS
|
||||
.TP
|
||||
.I "-h", "-?"
|
||||
Display basic help about this tool.
|
||||
.TP
|
||||
.I "-h config", "-? config"
|
||||
Display configuration related help about this tool.
|
||||
.TP
|
||||
.I "-h csp", "-? csp"
|
||||
Display Cryptographic Service Provider related help about this tool.
|
||||
.TP
|
||||
.I "-h convert", "-? convert"
|
||||
Display convertion related help about this tool.
|
||||
.TP
|
||||
.I "-h sn", "-? sn"
|
||||
Display strongname related help about this tool.
|
||||
.SH AUTHOR
|
||||
Written by Sebastien Pouliot
|
||||
.SH COPYRIGHT
|
||||
Copyright (C) 2003 Motus Technologies.
|
||||
Released under BSD license.
|
||||
.SH MAILING LISTS
|
||||
Visit http://mail.ximian.com/mailman/mono-list for details.
|
||||
.SH WEB SITE
|
||||
Visit: http://www.go-mono.com for details
|
||||
.SH SEE ALSO
|
||||
.BR secutil(1)
|
||||
@@ -1,97 +1,3 @@
|
||||
2003-10-28 Jackson Harper <[email protected]>
|
||||
|
||||
* INSTALL.txt: Tell users where to find monocharges, do not
|
||||
reference README.building.
|
||||
|
||||
2003-07-22 Peter Williams <[email protected]>
|
||||
|
||||
* README: INSTALL.txt, not INSTALL.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* nunit20/nunit-console/Makefile (PROGRAM): Put nunit-console.exe
|
||||
in $(topdir)/class/lib so we can find our DLL's.
|
||||
|
||||
2003-07-18 Peter Williams <[email protected]>
|
||||
|
||||
* build/library.make (dist-local): Fancy make dist magic gives
|
||||
way to boring old 'for'.
|
||||
|
||||
* build/executable.make (dist-local): Ditto.
|
||||
|
||||
2003-07-17 Peter Williams <[email protected]>
|
||||
|
||||
* build/profiles/default.make: Actually fix this. Use the platform
|
||||
compiler all the way.
|
||||
|
||||
2003-07-17 Peter Williams <[email protected]>
|
||||
|
||||
* build/profiles/default.make: Try to make this smarter so
|
||||
that we can build on Windows. Specifically, don't require
|
||||
the mono runtime. Combined with the corlib $(BOOT_COMPILE) change,
|
||||
this should make corlib build out of the box, I think.
|
||||
|
||||
2003-07-16 Peter Williams <[email protected]>
|
||||
|
||||
A whole passel of build system changes. Doc updates:
|
||||
|
||||
* build/README.makefiles: Doc updates.
|
||||
|
||||
* build/profiles/net_1_0.make: Doc changes.
|
||||
|
||||
* INSTALL.txt: A few more touchups.
|
||||
|
||||
Better defaults:
|
||||
|
||||
* build/config-default.make (prefix): Default install prefix
|
||||
should be /usr/local.
|
||||
|
||||
* build/profiles/bootstrap.make: This profile ...
|
||||
|
||||
* build/profiles/default.make: ... is now the default.
|
||||
|
||||
* build/profiles/atomic.make: And the default is now this.
|
||||
|
||||
Fixes for pre-build checks:
|
||||
|
||||
* Makefile: Do the platform and (new) profile checks
|
||||
before the build, which took some infrastructure changes.
|
||||
|
||||
* build/rules.make: Allow a Makefile to specify its own all/install/etc
|
||||
targets.
|
||||
|
||||
* build/profiles/default.make (profile-check): Add a blank
|
||||
target here.
|
||||
|
||||
* build/profiles/atomic.make: Check for a full MCS install to
|
||||
build against.
|
||||
|
||||
HP/UX fixes with help from Bernie Solomon:
|
||||
|
||||
* build/config-default.make (ECHO_ESCAPE): HP/UX 'echo'
|
||||
doesn't need a -e parameter to interpret escape codes. Test for
|
||||
that and define a configuration parameter.
|
||||
|
||||
* build/library.make ($(makefrag)): Use $(ECHO_ESCAPE)
|
||||
instead of assuming that 'echo -e' will interpret escape
|
||||
codes.
|
||||
|
||||
* build/executable.make ($(makefrag)): Here too.
|
||||
|
||||
A make distcheck fix:
|
||||
|
||||
* Makefile: Inherit the current prefix so that the build can
|
||||
find the right System.Xml.dll.
|
||||
|
||||
And Windows build fixes with the invaluable help of Sebastian
|
||||
Pouliot (in various subdirectories).
|
||||
|
||||
2003-07-14 Peter Williams <[email protected]>
|
||||
|
||||
* build/rules.make (dist-recursive): Fix recursive rules
|
||||
to work on HP/UX /bin/sh. Patch from Bernie Solomon
|
||||
<[email protected]>.
|
||||
|
||||
2003-05-10 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* makefile:
|
||||
|
||||
+29
-137
@@ -1,161 +1,53 @@
|
||||
Basic Installation
|
||||
==================
|
||||
|
||||
The Mono project has developed mono, a CLI runtime. The build process
|
||||
of each of these depends on nothing more than a C compiler and glib2.
|
||||
The Mono project has developed mono, an x86-specific CL JIT compiler and
|
||||
mint, a portable CLI interpreter. The build process of each of these
|
||||
depends on nothing more than a C compiler, glib2 and libgc.
|
||||
|
||||
However, to provide a working runtime environment, these programs must
|
||||
be supplemented by the class libraries, which are written in C#. This
|
||||
package contains the components written in C#: class libraries,
|
||||
compilers and tools.
|
||||
be supplemented by corlib, a CLR assembly to which they are closely
|
||||
tied. This package provides the C# sources for corlib as well as some
|
||||
additional assemblies and mcs, the Mono C# compiler.
|
||||
|
||||
Build Process for Users.
|
||||
========================
|
||||
To build this package, you must already have a C# compiler installed.
|
||||
Build instructions for *NIX and Microsoft Windows follow.
|
||||
|
||||
If you only want to build a snapshot or a fresh CVS checkout of the
|
||||
sources, you should go into the `mono' sibling directory and issue the
|
||||
following command:
|
||||
Building mcs on *NIX
|
||||
====================
|
||||
|
||||
./autogen --prefix=/usr/local
|
||||
make fullbuild
|
||||
|
||||
That will build and install the code in a single pass. The
|
||||
compilation is bundled with the build due to dependencies on the class
|
||||
libraries on the runtime.
|
||||
|
||||
Build Features for Developers.
|
||||
==============================
|
||||
|
||||
These instructions apply to both Linux and Windows. To build this
|
||||
package, you must already have a C# compiler installed. This means
|
||||
that to build on Linux, you need to get a distribution of the MCS
|
||||
binaries; these are called monocharges. They can be found at
|
||||
www.go-mono.com/daily. On Windows, you can just use the
|
||||
Microsoft compiler. You also need GNU make to build the software (on
|
||||
Windows, you will need for example the Cygwin environment setup).
|
||||
mcs provides a set of makefiles which make it easy to build and install
|
||||
mcs on *NIX systems like Linux or FreeBSD where mcs is already
|
||||
installed.
|
||||
|
||||
To build the compiler and class libraries, run:
|
||||
|
||||
make
|
||||
make -f makefile.gnu
|
||||
|
||||
The libraries will be placed in the directory class/lib/ and the mcs
|
||||
compiler executable in mcs/.
|
||||
|
||||
To install them, run the following:
|
||||
To install them, run the following, where prefix identifies where you
|
||||
want the files installed:
|
||||
|
||||
make install
|
||||
|
||||
The default prefix is /usr/local. To change this configuration option type:
|
||||
|
||||
echo prefix=/your-prefix >> build/config.make
|
||||
|
||||
If you get "corlib out of sync" errors, try
|
||||
|
||||
make PROFILE="atomic"
|
||||
|
||||
The difference between the two modes is explained farther down.
|
||||
|
||||
Troubleshooting
|
||||
===============
|
||||
|
||||
Occasionally, something in the compiler or runtime changes enough that
|
||||
an existing installation cannot complete a full build from cvs. In this case,
|
||||
go to http://go-mono.com/daily and download a monocharge or monolite tarball.
|
||||
Unpack and copy the .dlls to $prefix/lib and .exes to $prefix/bin/. Then
|
||||
you should be able to complete the build normally (i.e. using make fullbuild).
|
||||
|
||||
wget http://go-mono.com/daily/monolite-20031028.tar.gz
|
||||
tar -zxvf monolite-20031028.tar.gz
|
||||
cd monolite-20031028
|
||||
cp *.exe /usr/local/bin/.
|
||||
cp *.dll /usr/local/lib/.
|
||||
|
||||
Monocharges
|
||||
===========
|
||||
make -f makefile.gnu install prefix=/usr/local
|
||||
|
||||
If you are tracking Mono's development, you may sometimes need to share
|
||||
the compiled libraries with others, you can do:
|
||||
the compiled libraries with others. If you want to produce an easily
|
||||
distributable tarball, run:
|
||||
|
||||
make monocharge
|
||||
make -f makefile.gnu dist
|
||||
|
||||
Or a light version, which contains only the essential libraries and
|
||||
results in a much smaller file:
|
||||
Building mcs on Windows
|
||||
=======================
|
||||
|
||||
make monocharge-lite
|
||||
It is also possible to build mcs on Windows using the Microsoft .NET
|
||||
framework. This may be convenient if you do not have access to a working
|
||||
mcs setup. To build the compiler and class libraries, run:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
make
|
||||
|
||||
If you want to change the configuration options for the build process,
|
||||
place your configuration options in build/config.make
|
||||
The libraries will be placed in the directory class/lib/ and the mcs
|
||||
compiler executable in mcs/. They can then be copied to /usr/lib and
|
||||
/usr/bin or wherever desired on the target system.
|
||||
|
||||
A list of variables that control the build are listed in the file
|
||||
build/config-default.make.
|
||||
|
||||
Build profiles? What?
|
||||
======================
|
||||
|
||||
Don't worry about them too much. If you're wondering which to use:
|
||||
use the default if you can (that's why it's the default!) and use
|
||||
the atomic if you have to.
|
||||
|
||||
The default profile uses the C# compiler and class libaries as they
|
||||
are built. This lets you build MCS without needing to have already
|
||||
installed it, but can fail if the libraries change significantly.
|
||||
(This is the source of the dreaded "corlib out of sync" warning, most
|
||||
of the time.)
|
||||
|
||||
The atomic profile tries to use the system compiler and preexisting
|
||||
MCS libraries. New libaries are built against this constant reference
|
||||
point, so if a newly built library has a binary incompatibility, the
|
||||
rest of your build can proceed.
|
||||
|
||||
If you want to always use the atomic profile, run this command:
|
||||
|
||||
echo PROFILE=atomic >> build/config.make
|
||||
|
||||
More About the Build System
|
||||
===========================
|
||||
|
||||
More information is found in build/README.*. Here's a quick rundown
|
||||
of the features:
|
||||
|
||||
* Unified build system for Windows and Linux. Windows is still
|
||||
fairly untested, but "should work." Unfortunately I don't
|
||||
have a Windows machine to test on, but Gonzalo can get
|
||||
corlib to build I think and that's about as complicated as
|
||||
it gets.
|
||||
|
||||
* Profile support. 'make PROFILE=profilename' or 'export
|
||||
PROFILE=profilename ; make' will work. Profiles are defined
|
||||
in build/profiles/profilename.make ; right now there isn't
|
||||
too much going on. The 'bootstrap' profile will build the
|
||||
way makefile.gnu did on Linux, by setting MONO_PATH and
|
||||
using mcs/mcs.exe; the default profile will build against
|
||||
the existing system libraries and compile with 'mcs', which
|
||||
should reduce a lot of 'corlib out of sync' warnings.
|
||||
|
||||
* Important variables are shared among makefiles now; you can
|
||||
edit build/config.make (see build/config-default.make for a
|
||||
template) and give global settings, or just have a much
|
||||
saner time of writing new makefiles.
|
||||
|
||||
* Response files, stamps, and other build trivia now all land
|
||||
in build/deps/, making the library build directories
|
||||
cleaner.
|
||||
|
||||
* Test libraries now live in class/Library/Library_test.dll,
|
||||
not class/Library/Test. 'make test' will build the test DLL,
|
||||
'make run-test' will actually run the nunit tests. Set the
|
||||
variable TEST_HARNESS to run with a program other than
|
||||
nunit-console (for example, nunit-gtk).
|
||||
|
||||
* Standardized recursive targets: all, clean, install, test,
|
||||
run-test. Read build/README.makefiles for definitions of
|
||||
what they should do
|
||||
|
||||
* (Relatively) sane 'make dist' target; 'make distcheck'
|
||||
support; cute 'make monocharge' and 'make monocharge-lite'
|
||||
targets. They're made possible because 'make install' now
|
||||
supports DESTDIR a la automake, which I'm sure someone cares
|
||||
about.
|
||||
-108
@@ -1,108 +0,0 @@
|
||||
thisdir := .
|
||||
SUBDIRS := build jay mcs class mbas nunit20 monoresgen ilasm tools tests errors docs
|
||||
OVERRIDE_BARE_TARGETS = hells yeah
|
||||
include build/rules.make
|
||||
|
||||
# Define these ourselves to that the platform checks come first
|
||||
|
||||
all: platform-check profile-check all-recursive #all-local
|
||||
|
||||
install: platform-check profile-check install-recursive #install-local
|
||||
|
||||
uninstall: platform-check profile-check uninstall-recursive #uninstall-local
|
||||
|
||||
test: platform-check profile-check test-recursive #test-local
|
||||
|
||||
run-test: run-test-recursive #run-test-local
|
||||
|
||||
clean: clean-recursive #clean-local
|
||||
|
||||
# fun specialty targets
|
||||
|
||||
testcorlib:
|
||||
@cd class/corlib && $(MAKE) test run-test
|
||||
|
||||
# Disting. We need to override $(distdir) here.
|
||||
|
||||
package := mcs-$(VERSION)
|
||||
top_distdir = $(dots)/$(package)
|
||||
distdir = $(top_distdir)
|
||||
export package
|
||||
|
||||
DISTFILES = \
|
||||
AUTHORS \
|
||||
ChangeLog \
|
||||
COPYING \
|
||||
COPYING.LIB \
|
||||
INSTALL.txt \
|
||||
LICENSE \
|
||||
LICENSE.GPL \
|
||||
LICENSE.LGPL \
|
||||
Makefile \
|
||||
mkinstalldirs \
|
||||
MIT.X11 \
|
||||
MonoIcon.png \
|
||||
README \
|
||||
ScalableMonoIcon.svg \
|
||||
winexe.in
|
||||
|
||||
dist-pre:
|
||||
rm -rf $(package)
|
||||
|
||||
dist-post:
|
||||
tar cvzf $(package).tar.gz $(package)
|
||||
|
||||
dist-local: dist-default
|
||||
|
||||
dist-tarball: dist-pre dist-recursive dist-post
|
||||
|
||||
dist: dist-tarball
|
||||
rm -rf $(package)
|
||||
|
||||
# the egrep -v is kind of a hack (to get rid of the makefrags)
|
||||
# but otherwise we have to make dist then make clean which
|
||||
# is sort of not kosher. And it breaks with DIST_ONLY_SUBDIRS.
|
||||
#
|
||||
# We need to set prefix on make so class/System/Makefile can find
|
||||
# the installed System.Xml to build properly
|
||||
|
||||
distcheck:
|
||||
rm -rf InstallTest Distcheck-MCS ; \
|
||||
mkdir InstallTest ; \
|
||||
destdir=`cd InstallTest && pwd` ; \
|
||||
$(MAKE) dist-tarball || exit 1 ; \
|
||||
mv $(package) Distcheck-MCS ; \
|
||||
(cd Distcheck-MCS && \
|
||||
$(MAKE) prefix=$(prefix) && $(MAKE) test && $(MAKE) install DESTDIR="$$destdir" && \
|
||||
$(MAKE) clean && $(MAKE) dist || exit 1) || exit 1 ; \
|
||||
mv Distcheck-MCS $(package) ; \
|
||||
tar tzf $(package)/$(package).tar.gz |sed -e 's,/$$,,' |sort >distdist.list ; \
|
||||
rm $(package)/$(package).tar.gz ; \
|
||||
tar tzf $(package).tar.gz |sed -e 's,/$$,,' |sort >before.list ; \
|
||||
find $(package) |egrep -v '(makefrag|response)' |sed -e 's,/$$,,' |sort >after.list ; \
|
||||
cmp before.list after.list || exit 1 ; \
|
||||
cmp before.list distdist.list || exit 1 ; \
|
||||
rm -f before.list after.list distdist.list ; \
|
||||
rm -rf $(package) InstallTest
|
||||
|
||||
monocharge:
|
||||
chargedir=monocharge-`date -u +%Y%m%d` ; \
|
||||
mkdir "$$chargedir" ; \
|
||||
DESTDIR=`cd "$$chargedir" && pwd` ; \
|
||||
$(MAKE) install DESTDIR="$$DESTDIR" || exit 1 ; \
|
||||
tar cvzf "$$chargedir".tgz "$$chargedir" ; \
|
||||
rm -rf "$$chargedir"
|
||||
|
||||
# A bare-bones monocharge.
|
||||
|
||||
monocharge-lite:
|
||||
chargedir=monocharge-lite-`date -u +%Y%m%d` ; \
|
||||
mkdir "$$chargedir" ; \
|
||||
DESTDIR=`cd "$$chargedir" && pwd` ; \
|
||||
$(MAKE) -C mcs install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
$(MAKE) -C class/corlib install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
$(MAKE) -C class/System install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
$(MAKE) -C class/System.XML install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
$(MAKE) -C class/Mono.CSharp.Debugger install DESTDIR="$$DESTDIR" || exit 1; \
|
||||
tar cvzf "$$chargedir".tgz "$$chargedir" ; \
|
||||
rm -rf "$$chargedir"
|
||||
+2
-1
@@ -1,7 +1,8 @@
|
||||
|
||||
This contains the Mono C# compiler as well as the Mono runtime
|
||||
library.
|
||||
|
||||
See INSTALL.txt for a guide to building and installing mcs.
|
||||
See INSTALL for a guide to building and installing mcs.
|
||||
|
||||
Layout:
|
||||
|
||||
|
||||
@@ -0,0 +1,33 @@
|
||||
|
||||
[1] Building mono + mcs from CVS on *NIX. The Easy Way (tm)
|
||||
-------------------------------------------------------------
|
||||
1. Get mono and mcs from CVS (http://www.go-mono.com/download.html)
|
||||
|
||||
2. Use the script to build mono (mono/doc/mono-build.sh).
|
||||
|
||||
3. Copy the dlls and mcs.exe from the latest monocharge tarball
|
||||
(http://www.gnome-db.org/~gonzalo/mono/) to /where/you/installed/mono/lib and
|
||||
..../bin respectively.
|
||||
|
||||
|
||||
|
||||
[2] Keeping the stuff up to date
|
||||
----------------------------------
|
||||
Once you have followed the above steps, do these ones to keep your installation
|
||||
up to date:
|
||||
|
||||
1. In mcs directory,
|
||||
|
||||
cvs -z3 update -Pd
|
||||
make -f makefile.gnu
|
||||
|
||||
2. Use the mono-build.sh script to update, rebuild and install mono from CVS.
|
||||
Doing a cvs update of mono/doc/mono-build.sh file is also a good idea.
|
||||
|
||||
3. In mcs directory:
|
||||
|
||||
make -f makefile.gnu install prefix=/prefix/of/your/installation/path
|
||||
|
||||
4. In case of troubles (ie, unable to compile mcs/* sources) go to [1].
|
||||
|
||||
-Gonzalo
|
||||
@@ -1,2 +0,0 @@
|
||||
pre-config.make
|
||||
config.make
|
||||
@@ -1,93 +0,0 @@
|
||||
2003-11-12 Jackson Harper <[email protected]>
|
||||
|
||||
* rules.make:
|
||||
* platforms/linux.make: corlib name is now mscorlib.
|
||||
|
||||
2003-11-09 Ben Maurer <[email protected]>
|
||||
|
||||
* profiles/generics.make: add the -2 flag.
|
||||
|
||||
2003-10-28 Jackson Harper <[email protected]>
|
||||
|
||||
* platforms/linux.make: Tell users to read INSTALL.txt not the
|
||||
non-existant README.building.
|
||||
|
||||
2003-10-22 Dick Porter <[email protected]>
|
||||
|
||||
* platforms/win32.make:
|
||||
* platforms/linux.make:
|
||||
* rules.make: Added RESGEN platform-specific tool.
|
||||
|
||||
2003-08-03 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* config-default.make: the /nowarn arguments are now set on a per
|
||||
library basis.
|
||||
|
||||
2003-07-29 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* executable.make: install-local depends on the program too.
|
||||
|
||||
2003-07-25 Peter Williams <[email protected]>
|
||||
|
||||
* rules.make (run-test): Make it depend on 'test-local'
|
||||
then 'run-test-local' after 'run-test-recursive'. This way,
|
||||
'make run-test' from the toplevel doesn't recurse through all
|
||||
the directories doing a make test before we run anything.
|
||||
|
||||
2003-07-24 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* rules.make: run-test depends now on 'test'.
|
||||
|
||||
2003-07-24 Gonzalo Paniagua Javier <[email protected]>
|
||||
|
||||
* rules.make: set corlib to PLATFORM_CORLIB if this is defined.
|
||||
|
||||
2003-07-22 Peter Williams <[email protected]>
|
||||
|
||||
* rules.make (withmcs): Add this developer utility target.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* README.platforms: Update docs for changes below.
|
||||
|
||||
* platforms/win32.make (PLATFORM_CORLIB): Set this variable
|
||||
to 'mscorlib.dll', instead of $(corlib) which everything links
|
||||
against. *Almost* everything should link against our corlib --
|
||||
with the exception of corlib_cmp and corlib_res.
|
||||
|
||||
* platforms/linux.make: Same here: corlib.dll
|
||||
|
||||
* rules.make: Define $(corlib) here.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* config-default.make (TEST_RUNTIME): Use the platform runtime
|
||||
to run tests, by default.
|
||||
|
||||
* profiles/default.make (TEST_RUNTIME): If our test runtime is
|
||||
mono, use the --debug flag.
|
||||
|
||||
* executable.make (sourcefile): Add a basename so that we can
|
||||
find the nunit sources and so we behave a bit more like
|
||||
library.make
|
||||
|
||||
* config-default.make (TEST_HARNESS): Find nunit-console in its
|
||||
new home.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* library.make ($(response)): Do a "Creating ..." line here.
|
||||
|
||||
* executable.make ($(response)): Same.
|
||||
|
||||
* config-default.make: Make warning more forceful.
|
||||
|
||||
* rules.make: Define a useful 'PLATFORM_MONO_NATIVE' that is
|
||||
set if the platform does not have a native runtime (ie, linux).
|
||||
Also reorder some definitions.
|
||||
|
||||
2003-07-20 Peter Williams <[email protected]>
|
||||
|
||||
* Created. See ../ChangeLog for entries earlier than
|
||||
this.
|
||||
|
||||
@@ -1,22 +0,0 @@
|
||||
thisdir = build
|
||||
SUBDIRS =
|
||||
include ../build/rules.make
|
||||
|
||||
all-local install-local test-local run-test-local clean-local uninstall-local:
|
||||
|
||||
DISTFILES = \
|
||||
README.makefiles \
|
||||
README.platforms \
|
||||
README.configury \
|
||||
config-default.make \
|
||||
executable.make \
|
||||
library.make \
|
||||
rules.make \
|
||||
platforms/linux.make \
|
||||
platforms/win32.make \
|
||||
profiles/default.make \
|
||||
profiles/atomic.make \
|
||||
profiles/net_1_0.make
|
||||
|
||||
dist-local: dist-default
|
||||
mkdir $(distdir)/deps
|
||||
@@ -1,23 +0,0 @@
|
||||
Configuring the build (-*- outline -*-)
|
||||
Peter Williams <[email protected]>
|
||||
|
||||
** Configuring the build
|
||||
|
||||
It's pretty easy. You can create two files in this directory to tweak
|
||||
settings: pre-config.make and config.make.
|
||||
|
||||
pre-config.make is included before $(PLATFORM).make and
|
||||
$(PROFILE).make, so you can set either of these variables if you want
|
||||
to change the default.
|
||||
|
||||
Just about any other change should go in config.make, which is
|
||||
included after $(PLATFORM).make and $(PROFILE).make, so you can use
|
||||
the values defined in those files if you wish. For example,
|
||||
|
||||
MCS_FLAGS = $(DEFAULT_MCS_FLAGS) /my-experimental-optimizer-flag
|
||||
|
||||
or something.
|
||||
|
||||
(You shouldn't need to edit any of the existing Makefiles for
|
||||
site-specific hacks. CVS would complain at you and `make dist'
|
||||
wouldn't be happy.)
|
||||
@@ -1,736 +0,0 @@
|
||||
The MCS makefiles (-*- outline -*-)
|
||||
Peter Williams <[email protected]>
|
||||
|
||||
The new makefiles try to abstract building on Windows and Linux. They
|
||||
try to provide a consistent set of ways to express the things that our
|
||||
build system needs to let us do, specifically:
|
||||
|
||||
* Build recursively
|
||||
* Build libraries and executables easily
|
||||
* Let developers use different runtimes and class libaries
|
||||
* Make distributions easily
|
||||
* Provide a framework for testing
|
||||
* Build platform-independently whenever possible
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Makefile structure
|
||||
|
||||
A general makefile looks like this:
|
||||
|
||||
========================================
|
||||
thisdir = class/Mono.My.Library
|
||||
SUBDIRS =
|
||||
include ../../build/rules.make
|
||||
|
||||
all-local:
|
||||
do some stuff
|
||||
|
||||
install-local:
|
||||
$(MKINSTALLDIRS) $(DESTDIR)$(prefix)/share/
|
||||
$(INSTALL_DATA) myfile.txt $(DESTDIR)$(prefix)/share/myfiledir
|
||||
|
||||
clean-local:
|
||||
rm -f my-generated-file
|
||||
|
||||
test-local: my_test_program.exe
|
||||
|
||||
run-test-local:
|
||||
$(RUNTIME) my_test_program.exe
|
||||
|
||||
DISTFILES = myfile.txt my_test_source.cs
|
||||
|
||||
dist-local: dist-default
|
||||
|
||||
my_test_program.exe: my_test_source.cs
|
||||
$(CSCOMPILE) /target:exe /out:$@ $<
|
||||
========================================
|
||||
|
||||
Each makefile follows the same pattern: it does some setup, includes
|
||||
the standard make rules, and provides rules for six standard targets:
|
||||
all, install, test, run-test, clean, and dist.
|
||||
|
||||
"Some setup" is defining two variables: $(thisdir) and
|
||||
$(SUBDIRS). $(thisdir) is the directory that the makefile lives in,
|
||||
relative to the top directory (ie, class/corlib) and $(SUBDIRS)
|
||||
defines the subdirectories that should be built in.
|
||||
|
||||
The six targets do the following:
|
||||
|
||||
* all-local builds whatever someone would expect to be built
|
||||
when they just type 'make'. Most likely Foo.dll or Foo.exe
|
||||
|
||||
* install-local installs whatever got built by all-local.
|
||||
|
||||
* test-local _builds_ the test programs or libraries but does
|
||||
_not_ run them.
|
||||
|
||||
* run-test-local actually runs the tests. It shouldn't
|
||||
necessarily exit in an error if the test fails, but should make that
|
||||
situation obvious. It should only run tests that take care of
|
||||
themselves automatically; interactive tests should have an individual
|
||||
target. The idea is that 'make run-test' from the toplevel should be
|
||||
able to proceed unsupervised and test everything that can be tested in
|
||||
such a manner.
|
||||
|
||||
* clean-local removes built files; 'make clean' should leave
|
||||
only files that go into a distribution tarball. (But it is not necessarily
|
||||
true that all files that go into a tarball need to be left after a make clean.)
|
||||
|
||||
* dist-local copies files into the distribution tree, which is
|
||||
given by the variable $(distdir). dist-local always depends on the
|
||||
target 'dist-default'. See ** 'make dist' below.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Build configuration
|
||||
|
||||
In general, MCS needs to be able to build relying only on the
|
||||
existence of a runtime and core libraries (corlib, System,
|
||||
System.Xml). So there shouldn't be any checking for libraries or
|
||||
whatnot; MCS should be able to build out of the box. We try to keep
|
||||
platform detection and feature testing (ie, for HP/UX echo) inside
|
||||
the makefiles; right now, there's no configuration script, and it'd
|
||||
be nice to keep it that way. (I am told that some people build on
|
||||
both Windows and Linux in the same tree, which would be impossible to
|
||||
do if we cached platform-related configury values.)
|
||||
|
||||
That being said, it's very convenient for developers to be able to
|
||||
customize their builds to suit their needs. To allow this, the
|
||||
Makefile rules are set up to allow people to override pretty much any
|
||||
important variable.
|
||||
|
||||
Configuration variables are given defaults in `config-default.make';
|
||||
`rules.make' optionally includes `$(topdir)/build/config.make', so you
|
||||
can customize your build without CVS trying to commit your modified
|
||||
`config-default.make' all the time. Platform-specific variables are
|
||||
defined in `$(topdir)/build/platforms/$(PLATFORM).make', where
|
||||
$(PLATFORM) is detected in config-default.make. (Currently, the only
|
||||
choices are linux.make and win32.make.)
|
||||
|
||||
The best way to learn what the configuration variables are is to read
|
||||
`config.make' and `platform.make'. There aren't too many and hopefully
|
||||
they should be self-explanatory; see the numerous examples below for
|
||||
more information if you're confused.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Recommendations for platform specifics
|
||||
|
||||
If you find yourself needing a platform-specific customization, try
|
||||
and express it in terms of a feature, rather than a platform test. In
|
||||
other words, this is good:
|
||||
|
||||
========================================
|
||||
run-test-local: my-test.exe
|
||||
ifdef PLATFORM_NEEDS_CRAZY_CRAP
|
||||
crazy-crap
|
||||
endif
|
||||
$(RUNTIME) my-test.exe
|
||||
========================================
|
||||
|
||||
and this is bad:
|
||||
|
||||
========================================
|
||||
run-test-local: my-test.exe
|
||||
ifdef WINDOWS
|
||||
crazy-crap
|
||||
else
|
||||
ifdef AMIGA
|
||||
crazy-crap
|
||||
endif
|
||||
endif
|
||||
$(RUNTIME) my-test.exe
|
||||
========================================
|
||||
|
||||
The latter accumulates and gets unpleasant and it sucks. Granted,
|
||||
right now we only have two platforms, so it's not a big deal, but it's
|
||||
good form to get used to and practice. Anyway, take a look at how we
|
||||
do the various corlib building hacks for examples of how we've done
|
||||
platform-specificity. It certainly isn't pretty, but at least it's a
|
||||
little structured.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Saving effort
|
||||
|
||||
The point of the build system is to abstract things and take
|
||||
care of all the easy stuff. So if you find yourself writing a
|
||||
Makefile, know that there's probably already infrastructure to do what
|
||||
you want. Here are all the common cases I can think of ...
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Compiling C# code? use:
|
||||
|
||||
========================================
|
||||
my-program.exe: my-source.cs
|
||||
$(CSCOMPILE) /target:exe /out:$@ $^
|
||||
========================================
|
||||
|
||||
or
|
||||
|
||||
========================================
|
||||
my-lib.dll: my-source.cs
|
||||
$(CSCOMPILE) /target:library /out:$@ $^
|
||||
========================================
|
||||
|
||||
Note the '$@' and '$^' variables. The former means "the name of the
|
||||
file that I am trying to make" and the latter means "all the
|
||||
dependencies of the file I am trying to make." USE THESE VARIABLES
|
||||
AGGRESSIVELY. Say that you add a new source to your program:
|
||||
|
||||
========================================
|
||||
my-program.exe: my-source.cs my-new-source.cs
|
||||
$(CSCOMPILE) /target:exe /out:$@ $^
|
||||
========================================
|
||||
|
||||
Because of the $^ variable, you don't need to remember to add another
|
||||
file to the command line. Similarly, if you rename your program, you
|
||||
won't need to remember to change the rule:
|
||||
|
||||
========================================
|
||||
MonoVaporizer.exe: my-source.cs my-new-source.cs
|
||||
$(CSCOMPILE) /target:exe /out:$@ $^
|
||||
========================================
|
||||
|
||||
will still work. Another useful variable is $<, which means "the first
|
||||
dependency of whatever I'm building." If you order your dependencies
|
||||
carefully it can be extremely useful.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Just building an executable? use:
|
||||
|
||||
========================================
|
||||
PROGRAM = myprogram.exe
|
||||
LOCAL_MCS_FLAGS = /r:System.Xml.dll
|
||||
|
||||
include ../build/executable.make
|
||||
========================================
|
||||
|
||||
executable.make builds a program in the current directory. Its name is
|
||||
held in $(PROGRAM), and its sources are listed in the file
|
||||
$(PROGRAM).sources. It might seem to make more sense to just list the
|
||||
program's sources in the Makefile, but when we build on Windows we
|
||||
need to change slashes around, which is much easier to do if the
|
||||
sources are listed in a file. The variable $(LOCAL_MCS_FLAGS) changes
|
||||
the flags given to the compiler; it is included in $(CSCOMPILE) so you
|
||||
don't need to worry about it.
|
||||
|
||||
executable.make does a lot for you: it builds the program in 'make
|
||||
all-local', installs the program in $(prefix)/bin, distributes the
|
||||
sources, and defines empty test targets. Now, if your program has a
|
||||
test, set the variable HAS_TEST:
|
||||
|
||||
========================================
|
||||
PROGRAM = myprogram.exe
|
||||
LOCAL_MCS_FLAGS = /r:System.Xml.dll
|
||||
HAS_TEST = yes
|
||||
include ../build/executable.make
|
||||
|
||||
test-local: mytester.exe
|
||||
|
||||
run-test-local: mytester.exe
|
||||
$(RUNTIME) $<
|
||||
|
||||
mytester.exe: mytester.cs
|
||||
$(CSCOMPILE) /target:exe /out:$@ mytester.cs
|
||||
========================================
|
||||
|
||||
If your program has 'built sources', that is, source files generated
|
||||
from other files (say, generated by jay), define a variable called
|
||||
BUILT_SOURCES and do *not* list the sources in $(PROGRAM).sources:
|
||||
|
||||
========================================
|
||||
PROGRAM = myprogram.exe
|
||||
LOCAL_MCS_FLAGS = /r:System.Xml.dll
|
||||
BUILT_SOURCES = parser.cs
|
||||
CLEAN_FILES = y.output
|
||||
|
||||
include ../build/executable.make
|
||||
|
||||
parser.cs: parser.jay
|
||||
$(topdir)/jay/jay $< > $@
|
||||
========================================
|
||||
|
||||
executable.make will automatically delete the $(BUILT_SOURCES) files
|
||||
on 'make clean'. Since this situation is a common occurrence and jay
|
||||
happens to leave behind y.output files, you can also define a variable
|
||||
called $(CLEAN_FILES) that lists extra files to be deleted when 'make clean' is
|
||||
called. (That's in addition to your executable and the built sources).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Buildling a library? Use
|
||||
|
||||
========================================
|
||||
LIBRARY = Mono.MyLib.dll
|
||||
LIB_MCS_FLAGS = /unsafe
|
||||
TEST_MCS_FLAGS = /r:System.Xml.dll
|
||||
|
||||
include ../../build/library.make
|
||||
========================================
|
||||
|
||||
Where you library is called $(LIBRARY); it will be put into
|
||||
$(topdir)/class/lib. LIB_MCS_FLAGS is the set of MCS flags to use when
|
||||
compiling the library; in addition, a global set of flags called
|
||||
$(LIBRARY_FLAGS) is added (that variable is defined in
|
||||
config-defaults.make), as well as the usual $(LOCAL_MCS_FLAGS).
|
||||
|
||||
As in executable.make, the sources for your library are listed in
|
||||
$(LIBRARY).sources. Note: these source lists should have Unix forward
|
||||
slashes and Unix newlines (\n, not \r\n.) If you get an error about
|
||||
"touch: need a filename", that means your .sources file doesn't end in
|
||||
a newline. It should.
|
||||
|
||||
Now library.make also assumes that your library has an NUnit2 test
|
||||
harness. The files should be in a subdirectory called Test/, and if
|
||||
your library is called Mono.Foo.dll, they should be listed in
|
||||
Mono.Foo_test.dll.sources. The names in that files should *not* have
|
||||
the Test/ prefix. 'make test' will build Mono.Foo_test.dll in the
|
||||
current directory, automatically supplying the flags to reference the
|
||||
original library and NUnit.Framework.dll.
|
||||
|
||||
If you don't have a test, just do this:
|
||||
|
||||
========================================
|
||||
LIBRARY = Mono.MyLib.dll
|
||||
LIB_MCS_FLAGS = /unsafe
|
||||
NO_TEST = yes
|
||||
|
||||
include ../../build/library.make
|
||||
========================================
|
||||
|
||||
and feel ashamed. Every good library has a test suite!
|
||||
|
||||
Extra flags needed to compile the test library should be listed in
|
||||
$(TEST_MCS_FLAGS); often you will have a line like this:
|
||||
|
||||
========================================
|
||||
TEST_MCS_FLAGS = $(LIB_MCS_FLAGS)
|
||||
========================================
|
||||
|
||||
Again, library.make does a lot for you: it builds the dll, it
|
||||
generates makefile fragments to track the dependencies, it installs
|
||||
the library, it builds the test dll on 'make test', it runs
|
||||
$(TEST_HARNESS) on it on 'make run-test', it removes the appropriate
|
||||
files on 'make clean', and it distributes all the source files on
|
||||
'make dist'. (TEST_HARNESS defaults to be nunit-console.exe but it may
|
||||
be overridden to, say, nunit-gtk). If you have extra files to
|
||||
distribute when using either library.make or executable.make, use the
|
||||
variable $(EXTRA_DISTFILES):
|
||||
|
||||
========================================
|
||||
EXTRA_DISTFILES = \
|
||||
Test/testcase1.in \
|
||||
Test/testcase1.out \
|
||||
README
|
||||
========================================
|
||||
|
||||
Again, library.make and executable.make do the right things so that we
|
||||
can build on Windows, doing some trickery to invert slashes and
|
||||
overcome command-line length limitations. Use them unless you have a
|
||||
really good reason not to. If you're building a bunch of small
|
||||
executables, check out tools/Makefile or tools/security/Makefile; if
|
||||
all the files are in the current directory, changing slashes isn't a
|
||||
big deal, and command-line lengths won't be a problem, so
|
||||
executable.make isn't necessary (and indeed it won't work, since it
|
||||
can only build one .exe in a directory).
|
||||
|
||||
If you're building a library, library.make is highly recommended; the
|
||||
only DLL that doesn't use it is corlib, because building corlib is a
|
||||
fair bit more complicated than it should be. Oh well.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Running a C# program? Use $(RUNTIME)
|
||||
|
||||
========================================
|
||||
run-test-local: myprog.exe
|
||||
$(RUNTIME) myprog.exe
|
||||
========================================
|
||||
|
||||
$(RUNTIME) might be empty (if you're on windows), so don't expect to
|
||||
be able to give it any arguments. If you're on a platform which has an
|
||||
interpreter or jitter, $(RUNTIME_FLAGS) is included in $(RUNTIME), so
|
||||
set that variable.
|
||||
|
||||
$(TEST_RUNTIME) is the runtime to use when running tests. Right now it's
|
||||
just "mono --debug".
|
||||
|
||||
|
||||
|
||||
* Calling the compiler directly? Use $(MCS).
|
||||
|
||||
Really, you should use $(CSCOMPILE) whenever possible, but $(MCS) is
|
||||
out there. $(BOOTSTRAP_MCS) is the C# compiler that we use to build
|
||||
mcs.exe; on Linux, we then use mcs.exe to build everything else, but
|
||||
on Windows, we use csc.exe to build everything. Only use
|
||||
$(BOOTSTRAP_MCS) if you know what you're doing.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Compiling C code? Use $(CCOMPILE)
|
||||
|
||||
To give it flags, set $(LOCAL_CFLAGS). As with compiling C#, the
|
||||
variable $(CFLAGS) will automatically be included on the command line.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Installing files? Use $(MKINSTALLDIRS), $(INSTALL_DATA) or
|
||||
$(INSTALL_BIN), $(prefix), and $(DESTDIR).
|
||||
|
||||
Every time a file is installed the commands should look like this:
|
||||
|
||||
========================================
|
||||
install-local:
|
||||
$(MKINSTALLDIRS) $(DESTDIR)$(prefix)/my/dir
|
||||
$(INSTALL_DATA) myfile $(DESTDIR)$(prefix)/my/dir
|
||||
========================================
|
||||
|
||||
This way the directory is created recursively if needed (admittedly, we could
|
||||
probably rely on mkdir -p), the file is given the correct permissions,
|
||||
the user can override $(MKINSTALLDIRS) and $(INSTALL) if they need to,
|
||||
and we can support $(DESTDIR) installs. We use $(DESTDIR) to make
|
||||
monocharge tarballs, and it's useful otherwise, so try and use it
|
||||
consistently.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* 'make dist'? Use $(DISTFILES)
|
||||
|
||||
The 'dist-default' target will copy the files listed in $(DISTFILES)
|
||||
into the distribution directory, as well as Makefile and ChangeLog if
|
||||
they exist. This is almost always all that you need, so ideally your
|
||||
make dist support should only be:
|
||||
|
||||
========================================
|
||||
DISTFILES = README Test/thoughts.txt
|
||||
|
||||
dist-local: dist-default
|
||||
========================================
|
||||
|
||||
DISTFILES will cope correctly with files in subdirectories, by the
|
||||
way. Note that if you put a nonexistant file or a directory in
|
||||
DISTFILES it will *not* complain; it will just ignore it.
|
||||
|
||||
If you want to test your 'make dist' code, you can try
|
||||
|
||||
========================================
|
||||
$ cd class/Mono.MyClass
|
||||
$ make dist-local distdir=TEST
|
||||
========================================
|
||||
|
||||
And your files should be copied into TEST/ in the current directory.
|
||||
There is a toplevel 'make distcheck' target, which will build a dist
|
||||
tarball, try to build it, install files to a temporary prefix, make
|
||||
clean it, make a distribution, and compare the files left over to the
|
||||
files originally in the tarball: they should be the same. But this
|
||||
takes about 15 minutes to run on my 1.1 Ghz computer, so it's not for
|
||||
the faint of heart.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Lots of files? Use $(wildcard *.foo)
|
||||
|
||||
When specifying the sources to a library or executable, wildcards are
|
||||
not encouraged; in fact they're not allowed if you use library.make or
|
||||
executable.make. But there are times when they're useful, eg:
|
||||
|
||||
========================================
|
||||
DISTFILES = $(wildcard Test/*.in) $(wildcard Test/*.out)
|
||||
========================================
|
||||
|
||||
Just so you know that 'make' has this feature.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Referencing files in other directories? Use $(topdir).
|
||||
|
||||
$(topdir) is the path to the top directory from the current build
|
||||
directory. Basically it's a sequence of ../.. computed from the value
|
||||
that you give $(thisdir) at the top of your Makefile. Try to reference
|
||||
things from $(topdir), so your code can be moved or cut-and-pasted
|
||||
around with a minimum of fuss.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* Conditional building? Use ifdef/ifndef/endif
|
||||
|
||||
Now in general we want to avoid conditional building, but sometimes
|
||||
something doesn't work on Linux or already exists on Windows or
|
||||
whatnot. (See below on recommended form for how to build
|
||||
platform-specifically.) GNU Make supports the following construction:
|
||||
|
||||
========================================
|
||||
BUILD_EXPERIMENTAL = yes
|
||||
|
||||
ifdef BUILD_EXPERIMENTAL
|
||||
experimental_stuff = my-experiment.exe
|
||||
else
|
||||
experimental_stuff =
|
||||
endif
|
||||
|
||||
all-local: my-sane.exe $(experimental_stuff)
|
||||
========================================
|
||||
|
||||
'ifdef' means 'if the variable is set to nonempty', so you could have
|
||||
|
||||
========================================
|
||||
BUILD_EXPERIMENTAL = colorless green ideas sleep furiously
|
||||
========================================
|
||||
|
||||
and Make would be happy. I hope that the meaning of 'ifndef' should be
|
||||
obvious. If you want to only sometimes build a target, the above
|
||||
construction is the recommended way to go about it; it's nice to have
|
||||
the rules exist in a Makefile even if they aren't invoked.
|
||||
|
||||
If you want to see why conditionals aren't nice, take a look at
|
||||
library.make or class/corlib/Makefile.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
* 'Private' directories that shouldn't be built by default? Use DIST_ONLY_SUBDIRS
|
||||
|
||||
Several of the MCS class libraries have demo or experimental
|
||||
implementations that depend on things not included with MCS (say,
|
||||
Gtk#). We don't want to build them by default, because the user might
|
||||
not have those dependencies installed, but it's nice to have a
|
||||
Makefile for them to be built nicely.
|
||||
|
||||
First of all, there's nothing stopping you from writing a Makefile for
|
||||
such a directory; just don't put it in the SUBDIRS line of its parent
|
||||
directory. That way, you can do all the normal build things like 'make
|
||||
all' or 'make clean' in that directory, but people trying to bootstrap
|
||||
their system won't run into problems.
|
||||
|
||||
At the same time you probably want to include this directory in the
|
||||
distribution so that people can use your demo or experimental code if
|
||||
they know what they're doing. Hence the variable
|
||||
$(DIST_ONLY_SUBDIRS). As you might guess, it's like the SUBDIRS
|
||||
variable: it lists subdirectories that a regular shouldn't recurse
|
||||
into, but should have their 'make dist' rules invoked.
|
||||
|
||||
Say you've written Mono.MyFancyLib.dll and you have
|
||||
a demo app using Gtk# called MyFancyDemo. The Makefile rules might
|
||||
look like this:
|
||||
|
||||
class/Mono.MyFancyLib/Makefile
|
||||
========================================
|
||||
thisdir = class/Mono.MyFancyLib
|
||||
SUBDIRS =
|
||||
DIST_ONLY_SUBDIRS = MyFancyDemo
|
||||
include ../../build/rules.make
|
||||
|
||||
LIBRARY = Mono.MyFancyLib.dll
|
||||
LIB_MCS_FLAGS = /r:System.dll
|
||||
TEST_MCS_FLAGS = $(LIB_MCS_FLAGS)
|
||||
|
||||
include ../../build/library.make
|
||||
========================================
|
||||
|
||||
class/Mono.MyFancyLib/MyFancyDemo/Makefile
|
||||
========================================
|
||||
thisdir = class/Mono.MyFancyLib/MyFancyDemo
|
||||
SUBDIRS =
|
||||
include ../../../build/rules.make
|
||||
|
||||
PROGRAM = FancyDemo.exe
|
||||
LOCAL_MCS_FLAGS = /r:gtk-sharp.dll
|
||||
|
||||
include ../../../build/executable.make
|
||||
========================================
|
||||
|
||||
|
||||
|
||||
|
||||
* Special recursion needs? Use OVERRIDE_BARE_TARGETS
|
||||
|
||||
By default, rules.make defines the all, install, clean, etc. targets
|
||||
to look something like this:
|
||||
|
||||
all: all-recursive all-local
|
||||
|
||||
Sometimes that doesn't cut it; say for example you want to check for
|
||||
something before doing a lengthy recursive build (see
|
||||
$(topdir)/Makefile) or you have a something like this
|
||||
|
||||
class/MyLibrary:
|
||||
Build MyLibrary.dll
|
||||
class/MyLibrary/Test:
|
||||
Build TestMyLibrary.exe
|
||||
|
||||
'make clean test' will fail here, because the build will happen in
|
||||
the Test subdirectory first, so there will be no MyLibrary.dll to link
|
||||
against. (Unless you write a nasty evil relative path rule which is
|
||||
strongly discouraged.)
|
||||
|
||||
Anyway, to solve this problem you can do
|
||||
|
||||
========================================
|
||||
OVERRIDE_BARE_TARGETS = yes
|
||||
thisdir = class/MyLibrary
|
||||
SUBDIRS = Test
|
||||
include ../../build/rules.make
|
||||
|
||||
# This is normally "all-recursive all-local"
|
||||
all: all-local all-recursive
|
||||
|
||||
test: test-local test-recursive
|
||||
...
|
||||
========================================
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** A few implementation details
|
||||
|
||||
The way rules.make does its recursion is very standard; it maps
|
||||
{all,install,clean, dist,test} to $@-recursive, which executes that
|
||||
rule in each directory in $(SUBDIRS), and then calls $@-local in the
|
||||
current directory. So something that gets built in a subdirectory
|
||||
cannot rely on something that gets built in its parent directory. If
|
||||
this is a problem, see the bit about using OVERRIDE_BARE_TARGETS;
|
||||
since the recursive rules do $(MAKE) $* in their subdirectories,
|
||||
changing the 'all' target will do the right thing in a recursive
|
||||
build. Note that the recursive rule for 'dist' is different; it makes
|
||||
dist-recursive in subdirectories, so you at least have to define that
|
||||
rule, even if you use OVERRIDE_BARE_TARGETS.
|
||||
|
||||
Note that even a directory that doesn't, for example, have any tests
|
||||
must still define test-local; otherwise 'make test' run from the
|
||||
toplevel directory will break.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Flags for Tools
|
||||
|
||||
We want to make it so that the user can specify certain flags to
|
||||
always be given to a tool, so there's a general way of implementing
|
||||
FLAGS variables:
|
||||
|
||||
* $(foo_FLAGS) remains unset or defaulted to something
|
||||
sensible; the user can provide overrides this way.
|
||||
|
||||
* $(LOCAL_foo_FLAGS) is set in a specific Makefile to
|
||||
provide necessary values.
|
||||
|
||||
* $(PLATFORM_foo_FLAGS) is set in the platform configuration
|
||||
to provide platform-specific values.
|
||||
|
||||
* $(PROFILE_foo_FLAGS) is set in the profile configuration
|
||||
to provide profile-specific values.
|
||||
|
||||
* $(USE_foo_FLAGS) is defined to be the combination of all of
|
||||
the above, and it's what is actually passed to $(foo).
|
||||
|
||||
$(MCS_FLAGS) and $(CFLAGS) follow this model. If you end up finding
|
||||
that another tool is used commonly (hm, jay...), please follow this form.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Portability tips
|
||||
|
||||
Always use the icky Windows /argument way of passing parameters to the C#
|
||||
compiler so that csc can be used.
|
||||
|
||||
Always use /r:foo.dll, not /r:foo. Windows requires the former.
|
||||
|
||||
Use /r:$(corlib), not /r:corlib. Windows wants mscorlib.dll and Linux
|
||||
wants corlib.dll; eventually, the Mono runtime is supposed to accept
|
||||
mscorlib.dll too, but in the meantime, use the variable.
|
||||
|
||||
If you're writing shell script code as part of a make rule, remember
|
||||
that Windows has command-line length limits. So something like
|
||||
|
||||
========================================
|
||||
mytool $(all_the_sources_to_corlib)
|
||||
========================================
|
||||
|
||||
Is probably going to cause problems. As I understand it,
|
||||
|
||||
========================================
|
||||
for f in $(all_the_sources_to_corlib) ; do ...
|
||||
========================================
|
||||
|
||||
is ok, since the shell itself doesn't have those limitations. Other
|
||||
than that, you should still try to write fairly portable shell
|
||||
script. Linux and Cygwin both use the GNU utilities, but there's at
|
||||
least one hardy soul trying to build Mono on HP/UX, and no doubt there
|
||||
will be ports to more Unices as time goes on.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
** Misc
|
||||
|
||||
We still don't use /d:NET_1_1 ; it causes some build problems right
|
||||
now.
|
||||
|
||||
There's a hack in class/System.Data/Makefile to work around a very
|
||||
strange crash in the runtime with some custom attribute stuff. It'd be
|
||||
nice to fix it.
|
||||
|
||||
Also, there's a /lib:$(prefix)/lib in the System.dll Makefile, which
|
||||
is for some reason necessary if System.Xml.dll hasn't been built yet.
|
||||
(Well, it's necessary because of the /r:System.Xml.dll, but that
|
||||
should be in the search path, it seems.)
|
||||
|
||||
A lot of the weird targets in the old makefiles have been dropped; I
|
||||
have a feeling that a lot of them are archaic and not needed anymore.
|
||||
|
||||
I'd really like to write a build tool in C#. It would be nice to have
|
||||
something really extensible and well-designed and clean. NAnt is,
|
||||
IMHO, an apalling abomination and a tragically bad attempt at solving
|
||||
the software building problem. Just so you know.
|
||||
|
||||
(On the other hand, NUnit is really neat.)
|
||||
|
||||
Peter
|
||||
@@ -1,41 +0,0 @@
|
||||
A platform makefile should define the following variables:
|
||||
|
||||
PLATFORM_DEBUG_FLAGS
|
||||
The flags to pass to the C# compiler to generate appropriate
|
||||
debug information
|
||||
|
||||
PLATFORM_MCS_FLAGS
|
||||
Flags that are always passed to the C# compiler
|
||||
|
||||
PLATFORM_RUNTIME
|
||||
The system runtime for executing CLR programs. Blank on Win32,
|
||||
probably $(RUNTIME) (the Mono runtime) on everything else.
|
||||
|
||||
PLATFORM_CORLIB
|
||||
The name of the system's corlib. 'mscorlib.dll' for windows,
|
||||
corlib.dll for mono-based.
|
||||
|
||||
PLATFORM_MAKE_CORLIB_CMP
|
||||
Define it to something nonempty if corlib_cmp.dll should be built
|
||||
on this platform. Only should be done if the platform provides its
|
||||
own non-Mono runtime that we can compare corlibs with.
|
||||
|
||||
PLATFORM_TWEAK_CORLIB_SOURCES
|
||||
A command to futz around with the sources to corlib.dll. See linux.make
|
||||
and win32.make for examples. Should be 'cat' unless you know what you're
|
||||
doing.
|
||||
|
||||
PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
A command to change filename separators given on stdin. Leave undefined
|
||||
if Unixy filenames will work. See win32.make.
|
||||
|
||||
BOOTSTRAP_MCS
|
||||
The C# compiler used to compile mcs/mcs.exe, and possibly other
|
||||
assemblies if the user is doing a standalone build (that is, not
|
||||
a bootstrap).
|
||||
|
||||
hidden_prefix, hidden_suffix
|
||||
Prefix and suffix for hidden/temporary files. Unused right now, I think.
|
||||
|
||||
platform-check:
|
||||
A target to make sure that we can build on this platform.
|
||||
@@ -1,38 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# This makefile fragment has (default) configuration
|
||||
# settings for building MCS.
|
||||
|
||||
# DO NOT EDIT THIS FILE! Create config.make and override settings
|
||||
# there.
|
||||
|
||||
RUNTIME_FLAGS =
|
||||
TEST_HARNESS = $(topdir)/class/lib/nunit-console.exe
|
||||
MCS_FLAGS = $(PLATFORM_DEBUG_FLAGS)
|
||||
LIBRARY_FLAGS = /noconfig
|
||||
CFLAGS = -g -O2
|
||||
INSTALL = /usr/bin/install
|
||||
RUNTIME = mono $(RUNTIME_FLAGS)
|
||||
TEST_RUNTIME=$(PLATFORM_RUNTIME)
|
||||
prefix = /usr/local
|
||||
|
||||
# In case you want to add MCS_FLAGS, this lets you not have to
|
||||
# keep track of the default value
|
||||
|
||||
DEFAULT_MCS_FLAGS := $(MCS_FLAGS)
|
||||
|
||||
# Not all echos are alike. HP/UX doesn't need a -e command.
|
||||
# Test for this here
|
||||
|
||||
ifeq ($(shell echo -e foo),foo)
|
||||
ECHO_ESCAPE=echo -e
|
||||
else
|
||||
ECHO_ESCAPE=echo
|
||||
endif
|
||||
|
||||
# You shouldn't need to set these but might on a
|
||||
# weird platform.
|
||||
|
||||
# CC = cc
|
||||
# SHELL = /bin/sh
|
||||
# MAKE = gmake
|
||||
@@ -1,3 +0,0 @@
|
||||
*.makefrag
|
||||
*.response
|
||||
*.stamp
|
||||
Whitespace-only changes.
@@ -1,76 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# The rules for building a program.
|
||||
|
||||
# I'd rather not create a response file here,
|
||||
# but since on Win32 we need to munge the paths
|
||||
# anyway, we might as well.
|
||||
|
||||
base_prog = $(shell basename $(PROGRAM))
|
||||
sourcefile = $(base_prog).sources
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
response = $(depsdir)/$(base_prog).response
|
||||
else
|
||||
response = $(sourcefile)
|
||||
endif
|
||||
stampfile = $(depsdir)/$(base_prog).stamp
|
||||
makefrag = $(depsdir)/$(base_prog).makefrag
|
||||
pdb = $(patsubst %.exe,%.pdb,$(PROGRAM))
|
||||
|
||||
all-local: $(PROGRAM)
|
||||
|
||||
install-local: $(PROGRAM)
|
||||
$(MKINSTALLDIRS) $(DESTDIR)$(prefix)/bin
|
||||
$(INSTALL_BIN) $(PROGRAM) $(DESTDIR)$(prefix)/bin
|
||||
|
||||
uninstall-local:
|
||||
-rm -f $(DESTDIR)$(prefix)/bin/$(base_prog)
|
||||
|
||||
clean-local:
|
||||
-rm -f *.exe $(BUILT_SOURCES) $(CLEAN_FILES) $(pdb) $(stampfile) $(makefrag)
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
-rm -f $(response)
|
||||
endif
|
||||
|
||||
ifndef HAS_TEST
|
||||
test-local: $(PROGRAM)
|
||||
|
||||
run-test-local:
|
||||
endif
|
||||
|
||||
DISTFILES = $(sourcefile) $(EXTRA_DISTFILES)
|
||||
|
||||
dist-local: dist-default
|
||||
for f in `cat $(sourcefile)` ; do \
|
||||
dest=`dirname $(distdir)/$$f` ; \
|
||||
$(MKINSTALLDIRS) $$dest && cp $$f $$dest || exit 1 ; \
|
||||
done
|
||||
|
||||
# Changing makefile probably means changing the
|
||||
# sources, so let's be safe and add a Makefile dep
|
||||
|
||||
$(PROGRAM): $(makefrag) $(response) $(stampfile)
|
||||
$(CSCOMPILE) /target:exe /out:$@ $(BUILT_SOURCES) @$(response)
|
||||
|
||||
$(makefrag): $(sourcefile)
|
||||
@echo Creating $@ ...
|
||||
@echo "HAVE_MAKEFRAG = yes" >[email protected]
|
||||
@echo "$(stampfile): $(BUILT_SOURCES) \\" >>[email protected]
|
||||
@cat $< |sed -e 's,\.cs[ \t]*$$,\.cs \\,' >>[email protected]
|
||||
@cat [email protected] |sed -e '$$s, \\$$,,' >$@
|
||||
@$(ECHO_ESCAPE) "\ttouch \$$@" >>$@
|
||||
@rm -rf [email protected]
|
||||
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
$(response): $(sourcefile)
|
||||
@echo Creating $@ ...
|
||||
@cat $< |$(PLATFORM_CHANGE_SEPARATOR_CMD) >$@
|
||||
endif
|
||||
|
||||
-include $(makefrag)
|
||||
|
||||
ifndef HAVE_MAKEFRAG
|
||||
$(stampfile):
|
||||
touch $@
|
||||
endif
|
||||
|
||||
@@ -1,135 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# The rules for building our class libraries.
|
||||
#
|
||||
# The NO_TEST stuff is not too pleasant but whatcha
|
||||
# gonna do.
|
||||
|
||||
# All the dep files now land in the same directory so we
|
||||
# munge in the library name to keep the files from clashing.
|
||||
|
||||
sourcefile = $(LIBRARY).sources
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
response = $(depsdir)/$(LIBRARY).response
|
||||
else
|
||||
response = $(sourcefile)
|
||||
endif
|
||||
makefrag = $(depsdir)/$(LIBRARY).makefrag
|
||||
stampfile = $(depsdir)/$(LIBRARY).stamp
|
||||
the_lib = $(topdir)/class/lib/$(LIBRARY)
|
||||
the_pdb = $(patsubst %.dll,%.pdb,$(the_lib))
|
||||
|
||||
ifndef NO_TEST
|
||||
test_lib = $(patsubst %.dll,%_test.dll,$(LIBRARY))
|
||||
test_pdb = $(patsubst %.dll,%.pdb,$(test_lib))
|
||||
test_sourcefile = $(test_lib).sources
|
||||
test_response = $(depsdir)/$(test_lib).response
|
||||
test_makefrag = $(depsdir)/$(test_lib).makefrag
|
||||
test_stampfile = $(depsdir)/$(test_lib).stamp
|
||||
test_flags = /r:$(the_lib) /r:$(topdir)/class/lib/NUnit.Framework.dll $(TEST_MCS_FLAGS)
|
||||
endif
|
||||
|
||||
all-local: $(the_lib)
|
||||
|
||||
install-local: $(the_lib)
|
||||
$(MKINSTALLDIRS) $(DESTDIR)$(prefix)/lib
|
||||
$(INSTALL_LIB) $(the_lib) $(DESTDIR)$(prefix)/lib
|
||||
|
||||
uninstall-local:
|
||||
-rm -f $(DESTDIR)$(prefix)/lib/$(LIBRARY)
|
||||
|
||||
clean-local:
|
||||
-rm -f $(the_lib) $(makefrag) $(test_lib) \
|
||||
$(test_makefrag) $(test_response) \
|
||||
$(stampfile) $(test_stampfile) \
|
||||
$(the_pdb) $(test_pdb) \
|
||||
TestResult.xml
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
-rm -rf $(response)
|
||||
endif
|
||||
|
||||
ifndef NO_TEST
|
||||
test-local: $(the_lib) $(test_lib)
|
||||
|
||||
run-test-local:
|
||||
$(TEST_RUNTIME) $(TEST_HARNESS) $(test_lib)
|
||||
|
||||
else
|
||||
test-local: $(the_lib)
|
||||
|
||||
run-test-local:
|
||||
endif
|
||||
|
||||
DISTFILES = $(sourcefile) $(test_sourcefile) $(EXTRA_DISTFILES)
|
||||
|
||||
ifdef NO_TEST
|
||||
TEST_FILES =
|
||||
else
|
||||
TEST_FILES = `cat $(test_sourcefile) |sed -e 's,^\(.\),Test/\1,'`
|
||||
endif
|
||||
|
||||
dist-local: dist-default
|
||||
for f in `cat $(sourcefile)` $(TEST_FILES) ; do \
|
||||
dest=`dirname $(distdir)/$$f` ; \
|
||||
$(MKINSTALLDIRS) $$dest && cp $$f $$dest || exit 1 ; \
|
||||
done
|
||||
|
||||
# Fun with dependency tracking
|
||||
|
||||
$(the_lib): $(makefrag) $(stampfile) $(response)
|
||||
$(CSCOMPILE) $(LIBRARY_FLAGS) $(LIB_MCS_FLAGS) /target:library /out:$@ @$(response)
|
||||
|
||||
$(makefrag): $(sourcefile)
|
||||
@echo Creating $@ ...
|
||||
@echo "HAVE_MAKEFRAG = yes" >[email protected]
|
||||
@echo "$(stampfile): \\" >>[email protected]
|
||||
@cat $< |sed -e 's,\.cs[ \t]*$$,\.cs \\,' >>[email protected]
|
||||
@cat [email protected] |sed -e '$$s, \\$$,,' >$@
|
||||
@$(ECHO_ESCAPE) "\ttouch \$$@" >>$@
|
||||
@rm -rf [email protected]
|
||||
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
$(response): $(sourcefile)
|
||||
@echo Creating $@ ...
|
||||
@cat $< |$(PLATFORM_CHANGE_SEPARATOR_CMD) >$@
|
||||
endif
|
||||
|
||||
-include $(makefrag)
|
||||
|
||||
ifndef HAVE_MAKEFRAG
|
||||
$(stampfile):
|
||||
touch $@
|
||||
endif
|
||||
|
||||
# for now, don't give any /lib flags or set MONO_PATH, since we
|
||||
# give a full path to the assembly.
|
||||
|
||||
ifndef NO_TEST
|
||||
$(test_lib): $(test_makefrag) $(the_lib) $(test_response) $(test_stampfile)
|
||||
$(CSCOMPILE) /target:library /out:$@ $(test_flags) @$(test_response)
|
||||
|
||||
$(test_response): $(test_sourcefile)
|
||||
@echo Creating $@ ...
|
||||
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
|
||||
@cat $< |sed -e 's,^\(.\),Test/\1,' |$(PLATFORM_CHANGE_SEPARATOR_CMD) >$@
|
||||
else
|
||||
@cat $< |sed -e 's,^\(.\),Test/\1,' >$@
|
||||
endif
|
||||
|
||||
$(test_makefrag): $(test_response)
|
||||
@echo Creating $@ ...
|
||||
@echo "HAVE_TEST_MAKEFRAG = yes" >[email protected]
|
||||
@echo "$(test_stampfile): \\" >>[email protected]
|
||||
@cat $< |sed -e 's,\.cs[ \t]*$$,\.cs \\,' >>[email protected]
|
||||
@cat [email protected] |sed -e '$$s, \\$$,,' >$@
|
||||
@$(ECHO_ESCAPE) "\ttouch \$$@" >>$@
|
||||
@rm -rf [email protected]
|
||||
|
||||
-include $(test_makefrag)
|
||||
endif
|
||||
|
||||
ifndef HAVE_TEST_MAKEFRAG
|
||||
$(test_stampfile):
|
||||
touch $@
|
||||
endif
|
||||
|
||||
@@ -1,45 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# Platform-specific makefile rules. This one's for linux.
|
||||
#
|
||||
|
||||
PLATFORM_DEBUG_FLAGS = -g
|
||||
PLATFORM_MCS_FLAGS =
|
||||
PLATFORM_RUNTIME = $(RUNTIME)
|
||||
PLATFORM_CORLIB = mscorlib.dll
|
||||
|
||||
BOOTSTRAP_MCS = mcs
|
||||
RESGEN = monoresgen
|
||||
|
||||
# Define this if this ever will work on Linux
|
||||
# PLATFORM_MAKE_CORLIB_CMP = yes
|
||||
|
||||
# This is for the security permission attribute problem
|
||||
# on windows
|
||||
PLATFORM_TWEAK_CORLIB_SOURCES = cat
|
||||
|
||||
# This is for changing / to \ on windows
|
||||
# Don't define it so we don't needlessly copy the sources
|
||||
# file. This command is handy for testing:
|
||||
#
|
||||
# PLATFORM_CHANGE_SEPARATOR_CMD=sed -e 's,/,/./,g'
|
||||
|
||||
hidden_prefix = .
|
||||
hidden_suffix =
|
||||
|
||||
platform-check:
|
||||
@if ! type $(BOOTSTRAP_MCS) >/dev/null 2>&1 ; then \
|
||||
echo "*** You need a C# compiler installed to build MCS." ; \
|
||||
echo "*** Read INSTALL.txt for information on how to bootstrap" ; \
|
||||
echo "*** a Mono installation." ; \
|
||||
exit 1 ; \
|
||||
fi
|
||||
|
||||
|
||||
# I tried this but apparently Make's version strings aren't that
|
||||
# ... consistent between releases. Whatever.
|
||||
#
|
||||
# @if ! $(MAKE) --version |grep '^GNU Make version 3' 1>/dev/null 2>&1 ; then \
|
||||
# echo "*** You need to build MCS with GNU make. Try \`gmake'" ; \
|
||||
# exit 1 ; \
|
||||
# fi
|
||||
@@ -1,22 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# Win32 platform-specific makefile rules.
|
||||
#
|
||||
|
||||
PLATFORM_DEBUG_FLAGS = /debug+ /debug:full
|
||||
PLATFORM_MCS_FLAGS = /nologo /optimize
|
||||
PLATFORM_RUNTIME =
|
||||
PLATFORM_CORLIB = mscorlib.dll
|
||||
|
||||
BOOTSTRAP_MCS = csc.exe
|
||||
MCS = $(BOOTSTRAP_MCS)
|
||||
RESGEN = resgen.exe
|
||||
|
||||
PLATFORM_MAKE_CORLIB_CMP = yes
|
||||
PLATFORM_TWEAK_CORLIB_SOURCES=cat - corlib.dll.win32-excludes |sort |uniq -u
|
||||
PLATFORM_CHANGE_SEPARATOR_CMD=tr '/' '\\\\'
|
||||
|
||||
hidden_prefix =
|
||||
hidden_suffix = .tmp
|
||||
|
||||
platform-check:
|
||||
@@ -1,38 +0,0 @@
|
||||
# -*- Makefile -*-
|
||||
#
|
||||
# The 'atomic' profile.
|
||||
|
||||
# In this profile we compile everything relative to the already-installed
|
||||
# runtime, so we use the bootstrap (external) compiler for everything and
|
||||
# don't set MONO_PATH.
|
||||
#
|
||||
# (So the libraries are compiled and installed atomically, not incrementally.)
|
||||
|
||||
MCS = $(BOOTSTRAP_MCS)
|
||||
|
||||
# Causes some build errors
|
||||
#PROFILE_MCS_FLAGS = /d:NET_1_1 /lib:$(prefix)/lib
|
||||
|
||||
# Get our installed libraries (an issue on windows)
|
||||
|
||||
PROFILE_MCS_FLAGS = /lib:$(prefix)/lib
|
||||
|
||||
# Check that installed libraries even exist.
|
||||
|
||||
profile-check:
|
||||
@if test '!' -f $(prefix)/lib/I18N.dll ; then \
|
||||
echo ; \
|
||||
echo "$(prefix)/lib/I18N.dll does not exist." ; \
|
||||
echo ; \
|
||||
echo "This probably means that you are building from a miniature" ; \
|
||||
echo "distribution of MCS or don't yet have an installed MCS at all." ; \
|
||||
echo "The current build profile needs a complete installation of" ; \
|
||||
echo "MCS to build against; you need to build using the default" ; \
|
||||
echo "profile. Use this command:" ; \
|
||||
echo ; \
|
||||
echo " $(MAKE) PROFILE=default" ; \
|
||||
echo ; \
|
||||
exit 1 ; \
|
||||
fi
|
||||
|
||||
# Exciting, no?
|
||||
@@ -1,28 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# The default 'bootstrap' profile -- builds so that we link against
|
||||
# the libraries as we build them.
|
||||
#
|
||||
# We use the platform's native C# runtime and compiler if possible.
|
||||
|
||||
# Note that we have sort of confusing terminology here; BOOTSTRAP_MCS
|
||||
# is what allows us to bootstrap ourselves, but when we are bootstrapping,
|
||||
# we use INTERNAL_MCS.
|
||||
|
||||
# When bootstrapping, compile against our new assemblies.
|
||||
# (MONO_PATH doesn't just affect what assemblies are loaded to
|
||||
# run the compiler; /r: flags are by default loaded from whatever's
|
||||
# in the MONO_PATH too).
|
||||
|
||||
ifdef PLATFORM_MONO_NATIVE
|
||||
MCS = MONO_PATH="$(topdir)/class/lib:$$MONO_PATH" $(INTERNAL_MCS)
|
||||
TEST_RUNTIME = MONO_PATH=".:$$MONO_PATH" $(RUNTIME) --debug
|
||||
else
|
||||
MCS = $(PLATFORM_RUNTIME) $(BOOTSTRAP_MCS) /lib:$(topdir)/class/lib
|
||||
endif
|
||||
|
||||
# nuttzing!
|
||||
|
||||
profile-check:
|
||||
|
||||
PROFILE_MCS_FLAGS = -d:NET_1_1
|
||||
@@ -1,28 +0,0 @@
|
||||
# -*- makefile -*-
|
||||
#
|
||||
# The default 'bootstrap' profile -- builds so that we link against
|
||||
# the libraries as we build them.
|
||||
#
|
||||
# We use the platform's native C# runtime and compiler if possible.
|
||||
|
||||
# Note that we have sort of confusing terminology here; BOOTSTRAP_MCS
|
||||
# is what allows us to bootstrap ourselves, but when we are bootstrapping,
|
||||
# we use INTERNAL_MCS.
|
||||
|
||||
# When bootstrapping, compile against our new assemblies.
|
||||
# (MONO_PATH doesn't just affect what assemblies are loaded to
|
||||
# run the compiler; /r: flags are by default loaded from whatever's
|
||||
# in the MONO_PATH too).
|
||||
|
||||
ifdef PLATFORM_MONO_NATIVE
|
||||
MCS = MONO_PATH="$(topdir)/class/lib:$$MONO_PATH" $(INTERNAL_MCS)
|
||||
TEST_RUNTIME = MONO_PATH=".:$$MONO_PATH" $(RUNTIME) --debug
|
||||
else
|
||||
MCS = $(PLATFORM_RUNTIME) $(BOOTSTRAP_MCS) /lib:$(topdir)/class/lib
|
||||
endif
|
||||
|
||||
# nuttzing!
|
||||
|
||||
profile-check:
|
||||
|
||||
PROFILE_MCS_FLAGS = -d:NET_1_1 -d:NET_1_2 -2
|
||||
Loaded 100 of 4437 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user