The VideoLAN Forums

Hi !

I've checked your default git - https://github.com/videolan/vlc

And there is a lot of 3rd party libraries which you need to integrate with vlc, and they are not included as source codes / not compiled with vlc project. (in folder 'contrib' there is huge amount of patches for each library / for each platform).
I want to have compilable / buildable projects / solutions of libvlc for windows and android platforms, including all 3-rd party libraries as source code.

Maybe such git repository already exists - or does makes any sense create new vlc clone with 3-rd party libraries ?

Commiting compiler code is not a good idea IMHO, and there is absolutely no plan to do that as an official repo. However, we do publish precompiled contribs: see https://nightlies.videolan.org/build/wi ... 13.tar.bz2 for instance.

Also, the github repo is a mirror. The official one is https://git.videolan.org/git/vlc.git

I have at work quite heavy 3rd party base, but what I have learned over the time, is that you cannot rely on 3rd party pre-compiled libraries.
Every library might have a bug, and over years they gets discovered one by one. Others libs like libjpeg gets evolved, and it's possible that you don't want to stay on same place.
Some libraries gets perished - you cannot find original source code, author or license - that's why I prefer to have all libraries and patches collected in same place. (As source codes with repo history)

I have now cross hacked libvlccore .dll / .so to make it compilable without autoconf / configure using my own tool for that purpose ( https://docs.google.com/document/d/1C1Y ... j5zHU/edit )
I've now somehow hacked some of codes, I'm not sure whether I'm hacking in right place and using right approach, but since there are quite many different source codes I would prefer to keep all my changes somewhere.

It's also useful to track in svn / git history of what was done and to what.

So I will create repository wanted or not, but if you can propose me some official place where it could be placed. I prefer by myself svn, because of it's simplicity - but if someone wants to co-develop e.g. using git - I can take that into account.

I have at work quite heavy 3rd party base, but what I have learned over the time, is that you cannot rely on 3rd party pre-compiled libraries.
Every library might have a bug, and over years they gets discovered one by one. Others libs like libjpeg gets evolved, and it's possible that you don't want to stay on same place.
Some libraries gets perished - you cannot find original source code, author or license - that's why I prefer to have all libraries and patches collected in same place. (As source codes with repo history)

That's why we have all the build rules and patches collected in VLC contribs.

I prefer to keep them in repository instead of patches. Patch is extra work.
For example there is reference to iconv library, also it's version, but no information on libintl or it's version.

I want also to get rid of all separate configure steps, and create projects / solutions to be compilable from windows (to windows and android).
I think *configure* file can be kept just if someone wants to use them still, but I want .sln & .vcxproj files.

Then why are you asking us?

Just if anyone is interested in joining the development.

I have now created svn for new vlc: https://sourceforge.net/projects/vlc2/

Currently just a copy, I'll start to patch it soon, hopefully tomorrow.

In future, I'll push messages to this thread: https://forum.videolan.org/viewtopic.ph ... 29#p455729

So my intention is to have windows + android + visual projects walk hand by hand, I propose to continue discussion there on cross platform level, on Android specific port issues, I'll post separate messages here.

But I haven't yet reached run-time, so expect more bugs because of my port.

That's a total waste of time.