Source

NPAPI-chrome-file-api / README.md

Diff from to

README.md

 * On Windows, Visual Studio 2005 or later. Note, it appears to be possible to build using the [free version of Visual Studio](http://www.firebreath.org/display/documentation/Building+with+Visual+Studio+Express) although I haven't tried this since I have the full version. 
 * On Linux, gcc, make, libgtk2.0-dev and git
 
-# [Download firebreath](http://www.firebreath.org/display/documentation/Download) and unzip it into it's own directory. Firebreath 1.6 is known to work.
-# Clone this project into it's own directory (i.e. 'git clone https://ryanackley@bitbucket.org/ryanackley/npapi-chrome-file-api.git') 
-# Create an output directory for the firebreath build scripts. Mine is named 'fbbuild'. You can name yours whatever you want.
-# Run the Firebreath prep script for your platform. Assuming you followed the previous steps and now have 3 directories under your current diectory: 'firebreath', 'npapi-chrome-file-api', 'fbbuild', the command line will look like this. 
+1. [Download firebreath](http://www.firebreath.org/display/documentation/Download) and unzip it into it's own directory. Firebreath 1.6 is known to work.
+2. Clone this project into it's own directory (i.e. 'git clone https://ryanackley@bitbucket.org/ryanackley/npapi-chrome-file-api.git') 
+3. Create an output directory for the firebreath build scripts. Mine is named 'fbbuild'. You can name yours whatever you want.
+4. Run the Firebreath prep script for your platform. Assuming you followed the previous steps and now have 3 directories under your current diectory: 'firebreath', 'npapi-chrome-file-api', 'fbbuild', the command line will look like this. 
 
 	Mac: 'firebreath/prepmac.sh npapi-chrome-file-api fbbuild'
 	Linux: 'firebreath/prepmake.sh npapi-chrome-file-api fbbuild'
 
 	These scripts prep the build for your favorite build tool. You will still need to use a compiler or IDE to compile and link the binary NPAPI library. For example, on Mac OS X, the prepmac.sh script generates an XCode project (therefore you need to have XCode on Mac to build this project). For Linux and Windows builds there are several options. In the example above, I prep the Linux build to use Make and the Windows build to use Visual Studio 2008. For a full explanation of the process and available options refer to the [Firebreath build documentation](http://www.firebreath.org/display/documentation/Building+FireBreath+Plugins).
 
-# After you've successfully run the prep script for your platform and desired build tool. The required build files should now be present in the fbbuild directory. The next step depends on the platform and build tool. If you're using an IDE, the project files should be in the 'fbbuild' directory. If you're using Make the makefile will be there instead.
-# You should now be able to build and compile the NPAPI library. 
+5. After you've successfully run the prep script for your platform and desired build tool. The required build files should now be present in the fbbuild directory. The next step depends on the platform and build tool. If you're using an IDE, the project files should be in the 'fbbuild' directory. If you're using Make the makefile will be there instead.
+6. You should now be able to build and compile the NPAPI library. 
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.