~ubuntu-branches/ubuntu/warty/dasher/warty

INPUT = ../../Src/DasherCore/DashEdit.h ../../Src/DasherCore/DasherScreen.h ../../Src/DasherCore/SettingsStore.h ../../Src/DasherCore/DasherAppInterface.h ../../Src/DasherCore/DasherWidgetInterface.h ../../Src/DasherCore/DasherSettingsInterface.h ../../Src/DasherCore/DasherInterface.h ../../Src/DasherCore/DasherTypes.h

349

350

# If the value of the INPUT tag contains directories, you can use the

351

# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp

352

# and *.h) to filter out the source-files in the directories. If left

353

# blank the following patterns are tested:

354

# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp

355

# *.h++ *.idl *.odl

356

357

FILE_PATTERNS =

358

359

# The RECURSIVE tag can be used to turn specify whether or not subdirectories

360

# should be searched for input files as well. Possible values are YES and NO.

361

# If left blank NO is used.

362

363

RECURSIVE = NO

364

365

# The EXCLUDE tag can be used to specify files and/or directories that should

366

# excluded from the INPUT source files. This way you can easily exclude a

367

# subdirectory from a directory tree whose root is specified with the INPUT tag.

368

369

EXCLUDE =

370

371

# The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories

372

# that are symbolic links (a Unix filesystem feature) are excluded from the input.

373

374

EXCLUDE_SYMLINKS = NO

375

376

# If the value of the INPUT tag contains directories, you can use the

377

# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude

378

# certain files from those directories.

379

380

EXCLUDE_PATTERNS =

381

382

# The EXAMPLE_PATH tag can be used to specify one or more files or

383

# directories that contain example code fragments that are included (see

384

# the \include command).

385

386

EXAMPLE_PATH =

387

388

# If the value of the EXAMPLE_PATH tag contains directories, you can use the

389

# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp

390

# and *.h) to filter out the source-files in the directories. If left

391

# blank all files are included.

392

393

EXAMPLE_PATTERNS =

394

395

# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be

396

# searched for input files to be used with the \include or \dontinclude

397

# commands irrespective of the value of the RECURSIVE tag.

398

# Possible values are YES and NO. If left blank NO is used.

399

400

EXAMPLE_RECURSIVE = NO

401

402

# The IMAGE_PATH tag can be used to specify one or more files or

403

# directories that contain image that are included in the documentation (see

404

# the \image command).

405

406

IMAGE_PATH =

407

408

# The INPUT_FILTER tag can be used to specify a program that doxygen should

409

# invoke to filter for each input file. Doxygen will invoke the filter program

410

# by executing (via popen()) the command <filter> <input-file>, where <filter>

411

# is the value of the INPUT_FILTER tag, and <input-file> is the name of an

412

# input file. Doxygen will then use the output that the filter program writes

413

# to standard output.

414

415

INPUT_FILTER =

416

417

# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using

418

# INPUT_FILTER) will be used to filter the input files when producing source

419

# files to browse (i.e. when SOURCE_BROWSER is set to YES).

420

421

FILTER_SOURCE_FILES = NO

422

423

#---------------------------------------------------------------------------

424

# configuration options related to source browsing

425

#---------------------------------------------------------------------------

426

427

# If the SOURCE_BROWSER tag is set to YES then a list of source files will

428

# be generated. Documented entities will be cross-referenced with these sources.

429

430

SOURCE_BROWSER = NO

431

432

# Setting the INLINE_SOURCES tag to YES will include the body

433

# of functions and classes directly in the documentation.

434

435

INLINE_SOURCES = NO

436

437

# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct

438

# doxygen to hide any special comment blocks from generated source code

439

# fragments. Normal C and C++ comments will always remain visible.

440

441

STRIP_CODE_COMMENTS = YES

442

443

# If the REFERENCED_BY_RELATION tag is set to YES (the default)

444

# then for each documented function all documented

445

# functions referencing it will be listed.

446

447

REFERENCED_BY_RELATION = YES

448

449

# If the REFERENCES_RELATION tag is set to YES (the default)

450

