x64 has triple the number of registers you can use for general purpose - that makes a big difference for code that can benefit from it. I imagine codecs would fall into that category.64 bits are mostly marketting gimmick when talking about x64 hardware. Only good thing is that it supports over 4 gigs of memory.
They have some additional x64 based MSYS build tools on their download page.Understanding Win64 developement environment
Since Sun's developer doesn't seem to know Win64 development environment by Bugzilla #227049, I explain it
There is 2 CPU arch for Win64
* IA64 (aka Itanium)
* x64 (aka AMD64, x86_64)
Win64 tools such as complier and assember are included in the following products.
* Platform SDK for Windows Server 2003
* Visual Studio 2005 Standard Edition or highr edition
Visual Studio 2005 Express Edition doesn't have Win64 complier and linker. If you want to get Win64 build environment by non-fee, you have to use Platfrom SDK for Windows Server 2003. Platform SDK has version 14.x of CL.EXE (as same as major version of Visual Studio 2005).
Also, how about Platform SDK for Windows Vista? It is not good chooise. Becasue, it doesn't include assember such as ML64.EXE. Although I don't know why Microsoft decides it has no assember command, we must buy VS2005 STD/PRO if you need latest compiler and assember.
Another point I might make, is that Adobe don't yet make (and have no plans within version 9 to make) a Flash plug-in for any 64bit platform, so watching flash videos on streaming / VOD sites (you know the ones) is presently restricted to the 32bit versions of browsers in windows... and I haven't seen a binary release of GNASH, so I'm guessing you'd have to build that yourself on 64bit Linux. Apple don't produce x64 Quicktime, and RealMedia seems to be a wasted technology strangled by it's own commercialism. 64bit demuxers exist for DirectShow which allow you to view RealMedia in x64 browser without RealPlayer.Latest Mozilla build system uses MSYS. But current stable version of MSYS doesn't work on Vista x64. Since latest Mozilla build system package uses stable version, it doesn't work well.
This issue is a famous issue. Because this is compatibility issue of Vista's WOW6432. To fork thread/process on Cygwin/MSYS, it uses CreateProcess() API and STARTUPINFO parameter. Due to a lack of Vista WOW6432 compatibility, it cannot pass fork information to waiting funtion. So sicne The wait object become invalid, fork always failed.
This issue already fix on latest code (version "1.0.11"). But it isn't released as stabled package. So you have to replace MSYS-1.0.DLL into \mozilla-build\msys\bin with 1.0.11 binaries. MSYS team has released 1.0.11 version DLL as MSYS-1.0.11-20071204.tar.bz2. After installing Mozilla build system, you extract it and have to replace DLLs.
Hello Jb,"As soon as we have a mingw64 compiler for windows on linux or on cygwin, I will work on it"
I don't care about MSVC, MSYS or anything else.
I don't think 32vs64 bit has anything to do with this. Vista 64 has the best Win32 software emulation in Windows universe. And if you find a way to crash VLC that you can easily repeat, please report it.32 build working not so good on vista x64-unstable and often crashing
i report it alreadyI don't think 32vs64 bit has anything to do with this. Vista 64 has the best Win32 software emulation in Windows universe. And if you find a way to crash VLC that you can easily repeat, please report it.32 build working not so good on vista x64-unstable and often crashing
...but where are the official Win64 builds ?Port to Android, iOS, OS/2 and Win64.
Return to “VLC media player Feature Requests”
Users browsing this forum: No registered users and 3 guests