Compare commits

..
1 Commits
Author SHA1 Message Date
nobody 24ca06b662 This commit was manufactured by cvs2svn to create tag 'MONO_0_25'.
svn path=/tags/MONO_0_25/mono/; revision=15654
2003-06-26 13:29:46 +00:00
2022 changed files with 34361 additions and 162948 deletions

No files matched your search

-51
View File
@@ -1,54 +1,3 @@
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 -26
View File
@@ -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,28 +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/corlib.dll runtime
cp ../mcs/mcs/mcs.exe runtime
xinstall-runtime:
if echo $(SUBDIRS) | grep "libgc " > /dev/null; then (cd libgc; make && make install); fi
(cd mono; make && make install)
mcs-rest:
(cd ../mcs/class; make)
remove-binaries:
rm ../mcs/class/lib/corlib.dll ../mcs/mcs/mcs.exe runtime/*dll runtime/*.exe >& /dev/null; echo
+6 -21
View File
@@ -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.
-4
View File
@@ -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,10 +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
-51
View File
@@ -1,51 +0,0 @@
/* config.h.in. Generated automatically from configure.in by autoheader 2.13. */
/* Define if you have the ANSI C header files. */
#undef STDC_HEADERS
#undef HAVE_INET_PTON
#undef HAVE_INET_ATON
#undef HAVE_SOL_IP
#undef HAVE_SOL_TCP
#undef HAVE_IP_PKTINFO
#undef HAVE_STRUCT_IP_MREQN
#undef HAVE_PTHREAD
#undef HAVE_PTHREAD_MUTEX_TIMEDLOCK
#undef USE_MONO_MUTEX
#undef HAVE_LARGE_FILE_SUPPORT
#undef PLATFORM_WIN32
#undef HAVE_NEW_ICONV
#undef NAME_DEV_RANDOM
#undef HAVE_CRYPT_RNG
#undef HAVE_BOEHM_GC
/* The number of bytes in a void *. */
#undef SIZEOF_VOID_P
/* Define if you have the inet_aton function. */
#undef HAVE_INET_ATON
/* Define if you have the inet_pton function. */
#undef HAVE_INET_PTON
/* Define if you have the <dlfcn.h> header file. */
#undef HAVE_DLFCN_H
/* Define if you have the <netdb.h> header file. */
#undef HAVE_NETDB_H
/* Define if you have the <sys/filio.h> header file. */
#undef HAVE_SYS_FILIO_H
/* Define if you have the <sys/sockio.h> header file. */
#undef HAVE_SYS_SOCKIO_H
/* Define if you have the <utime.h> header file. */
#undef HAVE_UTIME_H
/* Name of package */
#undef PACKAGE
/* Version number of package */
#undef VERSION
+14 -159
View File
@@ -1,7 +1,7 @@
AC_INIT(README)
AC_CANONICAL_SYSTEM
AM_CONFIG_HEADER(config.h)
AM_INIT_AUTOMAKE(mono,0.26)
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,20 +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"
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
@@ -112,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";
@@ -154,11 +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'
fi
CFLAGS="-g $WARN"
CFLAGS='-g -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-cast-qual -Wcast-align -Wwrite-strings'
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
if test "x$PKG_CONFIG" = "xno"; then
@@ -202,14 +182,6 @@ AC_SUBST(GMODULE_LIBS)
AC_ARG_WITH(gc, [ --with-gc=boehm,included,none],[gc=$with_gc],[gc=$gc_default])
# 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=
@@ -229,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)
@@ -361,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 *****************************
@@ -432,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 ***
@@ -476,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 *****************************
@@ -562,12 +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 working poll() (macosx defines it but doesn't ***
dnl *** have it in the library (duh)) ***
dnl ****************************************************************
AC_CHECK_FUNCS(poll)
else
AC_CHECK_LIB(ws2_32, main, LIBS="$LIBS -lws2_32", AC_ERROR(bad mingw install?))
AC_CHECK_LIB(psapi, main, LIBS="$LIBS -lpsapi", AC_ERROR(bad mingw install?))
@@ -650,77 +568,18 @@ TARGET="unknown"
ACCESS_UNALIGNED="yes"
JIT_SUPPORTED=no
LIBC="libc.so.6"
case "$host" in
# mips-sgi-irix5.* | mips-sgi-irix6.*)
# TARGET=MIPS;
# ACCESS_UNALIGNED="no"
# ;;
i*86-*-*)
TARGET=X86;
arch_target=x86;
JIT_SUPPORTED=yes
;;
sparc*-*-*)
TARGET=SPARC;
arch_target=sparc;
ACCESS_UNALIGNED="no"
;;
# alpha*-*-linux* | alpha*-*-osf*)
# TARGET=ALPHA;
# ACCESS_UNALIGNED="no"
# ;;
# ia64-*-linux* | ia64-*-hpux*)
# TARGET=IA64;
# arch_target=ia64;
# JIT_SUPPORTED=no;
# ACCESS_UNALIGNED="no";
# case "$host_os" in
# linux*) LIBC="libc.so.6.1";;
# hpux*) LIBC="libc.so.1";;
# esac
# ;;
# m68k-*-linux*)
# TARGET=M68K
# ;;
macppc-*-openbsd* | powerpc-*-linux* | powerpc-*-openbsd* | \
powerpc-*-sysv* | powerpc-*-darwin*)
TARGET=POWERPC;
arch_target=ppc;
JIT_SUPPORTED=yes
;;
arm-*-linux-* | armv4l-*-linux-*)
TARGET=ARM;
arch_target=arm;
ACCESS_UNALIGNED="no"
;;
s390-*-linux*)
TARGET=S390;
arch_target=s390;
ACCESS_UNALIGNED="no"
;;
#mips-sgi-irix5.* | mips-sgi-irix6.*) TARGET=MIPS; ACCESS_UNALIGNED="no";;
i*86-*-*) TARGET=X86; arch_target=x86; 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.")
@@ -735,7 +594,6 @@ 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)
@@ -743,6 +601,7 @@ AM_CONDITIONAL(S390, test x$TARGET = xS390)
AM_CONDITIONAL(JIT_SUPPORTED, test x$JIT_SUPPORTED = xyes)
LIBC="libc.so.6"
AC_SUBST(LIBC)
AC_SUBST(arch_target)
@@ -770,22 +629,18 @@ 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
])
+5
View File
@@ -4,3 +4,8 @@ EXTRA_DIST = config.in machine.config
mono_DATA = config machine.config
DISTCLEANFILES = config
config: config.in Makefile
sed -e 's^\@LIBC\@^libc.so.6^g' < $(srcdir)/config.in > config.tmp \
&& mv config.tmp config
-24
View File
@@ -21,12 +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" />
</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"
@@ -36,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>
@@ -55,20 +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="*" path="*.asax" type="System.Web.HttpForbiddenHandler, System.Web" />
<add verb="*" path="*.ascx" type="System.Web.HttpForbiddenHandler, System.Web" />
<add verb="*" path="*.config" type="System.Web.HttpForbiddenHandler, System.Web" />
<add verb="*" path="*.cs" type="System.Web.HttpForbiddenHandler, System.Web" />
<add verb="GET,HEAD" path="*" type="System.Web.StaticFileHandler, System.Web" />
<add verb="*" path="*" type="System.Web.HttpMethodNotAllowedHandler, System.Web" />
</httpHandlers>
@@ -93,15 +81,6 @@
uiculture="en-US" />
-->
<sessionState mode="InProc" />
<webServices>
<protocols>
<add name="HttpSoap"/>
<add name="HttpPost"/>
<add name="HttpGet"/>
<add name="Documentation"/>
</protocols>
<wsdlHelpGenerator href="DefaultWsdlHelpGenerator.aspx" />
</webServices>
</system.web>
<appSettings>
@@ -112,8 +91,5 @@
<system.diagnostics>
<trace autoflush="false" indentsize="4" />
</system.diagnostics>
<system.drawing>
</system.drawing>
</configuration>
+54 -40
View File
@@ -7,8 +7,9 @@
* Web Services (the SOAP-based rpc system).
</ul>
Both are functional at this point, and applications like
"IBuySpy" run with Mono.
There is work underway for both systems. The Web Forms
support is more advanced at this point, and various ".aspx"
programs can be run using the Mono runtime, including IBuySpy.
ASP.NET works either embedded into
our XSP server test server or the mod_mono Apache module.
@@ -16,57 +17,35 @@
We are now working bug fixing and adding missing features
after making the whole pipeline compatible with MS.
Tim started work on the Web Services. Lluis is in charge of
it now and web services are now supported. He also added a web
service sample to the XSP server set of tests.
Tim started work on the Web Services. Although we have a
SoapFormatter as part of the remoting infrastructure already
(contributed by Jesus), most people will be using the ASP.NET
Web Services support. Work for the supporting class libraries
just started recently.
** Hosting
The major missing element is a complete XmlSerializer.
ASP.NET provides a hosting interface. Today we ship support
for two different hosting mechanisms:
<ul>
* <a href="#xsp">XSP</a>: A light-weight C# web server.
** HttpRuntime
* <a href="#mod_mono">mod_mono</a>: An apache module
that can host the Mono runtime and the ASP.NET runtime
</ul>
Patrik has authored most of the HttpRuntime support (both on
the System.Web and on the foundation).
<a name="xsp">
** XSP
XSP is a simple web server written in C# that can be used to
run your ASP.NET applications. The code is available from our
<a href="download.html">download page</a> or from the <a
href="anoncvs.html">Anonymous CVS</a> repository (module name:
xsp)/.
This is where initial development of the .aspx/.ascx/.asax
compiler to C# took place. That compiler is now integrated in
System.Web classes mostly under System.Web.Compilation
namespace. We added a new web server that works with mono and
MS runtime and is being used to debug our classes. It resides
in xsp/server.
This is where initial development of the .aspx/.ascx/.asax compiler
to C# took place. That compiler is now integrated in System.Web classes
mostly under System.Web.Compilation namespace.
A couple of classes of this new server can be reused/extended
to make an apache module/cgi using mono (MonoWorkerRequest and
MonoApplicationHost). This server also uses a couple of
plugins distributed with Mono to support gzip HTTP transfers.
We added a new web server that works with mono and MS runtime and is
being used to debug our classes. It resides in xsp/server. A couple of
classes of this new server can be reused/extended to make an apache
module/cgi using mono (MonoWorkerRequest and MonoApplicationHost).
There is also a set of .aspx pages to test the server along with
a few user controls under xsp/test.
You can check it out from CVS and run 'make install' to test it.
<a name="mod_mono">
* mod_mono
This Apache module available at <a
href="http://www.apacheworld.org/modmono/">ApacheWorld.org</a>
hosts the Mono runtime and the Mono's ASP.NET runtime, and
allows apache to server asp.net web pages.
Work is underway to improve it.
** Controls
A lot of work has been put in the various classes that
@@ -84,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
-6
View File
@@ -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">
+21 -24
View File
@@ -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
@@ -119,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>
@@ -266,7 +275,7 @@
<ul>
* Nothing (yet) commited in CVS. However the classes in this
namespace are outside WS-Security scope. So development, for
those classes, could be done without signing this agreement.
those classes, could be done without signing any agreements.
</ul>
**** TODO
@@ -276,12 +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.
</ul>
<hr>
** Tools
@@ -303,17 +306,11 @@
(SPC) file - which is a long name for a simple PKCS#7 file.
* <code>makecert</code> to create X.509 test certificates that
can be used (once transformed in SPC) to sign assemblies. It's
now possible to generate SSL certificates for web servers.
can be used (once transformed in SPC) to sign assemblies.
</ul>
Somewhat usable, somewhat incomplete:
<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.
@@ -348,6 +345,7 @@
RC4, RSAManaged ...).
</ul>
<hr>
** How to Help
@@ -355,19 +353,18 @@
* 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>
@@ -375,4 +372,4 @@
informations about the status of the cryptographic classes.
<hr>
Last reviewed: August 9, 2003 (post mono 0.25)
Last reviewed: June 11, 2003 (post mono 0.24)
+28 -50
View File
@@ -32,7 +32,7 @@
<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/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>
@@ -44,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>
@@ -56,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>
@@ -112,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>
+1 -12
View File
@@ -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");
+45 -51
View File
@@ -130,17 +130,6 @@ A: Different parts of Mono will achieve usability at different stages,
Other higher level class libraries (ASP.NET, ADO.NET, WinForms) will
be released when they become stable.
Q: When will Mono 1.0 ship?
A: We are planning on releasing Mono 1.0 (Mono Core) which will ship all the
components of Mono that are known to be stable in Q4 2003.
This release will lack System.Windows.Forms and
Enterprise.Services, as they will not be production ready on this timeframe.
Mono 1.2 should come in Q2 2004 and include the missing components
libraries that will make Mono feature-compatible with .NET 1.0
Q: What major components will you include in Mono?
A: Hopefully everything that Microsoft ships on their Framework
@@ -726,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?
@@ -756,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
@@ -783,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?
@@ -834,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
@@ -1419,6 +1416,3 @@ A: It's possible to run VC++ generated apps under Mono, but we do not
or if you think that you found a bug, etc. Please visit the
<a href="http://geneura.ugr.es/~jaime/deploy/mono-common-problems.html">Mono Common Problems</a> document and try there.
** Credits
The FAQ contains material contributed by Miguel de Icaza, Jaime Anguiano, Lluis Sánchez.
+4 -198
View File
@@ -83,7 +83,7 @@
</tr>
<tr>
<td><b><a href="asp-net.html">ASP.NET</a></b></td>
<td>Webforms and WebServices working<br></td>
<td>Webforms working<br></td>
</tr>
<tr>
<td>
@@ -151,202 +151,10 @@
</tr>
</table>
@item Aug 9th, 2003: Python for .NET Preview 2 available; Mono Documentation site up.
@item Jun 23rd, 2003: DiaCanvas#, Turkish presentation
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>
http://enver.casdb.com/sunumlar/mono/
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
@@ -1284,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.
+15 -19
View File
@@ -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">
@@ -115,18 +114,6 @@
An FAQ document is available <a
href="http://www.zope.org/Members/Brian/PythonNet/FAQ.html">here</a>.
<a name="dotlisp">
** dotLisp
DotLisp is available from: <a
href="http://sourceforge.net/projects/dotlisp/">http://sourceforge.net/projects/dotlisp/</a>
<a name="JavaScript">
* Java Script
Cesar is working on Mono's implementation of JScript, the code
is available on CVS on module `mcs'.
* Missing languages
Here is a list of a few languages that we would like to see
@@ -135,6 +122,19 @@
implementing or adapting a compiler for any of these
languages:
<a name="JavaScript">
* Java Script
The Mozilla project has an implementation of JavaScript
written in Java called <a
href="http://www.mozilla.org/rhino/">Rhino</a>.
You could port this code from Java to C#.
Note that since JavaScript allows for evaluation at runtime,
the compiler has to be built as a class that can be invoked at
runtime.
<a name="c">
* C
@@ -152,10 +152,6 @@
<a name="Java">
* Java
Java bytecode can run directly on Mono using the <a
href="http://www.ikvm.net">IKVM</a> java virtual machine for
.NET.
We have a <a href="java.html">separate page</a> for Java.
-194
View File
@@ -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>
-246
View File
@@ -1,246 +0,0 @@
System.Object
System.Exception
System.ValueType
System.Delegate
System.MulticastDelegate
System.Enum
System.Activator
System.ArgIterator
System.__ComObject
System.TypedReference
System.Security.AllowPartiallyTrustedCallersAttribute
System.Runtime.Serialization.Formatter
System.Runtime.Serialization.FormatterConverter
System.Runtime.Serialization.FormatterServices
System.Runtime.Serialization.ObjectIDGenerator
System.Runtime.Serialization.ObjectManager
System.Reflection.ModuleResolveEventHandler
System.Reflection.Pointer
System.Globalization.CompareInfo
System.Globalization.HebrewCalendar
System.Globalization.HijriCalendar
System.Globalization.JapaneseCalendar
System.Globalization.KoreanCalendar
System.Globalization.SortKey
System.Globalization.StringInfo
System.Globalization.TaiwanCalendar
System.Globalization.TextElementEnumerator
System.Globalization.TextInfo
System.Globalization.ThaiBuddhistCalendar
System.IO.IsolatedStorage.IsolatedStorageFile
System.Reflection.Emit.MethodRental
System.Runtime.CompilerServices.AccessedThroughPropertyAttribute
System.Runtime.CompilerServices.CallConvCdecl
System.Runtime.CompilerServices.CallConvStdcall
System.Runtime.CompilerServices.CallConvThiscall
System.Runtime.CompilerServices.CallConvFastcall
System.Runtime.CompilerServices.CustomConstantAttribute
System.Runtime.CompilerServices.DateTimeConstantAttribute
System.Runtime.CompilerServices.DiscardableAttribute
System.Runtime.CompilerServices.DecimalConstantAttribute
System.Runtime.CompilerServices.CompilationRelaxationsAttribute
System.Runtime.CompilerServices.CompilerGlobalScopeAttribute
System.Runtime.CompilerServices.IDispatchConstantAttribute
System.Runtime.CompilerServices.IsVolatile
System.Runtime.CompilerServices.IUnknownConstantAttribute
System.Runtime.CompilerServices.RequiredAttributeAttribute
System.Runtime.InteropServices.ArrayWithOffset
System.Runtime.InteropServices.DispIdAttribute
System.Runtime.InteropServices.ClassInterfaceType
System.Runtime.InteropServices.ClassInterfaceAttribute
System.Runtime.InteropServices.ComVisibleAttribute
System.Runtime.InteropServices.LCIDConversionAttribute
System.Runtime.InteropServices.ComRegisterFunctionAttribute
System.Runtime.InteropServices.ComUnregisterFunctionAttribute
System.Runtime.InteropServices.ProgIdAttribute
System.Runtime.InteropServices.ImportedFromTypeLibAttribute
System.Runtime.InteropServices.IDispatchImplType
System.Runtime.InteropServices.IDispatchImplAttribute
System.Runtime.InteropServices.ComSourceInterfacesAttribute
System.Runtime.InteropServices.ComConversionLossAttribute
System.Runtime.InteropServices.TypeLibTypeFlags
System.Runtime.InteropServices.TypeLibFuncFlags
System.Runtime.InteropServices.TypeLibVarFlags
System.Runtime.InteropServices.TypeLibTypeAttribute
System.Runtime.InteropServices.TypeLibFuncAttribute
System.Runtime.InteropServices.TypeLibVarAttribute
System.Runtime.InteropServices.ComImportAttribute
System.Runtime.InteropServices.PreserveSigAttribute
System.Runtime.InteropServices.ComAliasNameAttribute
System.Runtime.InteropServices.AutomationProxyAttribute
System.Runtime.InteropServices.PrimaryInteropAssemblyAttribute
System.Runtime.InteropServices.CoClassAttribute
System.Runtime.InteropServices.ComEventInterfaceAttribute
System.Runtime.InteropServices.COMException
System.Runtime.InteropServices.ComMemberType
System.Runtime.InteropServices.CurrencyWrapper
System.Runtime.InteropServices.DispatchWrapper
System.Runtime.InteropServices.ErrorWrapper
System.Runtime.InteropServices.ExtensibleClassFactory
System.Runtime.InteropServices.HandleRef
System.Runtime.InteropServices.InvalidComObjectException
System.Runtime.InteropServices.InvalidOleVariantTypeException
System.Runtime.InteropServices.TypeLibImporterFlags
System.Runtime.InteropServices.ExporterEventKind
System.Runtime.InteropServices.ITypeLibExporterNotifySink
System.Runtime.InteropServices.ITypeLibConverter
System.Runtime.InteropServices.MarshalDirectiveException
System.Runtime.InteropServices.ObjectCreationDelegate
System.Runtime.InteropServices.RuntimeEnvironment
System.Runtime.InteropServices.RegistrationServices
System.Runtime.InteropServices.SafeArrayRankMismatchException
System.Runtime.InteropServices.SafeArrayTypeMismatchException
System.Runtime.InteropServices.SEHException
System.Runtime.InteropServices.TypeLibConverter
System.Runtime.InteropServices.BIND_OPTS
System.Runtime.InteropServices.UCOMIBindCtx
System.Runtime.InteropServices.UCOMIConnectionPointContainer
System.Runtime.InteropServices.UCOMIConnectionPoint
System.Runtime.InteropServices.UCOMIEnumMoniker
System.Runtime.InteropServices.CONNECTDATA
System.Runtime.InteropServices.UCOMIEnumConnections
System.Runtime.InteropServices.UCOMIEnumConnectionPoints
System.Runtime.InteropServices.UCOMIEnumString
System.Runtime.InteropServices.UCOMIEnumVARIANT
System.Runtime.InteropServices.FILETIME
System.Runtime.InteropServices.UCOMIMoniker
System.Runtime.InteropServices.UCOMIPersistFile
System.Runtime.InteropServices.UCOMIRunningObjectTable
System.Runtime.InteropServices.STATSTG
System.Runtime.InteropServices.UCOMIStream
System.Runtime.InteropServices.DESCKIND
System.Runtime.InteropServices.BINDPTR
System.Runtime.InteropServices.UCOMITypeComp
System.Runtime.InteropServices.TYPEKIND
System.Runtime.InteropServices.TYPEFLAGS
System.Runtime.InteropServices.IMPLTYPEFLAGS
System.Runtime.InteropServices.TYPEATTR
System.Runtime.InteropServices.FUNCDESC
System.Runtime.InteropServices.IDLFLAG
System.Runtime.InteropServices.IDLDESC
System.Runtime.InteropServices.PARAMFLAG
System.Runtime.InteropServices.PARAMDESC
System.Runtime.InteropServices.TYPEDESC
System.Runtime.InteropServices.ELEMDESC
System.Runtime.InteropServices.VARDESC
System.Runtime.InteropServices.DISPPARAMS
System.Runtime.InteropServices.EXCEPINFO
System.Runtime.InteropServices.FUNCKIND
System.Runtime.InteropServices.INVOKEKIND
System.Runtime.InteropServices.CALLCONV
System.Runtime.InteropServices.FUNCFLAGS
System.Runtime.InteropServices.VARFLAGS
System.Runtime.InteropServices.UCOMITypeInfo
System.Runtime.InteropServices.SYSKIND
System.Runtime.InteropServices.LIBFLAGS
System.Runtime.InteropServices.TYPELIBATTR
System.Runtime.InteropServices.UCOMITypeLib
System.Runtime.InteropServices.UnknownWrapper
System.Runtime.Remoting.IObjectHandle
System.Runtime.Remoting.IRemotingTypeInfo
System.Runtime.Remoting.IChannelInfo
System.Runtime.Remoting.IEnvoyInfo
System.Runtime.Remoting.RemotingConfiguration
System.Runtime.Remoting.TypeEntry
System.Runtime.Remoting.ActivatedClientTypeEntry
System.Runtime.Remoting.ActivatedServiceTypeEntry
System.Runtime.Remoting.WellKnownClientTypeEntry
System.Runtime.Remoting.WellKnownServiceTypeEntry
System.Runtime.Remoting.RemotingException
System.Runtime.Remoting.ServerException
System.Runtime.Remoting.RemotingTimeoutException
System.Runtime.Remoting.RemotingServices
System.Runtime.Remoting.InternalRemotingServices
System.Runtime.Remoting.SoapServices
System.Runtime.Remoting.Activation.UrlAttribute
System.Runtime.Remoting.Messaging.IMessageSink
System.Runtime.Remoting.Messaging.AsyncResult
System.Runtime.Remoting.Messaging.CallContext
System.Runtime.Remoting.Messaging.ILogicalThreadAffinative
System.Runtime.Remoting.Messaging.InternalMessageWrapper
System.Runtime.Remoting.Messaging.IMethodCallMessage
System.Runtime.Remoting.Messaging.MethodCallMessageWrapper
System.Runtime.Remoting.Messaging.HeaderHandler
System.Runtime.Remoting.Messaging.IMessageCtrl
System.Runtime.Remoting.Messaging.IRemotingFormatter
System.Runtime.Remoting.Messaging.ReturnMessage
System.Runtime.Remoting.Messaging.MethodCall
System.Runtime.Remoting.Messaging.ConstructionCall
System.Runtime.Remoting.Messaging.MethodResponse
System.Runtime.Remoting.Messaging.ConstructionResponse
System.Runtime.Remoting.Messaging.MethodReturnMessageWrapper
System.Runtime.Remoting.Messaging.OneWayAttribute
System.Runtime.Remoting.Messaging.MessageSurrogateFilter
System.Runtime.Remoting.Messaging.RemotingSurrogateSelector
System.Runtime.Remoting.Contexts.CrossContextDelegate
System.Runtime.Remoting.Contexts.ContextProperty
System.Runtime.Remoting.Contexts.IContextPropertyActivator
System.Runtime.Remoting.Contexts.IContributeClientContextSink
System.Runtime.Remoting.Contexts.IContributeDynamicSink
System.Runtime.Remoting.Contexts.IContributeEnvoySink
System.Runtime.Remoting.Contexts.IContributeObjectSink
System.Runtime.Remoting.Contexts.IContributeServerContextSink
System.Runtime.Serialization.Formatters.InternalRM
System.Runtime.Serialization.Formatters.InternalST
System.Runtime.Serialization.Formatters.SoapMessage
System.Runtime.Serialization.Formatters.SoapFault
System.Runtime.Serialization.Formatters.ServerFault
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
System.Security.Cryptography.CryptoConfig
System.Security.Cryptography.KeyedHashAlgorithm
System.Security.Cryptography.HMACSHA1
System.Security.Cryptography.MACTripleDES
System.Security.Cryptography.MaskGenerationMethod
System.Security.Cryptography.PasswordDeriveBytes
System.Security.Cryptography.PKCS1MaskGenerationMethod
System.Security.Cryptography.RC2
System.Security.Cryptography.RC2CryptoServiceProvider
System.Security.Cryptography.RSACryptoServiceProvider
System.Security.Cryptography.RSAOAEPKeyExchangeDeformatter
System.Security.Cryptography.RSAOAEPKeyExchangeFormatter
System.Security.Cryptography.RSAPKCS1KeyExchangeDeformatter
System.Security.Cryptography.RSAPKCS1KeyExchangeFormatter
System.Security.Cryptography.RSAPKCS1SignatureDeformatter
System.Security.Cryptography.RSAPKCS1SignatureFormatter
System.Security.Cryptography.SHA1Managed
System.Security.Cryptography.TripleDES
System.Security.Cryptography.TripleDESCryptoServiceProvider
System.Security.Permissions.EnvironmentPermission
System.Security.Permissions.FileDialogPermission
System.Security.Permissions.IsolatedStorageFilePermission
System.Security.Permissions.PrincipalPermissionAttribute
System.Security.Permissions.SecurityPermissionAttribute
System.Security.Permissions.PublisherIdentityPermissionAttribute
System.Security.Permissions.PublisherIdentityPermission
System.Security.Permissions.ReflectionPermission
System.Security.Permissions.RegistryPermission
System.Security.Permissions.PrincipalPermission
System.Security.Permissions.SiteIdentityPermission
System.Security.Permissions.StrongNameIdentityPermission
System.Security.Permissions.StrongNamePublicKeyBlob
System.Security.Permissions.UIPermission
System.Security.Permissions.UrlIdentityPermission
System.Security.Permissions.ZoneIdentityPermission
System.Security.Policy.ApplicationDirectory
System.Security.Policy.ApplicationDirectoryMembershipCondition
System.Security.Policy.FirstMatchCodeGroup
System.Security.Policy.Hash
System.Security.Policy.HashMembershipCondition
System.Security.Policy.NetCodeGroup
System.Security.Policy.PermissionRequestEvidence
System.Security.Policy.Publisher
System.Security.Policy.PublisherMembershipCondition
System.Security.Policy.Site
System.Security.Policy.SiteMembershipCondition
System.Security.Policy.StrongName
System.Security.Policy.StrongNameMembershipCondition
System.Security.Policy.UnionCodeGroup
System.Security.Policy.Url
System.Security.Policy.UrlMembershipCondition
System.Security.Policy.Zone
System.Security.Policy.ZoneMembershipCondition
System.Security.Principal.WindowsIdentity
System.Security.Principal.WindowsImpersonationContext
System.Security.Principal.WindowsPrincipal
System.Threading.CompressedStack
+4 -4
View File
@@ -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>
+18 -58
View File
@@ -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.
@@ -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
View File
@@ -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>
-1
View File
@@ -22,7 +22,6 @@
1,Documentation,documentation.html,documentation.src
1,Class Docs,classlib-doc.html,classlib-doc.src
1,Test Suite,testing.html,testing.src
1,Mono TODO,mono-todo.html,mono-todo.src
1,Tools,tools.html,tools.src
1,Porting,porting.html,porting.src
2,PowerPC,ppc.html,ppc.src
-1
View File
@@ -46,7 +46,6 @@ OBJECTS= \
deploy/mbas.html \
deploy/mono-beginning.html \
deploy/mono-contribution-howto.html \
deploy/mono-todo.html \
deploy/monodoc-xml.html \
deploy/other.html \
deploy/papers.html \
+8 -39
View File
@@ -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 -&gt; NUnit2 conversion</task>
<task>Mono Handbook, Documentation</task>
<task>Stubbing</task>
<task>DiaCanvas#</task>
<task>Mono Handbook work</task>
<task>Various fixes</task>
@@ -858,13 +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,38 +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>none.png</image>
<location>Cambridge, MA</location>
<organization></organization>
<description>Makefile Magician</description>
<tasks>
<task>MCS build system </task>
<task>Gtk# Documentation.</task>
</tasks>
Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.4 KiB

+5 -6
View File
@@ -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>
+1 -2
View File
@@ -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
-42
View File
@@ -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
-88
View File
@@ -1,88 +0,0 @@
.\"
.\" makecert manual page.
.\" Copyright 2003 Motus Technologies
.\" Author:
.\" Sebastien Pouliot ([email protected])
.\"
.TH Mono "MakeCert"
.SH NAME
MakeCert \- Create X.509 certificates for test purposes
.SH SYNOPSIS
.PP
.B MakeCert [options] certificate
.SH DESCRIPTION
Create an X.509 certificate using the provided informations. This
is useful for testing Authenticode signatures, SSL and S/MIME
technologies.
.SH PARAMETERS
.TP
.I "-# num"
Certificate serial number
.TP
.I "-n dn"
Subject Distinguished Name
.TP
.I "-in dn"
Issuert Distinguished Name
.TP
.I "-r"
Create a self-signed (root) certificate
.TP
.I "-sv pkvfile"
Private key file (.PVK) for the subject (created if missing)
.TP
.I "-iv pvkfile"
Private key file (.PVK) for the issuer
.TP
.I "-ic certfile"
Extract the issuer's name from the specified certificate
.TP
.I "-?"
Help (display this help message)
.TP
.I "-!"
Extended help (for advanced options)
.TP
.I "-a hash"
Select hash algorithm. Only MD5 and SHA1 are supported.
.TP
.I "-b date"
The date since when the certificate is valid (notBefore).
.TP
.I "-cy [authority|end]"
Basic constraints. Select Authority or End-Entity certificate.
.TP
.I "-e date"
The date until when the certificate is valid (notAfter).
.TP
.I "-eku oid[,oid]"
Add some extended key usage OID to the certificate.
.TP
.I "-h number"
Add a path length restriction to the certificate chain.
.TP
.I "-ic cert"
Take the issuer's name from the specified certificate.
.TP
.I "-in name"
Take the issuer's name from the specified parameter.
.TP
.I "-iv pvkfile"
Sign the certificate using the private key inside the PVK file.
.TP
.I "-m number"
Certificate validity period (in months).
.TP
.I "-sv pvkfile"
Create a new PVK file if non-existant, otherwise use the PVK file as the subject public key.
.SH AUTHOR
Written by Sebastien Pouliot
.SH COPYRIGHT
Copyright (C) 2003 Motus Technologies.
Released under BSD license.
.SH MAILING LISTS
Visit http://mail.ximian.com/mailman/mono-list for details.
.SH WEB SITE
Visit: http://www.go-mono.com for details
.SH SEE ALSO
.BR signcode(1)
-13
View File
@@ -1,13 +0,0 @@
<?xml version="1.0"?>
<manpages>
<manpage name="Mono" page="mono.1" />
<manpage name="Mint" page="mono.1" />
<manpage name="Mcs" page="mcs.1" />
<manpage name="Ilasm" page="ilasm.1" />
<manpage name="Monodis" page="mono.1" />
<manpage name="Cilc" page="cilc.1" />
<manpage name="Sql#" page="sqlsharp.1" />
<manpage name="SecUtil" page="secutil.1" />
<manpage name="MonoStyle" page="monostyle.1" />
</manpages>
-4
View File
@@ -1,4 +0,0 @@
<?xml version="1.0"?>
<monodoc>
<source provider="man" basefile="tree" path="manpages"/>
</monodoc>
-89
View File
@@ -1,92 +1,3 @@
2003-07-22 Peter Williams <[email protected]>
* README: INSTALL.txt, not INSTALL.
2003-07-20 Peter Williams <[email protected]>
* nunit20/nunit-console/Makefile (PROGRAM): Put nunit-console.exe
in $(topdir)/class/lib so we can find our DLL's.
2003-07-18 Peter Williams <[email protected]>
* build/library.make (dist-local): Fancy make dist magic gives
way to boring old 'for'.
* build/executable.make (dist-local): Ditto.
2003-07-17 Peter Williams <[email protected]>
* build/profiles/default.make: Actually fix this. Use the platform
compiler all the way.
2003-07-17 Peter Williams <[email protected]>
* build/profiles/default.make: Try to make this smarter so
that we can build on Windows. Specifically, don't require
the mono runtime. Combined with the corlib $(BOOT_COMPILE) change,
this should make corlib build out of the box, I think.
2003-07-16 Peter Williams <[email protected]>
A whole passel of build system changes. Doc updates:
* build/README.makefiles: Doc updates.
* build/profiles/net_1_0.make: Doc changes.
* INSTALL.txt: A few more touchups.
Better defaults:
* build/config-default.make (prefix): Default install prefix
should be /usr/local.
* build/profiles/bootstrap.make: This profile ...
* build/profiles/default.make: ... is now the default.
* build/profiles/atomic.make: And the default is now this.
Fixes for pre-build checks:
* Makefile: Do the platform and (new) profile checks
before the build, which took some infrastructure changes.
* build/rules.make: Allow a Makefile to specify its own all/install/etc
targets.
* build/profiles/default.make (profile-check): Add a blank
target here.
* build/profiles/atomic.make: Check for a full MCS install to
build against.
HP/UX fixes with help from Bernie Solomon:
* build/config-default.make (ECHO_ESCAPE): HP/UX 'echo'
doesn't need a -e parameter to interpret escape codes. Test for
that and define a configuration parameter.
* build/library.make ($(makefrag)): Use $(ECHO_ESCAPE)
instead of assuming that 'echo -e' will interpret escape
codes.
* build/executable.make ($(makefrag)): Here too.
A make distcheck fix:
* Makefile: Inherit the current prefix so that the build can
find the right System.Xml.dll.
And Windows build fixes with the invaluable help of Sebastian
Pouliot (in various subdirectories).
2003-07-14 Peter Williams <[email protected]>
* build/rules.make (dist-recursive): Fix recursive rules
to work on HP/UX /bin/sh. Patch from Bernie Solomon
<[email protected]>.
2003-05-10 Gonzalo Paniagua Javier <[email protected]>
* makefile:
+29 -122
View File
@@ -1,146 +1,53 @@
Basic Installation
==================
The Mono project has developed mono, a CLI runtime. The build process
of each of these depends on nothing more than a C compiler and glib2.
The Mono project has developed mono, an x86-specific CL JIT compiler and
mint, a portable CLI interpreter. The build process of each of these
depends on nothing more than a C compiler, glib2 and libgc.
However, to provide a working runtime environment, these programs must
be supplemented by the class libraries, which are written in C#. This
package contains the components written in C#: class libraries,
compilers and tools.
be supplemented by corlib, a CLR assembly to which they are closely
tied. This package provides the C# sources for corlib as well as some
additional assemblies and mcs, the Mono C# compiler.
Build Process for Users.
========================
To build this package, you must already have a C# compiler installed.
Build instructions for *NIX and Microsoft Windows follow.
If you only want to build a snapshot or a fresh CVS checkout of the
sources, you should go into the `mono' sibling directory and issue the
following command:
Building mcs on *NIX
====================
./autogen --prefix=/usr/local
make fullbuild
That will build and install the code in a single pass. The
compilation is bundled with the build due to depedencies on the class
libraries on the runtime.
Build Features for Developers.
==============================
These instructions apply to both Linux and Windows. To build this
package, you must already have a C# compiler installed. This means
that to build on Linux, you need to get a distribution of the MCS
binaries; these are called monocharges. See README.building for
information on where to get them. On Windows, you can just use the
Microsoft compiler. You also need GNU make to build the software (on
Windows, you will need for example the Cygwin environment setup).
mcs provides a set of makefiles which make it easy to build and install
mcs on *NIX systems like Linux or FreeBSD where mcs is already
installed.
To build the compiler and class libraries, run:
make
make -f makefile.gnu
The libraries will be placed in the directory class/lib/ and the mcs
compiler executable in mcs/.
To install them, run the following:
To install them, run the following, where prefix identifies where you
want the files installed:
make install
The default prefix is /usr/local. To change this configuration option type:
echo prefix=/your-prefix >> build/config.make
If you get "corlib out of sync" errors, try
make PROFILE="atomic"
The difference between the two modes is explained farther down.
Monocharges
===========
make -f makefile.gnu install prefix=/usr/local
If you are tracking Mono's development, you may sometimes need to share
the compiled libraries with others, you can do:
the compiled libraries with others. If you want to produce an easily
distributable tarball, run:
make monocharge
make -f makefile.gnu dist
Or a light version, which contains only the essential libraries and
results in a much smaller file:
Building mcs on Windows
=======================
make monocharge-lite
It is also possible to build mcs on Windows using the Microsoft .NET
framework. This may be convenient if you do not have access to a working
mcs setup. To build the compiler and class libraries, run:
Configuration
=============
make
If you want to change the configuration options for the build process,
place your configuration options in build/config.make
The libraries will be placed in the directory class/lib/ and the mcs
compiler executable in mcs/. They can then be copied to /usr/lib and
/usr/bin or wherever desired on the target system.
A list of variables that control the build are listed in the file
build/config-default.make.
Build profiles? What?
======================
Don't worry about them too much. If you're wondering which to use:
use the default if you can (that's why it's the default!) and use
the atomic if you have to.
The default profile uses the C# compiler and class libaries as they
are built. This lets you build MCS without needing to have already
installed it, but can fail if the libraries change significantly.
(This is the source of the dreaded "corlib out of sync" warning, most
of the time.)
The atomic profile tries to use the system compiler and preexisting
MCS libraries. New libaries are built against this constant reference
point, so if a newly built library has a binary incompatibility, the
rest of your build can proceed.
If you want to always use the atomic profile, run this command:
echo PROFILE=atomic >> build/config.make
More About the Build System
===========================
More information is found in build/README.*. Here's a quick rundown
of the features:
* Unified build system for Windows and Linux. Windows is still
fairly untested, but "should work." Unfortunately I don't
have a Windows machine to test on, but Gonzalo can get
corlib to build I think and that's about as complicated as
it gets.
* Profile support. 'make PROFILE=profilename' or 'export
PROFILE=profilename ; make' will work. Profiles are defined
in build/profiles/profilename.make ; right now there isn't
too much going on. The 'bootstrap' profile will build the
way makefile.gnu did on Linux, by setting MONO_PATH and
using mcs/mcs.exe; the default profile will build against
the existing system libraries and compile with 'mcs', which
should reduce a lot of 'corlib out of sync' warnings.
* Important variables are shared among makefiles now; you can
edit build/config.make (see build/config-default.make for a
template) and give global settings, or just have a much
saner time of writing new makefiles.
* Response files, stamps, and other build trivia now all land
in build/deps/, making the library build directories
cleaner.
* Test libraries now live in class/Library/Library_test.dll,
not class/Library/Test. 'make test' will build the test DLL,
'make run-test' will actually run the nunit tests. Set the
variable TEST_HARNESS to run with a program other than
nunit-console (for example, nunit-gtk).
* Standardized recursive targets: all, clean, install, test,
run-test. Read build/README.makefiles for definitions of
what they should do
* (Relatively) sane 'make dist' target; 'make distcheck'
support; cute 'make monocharge' and 'make monocharge-lite'
targets. They're made possible because 'make install' now
supports DESTDIR a la automake, which I'm sure someone cares
about.
-107
View File
@@ -1,107 +0,0 @@
thisdir := .
SUBDIRS := build jay mcs class mbas nunit20 monoresgen ilasm tools tests errors docs
OVERRIDE_BARE_TARGETS = hells yeah
include build/rules.make
# Define these ourselves to that the platform checks come first
all: platform-check profile-check all-recursive #all-local
install: platform-check profile-check install-recursive #install-local
test: platform-check profile-check test-recursive #test-local
run-test: run-test-recursive #run-test-local
clean: clean-recursive #clean-local
# fun specialty targets
testcorlib:
@cd class/corlib && $(MAKE) test run-test
# Disting. We need to override $(distdir) here.
package := mcs-$(VERSION)
top_distdir = $(dots)/$(package)
distdir = $(top_distdir)
export package
DISTFILES = \
AUTHORS \
ChangeLog \
COPYING \
COPYING.LIB \
INSTALL.txt \
LICENSE \
LICENSE.GPL \
LICENSE.LGPL \
Makefile \
mkinstalldirs \
MIT.X11 \
MonoIcon.png \
README \
README.building \
ScalableMonoIcon.svg \
winexe.in
dist-pre:
rm -rf $(package)
dist-post:
tar cvzf $(package).tar.gz $(package)
dist-local: dist-default
dist-tarball: dist-pre dist-recursive dist-post
dist: dist-tarball
rm -rf $(package)
# the egrep -v is kind of a hack (to get rid of the makefrags)
# but otherwise we have to make dist then make clean which
# is sort of not kosher. And it breaks with DIST_ONLY_SUBDIRS.
#
# We need to set prefix on make so class/System/Makefile can find
# the installed System.Xml to build properly
distcheck:
rm -rf InstallTest Distcheck-MCS ; \
mkdir InstallTest ; \
destdir=`cd InstallTest && pwd` ; \
$(MAKE) dist-tarball || exit 1 ; \
mv $(package) Distcheck-MCS ; \
(cd Distcheck-MCS && \
make prefix=$(prefix) && make test && make install DESTDIR="$$destdir" && \
make clean && make dist || exit 1) || exit 1 ; \
mv Distcheck-MCS $(package) ; \
tar tzf $(package)/$(package).tar.gz |sed -e 's,/$$,,' |sort >distdist.list ; \
rm $(package)/$(package).tar.gz ; \
tar tzf $(package).tar.gz |sed -e 's,/$$,,' |sort >before.list ; \
find $(package) |egrep -v '(makefrag|response)' |sed -e 's,/$$,,' |sort >after.list ; \
cmp before.list after.list || exit 1 ; \
cmp before.list distdist.list || exit 1 ; \
rm -f before.list after.list distdist.list ; \
rm -rf $(package) InstallTest
monocharge:
chargedir=monocharge-`date -u +%Y%m%d` ; \
mkdir "$$chargedir" ; \
DESTDIR=`cd "$$chargedir" && pwd` ; \
$(MAKE) install DESTDIR="$$DESTDIR" || exit 1 ; \
tar cvzf "$$chargedir".tgz "$$chargedir" ; \
rm -rf "$$chargedir"
# A bare-bones monocharge.
monocharge-lite:
chargedir=monocharge-lite-`date -u +%Y%m%d` ; \
mkdir "$$chargedir" ; \
DESTDIR=`cd "$$chargedir" && pwd` ; \
$(MAKE) -C mcs install DESTDIR="$$DESTDIR" || exit 1; \
$(MAKE) -C class/corlib install DESTDIR="$$DESTDIR" || exit 1; \
$(MAKE) -C class/System install DESTDIR="$$DESTDIR" || exit 1; \
$(MAKE) -C class/System.XML install DESTDIR="$$DESTDIR" || exit 1; \
$(MAKE) -C class/Mono.CSharp.Debugger install DESTDIR="$$DESTDIR" || exit 1; \
tar cvzf "$$chargedir".tgz "$$chargedir" ; \
rm -rf "$$chargedir"
+1 -1
View File
@@ -2,7 +2,7 @@
This contains the Mono C# compiler as well as the Mono runtime
library.
See INSTALL.txt for a guide to building and installing mcs.
See INSTALL for a guide to building and installing mcs.
Layout:
+33
View File
@@ -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
-2
View File
@@ -1,2 +0,0 @@
pre-config.make
config.make
-73
View File
@@ -1,73 +0,0 @@
2003-08-03 Gonzalo Paniagua Javier <[email protected]>
* config-default.make: the /nowarn arguments are now set on a per
library basis.
2003-07-29 Gonzalo Paniagua Javier <[email protected]>
* executable.make: install-local depends on the program too.
2003-07-25 Peter Williams <[email protected]>
* rules.make (run-test): Make it depend on 'test-local'
then 'run-test-local' after 'run-test-recursive'. This way,
'make run-test' from the toplevel doesn't recurse through all
the directories doing a make test before we run anything.
2003-07-24 Gonzalo Paniagua Javier <[email protected]>
* rules.make: run-test depends now on 'test'.
2003-07-24 Gonzalo Paniagua Javier <[email protected]>
* rules.make: set corlib to PLATFORM_CORLIB if this is defined.
2003-07-22 Peter Williams <[email protected]>
* rules.make (withmcs): Add this developer utility target.
2003-07-20 Peter Williams <[email protected]>
* README.platforms: Update docs for changes below.
* platforms/win32.make (PLATFORM_CORLIB): Set this variable
to 'mscorlib.dll', instead of $(corlib) which everything links
against. *Almost* everything should link against our corlib --
with the exception of corlib_cmp and corlib_res.
* platforms/linux.make: Same here: corlib.dll
* rules.make: Define $(corlib) here.
2003-07-20 Peter Williams <[email protected]>
* config-default.make (TEST_RUNTIME): Use the platform runtime
to run tests, by default.
* profiles/default.make (TEST_RUNTIME): If our test runtime is
mono, use the --debug flag.
* executable.make (sourcefile): Add a basename so that we can
find the nunit sources and so we behave a bit more like
library.make
* config-default.make (TEST_HARNESS): Find nunit-console in its
new home.
2003-07-20 Peter Williams <[email protected]>
* library.make ($(response)): Do a "Creating ..." line here.
* executable.make ($(response)): Same.
* config-default.make: Make warning more forceful.
* rules.make: Define a useful 'PLATFORM_MONO_NATIVE' that is
set if the platform does not have a native runtime (ie, linux).
Also reorder some definitions.
2003-07-20 Peter Williams <[email protected]>
* Created. See ../ChangeLog for entries earlier than
this.
-22
View File
@@ -1,22 +0,0 @@
thisdir = build
SUBDIRS =
include ../build/rules.make
all-local install-local test-local run-test-local clean-local:
DISTFILES = \
README.makefiles \
README.platforms \
README.configury \
config-default.make \
executable.make \
library.make \
rules.make \
platforms/linux.make \
platforms/win32.make \
profiles/default.make \
profiles/atomic.make \
profiles/net_1_0.make
dist-local: dist-default
mkdir $(distdir)/deps
-23
View File
@@ -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.)
-736
View File
@@ -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
-41
View File
@@ -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.
-38
View File
@@ -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
-3
View File
@@ -1,3 +0,0 @@
*.makefrag
*.response
*.stamp
View File
Whitespace-only changes.
-73
View File
@@ -1,73 +0,0 @@
# -*- makefile -*-
#
# The rules for building a program.
# I'd rather not create a response file here,
# but since on Win32 we need to munge the paths
# anyway, we might as well.
base_prog = $(shell basename $(PROGRAM))
sourcefile = $(base_prog).sources
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
response = $(depsdir)/$(base_prog).response
else
response = $(sourcefile)
endif
stampfile = $(depsdir)/$(base_prog).stamp
makefrag = $(depsdir)/$(base_prog).makefrag
pdb = $(patsubst %.exe,%.pdb,$(PROGRAM))
all-local: $(PROGRAM)
install-local: $(PROGRAM)
$(MKINSTALLDIRS) $(DESTDIR)$(prefix)/bin
$(INSTALL_BIN) $(PROGRAM) $(DESTDIR)$(prefix)/bin
clean-local:
-rm -f *.exe $(BUILT_SOURCES) $(CLEAN_FILES) $(pdb) $(stampfile) $(makefrag)
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
-rm -f $(response)
endif
ifndef HAS_TEST
test-local: $(PROGRAM)
run-test-local:
endif
DISTFILES = $(sourcefile) $(EXTRA_DISTFILES)
dist-local: dist-default
for f in `cat $(sourcefile)` ; do \
dest=`dirname $(distdir)/$$f` ; \
$(MKINSTALLDIRS) $$dest && cp $$f $$dest || exit 1 ; \
done
# Changing makefile probably means changing the
# sources, so let's be safe and add a Makefile dep
$(PROGRAM): $(makefrag) $(response) $(stampfile)
$(CSCOMPILE) /target:exe /out:$@ $(BUILT_SOURCES) @$(response)
$(makefrag): $(sourcefile)
@echo Creating $@ ...
@echo "HAVE_MAKEFRAG = yes" >[email protected]
@echo "$(stampfile): $(BUILT_SOURCES) \\" >>[email protected]
@cat $< |sed -e 's,\.cs[ \t]*$$,\.cs \\,' >>[email protected]
@cat [email protected] |sed -e '$$s, \\$$,,' >$@
@$(ECHO_ESCAPE) "\ttouch \$$@" >>$@
@rm -rf [email protected]
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
$(response): $(sourcefile)
@echo Creating $@ ...
@cat $< |$(PLATFORM_CHANGE_SEPARATOR_CMD) >$@
endif
-include $(makefrag)
ifndef HAVE_MAKEFRAG
$(stampfile):
touch $@
endif
-132
View File
@@ -1,132 +0,0 @@
# -*- makefile -*-
#
# The rules for building our class libraries.
#
# The NO_TEST stuff is not too pleasant but whatcha
# gonna do.
# All the dep files now land in the same directory so we
# munge in the library name to keep the files from clashing.
sourcefile = $(LIBRARY).sources
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
response = $(depsdir)/$(LIBRARY).response
else
response = $(sourcefile)
endif
makefrag = $(depsdir)/$(LIBRARY).makefrag
stampfile = $(depsdir)/$(LIBRARY).stamp
the_lib = $(topdir)/class/lib/$(LIBRARY)
the_pdb = $(patsubst %.dll,%.pdb,$(the_lib))
ifndef NO_TEST
test_lib = $(patsubst %.dll,%_test.dll,$(LIBRARY))
test_pdb = $(patsubst %.dll,%.pdb,$(test_lib))
test_sourcefile = $(test_lib).sources
test_response = $(depsdir)/$(test_lib).response
test_makefrag = $(depsdir)/$(test_lib).makefrag
test_stampfile = $(depsdir)/$(test_lib).stamp
test_flags = /r:$(the_lib) /r:$(topdir)/class/lib/NUnit.Framework.dll $(TEST_MCS_FLAGS)
endif
all-local: $(the_lib)
install-local: $(the_lib)
$(MKINSTALLDIRS) $(DESTDIR)$(prefix)/lib
$(INSTALL_LIB) $(the_lib) $(DESTDIR)$(prefix)/lib
clean-local:
-rm -f $(the_lib) $(makefrag) $(test_lib) \
$(test_makefrag) $(test_response) \
$(stampfile) $(test_stampfile) \
$(the_pdb) $(test_pdb) \
TestResult.xml
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
-rm -rf $(response)
endif
ifndef NO_TEST
test-local: $(the_lib) $(test_lib)
run-test-local:
$(TEST_RUNTIME) $(TEST_HARNESS) $(test_lib)
else
test-local: $(the_lib)
run-test-local:
endif
DISTFILES = $(sourcefile) $(test_sourcefile) $(EXTRA_DISTFILES)
ifdef NO_TEST
TEST_FILES =
else
TEST_FILES = `cat $(test_sourcefile) |sed -e 's,^\(.\),Test/\1,'`
endif
dist-local: dist-default
for f in `cat $(sourcefile)` $(TEST_FILES) ; do \
dest=`dirname $(distdir)/$$f` ; \
$(MKINSTALLDIRS) $$dest && cp $$f $$dest || exit 1 ; \
done
# Fun with dependency tracking
$(the_lib): $(makefrag) $(stampfile) $(response)
$(CSCOMPILE) $(LIBRARY_FLAGS) $(LIB_MCS_FLAGS) /target:library /out:$@ @$(response)
$(makefrag): $(sourcefile)
@echo Creating $@ ...
@echo "HAVE_MAKEFRAG = yes" >[email protected]
@echo "$(stampfile): \\" >>[email protected]
@cat $< |sed -e 's,\.cs[ \t]*$$,\.cs \\,' >>[email protected]
@cat [email protected] |sed -e '$$s, \\$$,,' >$@
@$(ECHO_ESCAPE) "\ttouch \$$@" >>$@
@rm -rf [email protected]
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
$(response): $(sourcefile)
@echo Creating $@ ...
@cat $< |$(PLATFORM_CHANGE_SEPARATOR_CMD) >$@
endif
-include $(makefrag)
ifndef HAVE_MAKEFRAG
$(stampfile):
touch $@
endif
# for now, don't give any /lib flags or set MONO_PATH, since we
# give a full path to the assembly.
ifndef NO_TEST
$(test_lib): $(test_makefrag) $(the_lib) $(test_response) $(test_stampfile)
$(CSCOMPILE) /target:library /out:$@ $(test_flags) @$(test_response)
$(test_response): $(test_sourcefile)
@echo Creating $@ ...
ifdef PLATFORM_CHANGE_SEPARATOR_CMD
@cat $< |sed -e 's,^\(.\),Test/\1,' |$(PLATFORM_CHANGE_SEPARATOR_CMD) >$@
else
@cat $< |sed -e 's,^\(.\),Test/\1,' >$@
endif
$(test_makefrag): $(test_response)
@echo Creating $@ ...
@echo "HAVE_TEST_MAKEFRAG = yes" >[email protected]
@echo "$(test_stampfile): \\" >>[email protected]
@cat $< |sed -e 's,\.cs[ \t]*$$,\.cs \\,' >>[email protected]
@cat [email protected] |sed -e '$$s, \\$$,,' >$@
@$(ECHO_ESCAPE) "\ttouch \$$@" >>$@
@rm -rf [email protected]
-include $(test_makefrag)
endif
ifndef HAVE_TEST_MAKEFRAG
$(test_stampfile):
touch $@
endif
-44
View File
@@ -1,44 +0,0 @@
# -*- makefile -*-
#
# Platform-specific makefile rules. This one's for linux.
#
PLATFORM_DEBUG_FLAGS = -g
PLATFORM_MCS_FLAGS =
PLATFORM_RUNTIME = $(RUNTIME)
PLATFORM_CORLIB = corlib.dll
BOOTSTRAP_MCS = mcs
# Define this if this ever will work on Linux
# PLATFORM_MAKE_CORLIB_CMP = yes
# This is for the security permission attribute problem
# on windows
PLATFORM_TWEAK_CORLIB_SOURCES = cat
# This is for changing / to \ on windows
# Don't define it so we don't needlessly copy the sources
# file. This command is handy for testing:
#
# PLATFORM_CHANGE_SEPARATOR_CMD=sed -e 's,/,/./,g'
hidden_prefix = .
hidden_suffix =
platform-check:
@if ! type $(BOOTSTRAP_MCS) >/dev/null 2>&1 ; then \
echo "*** You need a C# compiler installed to build MCS." ; \
echo "*** Read README.building for information on how to bootstrap" ; \
echo "*** a Mono installation." ; \
exit 1 ; \
fi
# I tried this but apparently Make's version strings aren't that
# ... consistent between releases. Whatever.
#
# @if ! $(MAKE) --version |grep '^GNU Make version 3' 1>/dev/null 2>&1 ; then \
# echo "*** You need to build MCS with GNU make. Try \`gmake'" ; \
# exit 1 ; \
# fi
-21
View File
@@ -1,21 +0,0 @@
# -*- makefile -*-
#
# Win32 platform-specific makefile rules.
#
PLATFORM_DEBUG_FLAGS = /debug+ /debug:full
PLATFORM_MCS_FLAGS = /nologo /optimize
PLATFORM_RUNTIME =
PLATFORM_CORLIB = mscorlib.dll
BOOTSTRAP_MCS = csc.exe
MCS = $(BOOTSTRAP_MCS)
PLATFORM_MAKE_CORLIB_CMP = yes
PLATFORM_TWEAK_CORLIB_SOURCES=cat - corlib.dll.win32-excludes |sort |uniq -u
PLATFORM_CHANGE_SEPARATOR_CMD=tr '/' '\\\\'
hidden_prefix =
hidden_suffix = .tmp
platform-check:
-38
View File
@@ -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?
-29
View File
@@ -1,29 +0,0 @@
# -*- makefile -*-
#
# The default 'bootstrap' profile -- builds so that we link against
# the libraries as we build them.
#
# We use the platform's native C# runtime and compiler if possible.
# Note that we have sort of confusing terminology here; BOOTSTRAP_MCS
# is what allows us to bootstrap ourselves, but when we are bootstrapping,
# we use INTERNAL_MCS.
# When bootstrapping, compile against our new assemblies.
# (MONO_PATH doesn't just affect what assemblies are loaded to
# run the compiler; /r: flags are by default loaded from whatever's
# in the MONO_PATH too).
ifdef PLATFORM_MONO_NATIVE
MCS = MONO_PATH="$(topdir)/class/lib:$$MONO_PATH" $(INTERNAL_MCS)
TEST_RUNTIME = MONO_PATH=".:$$MONO_PATH" $(RUNTIME) --debug
else
MCS = $(PLATFORM_RUNTIME) $(BOOTSTRAP_MCS) /lib:$(topdir)/class/lib
endif
# nuttzing!
profile-check:
# Causes some build errors
#PROFILE_MCS_FLAGS = /d:NET_1_1
-29
View File
@@ -1,29 +0,0 @@
# -*- makefile -*-
#
# The default 'bootstrap' profile -- builds so that we link against
# the libraries as we build them.
#
# We use the platform's native C# runtime and compiler if possible.
# Note that we have sort of confusing terminology here; BOOTSTRAP_MCS
# is what allows us to bootstrap ourselves, but when we are bootstrapping,
# we use INTERNAL_MCS.
# When bootstrapping, compile against our new assemblies.
# (MONO_PATH doesn't just affect what assemblies are loaded to
# run the compiler; /r: flags are by default loaded from whatever's
# in the MONO_PATH too).
ifdef PLATFORM_MONO_NATIVE
MCS = MONO_PATH="$(topdir)/class/lib:$$MONO_PATH" $(INTERNAL_MCS)
TEST_RUNTIME = MONO_PATH=".:$$MONO_PATH" $(RUNTIME) --debug
else
MCS = $(PLATFORM_RUNTIME) $(BOOTSTRAP_MCS) /lib:$(topdir)/class/lib
endif
# nuttzing!
profile-check:
# Causes some build errors
PROFILE_MCS_FLAGS = -d:GENERICS
-15
View File
@@ -1,15 +0,0 @@
# -*- Makefile -*-
#
# Only build .NET 1.0 classes.
#
# If we want to combine this with, say, the atomic profile,
# we should create 'atomic-net_1_0.make' which includes both.
#
# Ideally you could say 'make PROFILE="bootstrap net_1_0"' but
# that would be pretty hard to code.
include $(topdir)/build/profiles/default.make
PROFILE_MCS_FLAGS = /d:NET_1_0
# done
-145
View File
@@ -1,145 +0,0 @@
# -*- makefile -*-
#
# This is the makefile fragment with default rules
# for building things in MCS
#
# To customize the build, you should edit config.make.
# If you need to edit this file, that's a bug; email
# [email protected] about it.
# Some more variables. The leading period in the sed expression prevents
# thisdir = . from being changed into '..' for the toplevel directory.
dots := $(shell echo $(thisdir) |sed -e 's,[^./][^/]*,..,g')
topdir := $(dots)
VERSION = 0.25.99
USE_MCS_FLAGS = $(LOCAL_MCS_FLAGS) $(PLATFORM_MCS_FLAGS) $(PROFILE_MCS_FLAGS) $(MCS_FLAGS)
USE_CFLAGS = $(LOCAL_CFLAGS) $(CFLAGS)
CSCOMPILE = $(MCS) $(USE_MCS_FLAGS)
CCOMPILE = $(CC) $(USE_CFLAGS)
BOOT_COMPILE = $(BOOTSTRAP_MCS) $(USE_MCS_FLAGS)
INSTALL_DATA = $(INSTALL) -m 644
INSTALL_BIN = $(INSTALL) -m 755
INSTALL_LIB = $(INSTALL_BIN)
MKINSTALLDIRS = $(SHELL) $(topdir)/mkinstalldirs
INTERNAL_MCS = $(RUNTIME) $(topdir)/mcs/mcs.exe
corlib = corlib.dll
depsdir = $(topdir)/build/deps
distdir = $(dots)/$(package)/$(thisdir)
# Make sure these propagate if set manually
export PLATFORM
export PROFILE
export MCS
export MCS_FLAGS
export CC
export CFLAGS
export INSTALL
export MKINSTALLDIRS
export TEST_HARNESS
export BOOTSTRAP_MCS
export DESTDIR
# Get this so the platform.make platform-check rule doesn't become the
# default target
default: all
# Get initial configuration. pre-config is so that the builder can
# override PLATFORM or PROFILE
include $(topdir)/build/config-default.make
-include $(topdir)/build/pre-config.make
# Default PLATFORM and PROFILE if they're not already defined.
ifndef PLATFORM
ifeq ($(OS),Windows_NT)
PLATFORM = win32
else
PLATFORM = linux
endif
endif
# Platform config
include $(topdir)/build/platforms/$(PLATFORM).make
ifdef PLATFORM_CORLIB
corlib = $(PLATFORM_CORLIB)
endif
# Useful
ifeq ($(PLATFORM_RUNTIME),$(RUNTIME))
PLATFORM_MONO_NATIVE = yes
endif
# Rest of the configuration
ifndef PROFILE
PROFILE = default
endif
include $(topdir)/build/profiles/$(PROFILE).make
-include $(topdir)/build/config.make
# Simple rules
%-recursive:
@list='$(SUBDIRS)'; for d in $$list ; do \
(cd $$d && $(MAKE) $*) || exit 1 ; \
done
# note: dist-local dep, extra subdirs, $* has become $@
dist-recursive: dist-local
@list='$(SUBDIRS) $(DIST_ONLY_SUBDIRS)'; for d in $$list ; do \
(cd $$d && $(MAKE) $@) || exit 1 ; \
done
# We do this manually to not have a make[1]: blah message (That is,
# instead of using a '%: %-recursive %-local' construct.)
#
# Let the makefile override these for special situations (running checks
# in the toplevel makefile, or a directory that needs to be built before
# its subdirectories).
ifndef OVERRIDE_BARE_TARGETS
all: all-recursive all-local
install: install-recursive install-local
test: test-recursive test-local
run-test: run-test-recursive test-local run-test-local
clean: clean-recursive clean-local
endif
# Can only do this from the top dir
# ## dist: dist-recursive dist-local
# We invert the test here to not end in an error
# if ChangeLog doesn't exist.
#
# Note that we error out if we try to dist a nonexistant
# file. Seems reasonable to me.
dist-default:
-mkdir $(distdir)
test '!' -f ChangeLog || cp ChangeLog $(distdir)
for f in Makefile $(DISTFILES) ; do \
dest=`dirname $(distdir)/$$f` ; \
$(MKINSTALLDIRS) $$dest && cp $$f $$dest || exit 1 ; \
done
# Useful
withmcs:
$(MAKE) MCS='$(INTERNAL_MCS)' BOOTSTRAP_MCS='$(INTERNAL_MCS)' all
@@ -0,0 +1,38 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- NAnt build file for Accessibility.dll -->
<project name="System" default="build">
<property name="debug" value="false"/>
<target name="build">
<mkdir dir="../lib"/>
<csc target="library" output="../lib/Accessibility.dll" debug="${debug}">
<arg value="/nowarn:1595"/>
<arg value="/unsafe"/>
<arg value="/noconfig"/> <!-- don't reference ms assemblies -->
<arg value="/lib:../lib/"/>
<!-- cor compare dies with these currently -->
<!--arg value="/nostdlib"/--> <!-- don't reference mscorlib -->
<!--arg value="/r:corlib.dll"/-->
<sources>
<includes name="**/*.cs"/>
<excludes name="Test/**"/>
</sources>
</csc>
<copy file="../lib/Accessibility.dll" tofile="Test/Accessibility.dll"/>
<!-- TODO: missing tests & buildfile
<nant basedir="Test" target="build"/>
-->
</target>
<target name="test" depends="build">
<nant basedir="Test" target="test"/>
</target>
<target name="clean">
<nant basedir="Test" target="clean"/>
<delete file="../lib/Accessibility.dll" failonerror="false"/>
</target>
</project>
@@ -1,48 +0,0 @@
//
// AssemblyInfo.cs
//
// Author:
// Andreas Nahr ([email protected])
//
// (C) 2003 Ximian, Inc. http://www.ximian.com
//
using System;
using System.Reflection;
using System.Resources;
using System.Security;
using System.Runtime.CompilerServices;
using System.Runtime.InteropServices;
// General Information about the system assembly
#if (NET_1_0)
[assembly: AssemblyVersion("1.0.3300.0")]
[assembly: SatelliteContractVersion("1.0.3300.0")]
#endif
#if (NET_1_1)
[assembly: AssemblyVersion("1.0.5000.0")]
[assembly: SatelliteContractVersion("1.0.5000.0")]
[assembly: ComCompatibleVersion(1, 0, 3300, 0)]
[assembly: TypeLibVersion(1, 10)]
#endif
[assembly: AssemblyTitle("Accessibility.dll")]
[assembly: AssemblyDescription("Accessibility.dll")]
[assembly: AssemblyConfiguration("Development version")]
[assembly: AssemblyCompany("MONO development team")]
[assembly: AssemblyProduct("MONO CLI")]
[assembly: AssemblyCopyright("(c) 2003 Various Authors")]
[assembly: AssemblyTrademark("")]
[assembly: CLSCompliant(true)]
[assembly: AssemblyDefaultAlias("Accessibility.dll")]
[assembly: AssemblyInformationalVersion("0.0.0.1")]
[assembly: NeutralResourcesLanguage("en-US")]
[assembly: ComVisible(false)]
[assembly: AllowPartiallyTrustedCallers]
[assembly: Guid("1ea4dbf0-3c3b-11cf-810c-00aa00389b71")]
//[assembly: AssemblyDelaySign(false)]
//[assembly: AssemblyKeyFile("")]
@@ -1,4 +0,0 @@
2003-07-17 Andreas Nahr <[email protected]>
* AssemblyInfo.cs: Added
* ChangeLog: Added
-5
View File
@@ -1,8 +1,3 @@
2003-07-17 Andreas Nahr <[email protected]>
* Accessibility.dll.sources:
* list.unix: AssemblyInfo.cs added
2002-12-10 Jeroen Janssen <[email protected]>
* updated .build file to correctly build with Nant
-9
View File
@@ -1,9 +0,0 @@
thisdir = class/Accessibility
SUBDIRS =
include ../../build/rules.make
LIBRARY = Accessibility.dll
LIB_MCS_FLAGS = /r:$(corlib)
NO_TEST = yes
include ../../build/library.make
@@ -1,3 +1,2 @@
Accessibility/IAccessible.cs
Accessibility/IAccessibleHandler.cs
Assembly/AssemblyInfo.cs
+16
View File
@@ -0,0 +1,16 @@
topdir = ../..
TEST_DIR= Test
LIBRARY = $(topdir)/class/lib/Accessibility.dll
LIB_LIST = list.unix
LIB_FLAGS = -r corlib
SOURCES_INCLUDE=*.cs
SOURCES_EXCLUDE=\
./Test*
export MONO_PATH_PREFIX = $(topdir)/class/lib:
include $(topdir)/class/library.make
+44
View File
@@ -0,0 +1,44 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- NAnt build file for ByteFX.Data.dll -->
<project name="ByteFX.Data" default="build">
<property name="debug" value="false"/>
<target name="build">
<csc target="library" output="../lib/ByteFX.Data.dll" debug="${debug}">
<arg value="/nowarn:1595"/>
<arg value="/nowarn:0067"/>
<arg value="/nowarn:0109"/>
<arg value="/nowarn:0169"/>
<arg value="/nowarn:0649"/>
<arg value="/unsafe"/>
<arg value="/noconfig"/>
<arg value="/r:../lib/System.dll"/>
<arg value="/r:../lib/System.Xml.dll"/>
<arg value="/r:../lib/System.Data.dll"/>
<arg value="/r:../lib/ICSharpCode.SharpZipLib.dll"/>
<sources>
<includes name="**/*.cs"/>
<excludes name="Test/**"/>
</sources>
<references>
<includes name="../lib/corlib.dll"/>
<includes name="../lib/System.dll"/>
<includes name="../lib/System.Xml.dll"/>
<includes name="../lib/System.Data.dll"/>
<includes name="../lib/ICSharpCode.SharpZipLib.dll"/>
</references>
</csc>
</target>
<target name="test" depends="build">
<nant basedir="Test" target="test"/>
</target>
<target name="clean">
<delete file="../lib/ByteFX.Data.dll" failonerror="false"/>
</target>
</project>
-11
View File
@@ -1,11 +0,0 @@
thisdir = class/ByteFX.Data
SUBDIRS =
include ../../build/rules.make
LIBRARY = ByteFX.Data.dll
LIB_MCS_FLAGS = /r:$(corlib) /r:System.dll /r:System.Xml.dll \
/r:System.Data.dll /r:ICSharpCode.SharpZipLib.dll
NO_TEST = yes
EXTRA_DISTFILES = ChangeLog.txt lgpl.txt readme.txt
include ../../build/library.make
File renamed without changes.
+14
View File
@@ -0,0 +1,14 @@
topdir = ../..
LIBRARY = $(topdir)/class/lib/ByteFX.Data.dll
LIB_LIST = list
LIB_FLAGS = -r corlib -r System -r System.Xml -r System.Data -r ICSharpCode.SharpZipLib
SOURCES_INCLUDE=./*.cs ./Common/*.cs ./mysqlclient/*.cs
SOURCES_EXCLUDE=\
./Test*
export MONO_PATH_PREFIX = $(topdir)/class/lib:
include $(topdir)/class/library.make
-17
View File
@@ -1,20 +1,3 @@
2003-08-11 Duncan Mak <[email protected]>
* Makefile (SUBDIRS): Add Mono.Cairo.dll
2003-07-24 Gonzalo Paniagua Javier <[email protected]>
* Makefile: only build Mono.CSharp.Debugger under linux.
2003-07-23 Peter Williams <[email protected]>
* Makefile (SUBDIRS): Add System.Drawing.Design.dll to the
default build.
2003-07-22 Cesar Lopez Nataren <[email protected]>
* mcs/class/Makefile: Added Microsoft.Vsa.dll to the build.
2003-04-04 Miguel de Icaza <[email protected]>
*
@@ -0,0 +1,45 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- NAnt build file for Commons.Xml.Relaxng.dll -->
<project name="Commons.Xml.Relaxng" default="build">
<property name="debug" value="true"/>
<target name="build">
<mkdir dir="../lib"/>
<csc target="library" output="../lib/Commons.Xml.Relaxng.dll" debug="${debug}">
<!-- 'foo' is defined in multiple places; using definition from 'bar' -->
<arg value="/nowarn:1595"/>
<!-- Other languages may permit the internal virtual member 'foo' to be overridden -->
<arg value="/nowarn:0679"/>
<arg value="/nowarn:0649"/>
<sources>
<includes name="**/*.cs"/>
<excludes name="Test/**"/>
</sources>
<!--
<arg value="/nostdlib" />
<references basedir="..\lib">
<includes name="corlib.dll"/>
<includes name="System.dll"/>
<includes name="System.Xml.dll"/>
</references>
<arg value="/r:..\lib\System.dll" />
<arg value="/r:..\lib\System.Xml.dll" />
-->
</csc>
<nant basedir="Test" target="build"/>
</target>
<target name="test" depends="build">
<nant basedir="Test" target="test"/>
</target>
<target name="clean">
<nant basedir="Test" target="clean"/>
<delete file="../lib/Commons.Xml.Relaxng.dll" failonerror="false"/>
<delete file="Test/Commons.Xml.Relaxng.dll" failonerror="false"/>
<delete file="Test/System.Xml.dll" failonerror="false"/>
<delete file="../lib/Commons.Xml.Relaxng.pdb" failonerror="false"/>
</target>
</project>
@@ -1,3 +0,0 @@
RdpPatternTests.cs
RelaxngReaderTests.cs
RelaxngValidatingReaderTests.cs
-19
View File
@@ -1,19 +0,0 @@
thisdir = class/Commons.Xml.Relaxng
SUBDIRS =
include ../../build/rules.make
LIBRARY = Commons.Xml.Relaxng.dll
LIB_MCS_FLAGS = /r:$(corlib) /r:System.dll /r:System.Xml.dll
TEST_MCS_FLAGS = $(LIB_MCS_FLAGS)
EXTRA_DISTFILES = \
Test/ChangeLog \
Test/XmlFiles/ChangeLog \
Test/XmlFiles/SimpleElementPattern1.xml \
Test/XmlFiles/SimpleElementPattern1.rng \
Test/XmlFiles/SimpleElementPattern2.xml \
Test/XmlFiles/SimpleElementPattern2.rng \
Test/XmlFiles/team.xml \
Test/XmlFiles/team.rng
include ../../build/library.make
@@ -0,0 +1,55 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- NAnt build file for Commons.Xml.Relaxng_test.dll -->
<!-- Target build (default) builds tests -->
<!-- Target test runs tests -->
<project name="Commons.Xml.Relaxng_test" default="build">
<property name="debug" value="false"/>
<property name="nunit_home" value="..\..\..\nunit"/>
<target name="build">
</target>
<target name="assemblies">
<copy file="../../lib/Commons.Xml.Relaxng.dll" tofile="Commons.Xml.Relaxng.dll"/>
<csc target="library" output="Commons.Xml.Relaxng_test.dll" debug="${debug}">
<arg value="/nowarn:1595"/>
<sources>
<includes name="**/*.cs"/>
</sources>
<references basedir="..\..\..\nunit20">
<includes name="NUnit.Framework.dll"/>
</references>
<!--
<arg value="/nostdlib" />
<references basedir="..\..\lib">
<includes name="corlib.dll"/>
<includes name="System.dll"/>
<includes name="System.Xml.dll"/>
<includes name="Commons.Xml.Relaxng.dll"/>
</references>
<arg value="/r:..\..\lib\corlib.dll" />
<arg value="/r:..\..\lib\System.dll" />
<arg value="/r:..\..\lib\System.Xml.dll" />
-->
<references basedir="..\..\lib">
<includes name="Commons.Xml.Relaxng.dll"/>
</references>
<arg value="/r:Commons.Xml.Relaxng.dll" />
</csc>
<!--
<copy file="../../lib/corlib.dll" tofile="corlib.dll"/>
<copy file="../../lib/System.dll" tofile="System.dll"/>
<copy file="../../lib/System.Xml.dll" tofile="System.XML.dll"/>
-->
</target>
<target name="test" depends="assemblies">
<exec program="..\..\..\nunit20\nunit-console.exe" commandline="Commons.Xml.Relaxng_test.dll" failonerror="false"/>
</target>
<target name="clean">
<delete file="Commons.Xml.Relaxng_test.dll" failonerror="false"/>
</target>
</project>
@@ -0,0 +1,29 @@
topdir = ../../..
LIBRARY = Commons.Xml.Relaxng_test.dll
LIB_LIST = Commons.Xml.Relaxng_test.args
LIB_FLAGS = \
-r $(topdir)/class/lib/corlib.dll \
-r $(topdir)/class/lib/System.dll \
-r $(topdir)/class/lib/System.Xml.dll \
-r $(topdir)/class/lib/Commons.Xml.Relaxng.dll \
-r $(topdir)/class/lib/NUnit.Framework.dll
ifdef SUBDIR
USE_SOURCE_RULES=1
SOURCES_INCLUDE=./$(SUBDIR)/*.cs
SOURCES_EXCLUDE=_DUMMY_
endif
include $(topdir)/class/library.make
NUNITCONSOLE=$(topdir)/nunit20/nunit-console.exe
MONO_PATH = $(topdir)/nunit20:$(topdir)/class/lib:.
test: $(LIBRARY) run_test
.PHONY: run_test
run_test:
-MONO_PATH=$(MONO_PATH) mono --debug $(NUNITCONSOLE) $(LIBRARY)
+12
View File
@@ -0,0 +1,12 @@
Commons.Xml\XmlDefaultReader.cs
Commons.Xml.Relaxng\Misc.cs
Commons.Xml.Relaxng\RelaxngReader.cs
Commons.Xml.Relaxng\RelaxngValidatingReader.cs
Commons.Xml.Relaxng\RngGrammar.cs
Commons.Xml.Relaxng\RngNameClass.cs
Commons.Xml.Relaxng\RngPattern.cs
Commons.Xml.Relaxng\RngPatternType.cs
Commons.Xml.Relaxng.Derivative\RdpNameClasses.cs
Commons.Xml.Relaxng.Derivative\RdpObjects.cs
Commons.Xml.Relaxng.Derivative\RdpPatterns.cs
Commons.Xml.Relaxng.Derivative\Util.cs
@@ -0,0 +1,16 @@
topdir = ../..
TEST_DIR = Test
LIBRARY = $(topdir)/class/lib/Commons.Xml.Relaxng.dll
LIB_LIST = list.unix
LIB_FLAGS = -r:corlib -r:System -r:System.Xml
SOURCES_INCLUDE=*.cs
SOURCES_EXCLUDE=\
./Test* \
./System.Xml/Driver.cs
export MONO_PATH_PREFIX = $(topdir)/class/lib:
include $(topdir)/class/library.make
-4
View File
@@ -1,7 +1,3 @@
2003-07-03 Andreas Nahr <[email protected]>
* Cscompmgd.build: Removed unneeded unsafe compiler switch
2002-12-07 Jackson Harper <[email protected]>
* Cscompmgd.build: Added file
+27
View File
@@ -0,0 +1,27 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- NAnt build file for Cscompmgd.dll -->
<project name="Cscompmgd" default="build">
<property name="debug" value="false"/>
<target name="build">
<csc target="library" output="../lib/Cscompmgd.dll" debug="${debug}">
<arg value="/nowarn:1595"/>
<arg value="/unsafe"/>
<sources>
<includes name="**/*.cs"/>
<excludes name="Test/**"/>
</sources>
<references>
<includes name="../lib/corlib.dll"/>
<includes name="../lib/System.dll"/>
</references>
</csc>
</target>
<target name="clean">
<delete file="../lib/Cscompmgd.dll" failonerror="false"/>
</target>
</project>
-9
View File
@@ -1,9 +0,0 @@
thisdir = class/Cscompmgd
SUBDIRS =
include ../../build/rules.make
LIBRARY = Cscompmgd.dll
LIB_MCS_FLAGS = /r:$(corlib) /r:System.dll
NO_TEST = yes
include ../../build/library.make
File renamed without changes.
+15
View File
@@ -0,0 +1,15 @@
topdir = ../..
TEST_DIR= Test
LIBRARY = $(topdir)/class/lib/Cscompmgd.dll
LIB_LIST = list.unix
LIB_FLAGS = -r corlib -r System
SOURCES_INCLUDE=*.cs
SOURCES_EXCLUDE=\
./Test*
export MONO_PATH_PREFIX = $(topdir)/class/lib:
include $(topdir)/class/library.make
-9
View File
@@ -1,9 +0,0 @@
thisdir = class/Custommarshalers
SUBDIRS =
include ../../build/rules.make
LIBRARY = System.Runtime.InteropServices.CustomMarshalers.dll
LIB_MCS_FLAGS = /r:$(corlib) /r:System.dll
NO_TEST = yes
include ../../build/library.make
+13
View File
@@ -0,0 +1,13 @@
topdir = ../..
LIBRARY = $(topdir)/class/lib/Custommarshalers.dll
LIB_LIST = list
LIB_FLAGS = -r corlib -r System
SOURCES_INCLUDE=*.cs
SOURCES_EXCLUDE=./Test*
export MONO_PATH = $(topdir)/class/lib:
include $(topdir)/class/library.make
-11
View File
@@ -1,11 +0,0 @@
thisdir = class/I18N/CJK
SUBDIRS =
include ../../../build/rules.make
LIBRARY = I18N.CJK.dll
LOCAL_MCS_FLAGS = /unsafe /resource:big5.table /resource:gb2312.table /resource:jis.table /r:$(corlib) /r:I18N.dll
NO_TEST = yes
EXTRA_DISTFILES = big5.table jis.table gb2312.table
include ../../../build/library.make
File renamed without changes.
+13
View File
@@ -0,0 +1,13 @@
topdir = ../../..
LIBRARY = $(topdir)/class/lib/I18N.CJK.dll
LIB_LIST = list.unix
LIB_FLAGS = --unsafe --resource big5.table --resource gb2312.table --resource jis.table -r corlib -r mscorlib -r I18N
SOURCES_INCLUDE=*.cs
SOURCES_EXCLUDE=
export MONO_PATH_PREFIX = $(topdir)/class/lib:
include $(topdir)/class/library.make
-9
View File
@@ -1,9 +0,0 @@
thisdir = class/I18N/Common
SUBDIRS =
include ../../../build/rules.make
LIBRARY = I18N.dll
LOCAL_MCS_FLAGS = /r:$(corlib)
NO_TEST = yes
include ../../../build/library.make
File renamed without changes.
+13
View File
@@ -0,0 +1,13 @@
topdir = ../../..
LIBRARY = $(topdir)/class/lib/I18N.dll
LIB_LIST = list.unix
LIB_FLAGS = -r corlib -r mscorlib
SOURCES_INCLUDE=*.cs
SOURCES_EXCLUDE=
export MONO_PATH_PREFIX = $(topdir)/class/lib:
include $(topdir)/class/library.make
+111
View File
@@ -0,0 +1,111 @@
<?xml version="1.0"?>
<project name="pnetlib I18N" default="build">
<property name="debug" value="false"/>
<target name="build">
<!-- Build the primary I18N.dll library -->
<csc output="../lib/I18N.dll" target="library" debug="${debug}">
<arg value="/nowarn:1595"/>
<arg value="/unsafe"/>
<arg value="/noconfig"/> <!-- don't reference ms assemblies -->
<arg value="/lib:../lib/"/>
<arg value="/r:corlib.dll"/>
<sources>
<includes name="Common/*.cs"/>
</sources>
<!--<resources>
<file name="../resources/en_US/I18N/I18N.resources"/>
</resources>-->
</csc>
<!-- Build the I18N.CJK.dll library -->
<csc output="../lib/I18N.CJK.dll" target="library" debug="${debug}">
<arg value="/unsafe"/>
<arg value="/noconfig"/>
<arg value="/lib:../lib/"/>
<arg value="/r:I18N.dll"/>
<arg value="/resource:CJK/jis.table"/>
<sources>
<includes name="CJK/*.cs"/>
</sources>
</csc>
<!-- Build the I18N.MidEast.dll library -->
<csc output="../lib/I18N.MidEast.dll" target="library" debug="${debug}">
<arg value="/unsafe"/>
<arg value="/noconfig"/> <!-- don't reference ms assemblies -->
<arg value="/lib:../lib/"/>
<arg value="/r:I18N.dll"/>
<sources>
<includes name="MidEast/*.cs"/>
</sources>
</csc>
<!-- Build the I18N.Other.dll library -->
<csc output="../lib/I18N.Other.dll" target="library" debug="${debug}">
<arg value="/unsafe"/>
<arg value="/noconfig"/> <!-- don't reference ms assemblies -->
<arg value="/lib:../lib/"/>
<arg value="/r:I18N.dll"/>
<sources>
<includes name="Other/*.cs"/>
</sources>
</csc>
<!-- Build the I18N.Rare.dll library -->
<csc output="../lib/I18N.Rare.dll" target="library" debug="${debug}">
<arg value="/unsafe"/>
<arg value="/noconfig"/> <!-- don't reference ms assemblies -->
<arg value="/lib:../lib/"/>
<arg value="/r:I18N.dll"/>
<sources>
<includes name="Rare/*.cs"/>
</sources>
</csc>
<!-- Build the I18N.West.dll library -->
<csc output="../lib/I18N.West.dll" target="library" debug="${debug}">
<arg value="/unsafe"/>
<arg value="/noconfig"/> <!-- don't reference ms assemblies -->
<arg value="/lib:../lib/"/>
<arg value="/r:I18N.dll"/>
<sources>
<includes name="West/*.cs"/>
</sources>
</csc>
</target>
<target name="clean">
<delete failonerror="false">
<fileset basedir="../lib">
<includes name="I18N.dll"/>
<includes name="I18N.CJK.dll"/>
<includes name="I18N.MidEast.dll"/>
<includes name="I18N.Other.dll"/>
<includes name="I18N.Rare.dll"/>
<includes name="I18N.West.dll"/>
</fileset>
</delete>
<!-- Uncomment this if build file added for those.
<nant basedir="Common" target="clean"/>
<nant basedir="CJK" target="clean"/>
<nant basedir="MidEast" target="clean"/>
<nant basedir="Other" target="clean"/>
<nant basedir="Rare" target="clean"/>
<nant basedir="West" target="clean"/>
-->
</target>
</project>
-15
View File
@@ -1,15 +0,0 @@
thisdir = class/I18N
SUBDIRS = Common West MidEast Other Rare CJK
include ../../build/rules.make
DISTFILES = \
README \
README.mono \
mklist.sh \
tools/cvt.sh \
tools/ucm2cp.c \
tools/uni2tab.c
all-local install-local clean-local test-local run-test-local:
dist-local: dist-default
-11
View File
@@ -1,11 +0,0 @@
thisdir = class/I18N/MidEast
SUBDIRS =
include ../../../build/rules.make
LIBRARY = I18N.MidEast.dll
LOCAL_MCS_FLAGS = /r:$(corlib) /r:I18N.dll
NO_TEST = yes
EXTRA_DISTFILES = $(wildcard *.ucm)
include ../../../build/library.make
+13
View File
@@ -0,0 +1,13 @@
topdir = ../../..
LIBRARY = $(topdir)/class/lib/I18N.MidEast.dll
LIB_LIST = list.unix
LIB_FLAGS = -r corlib -r mscorlib -r I18N
SOURCES_INCLUDE=*.cs
SOURCES_EXCLUDE=
export MONO_PATH_PREFIX = $(topdir)/class/lib:
include $(topdir)/class/library.make
-11
View File
@@ -1,11 +0,0 @@
thisdir = class/I18N/Other
SUBDIRS =
include ../../../build/rules.make
LIBRARY = I18N.Other.dll
LOCAL_MCS_FLAGS = /r:$(corlib) /r:I18N.dll
NO_TEST = yes
EXTRA_DISTFILES = $(wildcard *.ucm)
include ../../../build/library.make
File renamed without changes.
+13
View File
@@ -0,0 +1,13 @@
topdir = ../../..
LIBRARY = $(topdir)/class/lib/I18N.Other.dll
LIB_LIST = list.unix
LIB_FLAGS = -r corlib -r mscorlib -r I18N
SOURCES_INCLUDE=*.cs
SOURCES_EXCLUDE=
export MONO_PATH_PREFIX = $(topdir)/class/lib:
include $(topdir)/class/library.make
-11
View File
@@ -1,11 +0,0 @@
thisdir = class/I18N/Rare
SUBDIRS =
include ../../../build/rules.make
LIBRARY = I18N.Rare.dll
LOCAL_MCS_FLAGS = /r:$(corlib) /r:I18N.dll
NO_TEST = yes
EXTRA_DISTFILES = $(wildcard *.ucm)
include ../../../build/library.make
File renamed without changes.
+13
View File
@@ -0,0 +1,13 @@
topdir = ../../..
LIBRARY = $(topdir)/class/lib/I18N.Rare.dll
LIB_LIST = list.unix
LIB_FLAGS = -r corlib -r mscorlib -r I18N
SOURCES_INCLUDE=*.cs
SOURCES_EXCLUDE=
export MONO_PATH_PREFIX = $(topdir)/class/lib:
include $(topdir)/class/library.make
-11
View File
@@ -1,11 +0,0 @@
thisdir = class/I18N/West
SUBDIRS =
include ../../../build/rules.make
LIBRARY = I18N.West.dll
LOCAL_MCS_FLAGS = /r:$(corlib) /r:I18N.dll
NO_TEST = yes
EXTRA_DISTFILES = $(wildcard *.ucm)
include ../../../build/library.make
Loaded 100 of 2022 files, more files were not shown because too many files have changed in this diff. Show more