Home > Store

Cross-Platform Development in C++: Building Mac OS X, Linux, and Windows Applications

Register your product to gain access to bonus material or receive a coupon.

Cross-Platform Development in C++: Building Mac OS X, Linux, and Windows Applications

eBook (Watermarked)

  • Your Price: $42.39
  • List Price: $52.99
  • Includes EPUB and PDF
  • About eBook Formats
  • This eBook includes the following formats, accessible from your Account page after purchase:

    ePub EPUB The open industry format known for its reflowable content and usability on supported mobile devices.

    Adobe Reader PDF The popular standard, used most often with the free Acrobat® Reader® software.

    This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.

Description

  • Copyright 2008
  • Pages: 576
  • Edition: 1st
  • eBook (Watermarked)
  • ISBN-10: 0-13-279987-1
  • ISBN-13: 978-0-13-279987-4

Cross-Platform Development in C++ is the definitive guide to developing portable C/C++ application code that will run natively on Windows, Macintosh, and Linux/Unix platforms without compromising functionality, usability, or quality.

Long-time Mozilla and Netscape developer Syd Logan systematically addresses all the technical and management challenges associated with software portability from planning and design through coding, testing, and deployment. Drawing on his extensive experience with cross-platform development, Logan thoroughly covers issues ranging from the use of native APIs to the latest strategies for portable GUI development. Along the way, he demonstrates how to achieve feature parity while avoiding the problems inherent to traditional cross-platform development approaches.

This book will be an indispensable resource for every software professional and technical manager who is building new cross-platform software, porting existing C/C++ software, or planning software that may someday require cross-platform support.

Build Cross-Platform Applications without Compromise

 

Throughout the book, Logan illuminates his techniques with realistic scenarios and extensive, downloadable code examples, including a complete cross-platform GUI toolkit based on Mozilla’s XUL that you can download, modify, and learn from. Coverage includes 

  • Policies and procedures used by Netscape, enabling them to ship Web browsers to millions of users on Windows, Mac OS, and Linux
  • Delivering functionality and interfaces that are consistent on all platforms
  • Understanding key similarities and differences among leading platform-specific GUI APIs, including Win32/.NET, Cocoa, and Gtk+
  • Determining when and when not to use native IDEs and how to limit their impact on portability
  • Leveraging standards-based APIs, including POSIX and STL
  • Avoiding hidden portability pitfalls associated with floating point, char types, data serialization, and types in C++
  • Utilizing platform abstraction libraries such as the Netscape Portable Runtime (NSPR)
  • Establishing an effective cross-platform bug reporting and tracking system
  • Creating builds for multiple platforms and detecting build failures across platforms when they occur
  • Understanding the native runtime environment and its impact on installation
  • Utilizing wxWidgets to create multi-platform GUI applications from a single code base
  • Thoroughly testing application portability
  • Understanding cross-platform GUI toolkit design with Trixul

Sample Content

Table of Contents

Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii

About the Author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Areas That Can Affect Software Portability . . . . . . . . . . . . . . . . . . . 3

The Role of Abstraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1 Policy and Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Item 1: Make All of Your Platforms a Priority . . . . . . . . . . . . . . . . . 17

Item 2: Code from a Common Codebase . . . . . . . . . . . . . . . . . . . . 22

Platform Factory Implementations . . . . . . . . . . . . . . . . . . . . . . . 29

Implementation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Platform-Specific ProcessesImpl Classes . . . . . . . . . . . . . . . . . . . 32

Creating the Instance Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . 42

Organizing the Project in CVS or SVN . . . . . . . . . . . . . . . . . . . 45

Makefiles and Building the Code . . . . . . . . . . . . . . . . . . . . . . . . . 49

Item 3: Require Developers to Compile Their Code

with Different Compilers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Item 4: Require Developers to Build Their Code on

Multiple Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Item 5: Test Builds on Each Supported Platform . . . . . . . . . . . . . . . 60

Item 6: Pay Attention to Compiler Warnings . . . . . . . . . . . . . . . . . . 61

GNU Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Microsoft Visual C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

2 Build System/Toolchain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Item 7: Use Whatever Compiler Makes the Most Sense

for a Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Item 8: Use Native IDEs When Appropriate . . . . . . . . . . . . . . . . . . 67

Item 9: Install and Use Cygwin on Windows . . . . . . . . . . . . . . . . . . 71

Item 10: Use a Cross-Platform Make System . . . . . . . . . . . . . . . . . . 76

