Cygwin Mac Os X Download

admin

Table of Contents

  • 1 Unix-like
  • 4 Windows
    • 4.1 Native Windows compilation using MinGW or MinGW-w64
    • 4.2 Microsoft Visual C++ or Intel C++ Compiler for Windows

Using MacPorts, the port is called 'cairo', so you can just type: sudo port install cairo. Download and run the Cygwin Setup.exe from Cygwin's website. Mac OS X already has Perl installed. Open a Terminal application (in the Utilities folder of your Applications folder) and run perl -v to find out which version. ActiveState Perl has binary distributions of Perl for Mac OS X. This is the simplest way to install the latest version of Perl. Download ActivePerl. Remember that the setup-x86.exe or setup-x8664.exe downloaded from is the official method for installing cygwin. If you install using some other method and have problems, you may get little or no official support. Just use the official gui installer to install and update packages.

Jq is written in C and has no runtime dependencies, so it should be possible to build it for nearly any platform. Prebuilt binaries are available for Linux, OS X and Windows. The binaries should just run, but on OS X and Linux you may need to make them executable first using chmod +x jq. Jq is licensed under the MIT license. Usually, uname with its various options will tell you what environment you're running in: pax uname -a CYGWINNT-5.1 IBM-L3F3936 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin pax uname -s CYGWINNT-5.1 And, according to the very helpful schot (in the comments), uname -s gives Darwin for OSX and Linux for Linux, while my Cygwin gives CYGWINNT-5.1.But you may have to experiment with.

1 Unix-like

Some parts of FFmpeg cannot be built with version 2.15 of the GNUassembler which is still provided by a few AMD64 distributions. Tomake sure your compiler really uses the required version of gasafter a binutils upgrade, run:

If not, then you should install a different compiler that has nohard-coded path to gas. In the worst case pass --disable-asmto configure.

1.1 Advanced linking configuration

If you compiled FFmpeg libraries statically and you want to use them tobuild your own shared library, you may need to force PIC support (with--enable-pic during FFmpeg configure) and add the following optionto your project LDFLAGS:

If your target platform requires position independent binaries, you shouldpass the correct linking flag (e.g. -pie) to --extra-ldexeflags.

1.2 BSD

BSD make will not build FFmpeg, you need to install and use GNU Make(gmake).

1.3 (Open)Solaris

GNU Make is required to build FFmpeg, so you have to invoke (gmake),standard Solaris Make will not work. When building with a non-c99 front-end(gcc, generic suncc) add either --extra-libs=/usr/lib/values-xpg6.oor --extra-libs=/usr/lib/64/values-xpg6.o to the configure optionssince the libc is not c99-compliant by default. The probes performed byconfigure may raise an exception leading to the death of configure itselfdue to a bug in the system shell. Simply invoke a different shell such asbash directly to work around this:

1.4 Darwin (Mac OS X, iPhone)

The toolchain provided with Xcode is sufficient to build the basicunaccelerated code.

Mac OS X on PowerPC or ARM (iPhone) requires a preprocessor fromhttps://github.com/FFmpeg/gas-preprocessor orhttps://github.com/yuvi/gas-preprocessor(currently outdated) to build the optimizedassembly functions. Put the Perl script somewherein your PATH, FFmpeg’s configure will pick it up automatically.

Mac OS X on amd64 and x86 requires nasm to build most of theoptimized assembly functions. Fink,Gentoo Prefix,Homebrewor MacPorts can easily provide it.

2 DOS

Using a cross-compiler is preferred for various reasons.http://www.delorie.com/howto/djgpp/linux-x-djgpp.html

3 OS/2

For information about compiling FFmpeg on OS/2 seehttp://www.edm2.com/index.php/FFmpeg.

4 Windows

To get help and instructions for building FFmpeg under Windows, check outthe FFmpeg Windows Help Forum at http://ffmpeg.zeranoe.com/forum/.

4.1 Native Windows compilation using MinGW or MinGW-w64

FFmpeg can be built to run natively on Windows using the MinGW-w64toolchain. Install the latest versions of MSYS2 and MinGW-w64 fromhttp://msys2.github.io/ and/or http://mingw-w64.sourceforge.net/.You can find detailed installation instructions in the download section andthe FAQ.

