[x264-devel] [PATCH] build: Generate dependency information as a side-effect of compilation

Steven Walters kemuri9 at gmail.com
Wed May 7 15:55:26 CEST 2014


On Wed, May 7, 2014 at 6:18 AM, Diego Biurrun <diego at biurrun.de> wrote:
> On Tue, May 06, 2014 at 08:48:43AM -0400, Steven Walters wrote:
>> On Tue, May 6, 2014 at 8:21 AM, Diego Biurrun <diego at biurrun.de> wrote:
>> > Most importantly, dependencies are already getting generated right now.
>> > So currently everybody is paying the cost of dependency generation every
>> > time x264 gets built.  And lo and behold, generating dependencies as a
>> > side-effect of compilation is quicker.  On my slow notebook build times
>> > decrease from 1m15s to 1.13s with --disable-asm --disable-opencl (used
>> > in order to mask out time spent assembling and running Perl scripts).
>>
>> This is under the assumption that dependency generation CAN be
>> generated as part of the actual compilation,
>> which it can not be for all compilers (such as MSVS).
>> MSVS is already slow to build with, making it even slower is rather undesirable.
>
> How would you build with MSVS?  I see no support in configure ...

It's pending the RTM release of MSVS 2013 Update 2 and a likely some
small bit of clean up still which may occur from that,
but the current work I have is at
https://github.com/kemuri-9/x264-devel/tree/msvs2013

>
> Diego
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> https://mailman.videolan.org/listinfo/x264-devel


More information about the x264-devel mailing list