Blame - import-layers/yocto-poky/documentation/sdk-manual/sdk-eclipse-project.xml - openbmc/owners-plugin-test

<ulink url='https://wiki.yoctoproject.org/wiki/TipsAndTricks/RunningEclipseAgainstBuiltImage'>Cookbook guide to Making an Eclipse Debug Capable Image</ulink>

122

wiki page.

123

</note>

124

</para></listitem>

125

126

<emphasis>Create and build your application</emphasis>:

127

At this point, you need to have source files for your

128

application.

129

Once you have the files, you can use the Eclipse IDE

130

to import them and build the project.

131

If you are not using Eclipse, you need to use the

132

cross-development tools you have installed to create

133

the image.</para></listitem>

134

135

<emphasis>Deploy the image with the

136

application</emphasis>:

137

Using the Eclipse IDE, you can deploy your image to the

138

hardware or to QEMU through the project's preferences.

139

You can also use Eclipse to load and test your image

140

under QEMU.

141

See the

142

"<ulink url='&YOCTO_DOCS_DEV_URL;#dev-manual-qemu'>Using the Quick EMUlator (QEMU)</ulink>"

143

chapter in the Yocto Project Development Tasks Manual

144

for information on using QEMU.

145

</para></listitem>

146

147

<emphasis>Test and debug the application</emphasis>:

148

Once your application is deployed, you need to test it.

149

Within the Eclipse IDE, you can use the debugging

150

environment along with supported performance enhancing

151

<ulink url='http://www.eclipse.org/linuxtools/'>Linux Tools</ulink>.

</para></listitem>

</orderedlist>

</para>

</section>

<title>Working Within Eclipse</title>

159

160

<para>

161

The Eclipse IDE is a popular development environment and it

162

fully supports development using the Yocto Project.

</para>

<para>

When you install and configure the Eclipse Yocto Project

167

Plug-in into the Eclipse IDE, you maximize your Yocto

168

Project experience.

169

Installing and configuring the Plug-in results in an

170

environment that has extensions specifically designed to let

171

you more easily develop software.

172

These extensions allow for cross-compilation, deployment, and

173

execution of your output into a QEMU emulation session as well

174

as actual target hardware.

175

You can also perform cross-debugging and profiling.

176

The environment also supports performance enhancing

177

<ulink url='http://www.eclipse.org/linuxtools/'>tools</ulink>

178

that allow you to perform remote profiling, tracing,

179

collection of power data, collection of latency data, and

180

collection of performance data.

181

<note>

182

This release of the Yocto Project supports both the Neon

183

and Mars versions of the Eclipse IDE.

184

This section provides information on how to use the Neon

185

release with the Yocto Project.

186

For information on how to use the Mars version of Eclipse

187

with the Yocto Project, see

188

"<link linkend='sdk-appendix-latest-yp-eclipse-plug-in'>Appendix C</link>.

</note>

</para>

<title>Setting Up the Neon Version of the Eclipse IDE</title>

194

195

<para>

196

To develop within the Eclipse IDE, you need to do the

following:

Install the Neon version of the Eclipse IDE.

201

</para></listitem>

202

203

Configure the Eclipse IDE.

204

</para></listitem>

205

206

Install the Eclipse Yocto Plug-in.

207

</para></listitem>

208

209

Configure the Eclipse Yocto Plug-in.

</para></listitem>

</orderedlist>

<note>

Do not install Eclipse from your distribution's package

214

repository.

215

Be sure to install Eclipse from the official Eclipse

216

download site as directed in the next section.

</note>

</para>

<title>Installing the Neon Eclipse IDE</title>

222

223

<para>

224

Follow these steps to locate, install, and configure

Neon Eclipse:

<emphasis>Locate the Neon Download:</emphasis>

229

Open a browser and go to

230

<ulink url='http://www.eclipse.org/neon/'>http://www.eclipse.org/neon/</ulink>.

231

</para></listitem>

232

233

<emphasis>Download the Tarball:</emphasis>

234

