Exploring x264

[ramprasad85]

Hi,
I am planning to learn and explore x264.
I would like to know Which OS and IDE is widely used.
Thank you

[cogman]

Hi,
I am planning to learn and explore x264.
I would like to know Which OS and IDE is widely used.
Thank you

Please change your thread title as there is a commonly used thread with the exact same title. Something like "Hey, how can I help with x264".

As for OS, it doesn't really matter, any will do.

IDE, doesn't matter, any will do.

Compiler. If you want to compile it for speed, the GCC is probably the best to use as it is what x264 is most optimized for. If you want to help out, I think they need help with the MSVC development, specifically getting all the GNU style asm to work with MSVC.

[Dark Shikari]

As for OS, it doesn't really matter, any will do.But developing without valgrind and oprofile requires a special kind of insanity.
IDE, doesn't matter, any will do.Better said, "none" will do.
Compiler. If you want to compile it for speed, the GCC is probably the best to use as it is what x264 is most optimized for. If you want to help out, I think they need help with the MSVC development, specifically getting all the GNU style asm to work with MSVC.No, we dropped support for MSVC because it doesn't support C99.

[akupenguin]

But developing with valgrind and oprofile requires a special kind of insanity.
You mean without?

[Dark Shikari]

You mean without?Yes, this is the result of posting at 4 AM.

[bob0r]

:) you made pengie think he is insane :)

[Guest]

I'm specially insane because I never heard of either of them. Some kind of Linux weanie thing?

[Dark Shikari]

I'm specially insane because I never heard of either of them.If you seriously don't know, oprofile is a very very powerful profiling tool. However, unlike valgrind, it has a Windows equivalent, Vtune. I personally much prefer oprofile though.

Valgrind is a tool which, as far as I know, is completely unique and has no commercial equivalent. It's an x86 emulator that can automatically find memory access violations, count cache misses/hits, find memory leaks, and all sorts of other magic. I've found it far more reliable at finding Heisenbugs than any other tool I've ever seen. For example, this bugfix (http://git.videolan.org/?p=x264.git;a=commit;h=a933a3e6a6be918a2ae56e3d94ecea29143b9ea5) was done using Valgrind. It's especially useful for finding bugs that don't necessarily cause crashes yet, but might result in weird stuff happening in the future.

I keep a Linux machine on SSH for almost the sole purpose of using these two tools.

Anyways, this thread is getting a bit derailed.

[Guest]

Ah, Vtune I know. Thanks for the explanation.

[Gabriel_Bouvigne]

No, we dropped support for MSVC because it doesn't support C99.
Although if someone wanted to use MSVC, that would not really be an issue with current code. (I am myself using mostly MSVC)

If you seriously don't know, oprofile is a very very powerful profiling tool. However, unlike valgrind, it has a Windows equivalent, Vtune.
Or CodeAnalyst


Valgrind is a tool which, as far as I know, is completely unique and has no commercial equivalent.
Purify (and before someone mentions it: yes, it is expensive)

[shark37]

Although if someone wanted to use MSVC, that would not really be an issue with current code. (I am myself using mostly MSVC)

Could not resist to mention another publicly available MSVC build of (modified) x264 -- roozhou's project direct264 (http://forum.doom9.org/showthread.php?t=141441&highlight=directshow+x264) :p