# then for each documented function all documented entities

451

# called/used by that function will be listed.

452

453

REFERENCES_RELATION = YES

454

455

#---------------------------------------------------------------------------

456

# configuration options related to the alphabetical class index

457

#---------------------------------------------------------------------------

458

459

# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index

460

# of all compounds will be generated. Enable this if the project

461

# contains a lot of classes, structs, unions or interfaces.

462

463

ALPHABETICAL_INDEX = NO

464

465

# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then

466

# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns

467

# in which this list will be split (can be a number in the range [1..20])

468

469

COLS_IN_ALPHA_INDEX = 5

470

471

# In case all classes in a project start with a common prefix, all

472

# classes will be put under the same header in the alphabetical index.

473

# The IGNORE_PREFIX tag can be used to specify one or more prefixes that

474

# should be ignored while generating the index headers.

475

476

IGNORE_PREFIX =

477

478

#---------------------------------------------------------------------------

479

# configuration options related to the HTML output

480

#---------------------------------------------------------------------------

481

482

# If the GENERATE_HTML tag is set to YES (the default) Doxygen will

483

# generate HTML output.

484

485

GENERATE_HTML = YES

486

487

# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.

488

# If a relative path is entered the value of OUTPUT_DIRECTORY will be

489

# put in front of it. If left blank `html' will be used as the default path.

490

491

HTML_OUTPUT = html

492

493

# The HTML_FILE_EXTENSION tag can be used to specify the file extension for

494

# each generated HTML page (for example: .htm,.php,.asp). If it is left blank

495

# doxygen will generate files with .html extension.

496

497

HTML_FILE_EXTENSION = .html

498

499

# The HTML_HEADER tag can be used to specify a personal HTML header for

500

# each generated HTML page. If it is left blank doxygen will generate a

501

# standard header.

502

503

HTML_HEADER =

504

505

# The HTML_FOOTER tag can be used to specify a personal HTML footer for

506

# each generated HTML page. If it is left blank doxygen will generate a

507

# standard footer.

508

509

HTML_FOOTER =

510

511

# The HTML_STYLESHEET tag can be used to specify a user defined cascading

512

# style sheet that is used by each HTML page. It can be used to

513

# fine-tune the look of the HTML output. If the tag is left blank doxygen

514

# will generate a default style sheet

515

516

HTML_STYLESHEET =

517

518

# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,

519

# files or namespaces will be aligned in HTML using tables. If set to

520

# NO a bullet list will be used.

521

522

HTML_ALIGN_MEMBERS = YES

523

524

# If the GENERATE_HTMLHELP tag is set to YES, additional index files

525

# will be generated that can be used as input for tools like the

526

# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)

527

# of the generated HTML documentation.

528

529

GENERATE_HTMLHELP = NO

530

531

# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can

532

# be used to specify the file name of the resulting .chm file. You

533

# can add a path in front of the file if the result should not be

534

# written to the html output dir.

535

536

CHM_FILE =

537

538

# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can

539

# be used to specify the location (absolute path including file name) of

540

# the HTML help compiler (hhc.exe). If non empty doxygen will try to run

541

# the html help compiler on the generated index.hhp.

542

543

HHC_LOCATION =

544

545

# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag

546

# controls if a separate .chi index file is generated (YES) or that

547

# it should be included in the master .chm file (NO).

548

549

GENERATE_CHI = NO

550

551

# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag

552

# controls whether a binary table of contents is generated (YES) or a

553

# normal table of contents (NO) in the .chm file.

554

555

BINARY_TOC = NO

556

557

# The TOC_EXPAND flag can be set to YES to add extra items for group members

558

# to the contents of the Html help documentation and to the tree view.

559

560

TOC_EXPAND = NO

561

562

# The DISABLE_INDEX tag can be used to turn on/off the condensed index at

563

# top of each HTML page. The value NO (the default) enables the index and

564

# the value YES disables it.

565

566

DISABLE_INDEX = NO

567

568

# This tag can be used to set the number of enum values (range [1..20])

569

# that doxygen will group on one line in the generated HTML documentation.