Click through the "Download" buttons to

download the file.

</para></listitem>

<emphasis>Unpack the Tarball:</emphasis>

239

Move to a clean directory and unpack the

tarball.

Here is an example:

$ cd ~

$ tar -xzvf ~/Downloads/eclipse-inst-linux64.tar.gz

245

</literallayout>

246

Everything unpacks into a folder named

"eclipse-installer".

</para></listitem>

<emphasis>Launch the Installer:</emphasis>

251

Use the following commands to launch the

252

installer:

253

254

$ cd ~/eclipse-installer

$ ./eclipse-inst

</literallayout>

</para></listitem>

<emphasis>Select Your IDE:</emphasis>

260

From the list, select the "Eclipse IDE for

C/C++ Developers".

</para></listitem>

<emphasis>Install the Software:</emphasis>

265

Accept the default "cpp-neon" directory and

266

click "Install".

267

Accept any license agreements and approve any

certificates.

</para></listitem>

<emphasis>Launch Neon:</emphasis>

272

Click the "Launch" button and accept the

default "workspace".

</para></listitem>

</orderedlist>

</para>

</section>

<title>Configuring the Neon Eclipse IDE</title>

281

282

<para>

283

Follow these steps to configure the Neon Eclipse IDE.

284

<note>

285

Depending on how you installed Eclipse and what

286

you have already done, some of the options will

287

not appear.

288

If you cannot find an option as directed by the

289

manual, it has already been installed.

</note>

Be sure Eclipse is running and you are in your

workbench.

</para></listitem>

Select "Install New Software" from the "Help"

pull-down menu.

</para></listitem>

Select

"Neon - http://download.eclipse.org/releases/neon"

303

from the "Work with:" pull-down menu.

304

</para></listitem>

305

306

Expand the box next to "Linux Tools" and select

307

the following:

308

309

C/C++ Remote (Over TCF/TE) Run/Debug Launcher

TM Terminal

</literallayout>

</para></listitem>

Expand the box next to "Mobile and Device

315

Development" and select the following

316

boxes:

317

318

C/C++ Remote (Over TCF/TE) Run/Debug Launcher

319

Remote System Explorer User Actions

320

TM Terminal

321

TCF Remote System Explorer add-in

TCF Target Explorer

</literallayout>

</para></listitem>

Expand the box next to "Programming Languages"

327

and select the following box:

328

329

C/C++ Development Tools SDK

</literallayout>

</para></listitem>

Complete the installation by clicking through

334

appropriate "Next" and "Finish" buttons.

</para></listitem>

</orderedlist>

</para>

</section>

<title>Installing or Accessing the Neon Eclipse Yocto Plug-in</title>

342

343

<para>

344

You can install the Eclipse Yocto Plug-in into the

345

Eclipse IDE one of two ways: use the Yocto Project's

346

Eclipse Update site to install the pre-built plug-in

347

or build and install the plug-in from the latest

source code.

</para>

<title>Installing the Pre-built Plug-in from the Yocto Project Eclipse Update Site</title>

353

354

<para>

355

To install the Neon Eclipse Yocto Plug-in from the

356

update site, follow these steps:

357

358

359

Start up the Eclipse IDE.

360

</para></listitem>

361

362

In Eclipse, select "Install New

363

Software" from the "Help" menu.

364

</para></listitem>

365

366

Click "Add..." in the "Work with:" area.

</para></listitem>

Enter

<filename>&ECLIPSE_DL_PLUGIN_URL;/neon</filename>

371

in the URL field and provide a meaningful

372

name in the "Name" field.

373

</para></listitem>

374

375

Click "OK" to have the entry added

376

to the "Work with:" drop-down list.

377

</para></listitem>

378

379

Select the entry for the plug-in

380

from the "Work with:" drop-down list.

381

</para></listitem>

382

383

Check the boxes next to the following:

384

385

Yocto Project SDK Plug-in

386

Yocto Project Documentation plug-in

</literallayout>

</para></listitem>

Complete the remaining software

391

