-external dependencies (eg cairo, libart, etc) -internal dependencies (our plugins and convenience libs) -working out how to do a lot of the decision making and versioning (this is something I really fleshed out later on though)
This might show my ignorance, but I'm not sure exactly what these three items mean.
What Inkscape depends on from libraries not included within its source
What libraries Inkscape builds itself (autotools tends to use libraries that are statically linked just if you want to have source in another directory)
Decision making: Scribus can use cairo or libart, etc.. and versioning.. how to name the binary. I finally worked out (CMake let me work it out) how to version a binary so a user could specify the binary to be called, eg, scribus-1.3.4cvs and have two versions installed in the same place.
-I read the cmake 2.4.0 (or so at the time) manual a lot..
I've been doing this for a while now. We've been using cmake with lib2geom for a while. lib2geom is a much smaller project though.
Then you are at least halfway there.. now its about iterating through directories and finding all those dependencies.. Use the Find*.cmake files Cmake comes with.
-A lot is repetitive, ls -1 helps a lot when listing dirs :)
I'd love to help out, but right now, work is making concentrating a lot at home hard. I'm happy to answer questions but doing the work won't be too productive.
Your physical help would be totally uncalled for. I know you have your own projects to work on. If you don't mind, however, I might contact you with a question once in a while.
Go for it.. :) email to cbradney@...715... if you need an answer in CET daytime.
I had no autotools experience apart from editing the Makefile.ams we had, the rest of the black magic remains just that.
That is encouraging.
:)
Craig