Hi! On Mon, Jan 11, 2016 at 5:54 AM, Larry Gritz <[email protected]> wrote: > Based on those logs, I think the specific problem has already been fixed. > > Can you try the current "top" of RB-1.6 to verify? If it works, I'll tag the > current top and declare a new release if you need.
I'll try asap. > So, how can we cut down even more to reduce the chances of breaking your > builds (and then us having to track it down and cut new releases just to fix > it)? There are a few things to consider: > > * Almost always, the Debian build breaks are "warnings" that are treated as > errors. You may wish to consider compiling with STOP_ON_WARNING=0 as standard > practice, and only every once in a while compile without it and report back > to us any errors you encounter -- OR, compile the usual way by default but > know that if it fails, try again with STOP_ON_WARNING=0 and use that build if > it succeeds. In any case, if STOP_ON_WARNING=0 succeeds, you should go with > that build. If you send us the logs, we can address the warning as promptly > as we can, but it should never hold up your updating the package. The > warnings are almost always harmless. OK, gonna use this as a standard, then. > * This particular problem (and some others we've had for your builds, IIRC) > are in a DASSERT, and thus only a build break for DEBUG builds. I think you > should seriously consider the merits of building in DEBUG mode. Why is it > helpful to your users? It seems to me that anyone who needs to debug *into* > OIIO can probably build from source, and for everybody else it's probably a > distraction and they would prefer only an optimized build? Is there a good > reason to provide a debug build? Is that standard for all libraries? I've checked our debian/rules file (that is the make file for Debian) and there's no explicit definition of compiling in debug mode. Then it's probably defined in the upstream code. Or I'm badly missing your point. > * Is there a way you can do a nightly (or less frequently, but periodic) > builds that can catch these little breakages as soon as they go in, rather > than only after we've tagged a release? Well, not officially. There's the jenkins.debian.net project but it's used for reproducibility tasks at the moment. Gonna ask for a possible of that for nightlies. Cheers. -- Matteo F. Vescovi _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