installation steps and then restart the

392

Eclipse IDE to finish the installation of

393

the plug-in.

394

<note>

395

You can click "OK" when prompted about

396

installing software that contains

unsigned content.

</note>

</para></listitem>

</orderedlist>

</para>

</section>

<title>Installing the Plug-in Using the Latest Source Code</title>

406

407

<para>

408

To install the Neon Eclipse Yocto Plug-in from the

409

latest source code, follow these steps:

410

411

412

Be sure your development system

has JDK 1.8+

</para></listitem>

Install X11-related packages:

417

418

$ sudo apt-get install xauth

</literallayout>

</para></listitem>

In a new terminal shell, create a

Git repository with:

$ cd ~

$ git clone git://git.yoctoproject.org/eclipse-poky

</literallayout>

</para></listitem>

Use Git to create the correct tag:

431

432

$ cd ~/eclipse-poky

433

$ git checkout neon/yocto-&DISTRO;

434

</literallayout>

435

This creates a local tag named

436

<filename>neon/yocto-&DISTRO;</filename>

437

based on the branch

438

<filename>origin/neon-master</filename>.

439

You are put into a detached HEAD state,

440

which is fine since you are only going to

441

be building and not developing.

442

</para></listitem>

443

444

Change to the <filename>scripts</filename>

445

directory within the Git repository:

$ cd scripts

</literallayout>

</para></listitem>

Set up the local build environment

452

by running the setup script:

$ ./setup.sh

</literallayout>

When the script finishes execution,

457

it prompts you with instructions on how to

458

run the <filename>build.sh</filename>

459

script, which is also in the

460

<filename>scripts</filename> directory of

461

the Git repository created earlier.

462

</para></listitem>

463

464

Run the <filename>build.sh</filename>

465

script as directed.

466

Be sure to provide the tag name,

467

documentation branch, and a release name.

468

</para>

469

<para>

470

Following is an example:

471

472

$ ECLIPSE_HOME=/home/scottrif/eclipse-poky/scripts/eclipse ./build.sh -l neon/yocto-&DISTRO; master yocto-&DISTRO; 2>&1 | tee build.log

473

</literallayout>

474

The previous example command adds the tag

475

you need for

476

<filename>mars/yocto-&DISTRO;</filename>

477

to <filename>HEAD</filename>, then tells

478

the build script to use the local (-l) Git

479

checkout for the build.

480

After running the script, the file

481

<filename>org.yocto.sdk-</filename><replaceable>release</replaceable><filename>-</filename><replaceable>date</replaceable><filename>-archive.zip</filename>

482

is in the current directory.

483

</para></listitem>

484

485

If necessary, start the Eclipse IDE

486

and be sure you are in the Workbench.

487

</para></listitem>

488

489

Select "Install New Software" from

490

the "Help" pull-down menu.

</para></listitem>

Click "Add".

</para></listitem>

Provide anything you want in the

"Name" field.

</para></listitem>

Click "Archive" and browse to the

501

ZIP file you built earlier.

502

This ZIP file should not be "unzipped", and

503

must be the

504

<filename>*archive.zip</filename> file

505

created by running the

506

<filename>build.sh</filename> script.

507

</para></listitem>

508

509

Click the "OK" button.

510

</para></listitem>

511

512

Check the boxes that appear in

513

the installation window to install the

514

following:

515

516

Yocto Project SDK Plug-in

517

Yocto Project Documentation plug-in

</literallayout>

</para></listitem>

Finish the installation by clicking

522

through the appropriate buttons.

523

You can click "OK" when prompted about

524

installing software that contains unsigned

content.

</para></listitem>

Restart the Eclipse IDE if necessary.

</para></listitem>

</orderedlist>

</para>

<para>

At this point you should be able to configure the

535

Eclipse Yocto Plug-in as described in the

536

"<link linkend='mars-configuring-the-eclipse-yocto-plug-in'>Configuring the Neon Eclipse Yocto Plug-in</link>"

section.

</para>

</section>

</section>

