On Monday 19 January 2009, Andreas Pakulat wrote: > On 18.01.09 23:33:21, Andreas Pakulat wrote: ... > > > The problem with that is when a new version is out. > > > > Not really, if a project uses boost, one of its dev should _check_ that > > it still works with the newer version (As I said in the other mail, > > kdevplatform for example doesn't build with 1.37). And if he verified > > that, he can simply commit the change. > > > > IMHO you can't assume that your boost-using project will work just fine > > with a newer version.
Are they that bad with keeping compatibility ? > PS: Re-Reading my post I guess it didn't come across that, I don't object > adding some globbing to find version.hpp. I was just trying to point out > the possible problems that come with that approach. Yes, I think some globbing sounds like a good idea. You could just do it in /usr/include and /usr/local/include, or go for everything: glob in each of CMAKE_PREFIX_PATH with include/ appended (empty by default) glob in each of CMAKE_SYSTEM_PREFIX_PATH with include/ appended glob in each of CMAKE_INCLUDE_PATH (usually empty) glob in each of CMAKE_SYSTEM_INCLUDE_PATH Alex _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