570

571

ENUM_VALUES_PER_LINE = 4

572

573

# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be

574

# generated containing a tree-like index structure (just like the one that

575

# is generated for HTML Help). For this to work a browser that supports

576

# JavaScript, DHTML, CSS and frames is required (for instance Mozilla,

577

# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are

578

# probably better off using the HTML help feature.

579

580

GENERATE_TREEVIEW = NO

581

582

# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be

583

# used to set the initial width (in pixels) of the frame in which the tree

584

# is shown.

585

586

TREEVIEW_WIDTH = 250

587

588

#---------------------------------------------------------------------------

589

# configuration options related to the LaTeX output

590

#---------------------------------------------------------------------------

591

592

# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will

593

# generate Latex output.

594

595

GENERATE_LATEX = YES

596

597

# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.

598

# If a relative path is entered the value of OUTPUT_DIRECTORY will be

599

# put in front of it. If left blank `latex' will be used as the default path.

600

601

LATEX_OUTPUT = latex

602

603

# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be

604

# invoked. If left blank `latex' will be used as the default command name.

605

606

LATEX_CMD_NAME = latex

607

608

# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to

609

# generate index for LaTeX. If left blank `makeindex' will be used as the

610

# default command name.

611

612

MAKEINDEX_CMD_NAME = makeindex

613

614

# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact

615

# LaTeX documents. This may be useful for small projects and may help to

616

# save some trees in general.

617

618

COMPACT_LATEX = NO

619

620

# The PAPER_TYPE tag can be used to set the paper type that is used

621

# by the printer. Possible values are: a4, a4wide, letter, legal and

622

# executive. If left blank a4wide will be used.

623

624

PAPER_TYPE = a4wide

625

626

# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX

627

# packages that should be included in the LaTeX output.

628

629

EXTRA_PACKAGES =

630

631

# The LATEX_HEADER tag can be used to specify a personal LaTeX header for

632

# the generated latex document. The header should contain everything until

633

# the first chapter. If it is left blank doxygen will generate a

634

# standard header. Notice: only use this tag if you know what you are doing!

635

636

LATEX_HEADER =

637

638

# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated

639

# is prepared for conversion to pdf (using ps2pdf). The pdf file will

640

# contain links (just like the HTML output) instead of page references

641

# This makes the output suitable for online browsing using a pdf viewer.

642

643

PDF_HYPERLINKS = NO

644

645

# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of

646

# plain latex in the generated Makefile. Set this option to YES to get a

647

# higher quality PDF documentation.

648

649

USE_PDFLATEX = NO

650

651

# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.

652

# command to the generated LaTeX files. This will instruct LaTeX to keep

653

# running if errors occur, instead of asking the user for help.

654

# This option is also used when generating formulas in HTML.

655

656

LATEX_BATCHMODE = NO

657

658

#---------------------------------------------------------------------------

659

# configuration options related to the RTF output

660

#---------------------------------------------------------------------------

661

662

# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output

663

# The RTF output is optimised for Word 97 and may not look very pretty with

664

# other RTF readers or editors.

665

666

GENERATE_RTF = NO

667

668

# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.

669

# If a relative path is entered the value of OUTPUT_DIRECTORY will be

670

# put in front of it. If left blank `rtf' will be used as the default path.

671

672

RTF_OUTPUT = rtf

673

674

# If the COMPACT_RTF tag is set to YES Doxygen generates more compact

675

# RTF documents. This may be useful for small projects and may help to

676

# save some trees in general.

677

678

COMPACT_RTF = NO

679

680

# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated

681

# will contain hyperlink fields. The RTF file will

682

# contain links (just like the HTML output) instead of page references.

683

# This makes the output suitable for online browsing using WORD or other

684

# programs which support those fields.

685

# Note: wordpad (write) and others do not support links.

686

687

RTF_HYPERLINKS = NO

688

689

# Load stylesheet definitions from file. Syntax is similar to doxygen's

690

# config file, i.e. a series of assigments. You only have to provide

691

# replacements, missing definitions are set to their default value.

692

693

