User Tools

Site Tools


build:compiling_avidemux

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
build:compiling_avidemux [2010/04/14 10:18]
j.m Imported the remaining remainder. Phewww...
build:compiling_avidemux [2010/04/17 09:00]
j.m
Line 63: Line 63:
   - <​code>​cmake .</​code>​ (the dot is required)   - <​code>​cmake .</​code>​ (the dot is required)
   - <​code>​make</​code>​   - <​code>​make</​code>​
- 
-For more information,​ see the [[http://​www.avidemux.org/​admForum/​viewtopic.php?​id=3281|Switch to CMAKE in progress]] thread in the Avidemux forum. 
  
 === Old method (Avidemux 2.3 and older) === === Old method (Avidemux 2.3 and older) ===
Line 273: Line 271:
 == MinGW == == MinGW ==
  
-  - Extract the contents of each MinGW tarball (binutils, gcc-core, gcc-g++, mingw-runtime,​ mingw-utils,​ w32api) to a folder on your hard-drive, e.g. C:DevMinGW.+  - Extract the contents of each MinGW tarball (binutils, gcc-core, gcc-g++, mingw-runtime,​ mingw-utils,​ w32api) to a folder on your hard-drive, e.g. <​nowiki>​C:\Dev\MinGW</​nowiki>​.
  
 == MSYS == == MSYS ==
  
-  - Run the MSYS installer (e.g. MSYS-1.0.11-2004.04.30-1.exe) and follow the install wizard. ​ Choose an appropriate destination folder, e.g. C:Devmsys.+  - Run the MSYS installer (e.g. MSYS-1.0.11-2004.04.30-1.exe) and follow the install wizard. ​ Choose an appropriate destination folder, e.g. <​nowiki>​C:\Dev\msys</​nowiki>​.
   - Agree to the post install process.   - Agree to the post install process.
   - State that MinGW is installed.   - State that MinGW is installed.
Line 299: Line 297:
 == Netwide Assembler == == Netwide Assembler ==
  
-  - Extract the contents of the NASM zip file to an appropriate folder, e.g. C:​Program ​FilesNasm.+  - Extract the contents of the NASM zip file to an appropriate folder, e.g. <​nowiki>​C:\Program ​Files\Nasm</​nowiki>​.
   - Make a copy of **nasmw.exe** and rename it to **nasm.exe** in the Nasm folder. ​ (The optional components expect the filename to be nasm.exe but the Win32 version of NASM has a filename of nasmw.exe)   - Make a copy of **nasmw.exe** and rename it to **nasm.exe** in the Nasm folder. ​ (The optional components expect the filename to be nasm.exe but the Win32 version of NASM has a filename of nasmw.exe)
   - Copy **nasm.exe** to the MinGW **bin** folder.   - Copy **nasm.exe** to the MinGW **bin** folder.
Line 316: Line 314:
   - Choose the **Directories** tab.   - Choose the **Directories** tab.
   - Select **Executable Files** from the **Show Directories For** dropdown box.   - Select **Executable Files** from the **Show Directories For** dropdown box.
-  - Add the path for NASM, e.g. C:​Program ​FilesNasm.+  - Add the path for NASM, e.g. <​nowiki>​C:\Program ​Files\Nasm</​nowiki>​.
  
 === Downloading source code from SVN === === Downloading source code from SVN ===
Line 328: Line 326:
   - Click **OK** to download the source code.   - Click **OK** to download the source code.
  
-==== Avidemux ​Dependencies ​====+==== Avidemux ​dependencies ​====
  
 === Download Dependencies === === Download Dependencies ===
Line 393: Line 391:
 == Netscape Portable Runtime == == Netscape Portable Runtime ==
  
-  - Extract the contents of the nspr zip file to a folder, e.g. C:\Dev.+  - Extract the contents of the nspr zip file to a folder, e.g. <​nowiki>​C:\Dev</​nowiki>​.
   - Copy **libnspr4.dll** from the NSPR **lib** folder to the MinGW **bin** folder.   - Copy **libnspr4.dll** from the NSPR **lib** folder to the MinGW **bin** folder.
  
Line 411: Line 409:
 == SpiderMonkey == == SpiderMonkey ==
  
-  - Extract the contents of the tarball to a folder, e.g. C:Dev.+  - Extract the contents of the tarball to a folder, e.g. <​nowiki>​C:\Dev</​nowiki>​.
   - Build Spidermonkey using Microsoft Visual C++ or MinGW:   - Build Spidermonkey using Microsoft Visual C++ or MinGW:
  
Line 543: Line 541:
 == Aften == == Aften ==
  
-  - Extract the contents of the Aften zip file to a temporary folder, e.g. C:\Dev.+  - Extract the contents of the Aften zip file to a temporary folder, e.g. <​nowiki>​C:\Dev</​nowiki>​.
   - Move the Aften **bin**, **include** and **lib** subdirectories to the corresponding MinGW folders.   - Move the Aften **bin**, **include** and **lib** subdirectories to the corresponding MinGW folders.
   - Open the file **aften.h** in the MinGW **include** folder with a text editor.   - Open the file **aften.h** in the MinGW **include** folder with a text editor.
Line 562: Line 560:
 == FAAC == == FAAC ==
  
-  - Extract the contents of the faac zip file to a temporary folder, e.g. C:\Dev.+  - Extract the contents of the faac zip file to a temporary folder, e.g. <​nowiki>​C:\Dev</​nowiki>​.
   - Open the header files **libfaac\frame.h** and **include\faac.h** with a text editor.   - Open the header files **libfaac\frame.h** and **include\faac.h** with a text editor.
   - Replace the following line in both files: <code cpp>#​define FAACAPI __stdcall</​code>​ with: <code cpp>#​define FAACAPI __cdecl</​code>​   - Replace the following line in both files: <code cpp>#​define FAACAPI __stdcall</​code>​ with: <code cpp>#​define FAACAPI __cdecl</​code>​
Line 597: Line 595:
 == FAAD == == FAAD ==
  
-  - Extract the contents of the FAAD zip file to a temporary folder, e.g. C:\Dev.+  - Extract the contents of the FAAD zip file to a temporary folder, e.g. <​nowiki>​C:\Dev</​nowiki>​.
   - Copy ***.h** in the FAAD **include** folder to the MinGW **include** folder.   - Copy ***.h** in the FAAD **include** folder to the MinGW **include** folder.
   - Build FAAD using Microsoft Visual C++ or MinGW:   - Build FAAD using Microsoft Visual C++ or MinGW:
Line 639: Line 637:
 == LAME == == LAME ==
  
-  - Extract the contents of the lame tarball to a temporary folder, e.g. C:\Dev.+  - Extract the contents of the lame tarball to a temporary folder, e.g. <​nowiki>​C:\Dev</​nowiki>​.
   - Start MSYS.   - Start MSYS.
   - Change directory to the lame folder. <​code>​cd /​c/​dev/​lame-3.97</​code>​   - Change directory to the lame folder. <​code>​cd /​c/​dev/​lame-3.97</​code>​
Line 650: Line 648:
 == Libdca == == Libdca ==
  
-  - Extract the contents of the libdca tarball to a temporary folder, e.g. C:\Dev.+  - Extract the contents of the libdca tarball to a temporary folder, e.g. <​nowiki>​C:\Dev</​nowiki>​.
   - Start MSYS.   - Start MSYS.
   - Change directory to the libdca folder. <​code>​cd /​c/​dev/​libdts-0.0.2</​code>​   - Change directory to the libdca folder. <​code>​cd /​c/​dev/​libdts-0.0.2</​code>​
Line 672: Line 670:
 == Ogg Vorbis == == Ogg Vorbis ==
  
-  - Extract the contents of the Ogg and Vorbis zip files to the same temporary folder, e.g. C:\Dev.+  - Extract the contents of the Ogg and Vorbis zip files to the same temporary folder, e.g. <​nowiki>​C:\Dev</​nowiki>​.
   - Build Ogg Vorbis using Microsoft Visual C++ or MinGW:   - Build Ogg Vorbis using Microsoft Visual C++ or MinGW:
  
Line 717: Line 715:
 == Simple DirectMedia Layer == == Simple DirectMedia Layer ==
  
-  - Extract the contents of the SDL zip file to a temporary folder, e.g. C:\Dev.+  - Extract the contents of the SDL zip file to a temporary folder, e.g. <​nowiki>​C:\Dev</​nowiki>​.
   - Start MSYS.   - Start MSYS.
   - Change directory to the SDL folder. <​code>​cd /​c/​dev/​sdl-1.2.11</​code>​   - Change directory to the SDL folder. <​code>​cd /​c/​dev/​sdl-1.2.11</​code>​
Line 763: Line 761:
 == Xvid == == Xvid ==
  
-  - Extract the contents of the Xvid tarball to a temporary folder, e.g. C:\Dev.+  - Extract the contents of the Xvid tarball to a temporary folder, e.g. <​nowiki>​C:\Dev</​nowiki>​.
   - Build Xvid using Microsoft Visual C++ or MinGW:   - Build Xvid using Microsoft Visual C++ or MinGW:
  
build/compiling_avidemux.txt ยท Last modified: 2012/11/11 08:51 (external edit)