<title>Configuring the Neon Eclipse Yocto Plug-in</title>

544

545

<para>

546

Configuring the Neon Eclipse Yocto Plug-in involves

547

setting the Cross Compiler options and the Target

548

options.

549

The configurations you choose become the default

550

settings for all projects.

551

You do have opportunities to change them later when

552

you configure the project (see the following section).

</para>

<para>

To start, you need to do the following from within the

Eclipse IDE:

Choose "Preferences" from the "Window" menu to

561

display the Preferences Dialog.

562

</para></listitem>

563

564

Click "Yocto Project SDK" to display

565

the configuration screen.

566

</para></listitem>

567

</itemizedlist>

568

The following sub-sections describe how to configure

569

the plug-in.

570

<note>

571

Throughout the descriptions, a start-to-finish

572

example for preparing a QEMU image for use with

573

Eclipse is referenced as the "wiki" and is linked

574

to the example on the

575

<ulink url='https://wiki.yoctoproject.org/wiki/TipsAndTricks/RunningEclipseAgainstBuiltImage'> Cookbook guide to Making an Eclipse Debug Capable Image</ulink>

wiki page.

</note>

</para>

<title>Configuring the Cross-Compiler Options</title>

582

583

<para>

584

Cross Compiler options enable Eclipse to use your

585

specific cross compiler toolchain.

586

To configure these options, you must select

587

the type of toolchain, point to the toolchain,

588

specify the sysroot location, and select the target

architecture.

<emphasis>Selecting the Toolchain

593

Type:</emphasis>

594

Choose between

595

<filename>Standalone pre-built toolchain</filename>

596

and

597

<filename>Build system derived toolchain</filename>

598

for Cross Compiler Options.

<filename>Standalone Pre-built Toolchain:</filename>

603

</emphasis>

604

Select this type when you are using

605

a stand-alone cross-toolchain.

606

For example, suppose you are an

607

application developer and do not

608

need to build a target image.

609

Instead, you just want to use an

610

architecture-specific toolchain on

611

an existing kernel and target root

612

filesystem.

613

In other words, you have downloaded

614

and installed a pre-built toolchain

615

for an existing image.

</para></listitem>

<filename>Build System Derived Toolchain:</filename>

620

</emphasis>

621

Select this type if you built the

622

toolchain as part of the

623

<ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>.

624

When you select

625

<filename>Build system derived toolchain</filename>,

626

you are using the toolchain built

627

and bundled inside the Build

628

Directory.

629

For example, suppose you created a

630

suitable image using the steps in the

631

<ulink url='https://wiki.yoctoproject.org/wiki/TipsAndTricks/RunningEclipseAgainstBuiltImage'>wiki</ulink>.

632

In this situation, you would select

633

the

634

<filename>Build system derived toolchain</filename>.

</para></listitem>

</itemizedlist>

</para></listitem>

<emphasis>Specify the Toolchain Root

640

Location:</emphasis>

641

If you are using a stand-alone pre-built

642

toolchain, you should be pointing to where

643

it is installed (e.g.

644

<filename>/opt/poky/&DISTRO;</filename>).

645

See the

646

"<link linkend='sdk-installing-the-sdk'>Installing the SDK</link>"

647

section for information about how the SDK is

648

installed.</para>

649

<para>If you are using a build system

650

derived toolchain, the path you provide for

651

the

652

<filename>Toolchain Root Location</filename>

653

field is the

654

<ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>

655

from which you run the

656

<filename>bitbake</filename> command (e.g

657

<filename>/home/scottrif/poky/build</filename>).

658

</para>

659

<para>For more information, see the

660

"<link linkend='sdk-building-an-sdk-installer'>Building an SDK Installer</link>"

section.

</para></listitem>

<emphasis>Specify Sysroot Location:

665

</emphasis>

666

This location is where the root filesystem

667

for the target hardware resides.

668

</para>

669

<para>This location depends on where you

670

separately extracted and installed the

671

target filesystem when you either built

672

it or downloaded it.