RTF_STYLESHEET_FILE =

694

695

# Set optional variables used in the generation of an rtf document.

696

# Syntax is similar to doxygen's config file.

697

698

RTF_EXTENSIONS_FILE =

699

700

#---------------------------------------------------------------------------

701

# configuration options related to the man page output

702

#---------------------------------------------------------------------------

703

704

# If the GENERATE_MAN tag is set to YES (the default) Doxygen will

705

# generate man pages

706

707

GENERATE_MAN = NO

708

709

# The MAN_OUTPUT tag is used to specify where the man pages will be put.

710

# If a relative path is entered the value of OUTPUT_DIRECTORY will be

711

# put in front of it. If left blank `man' will be used as the default path.

712

713

MAN_OUTPUT = man

714

715

# The MAN_EXTENSION tag determines the extension that is added to

716

# the generated man pages (default is the subroutine's section .3)

717

718

MAN_EXTENSION = .3

719

720

# If the MAN_LINKS tag is set to YES and Doxygen generates man output,

721

# then it will generate one additional man file for each entity

722

# documented in the real man page(s). These additional files

723

# only source the real man page, but without them the man command

724

# would be unable to find the correct page. The default is NO.

725

726

MAN_LINKS = NO

727

728

#---------------------------------------------------------------------------

729

# configuration options related to the XML output

730

#---------------------------------------------------------------------------

731

732

# If the GENERATE_XML tag is set to YES Doxygen will

733

# generate an XML file that captures the structure of

734

# the code including all documentation. Note that this

735

# feature is still experimental and incomplete at the

736

# moment.

737

738

GENERATE_XML = NO

739

740

# The XML_SCHEMA tag can be used to specify an XML schema,

741

# which can be used by a validating XML parser to check the

742

# syntax of the XML files.

743

744

XML_SCHEMA =

745

746

# The XML_DTD tag can be used to specify an XML DTD,

747

# which can be used by a validating XML parser to check the

748

# syntax of the XML files.

749

750

XML_DTD =

751

752

#---------------------------------------------------------------------------

753

# configuration options for the AutoGen Definitions output

754

#---------------------------------------------------------------------------

755

756

# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will

757

# generate an AutoGen Definitions (see autogen.sf.net) file

758

# that captures the structure of the code including all

759

# documentation. Note that this feature is still experimental

760

# and incomplete at the moment.

761

762

GENERATE_AUTOGEN_DEF = NO

763

764

#---------------------------------------------------------------------------

765

# configuration options related to the Perl module output

766

#---------------------------------------------------------------------------

767

768

# If the GENERATE_PERLMOD tag is set to YES Doxygen will

769

# generate a Perl module file that captures the structure of

770

# the code including all documentation. Note that this

771

# feature is still experimental and incomplete at the

772

# moment.

773

774

GENERATE_PERLMOD = NO

775

776

# If the PERLMOD_LATEX tag is set to YES Doxygen will generate

777

# the necessary Makefile rules, Perl scripts and LaTeX code to be able

778

# to generate PDF and DVI output from the Perl module output.

779

780

PERLMOD_LATEX = NO

781

782

# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be

783

# nicely formatted so it can be parsed by a human reader. This is useful

784

# if you want to understand what is going on. On the other hand, if this

785

# tag is set to NO the size of the Perl module output will be much smaller

786

# and Perl will parse it just the same.

787

788

PERLMOD_PRETTY = YES

789

790

# The names of the make variables in the generated doxyrules.make file

791

# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.

792

# This is useful so different doxyrules.make files included by the same

793

# Makefile don't overwrite each other's variables.

794

795

PERLMOD_MAKEVAR_PREFIX =

796

797

#---------------------------------------------------------------------------

798

# Configuration options related to the preprocessor

799

#---------------------------------------------------------------------------

800

801

# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will

802

# evaluate all C-preprocessor directives found in the sources and include

803

# files.

804

805

ENABLE_PREPROCESSING = YES

806

807

# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro

808

# names in the source code. If set to NO (the default) only conditional

809

# compilation will be performed. Macro expansion can be done in a controlled

810