Notes:

  • Building for the MSYS environment is discouraged, MSYS2 provides a fullMinGW-w64 environment through mingw64_shell.bat ormingw32_shell.bat that should be used instead of the environmentprovided by msys2_shell.bat.
  • Building using MSYS2 can be sped up by disabling implicit rules in theMakefile by calling make -r instead of plain make. Thisspeed up is close to non-existent for normal one-off builds and is onlynoticeable when running make for a second time (for example duringmake install).
  • In order to compile FFplay, you must have the MinGW development libraryof SDL and pkg-config installed.
  • By using ./configure --enable-shared when configuring FFmpeg,you can build the FFmpeg libraries (e.g. libavutil, libavcodec,libavformat) as DLLs.

4.1.1 Native Windows compilation using MSYS2

The MSYS2 MinGW-w64 environment provides ready to use toolchains and dependenciesthrough pacman.

Make sure to use mingw64_shell.bat or mingw32_shell.bat to havethe correct MinGW-w64 environment. The default install provides shortcuts tothem under MinGW-w64 Win64 Shell and MinGW-w64 Win32 Shell.

To target 32 bits replace x86_64 with i686 in the command above.

4.2 Microsoft Visual C++ or Intel C++ Compiler for Windows

Mac os x download iso

FFmpeg can be built with MSVC 2013 or later.

You will need the following prerequisites:

  • NASM(Also available via MSYS2’s package manager.)

Mac Os X Download For Windows

To set up a proper environment in MSYS2, you need to run msys_shell.bat fromthe Visual Studio or Intel Compiler command prompt.

Place yasm.exe somewhere in your PATH.

Next, make sure any other headers and libs you want to use, such as zlib, arelocated in a spot that the compiler can see. Do so by modifying the LIBand INCLUDE environment variables to include the Windows-stylepaths to these directories. Alternatively, you can try to use the--extra-cflags/--extra-ldflags configure options.

Finally, run:

If you wish to compile shared libraries, add --enable-shared to yourconfigure options. Note that due to the way MSVC and ICL handle DLL imports andexports, you cannot compile static and shared libraries at the same time, andenabling shared libraries will automatically disable the static ones.

Notes:

Cygwin Mac Os X Download Utorrent

  • If you wish to build with zlib support, you will have to grab a compatiblezlib binary from somewhere, with an MSVC import lib, or if you wish to linkstatically, you can follow the instructions below to build a compatiblezlib.lib with MSVC. Regardless of which method you use, you must stillfollow step 3, or compilation will fail.
    1. Grab the zlib sources.
    2. Edit win32/Makefile.msc so that it uses -MT instead of -MD, sincethis is how FFmpeg is built as well.
    3. Edit zconf.h and remove its inclusion of unistd.h. This getserroneously included when building FFmpeg.
    4. Run nmake -f win32/Makefile.msc.
    5. Move zlib.lib, zconf.h, and zlib.h to somewhere MSVCcan see.
  • FFmpeg has been tested with the following on i686 and x86_64:
    • Visual Studio 2013 Pro and Express
    • Intel Composer XE 2013
    • Intel Composer XE 2013 SP1

    Anything else is not officially supported.

4.2.1 Linking to FFmpeg with Microsoft Visual C++

If you plan to link with MSVC-built static libraries, you will needto make sure you have Runtime Library set toMulti-threaded (/MT) in your project’s settings.

You will need to define inline to something MSVC understands:

Also note, that as stated in Microsoft Visual C++, you will needan MSVC-compatible inttypes.h.

If you plan on using import libraries created by dlltool, you mustset References to No (/OPT:NOREF) under the linker optimizationsettings, otherwise the resulting binaries will fail during runtime.This is not required when using import libraries generated by lib.exe.This issue is reported upstream athttp://sourceware.org/bugzilla/show_bug.cgi?id=12633.

