From 95400e486920fd370443ec2ac6c2c74cd32e5e93 Mon Sep 17 00:00:00 2001 From: "dp%netscape.com" Date: Mon, 15 May 2000 07:21:12 +0000 Subject: [PATCH] Updated build instructions git-svn-id: svn://10.0.0.236/trunk@69765 18797224-902f-48f8-a5cc-f745e15eee43 --- mozilla/xpcom/doc/xpcom-standalone.html | 75 ++++++++++++------------- 1 file changed, 37 insertions(+), 38 deletions(-) diff --git a/mozilla/xpcom/doc/xpcom-standalone.html b/mozilla/xpcom/doc/xpcom-standalone.html index 297c97132d5..1d8320c70c9 100644 --- a/mozilla/xpcom/doc/xpcom-standalone.html +++ b/mozilla/xpcom/doc/xpcom-standalone.html @@ -23,35 +23,43 @@ set of libraries (shared mostly) that can be used to get all features of XPCOM. The contents of this standalone XPCOM in general are: -

-

-

2.0  Building Standalone XPCOM

Here are the instructions for building the Standalone XPCOM on unix: -
  -
    Step 1 : Pull the sources +
      +
      Step 1 : Pull the sources
    1. -cvs co mozilla/nsprpub mozilla/modules/libreg mozilla/xpcom
      2. +cvs -z 3 co -P -r NSPRPUB_CLIENT_BRANCH mozilla/nsprpub
    2. -<get other required files under mozilla/>
      3. +cvs -z 3 co -P mozilla/modules/libreg + +
    3. +cvs -z 3 co -P mozilla/xpcom
      4. + +
    4. +cvs -z 3 co -P mozilla/allmakefiles.sh mozilla/client.mk mozilla/aclocal.m4 +mozilla/configure mozilla/configure.in mozilla/Makefile.in mozilla/config +mozilla/build
        -
      Step 2 : Building XPCOM Standalone +
      Step 2 : Building XPCOM Standalone (unix)
    1. cd mozilla; configure --enable-xpcom-standalone
      2. +
    2. +cd config; gmake; cd ..
      3. +
    3. cd nsprpub; gmake; cd ..
      4. @@ -62,9 +70,6 @@ Here are the instructions for building the Standalone XPCOM on unix: cd xpcom; gmake; cd ..
    -

    -

    -

    3.0  Testing Standalone XPCOM

    xpcom/sample contains a sample application and a component. This @@ -88,30 +93,27 @@ cd to your bin/ directory setenv LD_LIBRARY_PATH .
  1. -./nsTestSample
    -Warning: MOZILLA_FIVE_HOME not set.
    2. +./nsTestSample +
    Warning: MOZILLA_FIVE_HOME not set.
    nsNativeComponentLoader: autoregistering begins.
    nsNativeComponentLoader: autoregistering succeeded -
    Inital print:  initial value -
    Set value to : XPCOM defies gravity -
    Final print:  XPCOM defies gravity +
    Inital print: initial value +
    Set value to: XPCOM defies gravity +
    Final print : XPCOM defies gravity
    Test passed.

-

- -

-4.0  Test FAILED: What went wrong ?

+4.0  Test FAILED: What went wrong ? The most common case of why the sample would have failed if you didn't -run it from the bin directoy. Here are some error messsages and possible +run it from the bin directory. Here are some error messsages and possible ways of fixing them.
  1. ./nsTestSample: error in loading shared libraries: libxpcom.so: cannot open shared object file: No such file or directory
    2. -
      LD_LIBRARY_PATH not set. To fix "setenv LD_LIBRARY_PATH ."
    +
      LD_LIBRARY_PATH not set. To fix "setenv LD_LIBRARY_PATH ."
  2. Link errors when building xpcom standalone
    3. @@ -126,27 +128,27 @@ Here is what we had to do to get a working standalone XPCOM
    1. Disabled all forms of unicode conversion. nsString, nsCRT were using this -in various forms. Only ASCII is expected to work. Other charsets including +in various forms. Only ASCII is expected to work. Other charsets including unicode are not guaranteed to work.
    2. -Disabled nsUnicharInputStream. This causes nsPersistentProperties to fail -always.
      3. +Disabled nsUnicharInputStream. This causes nsPersistentProperties to always +fail.
    3. Disabled control of XPT from preferences.
    4. -Disabled use of ZIP format of XPT files.
      5. +Disabled use of ZIP format of XPT files.

    -6.0  TODO for v 1.0

    +6.0  TODO for v 1.0
    1. -Enable XPCOM to work with unicode. Unicode, ASCII and ISO8859-1 will -be the charset that will be self supported by XPCOM.
      2. +Enable XPCOM to work with unicode. Unicode, ASCII and ISO8859-1 will be +the charset that will be self supported by XPCOM.
    2. Optional exclusion of specific features into standalone XPCOM like unicode @@ -157,22 +159,19 @@ in memory requirements and size.
      3. Get xpcom/tests directory upto date and documented.
    3. -Make standalone XPCOM the only deliverable from xpcom. No more #ifndef +Make standalone XPCOM the only deliverable from xpcom. No more #ifndef XPCOM_STANDALONE
    4. Update this document for both Windows and Mac.
    5. -API freeze and documentation
      6. +API freeze and documentation
    -

    -

    -

    7.0  Future (post v 1.0)

    -mmh! let me think... +mmh! let me think...


    Suresh Duddi <dp@netscape.com>