Make . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Building on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Autoconf/Automake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Imake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Installing on Mac OS X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Installing on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Using Imake, an Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Imakefiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Building a Complete Program from Multiple Sources . . . . . . . . . 95

Overriding Defaults with site.def . . . . . . . . . . . . . . . . . . . . . . . . 99

Eliminating #ifdefs in Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Files Used by Imake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Building Projects with Subdirectories . . . . . . . . . . . . . . . . . . . . 108

Building Debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

3 Software Configuration Management . . . . . . . . . . . . . . . . . . 131

Item 11: Use a Cross-Platform Bug Reporting and

Tracking System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Ability to Track Platform-Specific Bugs . . . . . . . . . . . . . . . . . . 133

Bugzilla . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Item 12: Set Up a Tinderbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Item 13: Use CVS or Subversion to Manage Source Code . . . . . . . 147

Setting Up and Using CVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Item 14: Use Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

An Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Patch Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Dealing with Rejects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Patch and Cross-Platform Development . . . . . . . . . . . . . . . . . . 163

4 Installation and Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Item 15: Provide Support for Native Installers . . . . . . . . . . . . . . . 165

XPInstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Platform Installs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

5 Operating System Interfaces and Libraries . . . . . . . . . . . . . . . 221

Item 16: Use Standards-Based APIs (For Example, POSIX) . . . . . . 222

POSIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Support for POSIX, SVID, XPG, and BSD . . . . . . . . . . . . . . . 226

Using Standards Support in GCC . . . . . . . . . . . . . . . . . . . . . . . 227

Microsoft Runtime Library Support for POSIX . . . . . . . . . . . . 231

Using GCC on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . 234

Deciding Which Standards to Support . . . . . . . . . . . . . . . . . . . 240

Item 17: Consider Using a Platform Abstraction Library

Such as NSPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Why NSPR? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

NSPR Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Additional NSPR Functionality . . . . . . . . . . . . . . . . . . . . . . . . 260

6 Miscellaneous Portability Topics . . . . . . . . . . . . . . . . . . . . . . . 273

Item 18: Take Care When Using Floating Point . . . . . . . . . . . . . . . 274

Don’t Serialize Floating-Point Values as Binary . . . . . . . . . . . . 276

Equality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Item 19: Be Explicit Regarding the Sign of Char Types . . . . . . . . . 278

Item 20: Avoid the Serialization of Binary Data . . . . . . . . . . . . . . 280

Item 21: Avoid Problems Related to the Size and

Organization of Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Size of Integer Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

NSPR and Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Sizes and Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Integer Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Struct Alignment and Ordering . . . . . . . . . . . . . . . . . . . . . . . . . 299

7 User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Item 22: Separate the User Interface from the Model . . . . . . . . . . 304

Separating the User Interface and Application Logic

with Model/View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Using Publish/Subscribe to Communicate between

the View and the Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Item 23: Develop a Cross-Platform User Interface Strategy . . . . . . 323

Issues Affecting Portable Cross-Platform GUI

Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Choosing a GUI Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

8 wxWidgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

wxWidgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Installing wxWidgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

A Simple Example: Hello wxWidgets . . . . . . . . . . . . . . . . . . . . 335

Creating the Application User Interface . . . . . . . . . . . . . . . . . . 337

Building wxWidgets Applications . . . . . . . . . . . . . . . . . . . . . . . 345

Controls and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

Container Widgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

Composite Widgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Internationalization and Localization . . . . . . . . . . . . . . . . . . . . 410

9 Developing a Cross-Platform GUI Toolkit in C++ . . . . . . . . . . . 427

What is XUL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

DHTML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

HTML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

Scripting Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

The Document Object Model . . . . . . . . . . . . . . . . . . . . . . . . . . 434

Style Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437

XUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438

Windows and Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440

Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441

Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441

Other Widgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442

Programming with XUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442

Adding Logic to the UI with JavaScript . . . . . . . . . . . . . . . . . . 443

Interfacing JavaScript and C/C++ Code with XPCOM

and XPConnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444

Trixul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446

Widget Support in Trixul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

Basic Operation of Trixul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

Widgets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

Implementation Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452

Creating Widget Implementation Objects . . . . . . . . . . . . . . . . . 459

Widget Factories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463

Application Main Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

Steps Taken by Trixul to Create a User Interface . . . . . . . . . . . . 471

Documents, Elements, and the DOM . . . . . . . . . . . . . . . . . . . . 472

Widget Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475

Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477

Scrolled Windows and Layout . . . . . . . . . . . . . . . . . . . . . . . . . 484

Integration with JavaScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485

Integrating with C++ Components . . . . . . . . . . . . . . . . . . . . . . 496

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020