X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/d1a6e2b7a103d761fbc15e0e9c1c20ab53a849d9..52f52ebc4e0be6a9899d328b08db9eb14629d219:/wxPython/docs/BUILD.txt diff --git a/wxPython/docs/BUILD.txt b/wxPython/docs/BUILD.txt index abf49a4be6..7a66aa330b 100644 --- a/wxPython/docs/BUILD.txt +++ b/wxPython/docs/BUILD.txt @@ -6,8 +6,8 @@ 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 one of the released wxPythonSrc-2.5.* tarballs. I'll also assume that -you know your way around your system, the compiler, etc. and that you -know what you are doing! ;-) +you know your way around your system, the compiler, etc. and most +importantly, that you know what you are doing! ;-) If you want to also install the version of wxPython you build to be in your site-packages dir and be your default version of wxPython, then a @@ -18,7 +18,7 @@ separate installation of wxPython and you can switch back and forth between this and the release version that you may already have installed. -If you want to make changes to any of the *.i files, (SWIG interface +If you want to make changes to any of the ``*.i`` files, (SWIG interface definition files,) or to regenerate the extension sources or renamer modules, then you will need an up to date version of SWIG. Either get and build the current CVS version, or version 1.3.20, and then apply @@ -92,7 +92,7 @@ place, then do the same for wxPython. command but there are other libraries besides the main wxWindows 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 + ".make" (I use the leading ". so when I do ``rm -r *`` in my build dir I don't lose my scripts too.) This is what it looks like:: make $* \ @@ -162,7 +162,7 @@ place, then do the same for wxPython. When the setup.py command is done you should have fully populated wxPython and wx packages locally in wxWindows/wxPython/wxPython and - .../wx, with all the extension modules (*.so files) located in the + .../wx, with all the extension modules (``*.so`` files) located in the wx package. @@ -177,7 +177,7 @@ place, then do the same for wxPython. OS X NOTE: You need to use "pythonw" on the command line to run wxPython applications. This version of the Python executable is part of the Python Framework and is allowed to interact with the - display. You can also Double Click on a .py or a .pyw file from + display. You can also double click on a .py or a .pyw file from the finder (assuming that PythonLauncher is still associated with these file extensions) and it will launch the Framework version of Python for you. For information about creating Applicaiton Bundles @@ -317,14 +317,14 @@ here. There is a copy of my build scripts in wxWindows\wxPython\distrib\msw If you have a debug version of Python and wxWindows 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. + 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 files) - located in the wx package. + wxWindows/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