Difference between revisions of "WinRTCompile"
Jump to navigation
Jump to search
(Created the first version of Compiling VLC for WinRT) |
|||
| (8 intermediate revisions by 6 users not shown) | |||
| Line 5: | Line 5: | ||
To develop VLC for WinRT, you would need to have: | To develop VLC for WinRT, you would need to have: | ||
* Windows 8.1 | * Windows 8.1 | ||
| − | * Visual Studio 2013 with Update 2 | + | * Visual Studio 2013 with Update 2 (or Update 3) |
* Windows 8.1 SDK (Recommended) | * Windows 8.1 SDK (Recommended) | ||
| − | * Latest version of Git | + | * Latest version of [[Git]] |
| − | * Lots of patience | + | * Lots of patience :D |
| − | |||
==Get the source== | ==Get the source== | ||
| Line 15: | Line 14: | ||
You can clone the VLC for WinRT git repository | You can clone the VLC for WinRT git repository | ||
| − | git clone | + | git clone https://code.videolan.org/videolan/vlc-winrt.git |
| Line 21: | Line 20: | ||
====Packaged 7zip file==== | ====Packaged 7zip file==== | ||
| − | You can download vlc.7z from [http://people.videolan.org/~ | + | You can download vlc.7z from [http://people.videolan.org/~hugo/vlc-Win32.7z here]. Extract the contents of vlc.7z and copy the contents to vlc folder of winrt source code |
====Cross Compiling==== | ====Cross Compiling==== | ||
| − | If you feel adventurous, you can try cross-compiling libVLC for WinRT. Refer to the [ | + | If you feel adventurous, you can try cross-compiling libVLC for WinRT. Refer to the [https://code.videolan.org/videolan/vlc-winrt README] file in the source folder for more information |
| − | |||
==Build and Deploy== | ==Build and Deploy== | ||
* Open the VLC_WinRT solution in app/VLC_WINRT.sln | * Open the VLC_WinRT solution in app/VLC_WINRT.sln | ||
| − | * Open Package.appxmanifest, and generate a test certificate. More information can be found in the [ | + | * Open Package.appxmanifest, and generate a test certificate. More information can be found in the [https://code.videolan.org/videolan/vlc-winrt/blob/master/README README] file in the source folder |
* Click on Build Solution and then Deploy | * Click on Build Solution and then Deploy | ||
| − | |||
==Additional Notes== | ==Additional Notes== | ||
* If building fails with lots of errors referring to Windows SDK headers, installing Windows 8.1 SDK usually helps | * If building fails with lots of errors referring to Windows SDK headers, installing Windows 8.1 SDK usually helps | ||
* It helps to right click the specific project (eg: Windows 8.1 project ) and then click deploy rather than trying to deploy the whole solution | * It helps to right click the specific project (eg: Windows 8.1 project ) and then click deploy rather than trying to deploy the whole solution | ||
| + | |||
| + | [[Category:Building]] | ||
| + | [[Category:Mobile documentation]] | ||
| + | [[Category:Windows]] | ||
Latest revision as of 06:51, 8 March 2019
This page will help you compile VLC for WinRT
Contents
Development Environment
To develop VLC for WinRT, you would need to have:
- Windows 8.1
- Visual Studio 2013 with Update 2 (or Update 3)
- Windows 8.1 SDK (Recommended)
- Latest version of Git
- Lots of patience :D
Get the source
You can clone the VLC for WinRT git repository
git clone https://code.videolan.org/videolan/vlc-winrt.git
Get libVLC source
Packaged 7zip file
You can download vlc.7z from here. Extract the contents of vlc.7z and copy the contents to vlc folder of winrt source code
Cross Compiling
If you feel adventurous, you can try cross-compiling libVLC for WinRT. Refer to the README file in the source folder for more information
Build and Deploy
- Open the VLC_WinRT solution in app/VLC_WINRT.sln
- Open Package.appxmanifest, and generate a test certificate. More information can be found in the README file in the source folder
- Click on Build Solution and then Deploy
Additional Notes
- If building fails with lots of errors referring to Windows SDK headers, installing Windows 8.1 SDK usually helps
- It helps to right click the specific project (eg: Windows 8.1 project ) and then click deploy rather than trying to deploy the whole solution
