From: Ian Scott <ian.m.scott@st...> - 2007-04-27 08:47:21
Please do not send HTML email to the list. Some news readers don't like
it. Mine, for instance, doesn't handle the line lengths properly when
quoting in a reply. Please read
Rebuilding large projects is always troublesome work - sometimes you can
get away with just building the modified code, but it is not trivial to
work out when this is possible. We make continuous improvements to VXL,
and many of these improvements are in core parts of the code, which have
many dependencies through-out the project. Often these improvements are
just comments (which should have no effect on the binaries) but your
compiler doesn't know that, and so forces a large rebuild.
The only suggestions I can make are the obvious ones
1. Get a faster compiler or computer.
2. Update VXL from CVS less often
3. Use VXL releases rather than the latest CVS version, then you will
only have to rebuild every six months or so.
> I think building vxl is troublesome work. Every time I find the source files in vxl have been changed, I must rebuild it, which is time-wasting, I think.
> I wanna know whether there is solution for this problem, such as, whether I can just build the changed file to get the latest versioin instead of rebuilding the whole vxl.
Get latest updates about Open Source Projects, Conferences and News.