I know C++ programming but I’m not used to work with the standard tools (gdb, subversion, git, etc.) to add new features to synfig or to solve a bug.
I would learn from the experts what’s the best way to frequently contribute to synfig code without need to ask others to apply a patch.
I would want to know:
What’s the best way to have a developing version of synfig and a working one in separated folders. What’s the config orders to give to maintain both separated folders properly updated.
If I add a new file (new feature) I cannot obtain it form the svn -diff command. how can I apply them to the code?
Once obtained the diff file, how can I apply it in SF?
I have more questions but those are my first needs to make a serious job.
Thanks super animator but the most important question is the last one:
Get a yahoo account so that you can ask questions by using
answers.yahoo.com. That’s how I got my answers.
To commit to sourceforge, just do this:
To insert new files to the commit the command is:
svn add file.cpp file.h
To do a commit just type the following code in the proper folder
It would prompt to a editor to describe the commit. Also the editor would show you some lines that describe the modified files. When saved, the patch file is created and it ask for a password to commit. Then the patch is sent.
3) To create a separate build the wiki says:
If you don’t want to install to a system-wide directory using sudo, run something like these commands before starting:
And when you run ./configure, run it with --prefix="$PREFIX" and don’t use sudo when you do make install.
When I do that everything go fine except that installing synfig-core it gives this message:
What to do?
Try make distclean and then rebuild.
Many thanks! it works now.
You’re so helpful pabs!
I added SVN use in the title of the message because that’s what the thread is about at the moment. I hope it’s ok - feel free to change it to something more appropriate
svn commit -m “my commit message” was what I used, the few time I ‘played’ with subversion. But well, it seems there’s a fairly good help with svn help