673

<note>

674

If you downloaded the root filesystem

675

for the target hardware rather than

676

built it, you must download the

677

<filename>sato-sdk</filename> image

678

in order to build any c/c++ projects.

679

</note>

680

As an example, suppose you prepared an

681

image using the steps in the

682

<ulink url='https://wiki.yoctoproject.org/wiki/TipsAndTricks/RunningEclipseAgainstBuiltImage'>wiki</ulink>.

683

If so, the

684

<filename>MY_QEMU_ROOTFS</filename>

685

directory is found in the

686

<ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>

687

and you would browse to and select that

688

directory (e.g.

689

<filename>/home/scottrif/poky/build/MY_QEMU_ROOTFS</filename>).

690

</para>

691

<para>For more information on how to

692

install the toolchain and on how to extract

693

and install the sysroot filesystem, see the

694

"<link linkend='sdk-building-an-sdk-installer'>Building an SDK Installer</link>"

section.

</para></listitem>

<emphasis>Select the Target Architecture:

699

</emphasis>

700

The target architecture is the type of

701

hardware you are going to use or emulate.

702

Use the pull-down

703

<filename>Target Architecture</filename>

704

menu to make your selection.

705

The pull-down menu should have the

706

supported architectures.

707

If the architecture you need is not listed

708

in the menu, you will need to build the

709

image.

710

See the

711

"<ulink url='&YOCTO_DOCS_QS_URL;#qs-building-images'>Building Images</ulink>"

712

section of the Yocto Project Quick Start

713

for more information.

714

You can also see the

715

<ulink url='https://wiki.yoctoproject.org/wiki/TipsAndTricks/RunningEclipseAgainstBuiltImage'>wiki</ulink>.

</para></listitem>

</itemizedlist>

</para>

</section>

<title>Configuring the Target Options</title>

723

724

<para>

725

You can choose to emulate hardware using the QEMU

726

emulator, or you can choose to run your image on

actual hardware.

Select this option if you will be using the

732

QEMU emulator.

733

If you are using the emulator, you also

734

need to locate the kernel and specify any

735

custom options.</para>

736

<para>If you selected the

737

<filename>Build system derived toolchain</filename>,

738

the target kernel you built will be located

739

in the

740

<ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>

741

in

742

<filename>tmp/deploy/images/<replaceable>machine</replaceable></filename>

743

directory.

744

As an example, suppose you performed the

745

steps in the

746

<ulink url='https://wiki.yoctoproject.org/wiki/TipsAndTricks/RunningEclipseAgainstBuiltImage'>wiki</ulink>.

747

In this case, you specify your Build

748

Directory path followed by the image (e.g.

749

<filename>/home/scottrif/poky/build/tmp/deploy/images/qemux86/bzImage-qemux86.bin</filename>).

750

</para>

751

<para>If you selected the standalone

752

pre-built toolchain, the pre-built image

753

you downloaded is located in the directory

754

you specified when you downloaded the

755

image.</para>

756

<para>Most custom options are for advanced

757

QEMU users to further customize their QEMU

758

instance.

759

These options are specified between paired

760

angled brackets.

761

Some options must be specified outside the

762

brackets.

763

In particular, the options

764

<filename>serial</filename>,

765

<filename>nographic</filename>, and

766

<filename>kvm</filename> must all be

767

outside the brackets.

768

Use the <filename>man qemu</filename>

769

command to get help on all the options and

770

their use.

771

The following is an example:

772

773

serial ‘<-m 256 -full-screen>’

774

</literallayout></para>

775

<para>

776

Regardless of the mode, Sysroot is already

777

defined as part of the Cross-Compiler

778

Options configuration in the

779

<filename>Sysroot Location:</filename>

field.

</para></listitem>

<emphasis>External HW:</emphasis>

784

Select this option if you will be using

785

actual hardware.</para></listitem>

</itemizedlist>

</para>

<para>

Click the "Apply" and "OK" to save your plug-in

configurations.

</para>

</section>

</section>

</section>

