Bommels05/Mozilla
Bommels05/Mozilla
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated build instructions

Browse Source 
git-svn-id: svn://10.0.0.236/trunk@69765 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
dp%netscape.com 2000-05-15 07:21:12 +00:00
parent 8b6f90cc88
commit 95400e4869
1 changed files with 37 additions and 38 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

75
mozilla/xpcom/doc/xpcom-standalone.html
View File

@ -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:
<ul>
<li>
NSPR&nbsp;:&nbsp;mozilla/nsprpub</li>
NSPR : mozilla/nsprpub</li>
<li>
Registry :&nbsp;mozilla/modules/libreg</li>
Registry : mozilla/modules/libreg</li>
<li>
XPCOM&nbsp;:&nbsp;mozilla/xpcom</li>
XPCOM : mozilla/xpcom</li>
</ul>
<h3>
</h3>
<h3>
2.0&nbsp; Building Standalone XPCOM</h3>
Here are the instructions for building the Standalone XPCOM on unix:
<br><b></b>&nbsp;
<ol><b>Step 1 :&nbsp;Pull the sources</b>
<br>&nbsp;
<ol><b>Step 1 : Pull the sources</b>
<li>
<tt>cvs co mozilla/nsprpub mozilla/modules/libreg mozilla/xpcom</tt></li>
<tt>cvs -z 3 co -P -r NSPRPUB_CLIENT_BRANCH mozilla/nsprpub</tt></li>
<li>
&lt;get other required files under mozilla/></li>
<tt>cvs -z 3 co -P mozilla/modules/libreg</tt></li>
<li>
<tt>cvs -z 3 co -P mozilla/xpcom</tt></li>
<li>
<tt>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</tt></li>
</ol>
<ol>&nbsp;
<br><b>Step 2 :&nbsp;Building XPCOM&nbsp;Standalone</b>
<br><b>Step 2 : Building XPCOM Standalone (unix)</b>
<li>
<tt>cd mozilla; configure --enable-xpcom-standalone</tt></li>
<li>
<tt>cd config; gmake; cd ..</tt></li>
<li>
<tt>cd nsprpub; gmake; cd ..</tt></li>
@ -62,9 +70,6 @@ Here are the instructions for building the Standalone XPCOM on unix:
<tt>cd xpcom; gmake; cd ..</tt></li>
</ol>
<h3>
</h3>
<h3>
3.0&nbsp; Testing Standalone XPCOM</h3>
<tt>xpcom/sample</tt> contains a sample application and a component. This
@ -88,30 +93,27 @@ cd to your <tt>bin/</tt> directory</li>
setenv LD_LIBRARY_PATH .</li>
<li>
<tt>./nsTestSample<br>
Warning: MOZILLA_FIVE_HOME not set.</tt></li>
<tt>./nsTestSample</tt></li>
<br><tt>Warning: MOZILLA_FIVE_HOME not set.</tt>
<br><tt>nsNativeComponentLoader: autoregistering begins.</tt>
<br><tt>nsNativeComponentLoader: autoregistering succeeded</tt>
<br><tt>Inital print:&nbsp; initial value</tt>
<br><tt>Set value to : XPCOM defies gravity</tt>
<br><tt>Final print:&nbsp; XPCOM defies gravity</tt>
<br><tt>Inital print: initial value</tt>
<br><tt>Set value to: XPCOM defies gravity</tt>
<br><tt>Final print : XPCOM defies gravity</tt>
<br><b><tt>Test passed.</tt></b></ol>
<h3>
</h3>
<h3>
4.0&nbsp; Test FAILED:&nbsp;What went wrong ?</h3>
4.0&nbsp; Test FAILED: What went wrong ?</h3>
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.
<ol>
<li>
<b><tt>./nsTestSample: error in loading shared libraries: libxpcom.so:
cannot open shared object file: No such file or directory</tt></b></li>
<ol>LD_LIBRARY_PATH&nbsp;not set. To fix "<tt>setenv LD_LIBRARY_PATH&nbsp;."</tt></ol>
<ol>LD_LIBRARY_PATH not set. To fix "<tt>setenv LD_LIBRARY_PATH ."</tt></ol>
<li>
<b>Link errors when building xpcom standalone</b></li>
@ -126,27 +128,27 @@ Here is what we had to do to get a working standalone XPCOM
<ol>
<li>
Disabled all forms of unicode conversion. nsString, nsCRT were using this
in various forms. Only ASCII&nbsp;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.</li>
<li>
Disabled nsUnicharInputStream. This causes nsPersistentProperties to fail
always.</li>
Disabled nsUnicharInputStream. This causes nsPersistentProperties to always
fail.</li>
<li>
Disabled control of XPT from preferences.</li>
<li>
Disabled use of ZIP format of XPT&nbsp;files.</li>
Disabled use of ZIP format of XPT files.</li>
</ol>
<h3>
6.0&nbsp; TODO&nbsp;for v 1.0</h3>
6.0&nbsp; TODO for v 1.0</h3>
<ol>
<li>
Enable XPCOM&nbsp;to work with unicode. Unicode, ASCII and ISO8859-1 will
be the charset that will be self supported by XPCOM.</li>
Enable XPCOM to work with unicode. Unicode, ASCII and ISO8859-1 will be
the charset that will be self supported by XPCOM.</li>
<li>
Optional exclusion of specific features into standalone XPCOM like unicode
@ -157,22 +159,19 @@ in memory requirements and size.</li>
Get <tt>xpcom/tests</tt> directory upto date and documented.</li>
<li>
Make standalone XPCOM&nbsp;the only deliverable from xpcom. No more <tt>#ifndef
Make standalone XPCOM the only deliverable from xpcom. No more <tt>#ifndef
XPCOM_STANDALONE</tt></li>
<li>
Update this document for both Windows and Mac.</li>
<li>
API&nbsp;freeze and documentation</li>
API freeze and documentation</li>
</ol>
<h3>
</h3>
<h3>
7.0&nbsp; Future (post v 1.0)</h3>
mmh!&nbsp;let me think...
mmh! let me think...
<p>
<hr WIDTH="100%">
<br>Suresh Duddi &lt;dp@netscape.com>