Maybe I’m missing something bright-blazingly obvious, but I cannot seem to be able to test synfig-studio from the Github. I can’t imagine that ya’ll are building the entire project from source every time you want to test your code.
How exactly do I go about simply opening this project up in Code::Blocks or Anjuta and building/running it for debugging?
From my (Debian wheezy) part, i used to build and debug with Anjuta (3.8.4).
You do’nt need to setup the wall project (from makefile has you can found (shipped from git) in each synfig sub-project folders xx/synfig-studio/synfig-studio.anjuta , xx/synfig-core/synfig-core.anjuta and xx/synfig-ETL/synfig-ETL.anjuta … (maybe you should configure also Anjuta/Menu/Execute/Project … i do’nt remember)
Now, i build / debug using Eclispe IDE (3.8) and CDT plugins , who have some advantage … but also some problem (can’t do pause / or add breakpoint at fly)…
Maybe soon i will test , the last Anjuta version ( 3.13.92 - September 14, 2014)
When i want to build from scratch the wall project i use this script (before with i little “make clean” in each sub project i have added as parameter)
firstly, are you able to configure / build outside an IDE , using the script i mentioned above ?
With libboost ( >= 1.53.0) no standard installation to /personal/boost/install/path/ :
[code]#!/bin/sh #move to synfig folder (to get the script out from git)
export CXX="/usr/bin/ccache /usr/bin/g++"
cd ETL &&
autoreconf --install --force &&
./configure --prefix $prefix &&
make install &&
The best way to work with code is to use the build scripts under autobuild folder.
Once you have run it for the first time it could take long time to compile all dependencies but you can recompile only the needed using custom commands in the script: github.com/synfig/synfig/blob/m … ild.sh#L16
Once you have run the scrip, you can tell your preferred IDE where is the source code and the symbols in case you want to debug. Change your code and re run the script (or make install in the propel folder) to compile you changes.
It is difficult to maintain a configuration for each platform/IDE so the scripts does reasonably well it’s job, specialy considering the amount of libraries in use.