<title>Creating the Project</title>

799

800

<para>

801

You can create two types of projects: Autotools-based, or

802

Makefile-based.

803

This section describes how to create Autotools-based

804

projects from within the Eclipse IDE.

805

For information on creating Makefile-based projects in a

806

terminal window, see the

807

"<link linkend='makefile-based-projects'>Makefile-Based Projects</link>"

808

section.

809

<note>

810

Do not use special characters in project names

811

(e.g. spaces, underscores, etc.). Doing so can

812

cause configuration to fail.

</note>

</para>

<para>

To create a project based on a Yocto template and then

818

display the source code, follow these steps:

819

820

821

Select "C Project" from the "File -> New" menu.

</para></listitem>

Expand

<filename>Yocto Project SDK Autotools Project</filename>.

826

</para></listitem>

827

828

Select <filename>Hello World ANSI C Autotools Projects</filename>.

829

This is an Autotools-based project based on a Yocto

template.

</para></listitem>

Put a name in the

<filename>Project name:</filename> field.

835

Do not use hyphens as part of the name

836

(e.g. <filename>hello</filename>).

</para></listitem>

Click "Next".

</para></listitem>

Add appropriate information in the various fields.

</para></listitem>

Click "Finish".

</para></listitem>

If the "open perspective" prompt appears,

849

click "Yes" so that you in the C/C++ perspective.

850

</para></listitem>

851

<listitem><para>The left-hand navigation pane shows

852

your project.

853

You can display your source by double clicking the

854

project's source file.

</para></listitem>

</orderedlist>

</para>

</section>

<title>Configuring the Cross-Toolchains</title>

<para>

The earlier section,

"<link linkend='neon-configuring-the-eclipse-yocto-plug-in'>Configuring the Neon Eclipse Yocto Plug-in</link>",

866

sets up the default project configurations.

867

You can override these settings for a given project by

868

following these steps:

869

870

871

Select "Yocto Project Settings" from

872

the "Project -> Properties" menu.

873

This selection brings up the Yocto Project Settings

874

Dialog and allows you to make changes specific to

875

an individual project.</para>

876

<para>By default, the Cross Compiler Options and

877

Target Options for a project are inherited from

878

settings you provided using the Preferences Dialog

879

as described earlier in the

880

"<link linkend='neon-configuring-the-eclipse-yocto-plug-in'>Configuring the Neon Eclipse Yocto Plug-in</link>"

881

section.

882

The Yocto Project Settings Dialog allows you to

883

override those default settings for a given

project.

</para></listitem>

Make or verify your configurations for the

888

project and click "OK".

889

</para></listitem>

890

891

Right-click in the navigation pane and

892

select "Reconfigure Project" from the pop-up menu.

893

This selection reconfigures the project by running

894

<filename>autogen.sh</filename> in the workspace

895

for your project.

896

The script also runs

897

<filename>libtoolize</filename>,

898

<filename>aclocal</filename>,

899

<filename>autoconf</filename>,

900

<filename>autoheader</filename>,

901

<filename>automake --a</filename>, and

902

<filename>./configure</filename>.

903

Click on the "Console" tab beneath your source code

904

to see the results of reconfiguring your project.

</para></listitem>

</orderedlist>

</para>

</section>

<title>Building the Project</title>

912

<para>

913

To build the project select "Build All" from the

914

"Project" menu.

915

The console should update and you can note the

916

cross-compiler you are using.

917

<note>

918

When building "Yocto Project SDK Autotools" projects,

919

the Eclipse IDE might display error messages for

920

Functions/Symbols/Types that cannot be "resolved",

921

even when the related include file is listed at the

922

project navigator and when the project is able to

923

build.

924

For these cases only, it is recommended to add a new

925

linked folder to the appropriate sysroot.

926

Use these steps to add the linked folder:

Select the project.

</para></listitem>

Select "Folder" from the

933

<filename>File > New</filename> menu.

934

</para></listitem>

935

936

In the "New Folder" Dialog, select "Link to

937

