@@ -1,122 +1,237 @@ -Installing Dependencies -======================= - - To build Moonlight, you need to install a few dependencies for - the basic runtime engine (this is needed to support both API - profiles: Silverlight 1.0 and 2.0). +Installation Instructions +************************* + +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, +2006, 2007 Free Software Foundation, Inc. + +This file is free documentation; the Free Software Foundation gives +unlimited permission to copy, distribute and modify it. + +Basic Installation +================== + +Briefly, the shell commands `./configure; make; make install' should +configure, build, and install this package. The following +more-detailed instructions are generic; see the `README' file for +instructions specific to this package. + + The `configure' shell script attempts to guess correct values for +various system-dependent variables used during compilation. It uses +those values to create a `Makefile' in each directory of the package. +It may also create one or more `.h' files containing system-dependent +definitions. Finally, it creates a shell script `config.status' that +you can run in the future to recreate the current configuration, and a +file `config.log' containing compiler output (useful mainly for +debugging `configure'). + + It can also use an optional file (typically called `config.cache' +and enabled with `--cache-file=config.cache' or simply `-C') that saves +the results of its tests to speed up reconfiguring. Caching is +disabled by default to prevent problems with accidental use of stale +cache files. + + If you need to do unusual things to compile the package, please try +to figure out how `configure' could check whether to do them, and mail +diffs or instructions to the address given in the `README' so they can +be considered for the next release. If you are using the cache, and at +some point `config.cache' contains results you don't want to keep, you +may remove or edit it. + + The file `configure.ac' (or `configure.in') is used to create +`configure' by a program called `autoconf'. You need `configure.ac' if +you want to change it or regenerate `configure' using a newer version +of `autoconf'. + +The simplest way to compile this package is: + + 1. `cd' to the directory containing the package's source code and type + `./configure' to configure the package for your system. + + Running `configure' might take a while. While running, it prints + some messages telling which features it is checking for. + + 2. Type `make' to compile the package. + + 3. Optionally, type `make check' to run any self-tests that come with + the package. + + 4. Type `make install' to install the programs and any data files and + documentation. + + 5. You can remove the program binaries and object files from the + source code directory by typing `make clean'. To also remove the + files that `configure' created (so you can compile the package for + a different kind of computer), type `make distclean'. There is + also a `make maintainer-clean' target, but that is intended mainly + for the package's developers. If you use it, you may have to get + all sorts of other programs in order to regenerate files that came + with the distribution. + + 6. Often, you can also type `make uninstall' to remove the installed + files again. + +Compilers and Options +===================== - You will need the following dependencies: - libexpat - glib2 - gtk+ - gtk-sharp2 - rsvg2-sharp - - To build the mozilla plugin you will need xulrunner packages - for your requisite firefox version. +Some systems require unusual options for compilation or linking that the +`configure' script does not know about. Run `./configure --help' for +details on some of the pertinent environment variables. - You will need alsa or pulse-audio for audio support. + You can give `configure' initial values for configuration parameters +by setting variables in the command line or in the environment. Here +is an example: -Build Mono -========== + ./configure CC=c99 CFLAGS=-g LIBS=-lposix - You currently need a working Mono from svn. The latest known working - revision is r134208. Check #moonlight on irc.gimp.org for more info + *Note Defining Variables::, for more details. - Check out mono,mcs,mono-basic from svn - svn co -rREV svn://anonsvn.mono-project.com/source/trunk/mono - svn co -rREV svn://anonsvn.mono-project.com/source/trunk/mcs - svn co svn://anonsvn.mono-project.com/source/trunk/mono-basic +Compiling For Multiple Architectures +==================================== - In mono, do the usual ./autogen.sh && make && make install +You can compile the package for more than one kind of computer at the +same time, by placing the object files for each architecture in their +own directory. To do this, you can use GNU `make'. `cd' to the +directory where you want the object files and executables to go and run +the `configure' script. `configure' automatically checks for the +source code in the directory that `configure' is in and in `..'. - See http://mono-project.com/Parallel_Mono_Environments - for tips on running in multiple Mono environments + With a non-GNU `make', it is safer to compile the package for one +architecture at a time in the source code directory. After you have +installed the package for one architecture, use `make distclean' before +reconfiguring for another architecture. - Make mono-basic - ./configure && make && make install +Installation Names +================== +By default, `make install' installs the package's commands under +`/usr/local/bin', include files under `/usr/local/include', etc. You +can specify an installation prefix other than `/usr/local' by giving +`configure' the option `--prefix=PREFIX'. -Moonlight Configuration Options -===================== - We do not support building moonlight 1.0 from HEAD anymore. - For only Moonlight 1.0 support, checkout our branch at - svn://anonsvn.mono-project.com/source/branches/moon-1-0 + You can specify separate installation prefixes for +architecture-specific files and architecture-independent files. If you +pass the option `--exec-prefix=PREFIX' to `configure', the package uses +PREFIX as the prefix for installing programs and libraries. +Documentation and other data files still use the regular prefix. - Moonlight is now focused on Silverlight 2.0 support. Moonlight needs - to know where to find the mcs and mono-basic directories. + In addition, if you use an unusual directory layout you can give +options like `--bindir=DIR' to specify different values for particular +kinds of files. Run `configure --help' for a list of the directories +you can set and what kinds of files go in them. - --with-mcspath=<path> + If the package supports it, you can cause programs to be installed +with an extra prefix or suffix on their names by giving `configure' the +option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. - By default moon looks for ../mcs. +Optional Features +================= - --with-mono-basic-path=<path> +Some packages pay attention to `--enable-FEATURE' options to +`configure', where FEATURE indicates an optional part of the package. +They may also pay attention to `--with-PACKAGE' options, where PACKAGE +is something like `gnu-as' or `x' (for the X Window System). The +`README' should mention any `--enable-' and `--with-' options that the +package recognizes. - By default moon looks for ../mono-basic. + For packages that use the X Window System, `configure' can usually +find the X include and library files automatically, but if it doesn't, +you can use the `configure' options `--x-includes=DIR' and +`--x-libraries=DIR' to specify their locations. - --with-alsa=yes,no +Specifying the System Type +========================== - To enable audio using the ALSA stack, this can be - mixed with --with-pulse-audio=yes +There may be some features `configure' cannot figure out automatically, +but needs to determine by the type of machine the package will run on. +Usually, assuming the package is built to be run on the _same_ +architectures, `configure' can figure that out, but if it prints a +message saying it cannot guess the machine type, give it the +`--build=TYPE' option. TYPE can either be a short name for the system +type, such as `sun4', or a canonical name which has the form: - --with-pulse-audio=yes,no + CPU-COMPANY-SYSTEM - To enable audio using the Pulse Audio stack, this can - be mixed with --with-alsa=yes +where SYSTEM can have one of these forms: - --with-testing=yes,no + OS KERNEL-OS - Enable/disable unit tests (default=yes) + See the file `config.sub' for the possible values of each field. If +`config.sub' isn't included in this package, then this package doesn't +need to know the machine type. - --with-performance=yes|no + If you are _building_ compiler tools for cross-compiling, you should +use the option `--target=TYPE' to select the type of system they will +produce code for. - Enable/disable the performance tests (default=yes) + If you want to _use_ a cross compiler, that generates code for a +platform different from the build platform, you should specify the +"host" platform (i.e., that on which the generated programs will +eventually be run) with `--host=TYPE'. +Sharing Defaults +================ +If you want to set default values for `configure' scripts to share, you +can create a site shell script called `config.site' that gives default +values for variables like `CC', `cache_file', and `prefix'. +`configure' looks for `PREFIX/share/config.site' if it exists, then +`PREFIX/etc/config.site' if it exists. Or, you can set the +`CONFIG_SITE' environment variable to the location of the site script. +A warning: not all `configure' scripts look for a site script. +Defining Variables +================== -Installing Moonlight -==================== +Variables not defined in a site shell script can be set in the +environment passed to `configure'. However, some packages may run +configure again during the build, and the customized values of these +variables may be lost. In order to avoid this problem, you should set +them in the `configure' command line, using `VAR=value'. For example: - (Note: if you are building Moonlight from an svn checkout, - you'll need to run ./autogen.sh first.) + ./configure CC=/usr/local2/bin/gcc - Configure the build system by running ./configure with any - configuration options you might want (see the "Configuration - Options" section). For example, a typical configure might be: +causes the specified `gcc' to be used as the C compiler (unless it is +overridden in the site shell script). - ./configure --prefix=/usr/local --with-mcs-path=<path/to/mcs> +Unfortunately, this technique does not work for `CONFIG_SHELL' due to +an Autoconf bug. Until the bug is fixed you can use this workaround: - Once ./configure has finished, you'll need to actually compile - and install Moonlight using the following command: + CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash - make && make install +`configure' Invocation +====================== - After Moonlight has finished building and installing, you'll - need to install the plugin so that Firefox will be able to - load it when it encounters a Silverlight-enabled website: +`configure' recognizes the following options to control how it operates. - make test-plugin +`--help' +`-h' + Print a summary of the options to `configure', and exit. -Building the .xpi -================ +`--version' +`-V' + Print the version of Autoconf used to generate the `configure' + script, and exit. - To build a mozilla plugin installer (XPI), you must have the Firefox - packages installed. Building the xpi builds a modified libmoon and - libmoonloader that the xpi will use. +`--cache-file=FILE' + Enable the cache: use and save the results of the tests in FILE, + traditionally `config.cache'. FILE defaults to `/dev/null' to + disable caching. - When you configured, you should have seen something like this: +`--config-cache' +`-C' + Alias for `--cache-file=config.cache'. - Browser Support: - Firefox: yes - Plugin Installer (.xpi): yes - Gecko 1.8 (Firefox 2): no (reason: missing FF2 development packages) - Gecko 1.9 (Firefox 3): yes +`--quiet' +`--silent' +`-q' + Do not print messages saying which checks are being made. To + suppress all normal output, redirect it to `/dev/null' (any error + messages will still be shown). - After you run make, then run make user-plugin +`--srcdir=DIR' + Look for the package's source code in directory DIR. Usually + `configure' can determine that directory automatically. - The plugin is located at moon/plugin/install/novell-moonlight.xpi +`configure' also accepts some other, not widely useful, options. Run +`configure --help' for more details. - To install the plugin open the .xpi with your mozilla-based browser - and follow the prompts. Moonlight should now be properly installed - and ready to be used. INSTALL @@ -1,3 +1,7 @@ +2009-05-21 Rusty Howell <rhowell@novell.com> + + * Makefile.am: Changed install dir to DIST_SUBDIRS for make dist + 2009-05-21 Andreia Gaita <avidigal@novell.com> * plugin-class.cpp: disable throwing js exceptions on html_object_invoke plugin/ChangeLog @@ -1,3 +1,7 @@ +2009-05-21 Rusty Howell <rhowell@novell.com> + + * Makefile.am: Changed templates to DIST_SUBDIRS for make dist + 2009-05-20 Rusty Howell <rhowell@novell.com> * Makefile.am: Added templates to SUBDIRS for 'make dist' test/ChangeLog @@ -1,5 +1,6 @@ SUBDIRS=harness parsertest sizes +DIST_SUBDIRS = templates if INCLUDE_BROWSER_MANAGED_CODE SUBDIRS += 2.0 test/Makefile.am @@ -1,3 +1,7 @@ +2009-05-21 Rusty Howell <rhowell@novell.com> + + * Makefile.am: Changed moonvisi to DIST_SUBDIRS for 'make dist' + 2009-05-20 Rusty Howell <rhowell@novell.com> * Makefile.am: Added moonvisi to SUBDIRS for 'make dist' tools/ChangeLog @@ -1,7 +1,8 @@ SUBDIRS = mopen generators if INCLUDE_MANAGED_CODE #don't include respack because the toplevel includes that already -SUBDIRS += xamlg xaml2html moonvisi mxap munxap unsign sockpol +SUBDIRS += xamlg xaml2html mxap munxap unsign sockpol +DIST_SUBDIRS = moonvisi # added as dist_subdir so as not to break make dist endif EXTRA_DIST = launcher.in Options.cs README tools/Makefile.am 464be727d53b189dcb7bb46ae408c4ce1fe5455a rhowell rhowell@e3ebcda4-bce8-0310-ba0a-eca2169e7518 http://github.com/myabc/moonlight/commit/e4b1a3ff6d3d531d0db14c140ba462317cafd442 e4b1a3ff6d3d531d0db14c140ba462317cafd442 2009-05-21T15:48:49-07:00 2009-05-21T15:48:49-07:00 * Changed toos/moonvisi and test/templates to DIST_SUBDIRS so they don't get built but get included in make dist git-svn-id: svn://anonsvn.mono-project.com/source/trunk/moon@134569 e3ebcda4-bce8-0310-ba0a-eca2169e7518 8530a7e30791f7e42b21abc021ace3a9586153b8 rhowell rhowell@e3ebcda4-bce8-0310-ba0a-eca2169e7518