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

minor updates to configure and rpm build steps; link to deb docs

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@40480 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2006-08-05 14:58:25 +00:00
parent bec8a09e4a
commit 83b7b21b1c
1 changed files with 11 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
docs/tech/tn0013.txt
View File

@@ -16,7 +16,7 @@ below.
a) Do a fresh checkout using the command a) Do a fresh checkout using the command
cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/packs/cvsroots/wxwidgets co wxGTK cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/packs/cvsroots/wxwidgets co wxGTK
NB: if you realize later that some needed files were not checked out NB: if you realize later that some needed files were not checked out
by this command, please modify CVSROOT/modules to include the missing by this command, please modify CVSROOT/modules to include the missing
@@ -24,13 +24,15 @@ a) Do a fresh checkout using the command
You also need the samples, demos and contrib directories, so change to You also need the samples, demos and contrib directories, so change to
wxWidgets directory created by the first cvs command and do "cvs up -d" wxWidgets directory created by the first cvs command and do "cvs up -d"
for each of them. for each of them. Of course, you can also check out everything (use
wxWidgets module name instead of wxGTK) if the bandwidth and disk space
are not a problem.
b) Create a build directory under wxWidgets, e.g. I use "gtk-release", b) Create a build directory under wxWidgets, e.g. I use "gtk-release",
"cd" to it and run configure: the options don't really matter, you can use "cd" to it and run configure: the options don't really matter, you can use
something like something like
../configure --no-recursion ../configure -C --without-subdirs
to make it run a bit faster. to make it run a bit faster.
@@ -91,16 +93,12 @@ b) Start RPM build by going to RPM_ROOT directory and typing "rpm -ba
you'll have to restart from the very beginning because rpm doesn't allow you'll have to restart from the very beginning because rpm doesn't allow
to short circuit the package generation). to short circuit the package generation).
If everything goes well, the following files are produced: If everything goes well, this should produce many files in SRPMS and
RPMS/i386 subdirectories.
SRPMS/wxGTK-${version}-1.src.rpm
RPMS/i386/wxGTK-${version}-1.i386.rpm
RPMS/i386/wxGTK-devel-${version}-1.i386.rpm
RPMS/i386/wxGTK-gl-${version}-1.i386.rpm
RPMS/i386/wxGTK-static-${version}-1.i386.rpm
Use "rpm -ba --with gtk2" to build GTK+2 version of wxGTK and use Use "rpm -ba --with gtk2" to build GTK+2 version of wxGTK and use
"rpm -ba --with gtk2 --with unicode" to build GTK+2 Unicode build. "rpm -ba --with gtk2 --with unicode" to build GTK+2 Unicode build
(these are defaults, you can use --without option to change this).
Note: you may want to set the environment variable SMP to 3 or 4 on an 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 SMP machine to speed up the build (it uses "make -j$SMP" if the
@@ -113,7 +111,8 @@ c) Test the resulting RPMs: install them using "rpm -i" (or "rpm -U) as usual
3. Building the DEBs 3. Building the DEBs
-------------------- --------------------
[Ron is doing this] This is explained in more details in debian/README.HowToBuild.txt.
4. Uploading the files 4. Uploading the files
---------------------- ----------------------