alternate location (linked folder)".

938

</para></listitem>

939

940

Click "Browse" to navigate to the include

941

folder inside the same sysroot location

942

selected in the Yocto Project

943

configuration preferences.

</para></listitem>

Click "OK".

</para></listitem>

Click "Finish" to save the linked folder.

</para></listitem>

</orderedlist>

</note>

</para>

</section>

<title>Starting QEMU in User-Space NFS Mode</title>

958

959

<para>

960

To start the QEMU emulator from within Eclipse, follow

these steps:

<note>

See the

"<ulink url='&YOCTO_DOCS_DEV_URL;#dev-manual-qemu'>Using the Quick EMUlator (QEMU)</ulink>"

965

chapter in the Yocto Project Development Tasks Manual

966

for more information on using QEMU.

967

</note>

968

969

<listitem><para>Expose and select "External Tools

970

Configurations ..." from the "Run -> External

Tools" menu.

</para></listitem>

Locate and select your image in the navigation

975

panel to the left

976

(e.g. <filename>qemu_i586-poky-linux</filename>).

977

</para></listitem>

978

979

Click "Run" to launch QEMU.

980

<note>

981

The host on which you are running QEMU must

982

have the <filename>rpcbind</filename> utility

983

running to be able to make RPC calls on a

984

server on that machine.

985

If QEMU does not invoke and you receive error

986

messages involving

987

<filename>rpcbind</filename>, follow the

988

suggestions to get the service running.

989

As an example, on a new Ubuntu 16.04 LTS

990

installation, you must do the following in

991

order to get QEMU to launch:

992

993

$ sudo apt-get install rpcbind

994

</literallayout>

995

After installing <filename>rpcbind</filename>,

996

you need to edit the

997

<filename>/etc/init.d/rpcbind</filename> file

998

to include the following line:

OPTIONS="-i -w"

</literallayout>

After modifying the file, you need to start the

1003

service:

1004

1005

$ sudo service portmap restart

</literallayout>

</note>

</para></listitem>

If needed, enter your host root password in

1011

the shell window at the prompt.

1012

This sets up a <filename>Tap 0</filename>

1013

connection needed for running in user-space NFS

mode.

</para></listitem>

Wait for QEMU to launch.

1018

</para></listitem>

1019

1020

Once QEMU launches, you can begin operating

1021

within that environment.

1022

One useful task at this point would be to determine

1023

the IP Address for the user-space NFS by using the

1024

<filename>ifconfig</filename> command.

1025

The IP address of the QEMU machine appears in the

1026

xterm window.

1027

You can use this address to help you see which

1028

particular

1029

IP address the instance of QEMU is using.

</para></listitem>

</orderedlist>

</para>

</section>

<title>Deploying and Debugging the Application</title>

1037

1038

<para>

1039

Once the QEMU emulator is running the image, you can deploy

1040

your application using the Eclipse IDE and then use

1041

the emulator to perform debugging.

1042

Follow these steps to deploy the application.

1043

<note>

1044

Currently, Eclipse does not support SSH port

1045

forwarding.

1046

Consequently, if you need to run or debug a remote

1047

application using the host display, you must create a

1048

tunneling connection from outside Eclipse and keep

1049

that connection alive during your work.

1050

For example, in a new terminal, run the following:

1051

1052

$ ssh -XY <replaceable>user_name</replaceable>@<replaceable>remote_host_ip</replaceable>

1053

</literallayout>

1054

Using the above form, here is an example:

1055

1056

$ ssh -XY root@192.168.7.2

1057

</literallayout>

1058

After running the command, add the command to be

1059

executed in Eclipse's run configuration before the

1060

application as follows:

export DISPLAY=:10.0

</literallayout>

Be sure to not destroy the connection during your QEMU

1065

session (i.e. do not

1066

exit out of or close that shell).

</note>

Select "Debug Configurations..." from the

"Run" menu.

</para></listitem>

In the left area, expand

1075

<filename>C/C++Remote Application</filename>.

1076

