when I was using Redhat linux os for a project I had to work with kdevelop IDE.the build system was cmake.there were some 3rd party libraries like qwt, glut&glew also included in the project.for loading the project into kdevelop first the cmake has to generate the make files which the kdevelop will recognise."Cmake -G kDevelop3" command will generate the specific files required for the IDE.then it is easy to import the project into kdevelop.debugging is easy in kdevelop as the variable values are shown when Hovered, and version control is also easy.compare it with Qtcreator for the pros and cons.
Thursday, June 27, 2013
Friday, June 14, 2013
SVN setup on a Local Machine
SVN setup on a Local Machine.
Sometimes it is required to setup a svn repository on a local machine, in some cases the Linux filesystem will be on a shared drive.Generally SVN needs URL terminology for referring to the repository,so we will setup a repository using a file system access.(file://).
The following step creates the repository.
svnadmin create --fs-type fsfs /redhat/svn/projectname/
The above project name directory is filled with some files and directories which are necessary for a repository customization etc.
The following step Imports an existing project.and generally it is a custom for svn projects for this kind of directory structure.
tags..
branches..
trunk..
here in the trunk directory the actual project files are present.once your project is ordered in this fashion and cleansed of any unwanted things like binaries and generated files or compiled code.
svn import /path/to/project/ file:///redhat/svn/projectname/trunk -m 'Initial import'
Here if the SVN_EDITOR and other variables are not set then a error message will be reported.
so -m option with the commit message “Initial Import” will avoid the error message.
The following step creates the subversion specific and version aware working copy.
svn checkout file:///redhat/svn/projectname .
The above step checkout(created)a copy of project in to the current directory “.”(dot).
there will be a .svn direcory in the working copy
The working copy information can be obtained by the info command.
The below command gives the details of the version controlled project copy.
svn info
Handling your project (editing and adding files).in your working copy
After adding a class or any new files in your project when you type “svn status” there will be response for the files that are present in your working copy.
if there is a “?” then it is a new file.
if there is “M” then it is a modified file.
svn status
? project/class.cpp
? project/class.h
M project/main.cpp
Now add the two files class.cpp and class.h to the svn using the following command.
svn add class.cpp class.h
Now the two files are under version control which can be confirmed by the command “svn status”.
when everything is fine compiling and working and you have decided for the commit do it the same way using the below command.
svn ci -m “Added a new class”
svn checkout -r 4 file:///redhat/svn/projectname
the above command will retrieve the particular version of your project which is revision 4,it can also mean,that you change the code to that date on which project is versioned as 4.
if we want to know the the information of individual files which are under version control we can do so by doing this.
svn info projectname/main.cpp
Path: /redhat/svn/projectname/main.cpp
Name: main.cpp
URL: file:///redhat/svn/projectname/main.cpp
Revision: 3
In the same way for finding the version of class.cpp and class.h do so by
svn info projectname/class.cpp
Path: /redhat/svn/projectname/class.cpp
Name: class.cpp
URL: file:///redhat/svn/projectname/class.cpp
Revision: 4
Other commands
---------------
revert undo all changes in the current directory.
update fetch all the changes committed from another working directory.
diff show the difference between the files in the current directory across the versions.
remote respository of your project will be accessed in the following way.
file:///redhat/svn/projectname ⇐===> svn+ssh://url.of.desktop/redhat/svn/projectname.
Subscribe to:
Comments (Atom)