AuroraMiddleware/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Namechange changes

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@26037 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robin Dunn 2004-03-02 23:49:39 +00:00
parent 2f4ad68c32
commit e8a71fa08c
6 changed files with 86 additions and 50 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

64
wxPython/docs/BUILD.txt
View File

@ -1,10 +1,10 @@
Building wxPython 2.5 for Development and Testing
=================================================
This file describes how I build wxWindows and wxPython while doing
This file describes how I build wxWidgets and wxPython while doing
development and testing, and is meant to help other people that want
to do the same thing. I'll assume that you are using either a CVS
snapshot from http://wxwindows.org/snapshots/, a checkout from CVS, or
snapshot from http://wxWidgets.org/snapshots/, a checkout from CVS, or
one of the released wxPythonSrc-2.5.* tarballs. I'll also assume that
you know your way around your system, the compiler, etc. and most
importantly, that you know what you are doing! ;-)
@ -39,12 +39,12 @@ Building on Unix-like Systems (e.g. Linux and OS X)
These platforms are built almost the same way while in development
so I'll combine the descriptions about their build process here.
First we will build wxWindows and install it to an out of the way
First we will build wxWidgets and install it to an out of the way
place, then do the same for wxPython.
1. Create a build directory in the main wxWindows dir, and configure
wxWindows. If you want to have multiple builds with different
1. Create a build directory in the main wxWidgets dir, and configure
wxWidgets. If you want to have multiple builds with different
configure options, just use different subdirectories. I normally
put the configure command in a script named ".configure" in each
build dir so I can easily blow away everything in the build dir and
@ -71,14 +71,14 @@ place, then do the same for wxPython.
path you want, such as a path in your HOME dir or even one of the
standard prefix paths such as /usr or /usr/local if you like, but
using /opt this way lets me easily have multiple versions and ports
of wxWindows "installed" and makes it easy to switch between them,
without impacting any versions of wxWindows that may have been
of wxWidgets "installed" and makes it easy to switch between them,
without impacting any versions of wxWidgets that may have been
installed via an RPM or whatever. For the rest of the steps below
be sure to also substitute "/opt/wx/2.5" with whatever prefix you
choose for your build.
If you want to use the image and zlib libraries included with
wxWindows instead of those already installed on your system, (for
wxWidgets instead of those already installed on your system, (for
example, to reduce dependencies on 3rd party libraries) then you
can add these flags to the configure command::
@ -88,8 +88,8 @@ place, then do the same for wxPython.
--with-zlib=builtin \
2. To build and install wxWindows you could just use the "make"
command but there are other libraries besides the main wxWindows
2. To build and install wxWidgets you could just use the "make"
command but there are other libraries besides the main wxWidgets
libs that also need to be built so again I make a script to do it
all for me so I don't forget anything. This time it is called
".make" (I use the leading ". so when I do ``rm -r *`` in my build
@ -108,13 +108,13 @@ place, then do the same for wxPython.
.make install
When it's done you should have an installed set of files under
/opt/wx/2.5 containing just wxWindows. Now to use this version of
wxWindows you just need to add /opt/wx/2.5/bin to the PATH and set
/opt/wx/2.5 containing just wxWidgets. Now to use this version of
wxWidgets you just need to add /opt/wx/2.5/bin to the PATH and set
LD_LIBRARY_PATH (or DYLD_LIBRARY_PATH on OS X) to /opt/wx/2.5/lib.
3. I also have a script to help me build wxPython and it is checked in
to the CVS as wxWindows/wxPython/b, but probably don't want to use
to the CVS as wxWidgets/wxPython/b, but probably don't want to use
it as it's very cryptic and expects that you want to run SWIG, so
if you don't have the latest patched up version of SWIG then you'll
probably get stuck. So I'll just give the raw commands instead.
@ -132,7 +132,7 @@ place, then do the same for wxPython.
using python2.3.
Make sure that the first wx-config found on the PATH is the one you
installed above, and then change to the wxWindows/wxPython dir and
installed above, and then change to the wxWidgets/wxPython dir and
run the this command::
cd wxPython
@ -161,7 +161,7 @@ place, then do the same for wxPython.
module.
When the setup.py command is done you should have fully populated
wxPython and wx packages locally in wxWindows/wxPython/wxPython and
wxPython and wx packages locally in wxWidgets/wxPython/wxPython and
.../wx, with all the extension modules (``*.so`` files) located in the
wx package.
@ -170,8 +170,8 @@ place, then do the same for wxPython.
PYTHONPATH to the wxPython dir in the CVS tree. For example::
export LD_LIBRARY=/opt/wx/2.5/lib
export PYTHONPATH=/myprojects/wxWindows/wxPython
cd /myprojects/wxWindows/wxPython/demo
export PYTHONPATH=/myprojects/wxWidgets/wxPython
cd /myprojects/wxWidgets/wxPython/demo
python2.3 demo.py
OS X NOTE: You need to use "pythonw" on the command line to run
@ -210,7 +210,7 @@ used. The Python executable that comes from PythonLabs and the
wxPython extensions that I distribute are built with MSVC 6 with all
the Service Packs applied.
If you want to build a debugable version of wxWindows and wxPython you
If you want to build a debugable version of wxWidgets and wxPython you
will need to have also built a debug version of Python and any other
extension modules you need to use. You can tell if you have them
already if there is a _d in the file names, for example python_d.exe
@ -220,18 +220,18 @@ version is fine, and you can use the regular python executables with
it.
Just like the unix versions I also use some scripts to help me build
wxWindows, but I use some non-standard stuff to do it. So if you want
wxWidgets, but I use some non-standard stuff to do it. So if you want
to use them too you'll need to get a copy or 4DOS or 4NT from
http://www.jpsoft.com/ and also a copy of unix-like cat and sed
programs. You can also do by hand what my scripts are doing, but
there are a lof steps involved and I won't be going into details
here. There is a copy of my build scripts in wxWindows\wxPython\distrib\msw
here. There is a copy of my build scripts in wxWidgets\wxPython\distrib\msw
1. Set an environment variable to the root of the wxWindows source
1. Set an environment variable to the root of the wxWidgets source
tree::
set WXWIN=e:\projects\wxWindows
set WXWIN=e:\projects\wxWidgets
2. Copy setup0.h to setup.h
@ -254,14 +254,14 @@ here. There is a copy of my build scripts in wxWindows\wxPython\distrib\msw
4. Make a %WXWIN%\BIN directory and add it to the PATH. My build
scripts will copy the wxWindows DLLs there.
scripts will copy the wxWidgets DLLs there.
5. Change to the %WXWIN%\build\msw directory and copy my build scripts
there.
6. Use the .make.btm command to build wxWindows. It needs one
6. Use the .make.btm command to build wxWidgets. It needs one
command-line parameter which controls what kind of build(s) to do.
Use one of the following::
@ -283,7 +283,7 @@ here. There is a copy of my build scripts in wxWindows\wxPython\distrib\msw
.make hybrid clean
7. When that is done it will have built the main wxWindows DLLs and
7. When that is done it will have built the main wxWidgets DLLs and
also some of the contribs DLLs. There should be a ton of DLLs in
%WXDIR%\bin and lots of lib files and other stuff in
%WXDIR%\lib\vc_dll.
@ -297,7 +297,7 @@ here. There is a copy of my build scripts in wxWindows\wxPython\distrib\msw
version the rest of the time. If you ever do want to install the
development verison please refer to INSTALL.txt.
Change to the wxWindows\wxPython dir and run the this command,
Change to the wxWidgets\wxPython dir and run the this command,
makeing sure that you use the version of python that you want to
build for (if you have more than one on your system)::
@ -310,28 +310,28 @@ here. There is a copy of my build scripts in wxWindows\wxPython\distrib\msw
USE_SWIG=1 SWIG=e:\projects\SWIG-cvs\swig.exe
If you built a Unicode version of wxWindows and want to also build
If you built a Unicode version of wxWidgets and want to also build
the Unicode version of wxPython then add this flag::
UNICODE=1
If you have a debug version of Python and wxWindows and want to
If you have a debug version of Python and wxWidgets and want to
build a debug version of wxPython too, add the --debug flag to the
command line. You should then end up with a set of ``*_d.pyd``
files in the wx package and you'll have to run ``python_d.exe`` to
use them. The debug and hybrid(release) versions can coexist.
When the setup.py command is done you should have fully populated
wxPython and wx packages locally in wxWindows/wxPython/wxPython and
wxWindows/wxPython/wx, with all the extension modules (``*.pyd``
wxPython and wx packages locally in wxWidgets/wxPython/wxPython and
wxWidgets/wxPython/wx, with all the extension modules (``*.pyd``
files) located in the wx package.
9. To run code with the development verison of wxPython, just set the
PYTHONPATH to the wxPython dir in the CVS tree. For example::
set PYTHONPATH=e:\projects\wxWindows\wxPython
cd e:\projects\wxWindows\wxPython
set PYTHONPATH=e:\projects\wxWidgets\wxPython
cd e:\projects\wxWidgets\wxPython
python demo.py

9
wxPython/docs/CHANGES.txt
View File

@ -8,6 +8,15 @@ CHANGES.txt for wxPython
big changes that have happened in this release and how you should
adapt your code.)
The wxWindows project and library is now known as wxWidgets. Please
see http://www.wxwindows.org/name.htm for more details. This won't
really affect wxPython all that much, other than the fact that the
wxwindows.org domain name will be changing to wxwidgets.org, so mail
list, CVS, and etc. addresses will be changing. We're going to try
and smooth the transition as much as possible, but I wanted you all to
be aware of this change if you run into any issues.
Many, many little fixes, changes and additions done as part of the move
to wxWidgets 2.5 that I have forgotten about.

24
wxPython/docs/INSTALL.txt
View File

@ -14,23 +14,23 @@ will take precedence.
Installing on Unix-like Systems (not OS X)
------------------------------------------
1. When building wxWindows you need to decide if you want it to be a
1. When building wxWidgets you need to decide if you want it to be a
private copy only accessed by wxPython, or if you would like it to
be installed in a stanard location such as /usr. Or perhaps you
already have a version of wxWindows installed on your system (such
already have a version of wxWidgets installed on your system (such
as from an RPM) and you want wxPython to use that version too. If
so then you'll want to ensure that the flags and options used to
build the installed version are compatible with wxPython.
2. If you do decide to build and install your own wxWindows then there
2. If you do decide to build and install your own wxWidgets then there
are a few tweaks to the configure flags described in BUILD.txt that
you will probably want to make. Instead of --enable-debug use
this configure flag::
--enable-optimize \
Normally I also use the following flag in order to have wxWindows
Normally I also use the following flag in order to have wxWidgets
runtime assertions turned into Python exceptions where possible.
It does add extra code to the build but probably not enough to
worry about it. However if you want to get as lean a build as
@ -39,12 +39,12 @@ Installing on Unix-like Systems (not OS X)
--enable-debug_flag \
If you are building a private copy of wxWindows (IOW, not installed
If you are building a private copy of wxWidgets (IOW, not installed
in a standard library location) then it can be kind of a hassle to
always have to set the LD_LIBRARY_PATH variable so wxPython can
find the wxWindows shared libraries. You can hard code the library
find the wxWidgets shared libraries. You can hard code the library
path into the binaries by using the rpath option when configuring
wxWindows. For example::
wxWidgets. For example::
--enable-rpath=/opt/wx/2.5/lib \
@ -86,9 +86,9 @@ Installing wxPython on OS X is nearly the same as the Unix
instructions above, except for a few small, but important details:
1. The --enable-rpath configure option is not needed since the path to
the wxWindows dylibs will automatically be encoded into the
the wxWidgets dylibs will automatically be encoded into the
extension modules when they are built. If you end up moving the
wxWindows dynlibs to some other location (such as inside the .app
wxWidgets dynlibs to some other location (such as inside the .app
bundle of your applicaiton for distribution to other users,) then
you will need to set DYLD_LIBRARY_PATH to this location so the
dylibs can be found at runtime.
@ -119,10 +119,10 @@ instructions above, except for a few small, but important details:
Installing on Windows
---------------------
1. Build wxWindows and wxPython as described in BUILD.txt. If you
1. Build wxWidgets and wxPython as described in BUILD.txt. If you
would rather have a version without the code that turns runtime
assertions into Python exceptions, then use "release" instead of
"hybrid" when building wxWindows and add "FINAL=1" to the setup.py
"hybrid" when building wxWidgets and add "FINAL=1" to the setup.py
command line.
2. Install wxPython like this::
@ -130,7 +130,7 @@ Installing on Windows
python setup.py install
3. Copy the wxWindows DLLs to the wx package directory so they can be
3. Copy the wxWidgets DLLs to the wx package directory so they can be
found at runtime by the extension modules without requiring that
they be installed on the PATH::

17
wxPython/docs/MigrationGuide.html
View File

@ -15,6 +15,16 @@
those changes. Be sure to also check in the CHANGES.txt file like
usual to see info about the not so major changes and other things that
have been added to wxPython.</p>
<div class="section" id="wxname-change">
<h1><a name="wxname-change">wxName Change</a></h1>
<p>The <strong>wxWindows</strong> project and library is now known as
<strong>wxWidgets</strong>. Please see <a class="reference" href="http://lists.wxwidgets.org/cgi-bin/ezmlm-cgi?13:mss:3:200402:eebaopdhchfoagmnideo">here</a> for more details.</p>
<p>This won't really affect wxPython all that much, other than the fact
that the wxwindows.org domain name will be changing to wxwidgets.org,
so mail list, CVS, and etc. addresses will be changing. We're going
to try and smooth the transition as much as possible, but I wanted you
all to be aware of this change if you run into any issues.</p>
</div>
<div class="section" id="module-initialization">
<h1><a name="module-initialization">Module Initialization</a></h1>
<p>The import-startup-bootstrap process employed by wxPython was changed
@ -31,7 +41,7 @@ potential problems are that the C++ side of the &quot;stock-objects&quot;
(wx.BLUE_PEN, wx.TheColourDatabase, etc.) are not initialized until
the wx.App object is created, so you should not use them until after
you have created your wx.App object. If you do then an exception will
be raised telling you that the C++ object has not bene initialized
be raised telling you that the C++ object has not been initialized
yet.</p>
<p>Also, you will probably not be able to do any kind of GUI or bitmap
operation unless you first have created an app object, (even on
@ -109,7 +119,8 @@ automatically generate a new ID if -1 is given, similar to using -1
with window classess. This means that you can create menu or toolbar
items and event bindings without having to predefine a unique menu ID,
although you still can use IDs just like before if you want. For
example, these are all equivallent other than ID values:</p>
example, these are all equivallent other than their specific ID
values:</p>
<pre class="literal-block">
1.
item = menu.Append(-1, &quot;E&amp;xit&quot;, &quot;Terminate the App&quot;)
@ -393,7 +404,7 @@ different API.</p>
</div>
<hr class="footer" />
<div class="footer">
Generated on: 2004-02-27 00:27 UTC.
Generated on: 2004-02-27 23:30 UTC.
</div>
</body>
</html>

20
wxPython/docs/MigrationGuide.txt
View File

@ -9,12 +9,27 @@ usual to see info about the not so major changes and other things that
have been added to wxPython.
wxName Change
-------------
The **wxWindows** project and library is now known as
**wxWidgets**. Please see here_ for more details.
.. _here: http://www.wxwindows.org/name.htm
This won't really affect wxPython all that much, other than the fact
that the wxwindows.org domain name will be changing to wxwidgets.org,
so mail list, CVS, and etc. addresses will be changing. We're going
to try and smooth the transition as much as possible, but I wanted you
all to be aware of this change if you run into any issues.
Module Initialization
---------------------
The import-startup-bootstrap process employed by wxPython was changed
such that wxWindows and the underlying gui toolkit are **not**
such that wxWidgets and the underlying gui toolkit are **not**
initialized until the wx.App object is created (but before wx.App.OnInit
is called.) This was required because of some changes that were made
to the C++ wxApp class.
@ -117,7 +132,8 @@ automatically generate a new ID if -1 is given, similar to using -1
with window classess. This means that you can create menu or toolbar
items and event bindings without having to predefine a unique menu ID,
although you still can use IDs just like before if you want. For
example, these are all equivallent other than ID values::
example, these are all equivallent other than their specific ID
values::
1.
item = menu.Append(-1, "E&xit", "Terminate the App")

2
wxPython/docs/README.txt
View File

@ -49,7 +49,7 @@ Please also see the following files:
to 2.5 that require changes to your
applications
licence/* Text of the wxWindows license.
licence/* Text of the wxWidgets license.