Git Product home page Git Product logo

phanirajkiran / documentation Goto Github PK

View Code? Open in Web Editor NEW

This project forked from freescale/documentation

0.0 2.0 0.0 512 KB

This project hosts the documentation of Freescale Community BSP and related repositories

Home Page: http://freescale.github.io

License: Creative Commons Attribution Share Alike 4.0 International

Makefile 10.27% Batchfile 9.32% Python 42.19% CSS 0.96% HTML 2.22% C++ 12.49% SourcePawn 2.36% Assembly 16.83% Shell 3.36%

documentation's Introduction

Freescale Community BSP Documentation
-------------------------------------

The documentation is written using the Sphinx documentation system. To
install it in Debian/Ubuntu, please do:

  #: apt-get install libfreetype6-dev libjpeg8-dev python-dev python-pip \
     python-sphinx texlive-fonts-recommended texlive-latex-extra zlib1g-dev
  #: pip install reportlab sphinxcontrib-blockdiag

Once this has been completed, you can run 'make' in each of the Documentation
folders to review the available targets for building.

How to generate the binary
--------------------------

Follow the instructions below inside each sub-project in order to generate the
desired binary.

In order to generate the HTML all-in-one:

 $ make singlehtml

In order to generate the PDF file:

 $ make latexpdf

In order to generate the printable PDF file:

 $ make latexpdf -t <option>

Where option can be:

 * a4twoside = A4 page size and two side print;
 * lettertwoside = letter page size and two side print;
 * the default value is letter page size and one side print;

Contributing
------------

To contribute to this repository you should submit the patches for
review to the mailing list: [email protected].

Please refer to:
http://openembedded.org/wiki/Commit_Patch_Message_Guidelines
for useful guidelines to be followed when submitting patches.

Mailing list:

    https://lists.yoctoproject.org/listinfo/meta-freescale

Source code:

    https://github.com/Freescale/Documentation

When creating patches, please use something like:

    git format-patch -s --subject-prefix='Documentation][PATCH' origin

When sending patches, please use something like:

    git send-email --to [email protected] <generated patch>

documentation's People

Contributors

otavio avatar angolini avatar alexandrebelloni avatar dv1 avatar

Watchers

James Cloos avatar Phanirajkiran avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.