Porting to linux started near september 2009
The main branch or trunk is called basis.
The release branch is called stage.
As a principle, if a commit (check-ins) is done at stage it also should be done at basis.
The commit will be unique when working directly in basis.
New product releases are developed from branches deriving from basis.
See the process for details.
A principle I would like that could be followed is:
It should exist only, and only one released - and supported - version.
Older versions, that may be available, would not be supported directly.
The changes that may happen due support to the released version of the product are made in stage of this product and in basis.
IIt may happen that components or methods are abandoned in new developing versions - basis development - and in this case certain changes to the released version are made only in stage. Maybe only adapted to the new context or idea.
SVN repository:
https://ca2svn.com/ link updated december 2009
To build an application, use TortoiseSVN to download the folder from the repository:
https://ca2svn.com/app/basis/ link updated december 2009
to a folder that should be called "app" inside a non system - e.g. not drive - folder..
Examples:
windows
C:\please test this ca2 repository\app
C:\first ca2 application\app
C:\veriwell musical player lite\app
linux
/home/ca2/port to ubuntu/app
The solution files will lay inside the subfolder seed/metaseed/*.sln in windows or seed/metaseed/codeblocks/*.workspace in linux.
Examples:
windows
C:\please test this ca2 repository\app\seed\metaseed\bergedge.sln
C:\first ca2 application\app\seed\metaseed\devedge.sln
C:\veriwell musical player lite\app\seed\metaseed\mplite.sln
linux
/home/ca2/port to ubuntu/app/seed/metaseed/codeblocks/all.workspace