CVS compiling for the uninitiated
I compiled CVS successfully a while back and was very excited. So today I tried:
cvs -z3 update -Pd make
and got:
Making all in ui make[3]: Entering directory `/usr/local/src/inkscape/share/ui' make[3]: *** No rule to make target `all'. Stop. make[3]: Leaving directory `/usr/local/src/inkscape/share/ui' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/inkscape/share' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/inkscape' make: *** [all] Error 2
If I were to take a stab in the dark I would guess my makefile is too old and it doesn't include rules for the new ui stuff. I could be very wrong, but this makes me wonder when and how often should I use commands like "make clean", autogen.sh and configure when working with Inkscape CVS. I don't think I saw these sorts of instructions in the wiki. (I do think I read a short blurb about using autogen.sh when new folders enter the tree.) Sorry for such rudimentary questions.
Education appreciated, Aaron Spike
On Mon, Mar 14, 2005 at 09:46:13PM -0600, fretfind@...540... wrote:
I compiled CVS successfully a while back and was very excited. So today I tried:
cvs -z3 update -Pd make
and got:
Making all in ui make[3]: Entering directory `/usr/local/src/inkscape/share/ui' make[3]: *** No rule to make target `all'. Stop. make[3]: Leaving directory `/usr/local/src/inkscape/share/ui' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/inkscape/share' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/inkscape' make: *** [all] Error 2
If I were to take a stab in the dark I would guess my makefile is too old and it doesn't include rules for the new ui stuff. I could be very wrong, but this makes me wonder when and how often should I use commands like "make clean", autogen.sh and configure when working with Inkscape CVS. I don't think I saw these sorts of instructions in the wiki. (I do think I read a short blurb about using autogen.sh when new folders enter the tree.) Sorry for such rudimentary questions.
It's a good question, and you're essentially correct. I probably should have mentioned this earlier, since this is caused by my doing.
The cause for this particular issue is the integration of the inkscape_gtkmm code, which involves creating some new subdirectories and some new Makefile_insert's.
When new subdirs are added, you have to refresh the Makefile structure. This requires running autogen.sh and configure. Technically, you don't need to do `make clean`, and in fact it will probably rebuild faster if you don't.
Now, the more important question - how often will you have to do this? Generally, you can expect to need to do this more frequently early on in the development cycle for a given release such as right now; later on in development we shift focus towards getting things polished and finished, and don't need to add directories as often.
Historically, Inkscape has not added new subdirs very often, so in general you shouldn't need to do it very often. Most code has been contained all in the top level directory. However, I think as we move forward, we may be breaking things up into subdirs more aggressively. Having all the code in a single dir gets to be a bit hard to comprehend, and hard for new people to get into. So I'm actually hopeful we'll see increased instances of new subdirs added.
Hope this answers the question, and I apologize for any extra work caused by the inkscape_gtkmm integration.
Bryce
Bryce Harrington wrote:
When new subdirs are added, you have to refresh the Makefile structure. This requires running autogen.sh and configure. Technically, you don't need to do `make clean`, and in fact it will probably rebuild faster if you don't.
<snip>
Hope this answers the question, and I apologize for any extra work caused by the inkscape_gtkmm integration.
Thanks for the wonderfully complete explanation. I'm always waiting to get blasted for asking stupid questions.
I think the important parts of this for me is not doing 'make clean' and rebuilding faster. I was worried that if I did autogen.sh and configure again that I would have to wait for the whole tree to rebuild. I'm happy to find that that is not the case.
For the truly uninitiated such as myself one question remains, "When do I need to use make clean?" I will go reasearch that.
Thank you very much, Aaron Spike
On Tue, Mar 15, 2005 at 07:41:20AM -0600, fretfind@...540... wrote:
For the truly uninitiated such as myself one question remains, "When do I need to use make clean?" I will go reasearch that.
Actually, due to how we have our Makefile structure built, I can't think of any time you'll have to do it. (I can't think of a single time I've ever done it for Inkscape, actually.) I have used "make distclean", but that's more for doing release packaging, etc.
Re-running autogen.sh and configure is generally all you have to do when a major change in structure happens. Most of the time automake/autoconf is smart enough that it'll re-run itself. :)
On Tue, Mar 15, 2005 at 07:41:20AM -0600, fretfind@...540... wrote:
Bryce Harrington wrote:
When new subdirs are added, you have to refresh the Makefile structure. This requires running autogen.sh and configure. Technically, you don't need to do `make clean`, and in fact it will probably rebuild faster if you don't.
<snip>
Hope this answers the question, and I apologize for any extra work caused by the inkscape_gtkmm integration.
Thanks for the wonderfully complete explanation. I'm always waiting to get blasted for asking stupid questions.
I think the important parts of this for me is not doing 'make clean' and rebuilding faster. I was worried that if I did autogen.sh and configure again that I would have to wait for the whole tree to rebuild. I'm happy to find that that is not the case.
By the way, if you're finding compile time to be an issue, check out a program called 'ccache'. This is a handy tool that helps speed up re-compilation of software.
One way to run it is like this:
CXX='ccache g++' ./configure make
For the truly uninitiated such as myself one question remains, "When do I need to use make clean?" I will go reasearch that.
Ideally, you shouldn't ever need to use it, however sometimes when you've got a really oddball compilation/linking issue, and you suspect something may be funky with the already compiled units and want to start over from scratch, you may want to do a make clean. Another situation is when you're developing a new chunk of code and want to make 100% sure that you've got it all hooked up right.
Bryce
participants (3)
-
unknown＠example.com -
Bryce Harrington -
Kees Cook