From msparks at yahoo-inc.com Tue Oct 2 15:40:43 2007 From: msparks at yahoo-inc.com (Michael Sparks) Date: Tue Oct 2 15:40:54 2007 Subject: Release build Message-ID: <47029EBB.8050908@yahoo-inc.com> Is there any chance someone could provide a release build along side the debug build "svndotnet_20070116_debug"? I've been developing against that for the last few weeks, and now it's time to deploy to another box, and I'm stuck mucking around trying to build everything from source so I can get it to run without MSVCR80D.DLL. I've seen in the mailing list that others have had the same problem. From toby at etjohnson.us Tue Oct 2 16:08:10 2007 From: toby at etjohnson.us (Toby Johnson) Date: Tue Oct 2 16:08:14 2007 Subject: Release build In-Reply-To: <47029EBB.8050908@yahoo-inc.com> References: <47029EBB.8050908@yahoo-inc.com> Message-ID: <4702A52A.3000009@etjohnson.us> Have you tried the "nant bootstrap" method of building? It should be able to build start to finish with whichever configuration you want. toby Michael Sparks wrote: > Is there any chance someone could provide a release build along side > the debug build "svndotnet_20070116_debug"? > > I've been developing against that for the last few weeks, and now it's > time to deploy to another box, and I'm stuck mucking around trying to > build everything from source so I can get it to run without MSVCR80D.DLL. > > I've seen in the mailing list that others have had the same problem. > > _______________________________________________ > svndotnet-users mailing list > Project homepage: > http://www.pumacode.org/projects/svndotnet/ > Subscribe/Unsubscribe/Admin: > http://lists.pumacode.org/mailman/listinfo/svndotnet-users-lists.pumacode.org > > From msparks at yahoo-inc.com Tue Oct 2 16:18:46 2007 From: msparks at yahoo-inc.com (Michael Sparks) Date: Tue Oct 2 16:18:57 2007 Subject: Release build In-Reply-To: <4702A52A.3000009@etjohnson.us> References: <47029EBB.8050908@yahoo-inc.com> <4702A52A.3000009@etjohnson.us> Message-ID: <4702A7A6.80705@yahoo-inc.com> I don't know anything about nant. That is part of the problem. So I should download and install nant, then run "nant bootstrap" from the main directory where I have SvnDotNet? Sorry for being that guy who expects you to do all of the work... I know that goes against the social norms of open-source projects. But I'm working against the social norms of .NET projects, which is, approximately, "give me the binaries and I'll use the object browser to figure out what I need to know". :-) Toby Johnson wrote: > Have you tried the "nant bootstrap" method of building? It should be > able to build start to finish with whichever configuration you want. > > toby > > Michael Sparks wrote: >> Is there any chance someone could provide a release build along side >> the debug build "svndotnet_20070116_debug"? >> >> I've been developing against that for the last few weeks, and now >> it's time to deploy to another box, and I'm stuck mucking around >> trying to build everything from source so I can get it to run without >> MSVCR80D.DLL. >> >> I've seen in the mailing list that others have had the same problem. >> >> _______________________________________________ >> svndotnet-users mailing list >> Project homepage: >> http://www.pumacode.org/projects/svndotnet/ >> Subscribe/Unsubscribe/Admin: >> http://lists.pumacode.org/mailman/listinfo/svndotnet-users-lists.pumacode.org >> >> > > _______________________________________________ > svndotnet-users mailing list > Project homepage: > http://www.pumacode.org/projects/svndotnet/ > Subscribe/Unsubscribe/Admin: > http://lists.pumacode.org/mailman/listinfo/svndotnet-users-lists.pumacode.org > > > From luke at lateral.net Wed Oct 3 04:32:24 2007 From: luke at lateral.net (Luke Jackson) Date: Wed Oct 3 04:32:51 2007 Subject: Release build In-Reply-To: <4702A7A6.80705@yahoo-inc.com> References: <47029EBB.8050908@yahoo-inc.com> <4702A52A.3000009@etjohnson.us> <4702A7A6.80705@yahoo-inc.com> Message-ID: <47035398.5080900@lateral.net> Hi Michael, I had the same issue a few months ago. This is what I did to build the release DLLs. I ended up needed a couple of extra steps to get things working. 1. Change the value of the property "svnproject" from false to true in the file "default.build". When set to false, the build file responsible for building the client DLL was being skipped. 2. Install ActivePerl - the openssl project requires it. 3. Using the Visual Studio Command Prompt: 1. Ensure "C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include" is listed in the INCLUDE environment variable, so that it can find the file windows.h. 2. Run "nant get" to download all the required dependencies. 3. Run "nant release all dotnet build" to build - this will take several minutes. (nant bootstrap should do 2 & 3 but this is not how i built mine) If you have any queries feel free to send me a mail. Cheers Luke Michael Sparks wrote: > I don't know anything about nant. That is part of the problem. > So I should download and install nant, then run "nant bootstrap" from > the main directory where I have SvnDotNet? > > Sorry for being that guy who expects you to do all of the work... I > know that goes against the social norms of open-source projects. But > I'm working against the social norms of .NET projects, which is, > approximately, "give me the binaries and I'll use the object browser > to figure out what I need to know". :-) > > > Toby Johnson wrote: >> Have you tried the "nant bootstrap" method of building? It should be >> able to build start to finish with whichever configuration you want. >> >> toby >> >> Michael Sparks wrote: >>> Is there any chance someone could provide a release build along side >>> the debug build "svndotnet_20070116_debug"? >>> >>> I've been developing against that for the last few weeks, and now >>> it's time to deploy to another box, and I'm stuck mucking around >>> trying to build everything from source so I can get it to run >>> without MSVCR80D.DLL. >>> >>> I've seen in the mailing list that others have had the same problem. >>> >>> _______________________________________________ >>> svndotnet-users mailing list >>> Project homepage: >>> http://www.pumacode.org/projects/svndotnet/ >>> Subscribe/Unsubscribe/Admin: >>> http://lists.pumacode.org/mailman/listinfo/svndotnet-users-lists.pumacode.org >>> >>> >> >> _______________________________________________ >> svndotnet-users mailing list >> Project homepage: >> http://www.pumacode.org/projects/svndotnet/ >> Subscribe/Unsubscribe/Admin: >> http://lists.pumacode.org/mailman/listinfo/svndotnet-users-lists.pumacode.org >> >> >> > > _______________________________________________ > svndotnet-users mailing list > Project homepage: > http://www.pumacode.org/projects/svndotnet/ > Subscribe/Unsubscribe/Admin: > http://lists.pumacode.org/mailman/listinfo/svndotnet-users-lists.pumacode.org > > -- Luke Jackson Lateral Net Ltd 47-49 Charlotte Road London EC2A 3QT t: +44 (0) 20 7613 4449 w: www.lateral.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pumacode.org/pipermail/svndotnet-users-lists.pumacode.org/attachments/20071003/256f45a9/attachment.html From toby at etjohnson.us Wed Oct 3 10:24:41 2007 From: toby at etjohnson.us (Toby Johnson) Date: Wed Oct 3 10:24:44 2007 Subject: Release build In-Reply-To: <47035398.5080900@lateral.net> References: <47029EBB.8050908@yahoo-inc.com> <4702A52A.3000009@etjohnson.us> <4702A7A6.80705@yahoo-inc.com> <47035398.5080900@lateral.net> Message-ID: <4703A629.7000200@etjohnson.us> Luke Jackson wrote: > Hi Michael, > > I had the same issue a few months ago. This is what I did to build > the release DLLs. I ended up needed a couple of extra steps to get > things working. > > 1. Change the value of the property "svnproject" from false to true > in the file "default.build". When set to false, the build file > responsible for building the client DLL was being skipped. > 2. Install ActivePerl - the openssl project requires it. > 3. Using the Visual Studio Command Prompt: > 1. Ensure "C:\Program Files\Microsoft Visual Studio > 8\VC\PlatformSDK\Include" is listed in the INCLUDE > environment variable, so that it can find the file windows.h. > 2. Run "nant get" to download all the required dependencies. > 3. Run "nant release all dotnet build" to build - this will > take several minutes. (nant bootstrap should do 2 & 3 but > this is not how i built mine) > > If you have any queries feel free to send me a mail. > > Cheers > > Luke Thanks for the help Luke. If you have a binary release build of the latest code then you can email it to my personal email and I'll post it to the website. Michael, I do fully intend to get to the point where we can just distribute binary builds (with a fully CLS-compliant public interface instead of exposing unsafe types) that others "just use" but of course we're not there yet... toby