[Mono-list] Newbie in NJ

[Jonathan Pryor]

It should be noted that C# development can also be done from Windows. 
It should be possible to write portions of the class library purely in
C#.  Test cases can also be done under Windows, as running them against
.NET provides validation for the test cases.  (Or we find .NET bugs,
which has happened before.)

With that out of the way...  Your questions:

1) Where did Red Carpet put the mono binaries?

	The mono-0.19 RPM for Red Hat 8.0 places installs the files with
	a prefix of "/usr".  In short, binaries (mcs.exe, mono, etc.)
	are placed in /usr/bin, Assemblies (corlib.dll, System.dll) are
	in /usr/lib, etc.

	I would imagine that all provided RPMs put files in the same 
	places.

2) How do I build mono from the CVS source so that it does not screw up
my existing mono installed from red Carpet?

	Short answer: change the prefix to be something other than /usr.

	Long answer.  When you "make -f makefile.gnu" in the mcs
	directory, you need to provide a "prefix", which is the root
	directory under which everything will be installed.  To change
	where your programs are, change the prefix, e.g.:

		make -f makefile.gnu install prefix=~/mono/install

	Just to be different, the "mono" module uses a configure script,
	which is generated from the "autogen.sh" script.  Just pass 
	--prefix to this script:

		cd <path-to-mono>/mono
		./autogen.sh --prefix=~/mono/install

	Make sure that the prefix you specify is the same for both mcs
	and mono.  Executables are placed under $prefix/bin, assemblies
	under $prefix/lib, etc.

I'd like to say that this is everything you need to know.  Well, it
isn't.  Experience helps, but that can be hard to summarize.

Another problem is that things don't currently work as well as
expected.  It's been reported that "mcs" is generating compile errors
when compiled with the mcs distributed with mono-0.19.  In other words,
it can't bootstrap itself.  This was just reported, so I'm not sure what
the workaround is, and thus it might be prudent to wait for the
solution.  (Or, if you're brave, do it anyway and edit the mcs code to
remove the errors mono-0.19's mcs is reporting.  I don't know if this
works, though.)

Hope this helps.

 - Jon


On Sat, 2003-02-15 at 19:57, Steve Szyszkiewicz wrote:
> I am looking at trying to get started, but I am, in general a newbie in
> Linux.I would like to spend an hour a day helping out. I think C# is
> cool. I program for a living on Windows, and my motivations for wanting
> to help are:
> 
> 1) I believe you have to code at least an hour a day to keep your skills
> sharp and I have gotten myself into a position where I am not coding as
> much as I used to.
> 
> 2) I think .NET and C# are really cool and would love to see it working
> everywhere.
> 
> What I have done
> 
> I have the CVS stuff working. I have a shell script that runs the
> following commands (according to the go-mono website instructions) and
> it seems to execute OK.
> 
> 	export CVSROOT=:pserver:anonymous@anoncvs.go-mono.com:/mono
> 	cvs -z3 update -dP mcs mono gtk-sharp
> 
> The CVS scripts seem to have created a directory off of my home directory called mono. I am logged into my system under an id that does not have root access. I have not tried to build anything from this source.
> 
> I also got mono through the Red Carpet service, and mcs works, although I really don't know where it was put on my Redhat 7.1 system or what system variables were set so that it knew enough to find mcs.
> 
> So what do I need?
> 
> 1) Where did Red Carpet put the mono binaries?
> 2) How do I build mono from the CVS source so that it does not screw up my existing mono installed from red Carpet?
> 3) I need some help building an effective build environment (I want to help build mono).
> 
> Sorry for such newbie questions, but I have to start somewhere.
> 
> Steve
> 
> _______________________________________________
> Mono-list maillist  -  Mono-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list