# way by setting EXPAND_ONLY_PREDEF to YES.

811

812

MACRO_EXPANSION = NO

813

814

# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES

815

# then the macro expansion is limited to the macros specified with the

816

# PREDEFINED and EXPAND_AS_PREDEFINED tags.

817

818

EXPAND_ONLY_PREDEF = NO

819

820

# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files

821

# in the INCLUDE_PATH (see below) will be search if a #include is found.

822

823

SEARCH_INCLUDES = YES

824

825

# The INCLUDE_PATH tag can be used to specify one or more directories that

826

# contain include files that are not input files but should be processed by

827

# the preprocessor.

828

829

INCLUDE_PATH =

830

831

# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard

832

# patterns (like *.h and *.hpp) to filter out the header-files in the

833

# directories. If left blank, the patterns specified with FILE_PATTERNS will

834

# be used.

835

836

INCLUDE_FILE_PATTERNS =

837

838

# The PREDEFINED tag can be used to specify one or more macro names that

839

# are defined before the preprocessor is started (similar to the -D option of

840

# gcc). The argument of the tag is a list of macros of the form: name

841

# or name=definition (no spaces). If the definition and the = are

842

# omitted =1 is assumed.

843

844

PREDEFINED =

845

846

# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then

847

# this tag can be used to specify a list of macro names that should be expanded.

848

# The macro definition that is found in the sources will be used.

849

# Use the PREDEFINED tag if you want to use a different macro definition.

850

851

EXPAND_AS_DEFINED =

852

853

# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then

854

# doxygen's preprocessor will remove all function-like macros that are alone

855

# on a line, have an all uppercase name, and do not end with a semicolon. Such

856

# function macros are typically used for boiler-plate code, and will confuse the

857

# parser if not removed.

858

859

SKIP_FUNCTION_MACROS = YES

860

861

#---------------------------------------------------------------------------

862

# Configuration::addtions related to external references

863

#---------------------------------------------------------------------------

864

865

# The TAGFILES tag can be used to specify one or more tagfiles.

866

867

TAGFILES =

868

869

# When a file name is specified after GENERATE_TAGFILE, doxygen will create

870

# a tag file that is based on the input files it reads.

871

872

GENERATE_TAGFILE =

873

874

# If the ALLEXTERNALS tag is set to YES all external classes will be listed

875

# in the class index. If set to NO only the inherited external classes

876

# will be listed.

877

878

ALLEXTERNALS = NO

879

880

# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed

881

# in the modules index. If set to NO, only the current project's groups will

882

# be listed.

883

884

EXTERNAL_GROUPS = YES

885

886

# The PERL_PATH should be the absolute path and name of the perl script

887

# interpreter (i.e. the result of `which perl').

888

889

PERL_PATH = /usr/bin/perl

890

891

#---------------------------------------------------------------------------

892

# Configuration options related to the dot tool

893

#---------------------------------------------------------------------------

894

895

# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will

896

# generate a inheritance diagram (in Html, RTF and LaTeX) for classes with base or

897

# super classes. Setting the tag to NO turns the diagrams off. Note that this

898

# option is superceded by the HAVE_DOT option below. This is only a fallback. It is

899

# recommended to install and use dot, since it yield more powerful graphs.

900

901

CLASS_DIAGRAMS = YES

902

903

# If set to YES, the inheritance and collaboration graphs will hide

904

# inheritance and usage relations if the target is undocumented

905

# or is not a class.

906

907

HIDE_UNDOC_RELATIONS = YES

908

909

# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is

910

# available from the path. This tool is part of Graphviz, a graph visualization

911

# toolkit from AT&T and Lucent Bell Labs. The other options in this section

912

# have no effect if this option is set to NO (the default)

913

914

HAVE_DOT = NO

915

916

# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen

917

# will generate a graph for each documented class showing the direct and

918

# indirect inheritance relations. Setting this tag to YES will force the

919

# the CLASS_DIAGRAMS tag to NO.

920

921

CLASS_GRAPH = YES

922

923

# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen

924

# will generate a graph for each documented class showing the direct and