To create import libraries that work with the /OPT:REF option(which is enabled by default in Release mode), follow these steps:

  1. Open the Visual Studio Command Prompt.

    Alternatively, in a normal command line prompt, call vcvars32.batwhich sets up the environment variables for the Visual C++ tools(the standard location for this file is something likeC:Program Files (x86_Microsoft Visual Studio 10.0VCbinvcvars32.bat).

  2. Enter the bin directory where the created LIB and DLL filesare stored.
  3. Generate new import libraries with lib.exe:

    Replace foo-version and foo with the respective library names.

4.3 Cross compilation for Windows with Linux

You must use the MinGW cross compilation tools available athttp://www.mingw.org/.

Then configure FFmpeg with the following options:

(you can change the cross-prefix according to the prefix chosen for theMinGW tools).

Then you can easily test FFmpeg with Wine.

4.4 Compilation under Cygwin

Please use Cygwin 1.7.x as the obsolete 1.5.x Cygwin versions lackllrint() in its C library.

Install your Cygwin with all the 'Base' packages, plus thefollowing 'Devel' ones:

In order to run FATE you will also need the following 'Utils' packages:

If you want to build FFmpeg with additional libraries, download Cygwin'Devel' packages for Ogg and Vorbis from any Cygwin packages repository:

Mac

These library packages are only available fromCygwin Ports:

The recommendation for x264 is to build it from source, as it evolves tooquickly for Cygwin Ports to be up to date.

4.5 Crosscompilation for Windows under Cygwin

Cygwin Mac Os X Download Iso

With Cygwin you can create Windows binaries that do not need the cygwin1.dll.

Just install your Cygwin as explained before, plus these additional'Devel' packages:

and add some special flags to your configure invocation.

Mac Os X Download Iso

For a static build run

and for a build with shared libraries

This document was generated on December 13, 2020 using makeinfo.

Hosting provided by telepoint.bg

Install Cygwin X Server

  • Latest version: 1.6.2
  • Release date: 28 Oct 2019

  • Source package:xcrysden-1.6.2.tar.gz

  • Linux x86_64 binary packages (64bit):
    • Shared: xcrysden-1.6.2-linux_x86_64-shared.tar.gz
      • Requires: libtk8.6.so, libtcl8.6.so, libTogl.so.2,libGLU.so.1, libGL.so.1, libfftw3.so.3, libXmu.so.6, libX11.so.6,libgfortran.so.5, ...
      • Recommends: ImageMagick, OpenBabel
      • On Debian-based systems these can be installed with:
  • Mac OS binary packages:
    (compiled on macOS Mojave 10.14)
    • Shared: xcrysden-1.6.2-macosx-shared.tar.gz
      • Requires the following MacPorts libraries:libtcl8.6.dylib, libtk8.6.dylib, libGL.1.dylib, libGLU.1.dylib,libX11.6.dylib, libXmu.6.dylib, libfftw3.3.dylib
      • Recommends: ImageMagick, OpenBabel
      • These can be installed with:
  • Mac OS MacPorts and Fink packages:

  • Windows - WSL binarypackage:
    (WSL = Windows Subsytem for Linux)
    • Shared: xcrysden-1.6.2-windows-wsl.tar.gz(Courtesy of Matic Poberznik)
      • Compiled under WSL(Ubuntu 18.04 LTS) @ Windows 10
      • Requires: XMing (https://sourceforge.net/projects/xming/)
        (make sure to define the DISPLAY enviromental variable,i.e., export DISPLAY=:0 )
      • Depends on: tk, libglu1-mesa, libtogl2, libfftw3-3,libxmu6, libgfortran4
      • Recommends: ImageMagick, OpenBabel
      • These packages can be installed with:
  • Windows - Cygwin64 binarypackage:
    • Shared: xcrysden-1.6.2-cygwin.tar.gz(Courtesy of Matic Poberznik)
      • Compiled under x86_64 cygwin (CYGWIN_NT-10.0) @ Windows10
      • Requires: Cygwin, XMing(https://sourceforge.net/projects/xming/)
        • make sure to define the DISPLAY enviromental variable,i.e., export DISPLAY=:0
        • also define export PATH=$PATH:/usr/lib
      • Depends on: tcl-tk8.6, tcl-togl, ImageMagick, xinit, mesa,libGLU1, libfftw3_3, libgfortran4. These packages can beinstalled with apt-cyg packagemanager. For the full list of required packages, see the fileREADME.cygwin inside the tarball.