The VideoLAN Forums

Hiya!

I recently installed VLC 1.3.0 and tried to open it via desktop link but it won't open at all, nothing happens when I double click it...

Here's installer which I used: vlc-1.3.0-git-20111204-0102-win32

UPDATE!!!!!

I found a reason why my VLC won't open, it doesn't create settings and stuff in C:\Users\Username\AppData\Roaming at all, like it should do, I tried to install VLC multiple times too to get those reguired folders and files there but it didn't help.

Even though the installer says -win32 at the end, did you download it from the win64 folder ?
I think that installer for win64 is broken. For me the vlc-cache-gen.exe crashes and there is a bug report on it.
The real 1.3.0 win32 version seems to be working (or crashing less).

Yes, I downloaded these in x64 folder, both was trunk versions: ( I downloaded .exe installers )

http://nightlies.videolan.org/build/win ... 1208-0102/
http://nightlies.videolan.org/build/win ... 1207-0104/

These both installers fails to install those required folders and files, I have not tried yet this newest trunk version which is released today.

I found a reason why my VLC won't open, it doesn't create settings and stuff in C:\Users\Username\AppData\Roaming at all, like it should do, I tried to install VLC multiple times too to get those reguired folders and files there but it didn't help.

Installer doesn't create %appdata%\vlc, vlc.exe does that.

For me vlc.exe doesn't create nothing in C:\Users\Username\AppData\Roaming

I even tried this newest installer:

vlc-1.3.0-git-20111209-0104-win32

What causes these very odd problems? No matter what 1.3.0 version of VLC I install it will not open the player because it will not create reguired files/folders...

When I clicked multiple times vlc-cache-gen.exe it managed to create those required files/folders there in AppData/Roaming..., but still it won't open vlc.exe at all....this is very annoying...

Like I said in my 2nd message the x64 installer and build are broken for me since they switched to 1.3.0 version. I could only use the x32 build.
The last x64 build that worked for me was the last 1.2.0 (vlc-1.2.0-pre1-20111122-0104-win32.exe)

This issue is not fault of installer.
x64 version VLC has been broken since 20111129.

I recently reported this issue to the issue tracker and vlc-dev mailing list.
VLC developer comfirmed this issue but it hasn't been fixed.

nkoriyama > what, more specifically, is the issue? I went to trac.videolan.org and tried to look up your reports but don't think I found what you're referring to:

https://trac.videolan.org/vlc/query?rep ... r=priority


I'm using the a git download I did today and trying to build - but on windows and for 32 bit - and can't even bootstrap:
When I google, I think this may be a problem with gettext however I've checked http://www.gnu.org/s/gettext/ and I believe I have the latest version (that is if the 0.18.1 that gettext --version reports is the same as the 0.18.1.1 on the gnu web site).

nkoriyama > what, more specifically, is the issue? I went to trac.videolan.org and tried to look up your reports but don't think I found what you're referring to:

https://trac.videolan.org/vlc/query?rep ... r=priority

Not my ticket. http://trac.videolan.org/vlc/ticket/5619
The issue is "nobody can use VLC-git Win64 build at the moment."
viewtopic.php?f=14&t=11470&start=100#p319904

I'm using the a git download I did today and trying to build - but on windows and for 32 bit - and can't even bootstrap:

If you want to build win32, see http://wiki.videolan.org/Win32Compile
I recommend corss-compile way.

thanks nkoriyama.

The PKG_PROG_PKG_CONFIG is m4_require'd but not m4_defun'd problem in bootstrap was my own. I'd forgotten
from http://wiki.videolan.org/Win32CompileMSYSNew

It seems there are many things that can cause one to stumble during the Windows build; and doubtless a cross-compile would be easier; but I don't have a linux machine available at the moment.

It seems there are many things that can cause one to stumble during the Windows build; and doubtless a cross-compile would be easier; but I don't have a linux machine available at the moment.

I stumbled over and over, and finally gave up my win32 build on Windows machine
Now I use Mac OS X for building both Mac OS X build and Windows build. It's very easy.
If I only have Windows machine, I might use Linux on virtual machine environment (e.g. virtualbox, vmware).

But I don't want to stop a bravery action. It's only my humble opinion

If I only have Windows machine, I might use Linux on virtual machine environment (e.g. virtualbox, vmware).

I would do that also.