Well, if some new feature is adding then core dev would anyway need to learn new api :)
However i agree adding more dependencies should be communicated better and if this dependency could be avoided -- better avoid it. On Tue, Nov 6, 2012 at 4:35 PM, Campbell Barton <[email protected]>wrote: > Using boost from a platform-maintainer perspective is a non-issue > because its already needed indirectly by other libraries. > > > But IMHO we should still get some agreement among developers when > adding new libraries used by blenders code (intern/ too), even if they > are already indirect dependencies. > > For example - python uses libssl, collada uses libPCRE, libXML (and > others), but I wouldn't want this to be an excuse for blender devs to > include/link to them directly - without some agreement first that this > is important to use in blender. > > > Adding dependencies in blenders code isn't necessarily zero cost: core > devs need to learn the api's to fix bugs in blenders code, we may have > to deal with bugs/issues in the api (rather then having the initial > upstream dependency manage it), and it becomes harder to drop, if the > dependency becomes un-maintained. > > In short - I think adding deps should go through mailing-list or > blendercoders weekly meeting, even if its already in svn's lib/ dir. > > - Campbell > > On Tue, Nov 6, 2012 at 5:29 AM, Daniel Genrich <[email protected]> > wrote: > > Hello, > > > > regarding the build effort on Windows: > > Building boost on windows is a piece of cake nowadays (msvc at least) > > because of some very nice and easy description in the lib folder (at > > least on win64). You just type "build.bat" and wait some minutes until > > you have the finished and updates libs + headers automatically copied in > > place. > > > > > > > > Am 05.11.2012 18:29, schrieb Sergey Sharybin: > >> Brecht, > >> > >> We need to define here which else libraries we're using for release > builds. > >> For as long OIIO, OSL are used you can not avoid maintaining boost > builds > >> for the release. On linux it's really easy to compile, on windows doubt > >> it's more tricky than building ffmpeg or collada. Zapping boost wouldn't > >> save so much time. You also don't need to update it so much often. So > can > >> not see point here. > >> > >> Further, if you already need boost for release build, why don't use > stuff > >> from it in cases it indeed helps you? > >> > >> In my opinion, it's ok for as long as you can disable boost and have > >> blender build with smaller subset of features. Same goes to sdl, carve > and > >> other libraries as well. > >> > >> > > > > _______________________________________________ > > Bf-committers mailing list > > [email protected] > > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > -- With best regards, Sergey Sharybin _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
