Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated script + FAQs

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@16036 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2002-07-04 09:38:39 +00:00
parent 3bc65ea95b
commit cd5082468f
5 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
distrib/msw/zipdistinno.bat
View File

@@ -7,7 +7,7 @@ set webfiles=c:\wx2dev\wxWebSite
set inno=0
Rem Set this to the required version
set version=2.3.2
set version=2.3.3
if "%src" == "" goto usage
if "%dest" == "" goto usage
@@ -244,7 +244,7 @@ call %WXWIN\distrib\msw\makeinno.bat
erase /Y %dest\setup.*
rem Now invoke Inno Setup on the new wxwin2.iss
set innocmd="C:\Program Files\Inno Setup 1.3\compil32.exe" /cc %WXWIN\distrib\msw\wxwin2.iss
set innocmd="C:\Program Files\Inno Setup 2\compil32.exe" /cc %WXWIN\distrib\msw\wxwin2.iss
echo Invoking %innocmd...
start "Inno Setup" /w %innocmd%
pause Press any key to continue with the wxWindows distribution...

4
docs/html/faqgen.htm
View File

@@ -130,10 +130,10 @@ platform-independent code, such as the wxTreeCtrl and wxListCtrl classes.<P>
No. This is a much-discussed topic that has (many times) ended with the conclusion that it is in
wxWindows&#39; best interests to avoid use of templates. Not all compilers can handle
templates adequately so it would dramatically reduce the number of compilers
and platforms that could be supported. It would also be undesirable to make
and platforms that could be supported. It would also be undersirable to make
wxWindows dependent on another large library that may have to be downloaded and installed.
In addition, use of templates can lead to executable bloat, which is something
wxWindows 2 is strenuously trying to avoid.<P>
wxWindows 2 is strenously trying to avoid.<P>
The standard C++ string class is not used, again because it is not available to all compilers,
and it is not necessarily a very efficient implementation. Also, we retain more flexibility

8
docs/html/faqmac.htm
View File

@@ -30,11 +30,11 @@ See also <a href="faq.htm">top-level FAQ page</a>.
<li><a href="#macosx">How is the Mac OS X port different from the Classic Mac OS port?</a></li>
<li><a href="#macclassic">How are improvements to the Classic Mac OS port integrated into the Mac OS X port?</a></li>
<li><a href="#compilers">What compilers are supported?</a></li>
<li><a href="#filetypes">How does CVS handle file types/creators under Mac OS 8.x/9.x?</a></li>
<li><a href="#filetypesx">How does CVS handle file types/creators under Mac OS X?</a></li>
<li><a href="#cwpro53">What steps are required to build wxMac using CodeWarrior Pro 5.3?</a></li>
<li><a href="#filetypes">How does CVS handle file types/creators under Mac OS 8.x /9.x?</a></li>
<li><a href="#filetypesx">How does CVS handle file types/creators under Mac OS X? </a></li>
<li><a href="#cwpro53">What steps are required to build wxMac using CodeWarrior P ro 5.3?</a></li>
<li><a href="#buildx">What steps are required to build wxMac under Mac OS X?</a></li>
<li><a href="#settings">What important settings are required in the CodeWarrior Project Preferences?</a></li>
<li><a href="#settings">What important settings are required in the CodeWarrior P roject Preferences?</a></li>
<li><a href="#smarterrors">What are the smart preprocessing errors with the Apple Developer Tools?</a></li>
<li><a href="#aboutmenu">How does wxMac support the standard Apple About menu item and Help menu?</a></li>
</ul>

2
docs/html/faqmot.htm
View File

@@ -64,7 +64,7 @@ system is in preparation.
<h3><a name="dialoged">Does Dialog Editor work with wxWindows for Motif?</a></h3>
Support for Dialog Editor is almost there, but there are some wrinkles to iron
Suport for Dialog Editor is almost there, but there are some wrinkles to iron
out. You may find it&#39;s useful though: compile it and see.
<P>

2
docs/html/faqmsw.htm
View File

@@ -305,7 +305,7 @@ The templates are described in tmake ref manual (1-2 pages of text)
and are quite simple. They do contain some Perl code, but my Perl is
primitive (very C like) so it should be possible for anybody to make
trivial modifications to it (I hope that only trivial modifications
will be needed). I&#39;ve tagged the old makefiles as MAKEFILES_WITHOUT_TMAKE
will be needed). I&#39;ve tagged the ol makefiles as MAKEFILES_WITHOUT_TMAKE
in the cvs, so you can always retrieve them and compare the new ones,
this will make it easier to solve the problems you might have.<P>