77007ad950
This patch performs some additional restructuring of the manual,
specifically in the User Guide. In detail:
- Rename 'Daily use' to 'General Buildroot usage'
- Move chapters 'make tips', 'Eclipse integration', and 'Advanced usage' as
sections under the 'General Buildroot usage' chapter.
- Rename 'Details on Buildroot configuration' into 'Buildroot configuration'
- Rework the 'Customization' section as follows:
- Move the short section on debugging the external toolchain wrapper into
the rest of the explanation on external toolchains.
- Remove the now redundant section on toolchains, as this is already
explained in much more detail in the 'Buildroot configuration' chapter.
- Move the sections on busybox/uclibc/kernel configuration from chapter
'Customization' into a separate chapter 'Configuration of other
components'.
- Rename the remaining part of the original 'Customization' chapter into
'Project-specific customization' and fold it together with the next
chapter 'Storing the configuration'
- Remove the chapter 'Going further in Buildroot innards' thanks to:
- Moving the chapter 'How Buildroot works' to the Developer guide.
- Moving the 'Advanced Buildroot usage' section to the 'General Buildroot
usage' chapter.
- Remove the chapter 'Hacking Buildroot' by:
- Adding a reference to adding packages to the 'Project-specific
customizations' chapter
- Leaving out the explicit reference to creating board support, as this is
part of the previous chapter already, so an extra reference is
redundant.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
31 lines
1.3 KiB
Plaintext
31 lines
1.3 KiB
Plaintext
// -*- mode:doc; -*-
|
|
// vim: set syntax=asciidoc:
|
|
|
|
=== Integration with Eclipse
|
|
|
|
While a part of the embedded Linux developers like classical text
|
|
editors like Vim or Emacs, and command-line based interfaces, a number
|
|
of other embedded Linux developers like richer graphical interfaces to
|
|
do their development work. Eclipse being one of the most popular
|
|
Integrated Development Environment, Buildroot integrates with Eclipse
|
|
in order to ease the development work of Eclipse users.
|
|
|
|
Our integration with Eclipse simplifies the compilation, remote
|
|
execution and remote debugging of applications and libraries that are
|
|
built on top of a Buildroot system. It does not integrate the
|
|
Buildroot configuration and build processes themselves with
|
|
Eclipse. Therefore, the typical usage model of our Eclipse integration
|
|
would be:
|
|
|
|
* Configure your Buildroot system with +make menuconfig+, +make
|
|
xconfig+ or any other configuration interface provided with
|
|
Buildroot.
|
|
* Build your Buildroot system by running +make+.
|
|
* Start Eclipse to develop, execute and debug your own custom
|
|
applications and libraries, that will rely on the libraries built
|
|
and installed by Buildroot.
|
|
|
|
The Buildroot Eclipse integration installation process and usage is
|
|
described in detail at
|
|
https://github.com/mbats/eclipse-buildroot-bundle/wiki.
|