فهرست منبع

Fixing typos and structure

BearishSun 9 سال پیش
والد
کامیت
64fadfa930
2فایلهای تغییر یافته به همراه6 افزوده شده و 5 حذف شده
  1. 2 1
      Documentation/GitHub/compiling.md
  2. 4 4
      Documentation/GitHub/dependencies.md

+ 2 - 1
Documentation/GitHub/compiling.md

@@ -33,6 +33,7 @@ Banshee relies on a variety of third party dependencies. We provide a set of pre
  
  
 For older versions of pre-compiled dependencies check the git release tag descriptions for links.
 For older versions of pre-compiled dependencies check the git release tag descriptions for links.
 
 
+## Other dependencies
 The following dependencies will need to be installed manually regardless if you used pre-compiled dependency package or have compiled them yourself.
 The following dependencies will need to be installed manually regardless if you used pre-compiled dependency package or have compiled them yourself.
 
 
 **DirectX SDK**
 **DirectX SDK**
@@ -59,5 +60,5 @@ The following dependencies will need to be installed manually regardless if you
   - Use logging libraries for the Debug builds, and non-logging for OptimizedDebug and Release builds
   - Use logging libraries for the Debug builds, and non-logging for OptimizedDebug and Release builds
   
   
 **Mono 4.2**
 **Mono 4.2**
- - If you wish to compile managed assemblies using Microsoft compiler (e.g. using Visual Studio) yet still be able to debug the generated assemblies, you must install Mono 4.2. and set up an environment variable MONO_INSTALL_DIR pointing to the Mono installation directory. When this is set up "pdb2mdb" script will trigger on next compile generating the needed debug symbols.
+ - If you wish to compile managed assemblies using a Microsoft compiler (e.g. using Visual Studio) yet still be able to debug the generated assemblies, you must install Mono 4.2. and set up an environment variable MONO_INSTALL_DIR pointing to the Mono installation directory. When this is set up "pdb2mdb" script will trigger on next compile generating the needed debug symbols.
  - http://www.mono-project.com/download/
  - http://www.mono-project.com/download/

+ 4 - 4
Documentation/GitHub/dependencies.md

@@ -3,13 +3,13 @@ To compile/retrieve dependencies manually follow the guides provided by each ind
 
 
 Rename and place the compiled/retrieved outputs into proper folders depending on their type:
 Rename and place the compiled/retrieved outputs into proper folders depending on their type:
   - Static libraries (.lib, .a): 
   - Static libraries (.lib, .a): 
-   - Place outputs in (BansheeSource)\Dependencies\(LibName)\lib\(Platform)
+   - Place outputs in (BansheeSource)/Dependencies/(LibName)/lib/(Platform)
   - Dynamic libraries (.dll, .so, .dylib)
   - Dynamic libraries (.dll, .so, .dylib)
-   - Place outputs in (BansheeSource)\bin\(Platform)\(Configuration)
+   - Place outputs in (BansheeSource)/bin/(Platform)/(Configuration)
   - Includes
   - Includes
-   - Place outputs in (BansheeSource)\Dependencies\(LibName)\include
+   - Place outputs in (BansheeSource)/Dependencies/(LibName)/include
   - Tools (executables)
   - Tools (executables)
-   - Place outputs in (BansheeSource)\Dependencies\(tools)\(LibName)  
+   - Place outputs in (BansheeSource)/Dependencies/(tools)/(LibName)  
    
    
 Each library below lists a set of outputs required by Banshee. After you compile/retrieve the library rename the outputs to what Banshee expects and place them relative to the above paths, depending on their type. Depending on which platform you're compiling for you will need to compile 32-bit or 64-bit versions of the libraries (or both).
 Each library below lists a set of outputs required by Banshee. After you compile/retrieve the library rename the outputs to what Banshee expects and place them relative to the above paths, depending on their type. Depending on which platform you're compiling for you will need to compile 32-bit or 64-bit versions of the libraries (or both).