<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Okay, on rereading that I see I formulated myself ambiguously; what I meant was that I've prototyped a default.build that first builds a 'lib' target then the 'opensim' target; not that I've actually managed to make build files for all libs...<BR>
<BR>
/Stefan<BR><BR><BR><BR><BR>
<BLOCKQUOTE>
<HR id=EC_stopSpelling>
From: stefan@tribalmedia.se<BR>To: opensim-dev@lists.berlios.de<BR>Date: Thu, 18 Oct 2007 06:33:22 +0200<BR>Subject: Re: [Opensim-dev] so many dll's, so little time<BR><BR>
<META content="Microsoft SafeHTML" name=Generator>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass EC_body.hmmessage
{font-size:10pt;font-family:Tahoma;}
</STYLE>
I think we should use 'vendor branches' <BR><A href="http://svnbook.red-bean.com/en/1.1/ch07s05.html" target=_blank>http://svnbook.red-bean.com/en/1.1/ch07s05.html</A><BR> <BR>I've already done a prototype .build that first builds a target consisting of the native dlls, then the main opensim build.<BR> <BR>Such a target can be very specific and hand-crafted; on vs we'd just make prebuild include a couple of non-generated vs projects (also hand-crafted and not necessarily c#) maybe in a run-on-the-side solution.<BR> <BR>That would be win-win for all environments, I'd say.<BR> <BR>/Stefan<BR><BR><BR> <BR>
<HR id=EC_stopSpelling>
<BR>> Date: Wed, 17 Oct 2007 11:18:07 -0700<BR>> From: danbmil99@yahoo.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] so many dll's, so little time<BR>> <BR>> The major issue for me is that we are in some cases apparently depending on<BR>> binary code without access to the correct source versions. This could<BR>> become quite an exercise in forensic compilation if we don't sort it out<BR>> now.<BR>> <BR>> What I plan to do is try to acquire the source code versions that we believe<BR>> most closely match the DLL's we have in subversion, and get them all into<BR>> trunk/libraries. Then we can compile them and test them against the<BR>> codebase, and work through any issues until we have the ability to compile<BR>> and run opensim 100% from source code. I'm not advocating we force all<BR>> developers to deal with this; just a few of us core ppl to get it straight,<BR>> then we provide manna from heaven to the rest in the form of precompiled<BR>> binaries. Eventually, all the C# code should be easily incorporated into<BR>> nant/prebuild (right?). The native libs will always be a bit trickier, but<BR>> the same approach should work -- collect the code, keep it in<BR>> trunk/libraries, and provide a mechanism for casual users to get binaries<BR>> appropriate to their platform.<BR>> <BR>> -danx0r<BR>> <BR>> <BR>> -danx0r<BR>> <BR>> --- Tleiades Hax <tleiades@gmail.com> wrote:<BR>> <BR>> > ><BR>> > > I'm not sure that I understand the option here. Are you proposing to<BR>> > > write your own XML-RPC implementation for login? XML-RPC is managed<BR>> > > code right, is there any reason that isn't intrinsically cross platform<BR>> > > already (or did I miss that part)?<BR>> > ><BR>> > <BR>> > <BR>> > I think it is quite obvious, by examining the sourceforge site for the<BR>> > project, that it is no longer being actively maintained. I guess the<BR>> > majority is for using an external component for handling the logon method.<BR>> > I'm ok with that.<BR>> > > _______________________________________________<BR>> > Opensim-dev mailing list<BR>> > Opensim-dev@lists.berlios.de<BR>> > https://lists.berlios.de/mailman/listinfo/opensim-dev<BR>> > <BR>> <BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR><BR></BLOCKQUOTE></body>
</html>