If your download is not starting, click here.
How to Format External Hard Drive for Mac Step 1. Connect your hard drive to your Mac. Open Finder and choose 'Applications Utilities Disk Utility' to launch. Once you open the Disk Utility app, you can see all the drives on your Mac are listed on. Best format for mac hard drive. How to Format an External Drive in OS X 1. Connect the drive to the Mac. Open Disk Utility. The easiest way to do that is hit CMD and the spacebar at. Select the drive you want to format. Give the drive a descriptive name and leave the default settings: OS X Extended.
Thank you for downloading AutoDockTools- for Mac from our software library. Each download we provide is subject to periodical scanning, but we strongly recommend you check the package for viruses on your side before running the installation. The version of the Mac application you are about to download is 4.2.
Each download we provide is subject to periodical scanning, but we strongly recommend you check the package for viruses on your side before running the installation. The version of the Mac application you are about to download is 4.2.3. The package you are about to download is authentic and was not repacked or modified in any way by us. AutoDockTools- is distributed free of charge.
This download is virus-free.This file was last analysed by Free Download Manager Lib 1 day ago.
Computer Skills
This is a build of Allegro 4.4.2 for Mac OS X (i386 arch). It's quite difficult to build this version of the library on modern systems due to the outdated dependencies it has. These instructions require the use of the OSX 10.4 SDK. Monogram generator for mac.
All examples that actually draw a window (such as the grabber
or miditest
, etc) will not work properly on retina displays. If you know how to fix this, please feel free to let me know. Presumably, this can be fixed by bundling them as .app
directories, which allows Mac OS X to run them with double pixels.
Extraneous files have been removed, as well as the demos. The examples are still there, though. The main reason for the existence of this repository is to have a premade build available for Mac OS X.
For those interested in building the library, here's a quick guide. Note that this repository only contains a build, and not the Allegro source files.
Allegro 4 is quite old and requires a number of deprecated header files that are long gone from the Xcode SDKs. To successfully compile the library, you'll need the following:
allegro-4.4.2.zip
)For the SDK, you need to download the Xcode 3.1 installer (named xcode31_2199_developerdvd.dmg
) which is available on the Apple Developer site. You need to register an account to get the download, which is listed as Xcode 3.1 Developer Tools.
Open the developer DVD image, then install the MacOSX10.4.Universal.pkg file in the Packages directory, which will place the SDK in /SDKs/MacOSX10.4u.sdk
. You can delete the Xcode 3.1 image now, since we only need this one file.
Now browse to your unzipped Allegro 4.4.2 source, make a directory called build
and go there, and then type the following:
Note that we're forcing a 32-bit build, which is necessary to use the 10.4 SDK. If all goes well, CMake will have found and configured everything successfully. If there are any missing dependencies, it will tell you here. Non-critical warnings can be ignored.
Then, just type make
. This should successfully build the framework and the associated binaries.
Unfortunately, there's a problem that I haven't been able to resolve yet: building in this way causes binaries (such as the very useful dat
utility) to look for the liballeg
dylib in the absolute path where it ended up after the build process finished.
To fix this, I've added a script fixrpath.bash
that relinks the dylib to a relative path (specifically, ./lib
). This has already been done in this build, but it's useful in case you want to make your own build. Of course, it would be much nicer to not have to deal with this problem at all, by fixing it in the Allegro CMake file, but I don't know how to do that.
To explain how the fixrpath.bash
script works, it's basically modifying the binary to look for the library elsewhere. In this example I'll make the dat
utility look for liballeg.4.4.dylib
in the ./lib/
directory, rather than the full path of my build.
Note that the absolute path I give is unique to my compilation setup, and will be different for you. To find the exact path string to replace, use otool -lv dat
. After this, the dat
utility should work as long as the liballeg.4.4.dylib
file is in the ./lib
directory.
I'm not sure if the instructions work for El Capitan 10.11, but I know they don't work for Sierra 10.12. The following error is displayed:
Apple LLVM version 8.0.0 (clang-800.0.38)
@(#)PROGRAM:ld PROJECT:ld64-274.1
This may be related to this question on Stack Overflow but I'm not sure. I haven't spent any time getting it to work.
If you have any questions, or things to contribute, please let me know!
© 2016, Michiel Sikma. MIT license. Allegro 4.4.2 is giftware licensed.