</para></listitem>

1077

1078

Locate your project and select it to bring

1079

up a new tabbed view in the Debug Configurations

Dialog.

</para></listitem>

Click on the "Debugger" tab to see the

1084

cross-tool debugger you are using.

1085

Be sure to change to the debugger perspective in

Eclipse.

</para></listitem>

Click on the "Main" tab.

1090

</para></listitem>

1091

1092

Create a new connection to the QEMU instance

1093

by clicking on "new".</para></listitem>

1094

<listitem><para>Select <filename>SSH</filename>, which

1095

means Secure Socket Shell and then click "OK".

1096

Optionally, you can select a TCF connection

instead.

</para></listitem>

Clear out the "Connection name" field and

1101

enter any name you want for the connection.

1102

</para></listitem>

1103

1104

Put the IP address for the connection in

1105

the "Host" field.

1106

For QEMU, the default is

1107

<filename>192.168.7.2</filename>.

1108

However, if a previous QEMU session did not exit

1109

cleanly, the IP address increments (e.g.

1110

<filename>192.168.7.3</filename>).

1111

<note>

1112

You can find the IP address for the current

1113

QEMU session by looking in the xterm that

1114

opens when you launch QEMU.

</note>

</para></listitem>

Enter <filename>root</filename>, which

1119

is the default for QEMU, for the "User" field.

1120

Be sure to leave the password field empty.

1121

</para></listitem>

1122

1123

Click "Finish" to close the New Connections Dialog.

1124

</para></listitem>

1125

1126

If necessary, use the drop-down menu now in the

1127

"Connection" field and pick the IP Address you

entered.

</para></listitem>

Assuming you are connecting as the root

1132

user, which is the default for QEMU x86-64 SDK

1133

images provided by the Yocto Project, in the

1134

"Remote Absolute File Path for C/C++ Application"

1135

field, browse to

1136

<filename>/home/root/</filename><replaceable>ProjectName</replaceable>

1137

(e.g. <filename>/home/root/hello</filename>).

1138

You could also browse to any other path you have

1139

write access to on the target such as

1140

<filename>/usr/bin</filename>.

1141

This location is where your application will be

1142

located on the QEMU system.

1143

If you fail to browse to and specify an appropriate

1144

location, QEMU will not understand what to remotely

1145

launch.

1146

Eclipse is helpful in that it auto fills your

1147

application name for you assuming you browsed to a

directory.

If you are prompted to provide a username

1153

and to optionally set a password, be sure

1154

you provide "root" as the username and you

1155

leave the password field blank.

1156

</para></listitem>

1157

1158

If browsing to a directory fails or times

1159

out, but you can

1160

<filename>ssh</filename> into your QEMU

1161

or target from the command line and you

1162

have proxies set up, it is likely that

1163

Eclipse is sending the SSH traffic to a

1164

proxy.

1165

In this case, either use TCF , or click on

1166

"Configure proxy settings" in the

1167

connection dialog and add the target IP

1168

address to the "bypass proxy" section.

1169

You might also need to change

1170

"Active Provider" from Native to Manual.

</para></listitem>

</itemizedlist>

</note>

</para></listitem>

Be sure you change to the "Debug" perspective in

Eclipse.

</para></listitem>

Click "Debug"

</para></listitem>

Accept the debug perspective.

</para></listitem>

</orderedlist>

</para>

</section>

<title>Using Linuxtools</title>

1191

1192

<para>

1193

As mentioned earlier in the manual, performance tools exist

1194

(Linuxtools) that enhance your development experience.

1195

These tools are aids in developing and debugging

1196

applications and images.

1197

You can run these tools from within the Eclipse IDE through

1198

the "Linuxtools" menu.

</para>

<para>

For information on how to configure and use these tools,

1203

see

1204

<ulink url='http://www.eclipse.org/linuxtools/'>http://www.eclipse.org/linuxtools/</ulink>.

</para>

</section>

</section>

</chapter>

<!--

vim: expandtab tw=80 ts=4

1211

-->