925

# indirect implementation dependencies (inheritance, containment, and

926

# class references variables) of the class with other documented classes.

927

928

COLLABORATION_GRAPH = YES

929

930

# If set to YES, the inheritance and collaboration graphs will show the

931

# relations between templates and their instances.

932

933

TEMPLATE_RELATIONS = YES

934

935

# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT

936

# tags are set to YES then doxygen will generate a graph for each documented

937

# file showing the direct and indirect include dependencies of the file with

938

# other documented files.

939

940

INCLUDE_GRAPH = YES

941

942

# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and

943

# HAVE_DOT tags are set to YES then doxygen will generate a graph for each

944

# documented header file showing the documented files that directly or

945

# indirectly include this file.

946

947

INCLUDED_BY_GRAPH = YES

948

949

# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen

950

# will graphical hierarchy of all classes instead of a textual one.

951

952

GRAPHICAL_HIERARCHY = YES

953

954

# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images

955

# generated by dot. Possible values are png, jpg, or gif

956

# If left blank png will be used.

957

958

DOT_IMAGE_FORMAT = png

959

960

# The tag DOT_PATH can be used to specify the path where the dot tool can be

961

# found. If left blank, it is assumed the dot tool can be found on the path.

962

963

DOT_PATH =

964

965

# The DOTFILE_DIRS tag can be used to specify one or more directories that

966

# contain dot files that are included in the documentation (see the

967

# \dotfile command).

968

969

DOTFILE_DIRS =

970

971

# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width

972

# (in pixels) of the graphs generated by dot. If a graph becomes larger than

973

# this value, doxygen will try to truncate the graph, so that it fits within

974

# the specified constraint. Beware that most browsers cannot cope with very

975

# large images.

976

977

MAX_DOT_GRAPH_WIDTH = 1024

978

979

# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height

980

# (in pixels) of the graphs generated by dot. If a graph becomes larger than

981

# this value, doxygen will try to truncate the graph, so that it fits within

982

# the specified constraint. Beware that most browsers cannot cope with very

983

# large images.

984

985

MAX_DOT_GRAPH_HEIGHT = 1024

986

987

# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will

988

# generate a legend page explaining the meaning of the various boxes and

989

# arrows in the dot generated graphs.

990

991

GENERATE_LEGEND = YES

992

993

# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will

994

# remove the intermedate dot files that are used to generate

995

# the various graphs.

996

997

DOT_CLEANUP = YES

998

999

#---------------------------------------------------------------------------

1000

# Configuration::addtions related to the search engine

1001

#---------------------------------------------------------------------------

1002

1003

# The SEARCHENGINE tag specifies whether or not a search engine should be

1004

# used. If set to NO the values of all tags below this one will be ignored.

1005

1006

SEARCHENGINE = NO

1007

1008

# The CGI_NAME tag should be the name of the CGI script that

1009

# starts the search engine (doxysearch) with the correct parameters.

1010

# A script with this name will be generated by doxygen.

1011

1012

CGI_NAME = search.cgi

1013

1014

# The CGI_URL tag should be the absolute URL to the directory where the

1015

# cgi binaries are located. See the documentation of your http daemon for

1016

# details.

1017

1018

CGI_URL =

1019

1020

# The DOC_URL tag should be the absolute URL to the directory where the

1021

# documentation is located. If left blank the absolute path to the

1022

# documentation, with file:// prepended to it, will be used.

1023

1024

DOC_URL =

1025

1026

# The DOC_ABSPATH tag should be the absolute path to the directory where the

1027

# documentation is located. If left blank the directory on the local machine

1028

# will be used.

1029

1030

DOC_ABSPATH =

1031

1032

# The BIN_ABSPATH tag must point to the directory where the doxysearch binary

1033

# is installed.

1034

1035

BIN_ABSPATH = /usr/local/bin/

1036

1037

# The EXT_DOC_PATHS tag can be used to specify one or more paths to

1038

# documentation generated for other projects. This allows doxysearch to search

1039

# the documentation for these projects as well.

1040

1041

EXT_DOC_PATHS =

Older »