[x264-devel] x264 on x64

Steven Walters kemuri9 at gmail.com
Tue Nov 23 03:50:26 CET 2010


No, x264 in it's current state does not support visual studio's
compiler as it does not support the C99 convention that x264 utilizes.
Direct264 is the next closest thing for the time being, as it removes
the C99 requirements of x264 so it can be compiled with MSVC.

I do however have a patch that adds support for Intel's compiler
(which does support C99), which then allows building of fully MSVC
compatible libraries.

This is has been in the works for a while but I lately halted it due
to an issue with pthread-win32 crashing in the 64bit version of x264.
This is on the back burner until i get another patch to alleviate the
pthread-win32 issue finalized and committed.

On Mon, Nov 22, 2010 at 9:08 PM, Scott Taylor <scott.taylor at abaslabs.com> wrote:
> We found the same problem. I tried different build environments / compilers
> and using MS' LIB tool, no success. Always got unresolved symbols.
>
> Fortunately we found an existing MSVC sln in Direct264:
> http://sourceforge.net/projects/direct264/
>
> We also found that we needed to extern "C" the include:
> extern "C"
> {
>   #include "x264.h"
> }
>
> Scott
>
>
>
> On 23/11/2010 11:35 AM, Santosh wrote:
>
> Thank you for the reply Steven.
> Is MSVC supported in x264 - i.e. are there .sln files which I can use ? or I
> need to create a MSVC solution from scratch ?
> Regards,
> Santosh
>
> On Mon, Nov 22, 2010 at 4:15 PM, Steven Walters <kemuri9 at gmail.com> wrote:
>>
>> 64bit MinGW and 64bit MSVC were still incompatible with each other
>> last time i checked.
>>
>> if this is still the case, you'll need to compile x264 with visual
>> studio if you want to use the static library in another visual studio
>> project
>> (which i'm inferring with your use of a .lib filename vs .a)
>>
>> On Mon, Nov 22, 2010 at 6:56 PM, Santosh <santoshkumarcs1986 at gmail.com>
>> wrote:
>> > Dear experts,
>> > I am having trouble linking libx264.lib to my application on x64
>> > machine.
>> > I am able to build it. But, when I try linking it, I get the following
>> > errors:
>> > .
>> > .
>> > libx264.lib(encoder.o) : error LNK2019: unresolved external symbol log2f
>> > referenced in function x264_validate_parameters
>> > libx264.lib(set.o) : error LNK2001: unresolved external symbol log2f
>> > libx264.lib(analyse.o) : error LNK2001: unresolved external symbol log2f
>> > libx264.lib(ratecontrol.o) : error LNK2001: unresolved external symbol
>> > log2f
>> > libx264.lib(encoder.o) : error LNK2019: unresolved external symbol
>> > fseeko64
>> > referenced in function x264_encoder_frame_end
>> > libx264.lib(common.o) : error LNK2001: unresolved external symbol
>> > fseeko64
>> > .
>> > .
>> > .
>> >
>> > I am building on a 64-bit Windows 7 machine and use the following
>> > configuration:
>> > ./configure --host=x86_64-w64-mingw32
>> > Is x264 supported on 64-bit machines ?
>> > Also, is there is any website where I can get static library
>> > (libx264.lib) ?
>> > Regards,
>> > Santosh
>> >
>> > _______________________________________________
>> > x264-devel mailing list
>> > x264-devel at videolan.org
>> > http://mailman.videolan.org/listinfo/x264-devel
>> >
>> >
>> _______________________________________________
>> x264-devel mailing list
>> x264-devel at videolan.org
>> http://mailman.videolan.org/listinfo/x264-devel
>
>
>
> --
> Jai Hind
>
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> http://mailman.videolan.org/listinfo/x264-devel
>
>
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> http://mailman.videolan.org/listinfo/x264-devel
>
>


More information about the x264-devel mailing list