Do not install mono-runtime for mono build #62

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
3 participants

pjvds commented Jul 28, 2013

The get-mono script does install the mono-runtime via apt-get before installing it from source. This leaves the machine in a state where the mono-runtime is installed on two different locations. This is because the make install from the mono source also installs the mono runtime.

Owner

gregoryyoung commented Jul 28, 2013

The script won't work if mono is not installed. Uninstall mono and try. If you have that part working we would be happy to accept it.

Owner

gregoryyoung commented Jul 28, 2013

see: http://www.mono-project.com/Compiling_Mono_From_Git

In order to use mcs and mono binaries during the build process which do not reside in your PATH, you can set two make variables, EXTERNAL_MCS and EXTERNAL_RUNTIME:

make EXTERNAL_MCS=/foo/bar/gmcs.exe EXTERNAL_RUNTIME=/somewhere/else/mono

Owner

jen20 commented Jul 28, 2013

We could make it use mono-lite instead I suppose. From the README:

    If you don't have a working Mono installation, an obvious choice
    is to install the latest released packages of 'mono' for your
    distribution and running autogen.sh; make; make install in the
    mono module directory.

    You can also try a slightly more risky approach: this may not work,
    so start from the released tarball as detailed above.

    This works by first getting the latest version of the 'monolite'
    distribution, which contains just enough to run the 'mcs'
    compiler.  You do this with:

        # Run the following line after ./autogen.sh
        make get-monolite-latest

    This will download and automatically gunzip and untar the
    tarball, and place the files appropriately so that you can then
    just run:

        make EXTERNAL_MCS=${PWD}/mcs/class/lib/monolite/gmcs.exe

    And that will use the files downloaded by 'make get-monolite-latest.
Owner

gregoryyoung commented Jul 28, 2013

open to a pull req ;-)

On Sun, Jul 28, 2013 at 5:42 PM, James Nugent notifications@github.comwrote:

We could make it use mono-lite instead I suppose. From the README:

If you don't have a working Mono installation, an obvious choice
is to install the latest released packages of 'mono' for your
distribution and running autogen.sh; make; make install in the
mono module directory.

You can also try a slightly more risky approach: this may not work,
so start from the released tarball as detailed above.

This works by first getting the latest version of the 'monolite'
distribution, which contains just enough to run the 'mcs'
compiler.  You do this with:

    # Run the following line after ./autogen.sh
    make get-monolite-latest

This will download and automatically gunzip and untar the
tarball, and place the files appropriately so that you can then
just run:

    make EXTERNAL_MCS=${PWD}/mcs/class/lib/monolite/gmcs.exe

And that will use the files downloaded by 'make get-monolite-latest.


Reply to this email directly or view it on GitHubhttps://github.com/EventStore/EventStore/pull/62#issuecomment-21684489
.

Le doute n'est pas une condition agréable, mais la certitude est absurde.

Owner

jen20 commented Jul 28, 2013

I don't care about it enough to want to write yet more build scripts ;-)

pjvds commented Jul 29, 2013

Thanks for the suggestions. I will toy around with a few options and update the pull request according to the outcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment