|
BuildingLinFu2
Describes how to build the latest sources for LinFu 2.0
Getting the latest source codeYou can obtain the latest stable sources for LinFu by entering the following command in subversion: svn checkout http://linfu.googlecode.com/svn/branches/stable/2.0 linfu-read-only The stable branch represents the latest build that has been tested to work under a live production environment. Before you start using it, however, you're going to need to build the source files--and that's the next thing I'll show you how to do. Building LinFu 2.0PrerequisitesYou'll need to have the following software installed in order to build LinFu:
Building the source treeEach release of LinFu 2.0 has a batch file named go.bat located in the root directory of the local LinFu source tree that was downloaded to your hard disk. To build the source tree, all you need to do is switch to the LinFu source directory (let's assume that it's "C:\LinFu" ) and type the following command from the VS2008 command line: c:\LinFu\go.bat The batch file will automatically run all unit tests associated with LinFu on every build. Aside from the tools from Microsoft, the source tree has all the files necessary in the /tools directory to complete the build, so there's no need to download anything else in order to get the build up and running. Once the build is successful, the output assemblies will be placed in the /build/Debug directory. Using ILMerge to merge the assemblies (optional)Assuming that you have ILMerge installed, you can opt to build LinFu into a single assembly using the following command: c:\LinFu\go.bat merge The batch file will automatically perform the build and merge the output files into a single assembly named LinFu.Core.dll and place it into the /build directory. LinFu.Core.dll will contain all the projects from LinFu so you won't have to reference more than one LinFu assembly in all your projects. |
Sign in to add a comment
Just to let you know, it seems like the 'log4net.dll' in the 'tools\nant' directory is invalid. It has a size of 0 when doing a checkout of the 2.0 tree.
Fixed. Sorry about that!