Changes between Version 83 and Version 84 of CompileClient


Ignore:
Timestamp:
May 8, 2015, 12:21:12 PM (10 years ago)
Author:
romw
Comment:

Simplify Windows documentation

Legend:

Unmodified
Added
Removed
Modified

  • CompileClient

    v83 v84  
    132132== Windows ==
    133133
    134 If you want to build the BOINC client and wxWidgets by hand, or are still building BOINC 5.10 and below, please follow [CompileWithWxWidgets CompileWithWxWidgets]
    135 
    136 === Building the client with Visual Studio 2005 and Visual Studio 2005 Express Edition. ===
    137 
    138 '''Supported Operating Systems''': Windows 2000; Windows Server 2003; Windows XP 64-bit; Windows XP Professional Edition ; Windows XP Service Pack 1 and above. This support is mostly for the Windows Platform Server 2003 R2 Platform SDK, which will not install on Windows Vista and Windows 7. If you want to build BOINC on these operating systems, see the build instructions for building BOINC with [http://boinc.berkeley.edu/trac/wiki/CompileClient#BuildingtheclientwithVisualStudio2008andVisualStudio2008ExpressEdition. Visual Studio 2008 (Express Edition)], or follow the VS2005 + Windows Vista/7 [http://boinc.berkeley.edu/trac/wiki/CompileClient#InstallingVS2005onWindowsVistaandWindows7 instructions below].
     134=== Visual Studio 2013 Community Edition Build Environment ===
    139135
    140136Software Prerequisites:
    141  * Download the [http://go.microsoft.com/fwlink/?linkid=57034 C++ 2005 Express Edition ISO file] (part of Visual Studio 8 Express).
    142   * You will need some program to burn the ISO file to CD or DVD, e.g. Nero Essentials.
    143   * After you burnt it to disk, reinsert the CD or DVD in the CD/DVD writer and Autostart will take care of the installation start. Follow that through.
    144 
    145  * Update to [http://www.microsoft.com/downloads/details.aspx?FamilyId=7B0B0339-613A-46E6-AB4D-080D4D4A8C4E&displaylang=en Visual Studio Service 2005 Express Edition Service Pack 1]
    146  * When using the full version of Visual Studio 2005, update to [http://www.microsoft.com/downloads/details.aspx?FamilyId=BB4A75AB-E2D4-4C96-B39D-37BAF6B5B1DC&displaylang=en Visual Studio 2005 Team Suite Service Pack 1]
    147  * When using Visual C++ 2005 Express Edition, you will also need to download and install [http://www.microsoft.com/downloads/details.aspx?FamilyId=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB Windows Platform Server 2003 R2 Platform SDK].
    148   * See this [http://msdn.microsoft.com/en-us/windowsserver/bb980924.aspx article] for further details.
    149  * Update Visual Studio 2005 SP1 with the security update available from Windows Update.
    150 
    151  * [SourceCode Download the current BOINC source code] (126MB)
    152  * Download the [source:boinc_depends_win_vs2005 VS2005 Additional Dependencies] (approx. 1GB)
    153   * See [SourceCodeGit#Windowsbuilddependencies Windows build dependencies] on how to download the additional dependencies.
    154  * In Windows, Start->(Settings)->Control Panel->System, select Advanced; click Environment Variables. Under 'User variables' click New. Create a variable named 'wxwin' with value as in the example below.
    155 
    156    || Build Target  || Build Platform || wxWidget Version || Environment Variable ||
    157    || Release       || Win32          || 2.8.x            || WXWIN                ||
    158    || Release       || x64            || 2.8.x            || WXWINX64             ||
    159    || Debug         || Win32          || 2.8.x            || WXWIN                ||
    160    || Debug         || x64            || 2.8.x            || WXWINX64             ||
    161 
    162 {{{
    163 Example Environment Variables:
    164 WXWIN=C:\Src\boinc_depends_win_vs2005\wxwidgets\mswin\Win32
    165 WXWINX64=C:\Src\boinc_depends_win_vs2005\wxwidgets\mswin\x64
    166 }}}
    167 The above are examples. If you saved the boinc_depends_win_vs2005 directory elsewhere, adjust the path.
    168 
    169  * Start Visual Studio 2005 -> Visual C++ 2005 (Express Edition)
    170  * First we set up VS 2005 to use the Platform SDKs:
    171   * Tools->Options.
    172   * Open Projects and Solutions->VC++ Directories.
    173   * Make sure your Platform is correctly set (Win32 for instance).
    174   * Now from the drop down menu in the top right corner, select Include files and point it to the Win Platform Server 2k3 R2 Platform SDK\Include directory.
    175   * Then select Library files from the drop down menu and point it to Win Platform Server 2k3 R2 Platform SDK\Lib
    176   * OK out of there.
    177  * Then go File->Open Solution-><BOINCSRCDIR/>\win_build\boinc.sln and click Open.
    178  * Set up Visual Studio to use the correct platform.
    179   * From the drop-down menu choose either Win32 (for 32 bit platforms) or x64 (for 64 bit platforms) and choose to make it a Release/Debug version.
    180   * Additional linker dependencies for Visual C++ Express (right click the project name, properties, Linker, Input, double click the ... box on Additional Dependencies and add those missing).
    181    * boinc_dll
    182     * advapi32.lib
    183     * user32.lib
    184     * kernel32.lib
    185    * boinc
    186     * advapi32.lib
    187     * gdi32.lib
    188     * user32.lib
    189     * kernel32.lib
    190    * boincmgr
    191     * ole32.lib
    192     * oleaut32.lib
    193  * Go to the Build menu, Build Solution.
    194 
    195 All files will be built to <BOINCSRCDIR/>\win_build\Build\Win32\Release (or Build\x64\Release for 64 bit versions).
    196 Versions compiled with Visual C++ 2005 Express use the optimizing compiler. Benchmarks are the same as on versions released by Berkeley. The above steps will always build a development version, if you want to change this, edit <BOINCSCRDIR/>\version.h
    197 
    198 You can easily ignore all of the warnings that you get when building. Most of them are for the eyes of the developers.
    199 
    200 === Installing VS2005 on Windows Vista and Windows 7 ===
    201 To apply Visual Studio 2005 (Express Edition) on Windows Vista and Windows 7, please check the following points step by step:
    202 
    203  * Download the [http://go.microsoft.com/fwlink/?linkid=57034 C++ 2005 Express Edition ISO file] (part of Visual Studio 8 Express).
    204    * You will need some program to burn the ISO file to CD or DVD, e.g. Nero Essentials.
    205    * After you burnt it to disk, reinsert the CD or DVD in the CD/DVD writer and Autostart will take care of the installation start. Follow that through.
    206 
    207  * Update to [http://www.microsoft.com/downloads/details.aspx?familyid=7b0b0339-613a-46e6-ab4d-080d4d4a8c4e&displaylang=en Visual Studio 2005 Express Edition Service Pack 1]. Please run it with administrator privileges (Right-click the icon >> "Run as Administrator")
    208    * When using the full version of Visual Studio 2005, update to [http://www.microsoft.com/downloads/details.aspx?FamilyId=BB4A75AB-E2D4-4C96-B39D-37BAF6B5B1DC&displaylang=en Visual Studio 2005 Team Suite Service Pack 1]
    209  * Update to [http://www.microsoft.com/downloads/details.aspx?FamilyID=90E2942D-3AD1-4873-A2EE-4ACC0AACE5B6&displaylang=en Visual Studio 2005 Service Pack 1 For Windows Vista And Windows 7]. Please run it with administrator privileges (Right-click the icon >> "Run as Administrator")
    210    * You will need this update on the full version of Visual Studio 2005 as well.
    211 
    212 Instead of using the Windows Platform Server 2003 R2 Platform SDK, which cannot be installed on Windows 7, we choose to use the [http://www.microsoft.com/downloads/details.aspx?familyid=C17BA869-9671-4330-A63E-1FD44E0E2505&displaylang=en Windows SDK for Windows 7 and .NET Framework 3.5 SP1] instead. Please run it with administrator privileges (Right-click the icon >> "Run as Administrator")
    213 
    214  * Update Visual Studio 2005 SP1 with the security update available from Windows Update. (Visual Studio 2005 update (KB971090) (249.1MB) and a CAPICOM update (349KB).
    215 
    216 Now continue with downloading the source code and setting up the environment variables as [http://boinc.berkeley.edu/trac/wiki/CompileClient#BuildingtheclientwithVisualStudio2005andVisualStudio2005ExpressEdition. shown above].
    217 
    218 === Fixing Visual Studio 2005 object files after having them compiled with VS2008 ===
    219 If you ever built BOINC with Visual Studio 2008, then your object files will have been converted to VS2008 style. When building the source code in VS2005, you'll find Fatal error LNK1103: debugging information corrupt errors. This can be fixed by downloading and installing the hotfix for VS2005 in [http://support.microsoft.com/kb/949009/ this Microsoft Knowledgebase article].
    220 
    221 
    222 === Building the client with Visual Studio 2008 and Visual Studio 2008 Express Edition. ===
    223 Building project using Visual Studio 2008 has become much simpler since it was first posted.
    224 
    225 
    226 
    227 Software Prerequisites:
    228 Visual Studio 2008 with at least C++ package included. For example C++ 2008 Express Edition, Developer Edition or Team Suite (contains all available packages).
    229  * Download and install [http://www.microsoft.com/express/download/default.aspx C++ 2008 Express Edition] (part of Visual Studio 9 Express).
    230  * Update it to [http://www.microsoft.com/downloads/details.aspx?FamilyId=F3FBB04E-92C2-4701-B4BA-92E26E408569&displaylang=en Service Pack 1].
    231  * When using the full version of Visual Studio 2008, use [http://www.microsoft.com/downloads/details.aspx?FamilyId=FBEE1648-7106-44A7-9649-6D9F6D58056E this link] to update to Service Pack 1.
    232 
    233  * Download and install the [http://www.microsoft.com/downloads/details.aspx?familyid=C17BA869-9671-4330-A63E-1FD44E0E2505 Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1]
    234 
    235  * Download and install [http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en the Microsoft Visual C++ 2008 Redistributable Package].
    236  * Update that to [http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en Service Pack 1] (Watch out, it uses the same file name as the original one!)
    237   * [http://www.microsoft.com/downloads/details.aspx?familyid=8b29655e-9da4-4b6b-9ac5-687ca0770f93&displaylang=en 64bit versions] of Microsoft Visual C++ Redistributable Packages are also available. See [http://support.microsoft.com/kb/973551/ this entry in the MSKB] for more information.
    238  * Update Visual Studio 2008 SP1 with the security update available from Windows Update.
    239 
    240 Preparing project source code:
    241 I would advise you to create single, short named directory at the root of windows drive, for example "C:/Boinc".
    242 Inside of this directory you will download and create two directories with source codes coming from two separate projects: "Boinc" and "boinc_depends_win_vs2005". Here is how you get them:
    243 
    244  * [SourceCode Download the current BOINC source code] [source:boinc Boinc] (126MB)
    245  * Download the [source:boinc_depends_win_vs2005 VS2005 Additional Dependencies] (approx. 830MB)
    246   * See [SourceCodeGit#Windowsbuilddependencies Windows build dependencies] on how to download the additional dependencies.
    247   * Yes, even for building with VS2008, you will need the Additional Dependency download, as the source code points to it.
    248 
    249  * In Windows, Start->(Settings)->Control Panel->System, select Advanced; click Environment Variables. Under 'User variables' click New. Create a variable named 'wxwin' with value 'c:\wx' as in the example below.
    250 
    251    || Build Target  || Build Platform || wxWidget Version || Environment Variable ||
    252    || Release       || Win32          || 2.8.x            || WXWIN                ||
    253    || Release       || x64            || 2.8.x            || WXWINX64             ||
    254    || Debug         || Win32          || 2.8.x            || WXWIN                ||
    255    || Debug         || x64            || 2.8.x            || WXWINX64             ||
    256 
    257 {{{
    258 Example Environment Variables:
    259 WXWIN=C:\Src\boinc_depends_win_vs2005\wxwidgets\mswin\Win32
    260 WXWINX64=C:\Src\boinc_depends_win_vs2005\wxwidgets\mswin\x64
    261 }}}
    262 The above are examples. If you saved the boinc_depends_win_vs2005 directory elsewhere, adjust the path.
    263 
    264  * Go File->Open Solution-><BOINCSRCDIR/>\win_build\boinc.sln and click Open.
    265  * Set up Visual Studio to use the correct platform. From the drop-down menu choose either Win32 (for 32 bit platforms) or x64 (for 64 bit platforms) and choose to make it a !Release/Debug version.
    266 
    267 Correct small error in the project "boincsvcctrl". Go to properties of the project (Right click, properties), Configuration !Properties/Manifest !Tool/Input and output - clean the "Additional Manifest Files" field.
    268 This will remove the conflict, that would otherwise give compilation error: Error 96 manifest authoring error.
    269 
    270  * Go to the Build menu, Build Solution.
    271 
    272 All files will be built to <BOINCSRCDIR/>\win_build\Build\Win32\Release (or Build\x64\Release for 64 bit versions).
    273 Versions compiled with Visual C++ 2008 Express use the optimizing compiler. Benchmarks are the same as on versions released by Berkeley. The above steps will always build a development version, if you want to change this, edit <BOINCSCRDIR/>\version.h
    274 
    275 You can easily ignore all of the warnings that you get when building. Most of them are for the eyes of the developers.
    276 
    277 To run the resulting projects, you will need the copy of the MSVCR80.dll, msvcp80.dll and msvcm80.dll. You can find them in Microsoft SDK products installed on your PC
    278 
    279 === Building library files for use with BOINC built on VS 2008 ===
    280 
    281 Next we're building the library files so they work with your compiled client.
    282 Download the source code for [[br]]
    283 * [http://www.openssl.org/source/openssl-0.9.8k.tar.gz OpenSSL];[[br]]
    284 * [http://www.zlib.net/zlib-1.2.3.tar.gz Zlib];[[br]]
    285 * [http://curl.haxx.se/download/curl-7.19.4.tar.gz libCurl];[[br]]
    286 * [http://www.sqlite.org/sqlite-amalgamation-3_6_14_2.zip Sqlite3][[br]]
    287 
    288 '''WARNING:''' Do not use the OpenSSL, zlib1, libCurl and sqlite3 versions from the additional_dependency_VS2005 download, these are prepped for VS2005 only and will not work in BOINC compiled with VS2008! You will need to build these files by hand for VS2008 compatibility.
    289 
    290 Unzip the files to easy to reach directories. In the next examples I'll use c:\openssl\, c:\zlib\, c:\curl\ and c:\sqlite3 as the directories of choice. Especially for the OpenSSL directory, make sure you have '''no''' spaces anywhere in the path, use hyphens or underscores if need be or else the command line build will break. For the write up I am assuming to use the 32bit option only. If you want to use the 64bit option, make sure you substitute Win32 with Win64 wherever mentioned.
    291 
    292 
    293 ==== zlib ====
    294 
    295 In Visual C++ go File->Open->!Project/Solution, navigate to c:\zlib\projects\visualc6\ and choose zlib.dsw
    296 If it asks to save to the sln file or to convert the present files, answer yes to everything.
    297 
    298 In the class view list choose zlib, then click Build->Project configuration.
    299 Set Active solution configuration to DLL Release.
    300 Make sure at least zlib is selected.
    301 Make sure the Platform is set to Win32.
    302 Click Close.
    303 
    304 Click Project->Properties.
    305 Make sure that the Configuration shows DLL Release or (Active)DLL Release.
    306 Click OK
    307 
    308 Click Build->Clean solution.
    309 
    310 Next click Build->Batch build.
    311 Click the Project column so all zlib options are at the top, select only the DLL Release|Win32 option in the Build column. Check that the rest of the Build options are not selected.
    312 click Build.
    313 
    314 When done click File->Close solution.
    315 File->Exit to exit the program.
    316 
    317 The output files will be in the c:\zlib\projects\visualc6\Win32_DLL_Release\ directory, you will need the zlib1.dll file. It should be copied to your BOINC binary directory.
    318 
    319 ==== Curl ====
    320 
    321 In Visual C++ go File->Open->!Project/Solution, navigate to c:\curl\ and choose vc6curl.dsw
    322 If it asks to convert the present files, answer yes to everything.
    323 
    324 In the class view list choose libcurl, then click Build->Project configuration.
    325 Set Active solution configuration to using libcurl DLL Release.
    326 Make sure libcurl is selected in the Build column.
    327 click close.
    328 
    329 Click Project->Properties.
    330 Make sure that the Configuration shows Release or (Active)Release.
    331 Make sure the Platform is set to Win32.
    332 Click Apply, click OK
    333 
    334 Click Build->Clean solution.
    335 
    336 Next click Build->Batch build.
    337 Click the Projects column header so all libcurl options are at the top.
    338 Select only the libcurl with DLL Release|Win32 in the Build column. Check that the rest of the Build options are not selected.
    339 Click Build.
    340 
    341 When done click File->Close solution.
    342 File->Exit to exit the program.
    343 
    344 The output files will be in the c:\curl\lib\DLL-Release\ directory, you will need the libcurl.dll file. It should be copied to your BOINC binary directory.
    345 
    346 
    347 ==== OpenSSL ====
    348 
    349 Lots of command line prompt work here. First off, read c:\openssl\INSTALL.W32 (for Windows 32bit) or \INSTALL.W64 (for Windows 64bit). It'll be explained in there as well how to do this, but in a more rudimentary form.
    350 
    351 You will need to get Perl to build OpenSSL. Any Perl will do, but if not sure, then use [http://www.activestate.com/activeperl/ ActivePerl]. It'll install by default to your C:\ drive (C:\Perl)
    352 
    353 You now need the Visual C++ command prompt, so start up Visual C++ 2008 (Express Edition).
    354 Go Tools->Visual Studio 2008 Command Prompt.
    355 
    356 If the line before the blinking cursor shows another drive than c:, we'll have to go to c: first:
    357  * Type '''c:''' in the command line window and press '''Enter'''.
    358 
    359 Else continue from here.
    360  * Type '''cd\openssl''' and press '''Enter'''.
    361  * Type '''perl Configure VC-WIN32 --prefix=c:/openssl/''' and press '''Enter'''. (make sure to use the forward slashes '/', not the backslashes '\' in this path, as the next script is using Unix paths, not Windows paths.)
    362  * Type '''ms\do_masm''' and press '''Enter'''.
    363  * Type '''nmake -f ms\ntdll.mak''' and press '''Enter'''.
    364 
    365 Although the perl Configure script and the do_masm batchfile will work from a normal command line window, the nmake script will not! Hence why you best run all from the VC++ command line window.
    366 
    367 The output files will be in the c:\openssl\out32dll\ directory, you will need the libeay32.dll and ssleay32.dll files. These should be copied to your BOINC binary directory.
    368 
    369 ==== Sqlite3 ====
    370 
    371 Open the c:\sqlite3\sqlite3.zip file that you downloaded, but do not unzip the contents yet. (Preferably use an external program such as 7zip, Winzip or WinRAR)
    372 
    373 Start Visual Studio 2008. [[br]]
    374 * File->New->Project [[br]]
    375 * Choose CLR plus Class Library. [[br]]
    376 * For Name fill in '''sqlite3''' [[br]]
    377 * For Location point to a new directory called sqlite3. Do '''not''' use the original directory. [[br]]
    378 * Uncheck "Create directory for solution". [[br]]
    379 * Click OK.[[br]]
    380 
    381 This will create the solution files (sqlite3.sln, sqlite3.suo, and sqlite3.ncb) and project files (sqlite3.vcproj, etc).[[br]]
    382 Now go to back the opened zip file for sqlite3 and extract the files in it to the new sqlite3 directory that was made by VS2008, the one containing the solution files. Click Yes to overwrite files.
    383 
    384 Visual Studio will tell you that the source code files have changed and should it reload them? Click Yes to all.
    385 In the Resource Files project there is a file called ''sqlite3.cpp'', right click on it and choose Remove. Click Remove again on the warning screen.
    386 
    387 * From the menu bar, make sure your Solution Configuration Shows Release and the platform you are building for (32bit or 64bit)[[br]]
    388 * Now click Build->Build Solution. [[br]]
    389 
    390 That's it. The sqlite3.dll file can be found in your \sqlite3\Release\ directory. It should be copied to your BOINC binary directory. 
    391 
    392 
    393 TODO: - instructions for creating an installer with Installshield X.[[br]]
    394 
    395 OLD:
    396 Before, the following steps must have been performed. As of 2009-12-01 they are not needed anymore
    397 
    398 Packages used in past:
    399 [http://www.microsoft.com/downloads/details.aspx?FamilyId=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB Windows Platform Server 2003 R2 Platform SDK].
    400 
    401 MSDN:
    402  * Update it with the [http://www.microsoft.com/express/download/default.aspx MSDN Express Library] for the Express Edition.
    403  * Use the [http://www.microsoft.com/downloads/details.aspx?FamilyID=7bbe5eda-5062-4ebb-83c7-d3c5ff92a373&DisplayLang=en MSDN Library for Visual Studio 2008 SP1] for the full version (DVD ISO file).
    404 
    405 This step will be performed automatically, so just verify:
    406  * Start Visual Studio 2008 -> Visual C++ 2008 (Express Edition)
    407  * First we set up VS 2008 to use the Platform SDK:
    408   * Tools->Options.
    409   * Open Projects and Solutions->VC++ Directories.
    410   * Make sure your Platform is correctly set (Win32 for X86 code generation, Win64 for X64 code generation).
    411   * Now from the drop down menu in the top right corner, select Include files and point it to the Win Platform Server 2k3 R2 Platform SDK\Include directory.
    412   * Also point it to use ..\Program Files\Microsoft SDKs\Windows\V6.0a\Include
    413   * Then select Library files from the drop down menu and point it to Win Platform Server 2k3 R2 Platform SDK\Lib
    414   * And point this to use ..\Program Files\Microsoft SDKs\Windows\V6.0a\Lib as well.
    415   * OK out of there.
    416 
    417   * Additional linker dependencies for Visual C++ Express (right click the project name, properties, Librarian, Input, double click the ... box on Additional Dependencies and add those missing).
    418    * boinc_dll
    419     * advapi32.lib
    420     * user32.lib
    421     * kernel32.lib
    422    * boinc
    423     * advapi32.lib
    424     * gdi32.lib
    425     * user32.lib
    426     * kernel32.lib
    427    * boincmgr
    428     * ole32.lib
    429     * oleaut32.lib
    430 
     137 * Download and install [http://go.microsoft.com/fwlink/?LinkId=517284 Visual Studio 2013 Community Edition].
     138 * Download the [SourceCodeGit BOINC source code].
     139 * Download the [SourceCodeGit#Windowsbuilddependencies Visual Studio 2013 Dependency Store].
     140  * All dependency stores can be found [http://boinc.berkeley.edu/gitweb/ here].
     141
     142All the Visual Studio project files assume that the dependency store is a sibling of the BOINC source repo.
     143An example directory layout would look like this:
     144{{{
     145C:\Src
     146|
     147+--+ boinc
     148|
     149*--+ boinc_depends_win_vs2013
     150}}}
     151
     152==== Building via the Command Line ====
     153
     154Most everything developers will need to do during release management is handled by batch files.  All
     155these collections of batch files depend on the BOINC Build Environment for Windows.
     156
     157Launching the BOINC Build Environment for Windows:
     158{{{
     159cd \src\boinc\win_build
     160buildenv type release platform x64
     161}}}
     162
     163Buildenv accepts several different parameters to customize what you are going to be able to build.  Command
     164parameters are as follows:
     165{{{
     166Initializing BOINC Build Environment for Windows
     167Usage: buildenv.cmd TYPE <type> PLATFORM <platform> [Optional Commands]
     168
     169  Commands:
     170    DEVENVDIR:  Which build environment executed this batch file.
     171    TYPE:  Which build environment are you building executables for.
     172      Current Values: Release/Debug
     173    PLATFORM: Which platform are you building for.
     174      Current Values: x86/amd64/ia64
     175}}}
     176
     177You should get this output on success:
     178{{{
     179Initializing BOINC Build Environment for Windows
     180Software Platform Detected: Visual Studio 2013
     181}}}
     182
     183To build everything, execute 'build all' from the build environment:
     184{{{
     185C:\Src\boinc>build all
     186Building the World...
     187  Building BOINC:
     188    Success
     189  Building BOINC Manager:
     190    Success
     191  Building BOINC Command:
     192    Success
     193  Building BOINC Screen Saver:
     194    Success
     195  Building BOINC Screen Saver Controller:
     196    Success
     197  Building BOINC Service Controller:
     198    Success
     199  Building BOINC System Tray:
     200    Success
     201}}}
     202
     203==== Building via Visual Studio ====
     204
     205Double-click on the boinc_vs2013.sln file in the win_build directory to launch Visual Studio 2013.  From here
     206you should be able to perform any build operation you want.
    431207
    432208== Mac OS X ==