diff options
Diffstat (limited to 'documentation/sdk-manual/sdk-using.xml')
| -rw-r--r-- | documentation/sdk-manual/sdk-using.xml | 22 |
1 files changed, 9 insertions, 13 deletions
diff --git a/documentation/sdk-manual/sdk-using.xml b/documentation/sdk-manual/sdk-using.xml index c752656ce4..10089ca3ae 100644 --- a/documentation/sdk-manual/sdk-using.xml +++ b/documentation/sdk-manual/sdk-using.xml @@ -24,18 +24,10 @@ <title>Why use the Standard SDK and What is in It?</title> <para> - Fundamentally, the standard SDK exists so that you can access - cross-development tools. - This paragraph describes why you use the Standard SDK. - Probably need to compare that against why you would not be interested - in the extensible SDK here as well. - According to Paul, the most interest lies in the extensible SDK. - So providing this comparison would be helpful. - Currently, my understanding boils down to this: The only reason to use - the Standard SDK is if you want to build and debug source code that - you have. - That pretty much sums it up. - If there is more detail, I need to know about it. + The Standard SDK provides a cross-development toolchain and libraries + tailored to the contents of a specific image. + You would use the Standard SDK if you want a more traditional toolchain + experience. </para> <para> @@ -125,6 +117,10 @@ <note> You must change the permissions on the toolchain installer script so that it is executable. + Here is an example: + <literallayout class='monospaced'> + $ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-2.1.sh + </literallayout> </note> </para> @@ -440,7 +436,7 @@ </section> <section id='sdk-developing-applications-using-eclipse'> - <title>Devloping Applications Using <trademark class='trade'>Eclipse</trademark></title> + <title>Developing Applications Using <trademark class='trade'>Eclipse</trademark></title> <para> If you are familiar with the popular Eclipse IDE, you can use an |