From 00fd036c18e0fbc369e6855cf48c5bc942459563 Mon Sep 17 00:00:00 2001 From: Vadim Zeitlin Date: Sun, 15 Sep 2002 18:17:02 +0000 Subject: [PATCH] updated the build technote and the technote index; removed obsolete and incorrect technote git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@17204 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- docs/tech/index.txt | 33 ++++++++++++++++++--------------- docs/tech/tn0006.txt | 41 ----------------------------------------- docs/tech/tn0013.txt | 42 ++++++++++++++++++++++++++++++------------ 3 files changed, 48 insertions(+), 68 deletions(-) delete mode 100644 docs/tech/tn0006.txt diff --git a/docs/tech/index.txt b/docs/tech/index.txt index 87d5f86239..603a59d424 100644 --- a/docs/tech/index.txt +++ b/docs/tech/index.txt @@ -1,18 +1,21 @@ -TN0001 How to add a new sample -TN0002 wxWindows translator guide -TN0003 Adding wxWindows class documentation -TN0004 Compiling a sample in the C++Builder IDE -TN0005 Adding a wxWindows contribution -TN0006 Making and installing RPMs for wxWindows -TN0007 Using and modifying the BC++ IDE files -TN0008 How to learn wxWindows programming -TN0009 Creating and converting icons -TN0010 Compiling wxWindows applications in the VC++ IDE -TN0011 All about version numbers -TN0012 wxWindows platform, toolkit and library names -TN0013 how to make a wxGTK distribution -TN0014 XRC resources format specification -TN0015 how to add new bitmaps to wxWindows UI elements + All wxWindows techincal notes at a glance + ========================================= + +tn0001.txt How to add a new sample +tn0002.txt wxWindows translator guide +tn0003.txt Adding wxWindows class documentation +tn0004.htm Compiling a sample in the C++Builder IDE +tn0005.txt Adding a wxWindows contribution +tn0006.txt *** REMOVED *** (obsoleted by tn0013.txt) +tn0007.txt Using and modifying the BC++ IDE files +tn0008.htm How to learn wxWindows programming +tn0009.htm Creating and converting icons +tn0010.htm Compiling wxWindows applications in the VC++ IDE +tn0011.txt All about version numbers +tn0012.txt wxWindows platform, toolkit and library names +tn0013.txt how to make a wxGTK distribution +tn0014.txt XRC resources format specification +tn0015.txt how to add new bitmaps to wxWindows UI elements Version: $Id$ diff --git a/docs/tech/tn0006.txt b/docs/tech/tn0006.txt deleted file mode 100644 index 295939c128..0000000000 --- a/docs/tech/tn0006.txt +++ /dev/null @@ -1,41 +0,0 @@ -How to make RPMs of the wxWindows sources -========================================= - -This is just a short description. It is assumed that you know what you are -doing. I do not take any responsibility for damaged systems, use at your own -risk! - - 1. Extract the archive in a temporary directory. Since you are - reading this text, you already have done this. - 2. Copy the .spec file to - (rpm-dir)/SPECS - 3. Copy the .tgz file to - (rpm-dir)/SOURCES - 4. Start the RPM manager with - rpm -bb (rpm-dir)/SPECS/(.spec-file) - or with - rpm -ba (rpm-dir)/SPECS/(.spec-file) - (the latter also builds the .src.rpm-file) - 5. You now have a nice set of RPMs in (rpm-dir)/RPMS - -Example -======= - -Here's how to install e.g. wxMotif 2.1.14: - - cp wxMotif.spec /usr/src/packages/SPECS - cp wxMotif-2.1.14.tgz /usr/src/packages/SOURCES - rpm -bb /usr/src/packages/SPECS/wxMotif.spec - -Install the resulting packages with - - rpm --install /usr/src/packages/RPMS/i386/wxMotif-2.1.14-0.i386.rpm - rpm --install /usr/src/packages/RPMS/i386/wxMotif-devel-2.1.14-0.i386.rpm - rpm --install /usr/src/packages/RPMS/i386/wxMotif-gl-2.1.14-0.i386.rpm - - - -That's all. You should now have a working wxWindows library. - -Regards, - Robert Fendt diff --git a/docs/tech/tn0013.txt b/docs/tech/tn0013.txt index 6ea1800f3a..7eca5935ac 100644 --- a/docs/tech/tn0013.txt +++ b/docs/tech/tn0013.txt @@ -5,7 +5,8 @@ --------------- This note explains what should be done, step by step, to prepare the packages -for a wxGTK distribution. +for a wxGTK distribution. Note that the same instructions should be used for +the other Unix-based ports including wxMotif, wxX11 and wxBase. 1. Preparing the sources ------------------------ @@ -23,8 +24,15 @@ a) Do a fresh checkout using the command for each of them. b) Create a build directory under wxWindows, e.g. I use "gtk-release", - "cd" to it and type "make -j1 dist bzip-dist-only". This should create - the following files; + "cd" to it and run configure: the options don't really matter, you can use + something like + + ../configure --no-recursion + + to make it run a bit faster. + +c) Then type "make -j1 dist bzip-dist-only". This should create the + following files; wxGTK-${version}.tar.bz2 wxGTK-demos-${version}.tar.bz2 @@ -39,7 +47,7 @@ b) Create a build directory under wxWindows, e.g. I use "gtk-release", allow parallelizing, if your make is aliased to "make -j4" (like mine), it simply won't work. - Note 2; there are also dist-only and bzip-dist targets, the "-only" suffix + Note 2: there are also dist-only and bzip-dist targets, the "-only" suffix means to just create the archive supposing that the files themselves are already under _dist_dir/wxGTK-${version} where "make dist" creates them @@ -47,10 +55,10 @@ b) Create a build directory under wxWindows, e.g. I use "gtk-release", 2. Building the RPMs -------------------- -Note that we didn't check if the library actually could be built - this is +Note that we didn't check if the library actually could be built -- this is because it is done during this step, during the RPM generation. If, for whatever reason, you don't build the RPMs, you must have checked previously -that the library could be built - nothing worse than a release which doesn't +that the library could be built -- nothing worse than a release which doesn't even compile! The rest of this section applies to a system with RPM installed (Redhat in my @@ -62,15 +70,16 @@ a) Setting up the RPM tree: you should have the RPM tree set up properly Otherwise you may do it (without root rights) in any directory RPM_ROOT. RPM_ROOT should have the following subdirectories: BUILD, RPMS, SOURCES, SPECS and SRPMS. RPMS should contain i386, i686 and noarch. You should - also create the file ~/.rpmmacros containing at least the following line: - "%_topdir /biton/zeitlin/rpm". + also create the file ~/.rpmmacros containing at least a line like this: + "%_topdir /biton/zeitlin/rpm" (replace the directory with $RPM_ROOT, of + course) In either case, put the file wxGTK-${version}.tar.bz2 in SOURCES subdirectory and wxGTK.spec in SPECS one (hint: you can just link them from - there - like this you won't forget to update them after redoing "make + there -- like this you won't forget to update them after redoing "make dist"). -b) Start RPM build by going to RPM_ROOT directory and typing "rpm -bb +b) Start RPM build by going to RPM_ROOT directory and typing "rpm -ba SPECS/wxGTK.spec". It may be a good idea to append "2&>1 | tee wxGTK.out" (or "|& tee" if you're using the one true shell ;-) as it might be not easy to detect errors in the verbose rpm output if anything goes wrong. @@ -87,6 +96,15 @@ b) Start RPM build by going to RPM_ROOT directory and typing "rpm -bb RPMS/i386/wxGTK-gl-${version}-1.i386.rpm RPMS/i386/wxGTK-static-${version}-1.i386.rpm + + Note: you may want to set the environment variable SMP to 3 or 4 on an + SMP machine to speed up the build (it uses "make -j$SMP" if the + variable is set) + +c) Test the resulting RPMs: install them using "rpm -i" (or "rpm -U) as usual + and try to build some samples using makefile.unx ("make -f makefile.unx") + so that they use wx-config in the PATH and not from the build tree + 3. Building the DEBs -------------------- @@ -122,7 +140,7 @@ d) GNOME (very effective, stays on front page for days): - Search for wxWindows - Update the version number - Ignore the error message - + e) MacNN: - http://www.macnn.com - Contact or Contribute or something @@ -133,7 +151,7 @@ f) MacRumors: g) Apple Developers Connection: mailto: adcnews@apple.com - + h) LinuxDevices.com: Interesting for wxUniversal. -- 2.45.2