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

get rid of references to CVS as we use SVN now

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@52035 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Francesco Montorsi
2008-02-24 14:23:30 +00:00
parent cf8e095724
commit 4d636bdf8b
4 changed files with 7 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/tech/tn0001.txt
View File

@@ -5,9 +5,9 @@ To add a new sample "foo" under directory "samples/foo" you need to do
the following: (note that all this applies also to demos: just replace the following: (note that all this applies also to demos: just replace
samples/ with demos/ where needed). samples/ with demos/ where needed).
1. Create the directory samples/foo locally and "cvs add" it. 1. Create the directory samples/foo locally and "svn add" it.
2. "cvs add" the sample sources (usually based on minimal.cpp) as well. 2. "svn add" the sample sources (usually based on minimal.cpp) as well.
Note that unless your sample requires something special you shouldn't Note that unless your sample requires something special you shouldn't
add foo.rc, foo.ico, ... any more, please just reuse the generic sample.* add foo.rc, foo.ico, ... any more, please just reuse the generic sample.*

2
docs/tech/tn0002.txt
View File

@@ -28,7 +28,7 @@ First of all, here is what you will need:
fine, but you'd have to use some kind of "for /s" loop with the fine, but you'd have to use some kind of "for /s" loop with the
command.com/cmd.exe. command.com/cmd.exe.
3. (at least read) access to the cvs is not necessary strictly speaking, but 3. (at least read) access to the subversion is not necessary strictly speaking, but
will make things a lot easier for you and others. will make things a lot easier for you and others.

4
docs/tech/tn0011.txt
View File

@@ -18,7 +18,7 @@
{wx}/build/bakefiles/wxpresets/presets/wx_win32.bkl {wx}/build/bakefiles/wxpresets/presets/wx_win32.bkl
{wx}/build/bakefiles/version.bkl {C:R:A} {wx}/build/bakefiles/version.bkl {C:R:A}
{wx}/build/script/win_docs.bat {windows doc and setup file} {wx}/build/script/win_docs.bat {windows doc and setup file}
{wx}/distrib/scripts/build-environ.cfg {cvs tar and zip files} {wx}/distrib/scripts/build-environ.cfg {SVN tar and zip files}
{wx}/include/wx/mac/carbon/config_xcode.h {wx}/include/wx/mac/carbon/config_xcode.h
The script misc/scripts/inc_release can be used for incrementing The script misc/scripts/inc_release can be used for incrementing
@@ -28,6 +28,8 @@
[ To be written... ] [ To be written... ]
See tn0020.txt for now.

12
docs/tech/tn0013.txt
View File

@@ -16,17 +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 svn checkout http://svn.wxwidgets.org/svn/wx/wxWidgets/trunk wxWidgets
NB: if you realize later that some needed files were not checked out
by this command, please modify CVSROOT/modules to include the missing
files so that it works for the next release!
You also need the samples and demos directories, so change to
wxWidgets directory created by the first cvs command and do "cvs up -d"
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