DDS for GIMP (Mountain Lion, Native, no X11 GUI)

-
I compiled gimp-dds for GIMP 2.8.6 for Mountain Lion (native).


Well, latter already has this DDS plug-in, but my compiled version is much newer (from gimp-dds-2.2.1). Put the binary file under the following directory (Gimp installation path may differ, so check yours):
/Application/Gimp.app/Contents/Resources/lib/gimp/2.0/plug-ins/

Tips: From Finder, Cmd+N to open a new window, Cmd+Shift+G to pop an input dialog, then put  the path mentioned above; then you can put the binary file. You can do the similar by right clicking Gimp.app to select "Show Package Contents" .

Loading option dialog
Mipmaps as layers
Main surface texture

Comments

Post a Comment

Popular posts from this blog

Make It Work: Global .gitattributes

-
Image
Git is the vanguard of distributed VCSs, and as a matter of course, it provide a way to perform diff or merge on certain files while intermediately treating them as documents of a certain other format. By reflecting appropriate changes to configuration and attributes of git as described in " Git - Git Attributes ," you can set up this intermediate conversion for files of your choice while in diff or merge process. This is best described with an example. Say, there exists a file format called "property list" (hereinafter plist) in Mac, and it can come in 3 forms: XML, binary or JSON (it's not exactly JSON, but is similar to it). To perform diff or merge on files of this type in a consistent way, use command plutil  provided by Mac OS X (or an open-source, GPL-licensed alternative libplist ). Then take the following 2 steps.
« Read More »

GCC and Clang: Library Incompatibility Issues in MacPorts

-
Jumble monolog (or quickly to What to do? ) Currently, I'm using Boost libraries and C++11 features in my Xcode project. But there is a problem. Boost libraries in my development environment was installed using MacPorts, and it seems these Boost libraries could not come along with C++11 features and LLDB in Xcode. Let's make things clear, it is a GCC-Clang compatibility issue. In Xcode build setting, you can choose GNU's libstdc++ for favor to Boost libraries (I'm not sure, but it seems they're built using GCC in my MacPorts environment), but then C++11 features and LLDB are crippled. Seemingly, libstdc++ provided by Apple LLVM is not C++11-ready. Vice versa, you can choose LLVM's libc++ for favor to C++11 features and LLDB, but then Boost libraries are crippled. I think the problem, on the surface, can be distilled to symbol name resolution failure.
« Read More »

Xcode: Easy Shared & Static Lib Management and Linking

-
Image
In Xcode, you can add existing frameworks (binary shared/static libraries or Apple's packaged framework) to a target in your project by choosing from the framework list or drag'n'drop from Finder. Several libraries under "Frameworks" group (e.g. libBusted.a) Benefit of doing this is obvious: you can manage and see what libraries your program is linked to. However, after doing that, I noticed one thing. Xcode does not link shared/static libraries in a simple way like: gcc -o qux libfoo.dylib libbar.a buz.o Instead, when libraries are going to be added, Xcode obtains paths to the directories containing these libraries, and appends these to the build setting "Library Search Path" of the target. So that the actual linking looks like: gcc -L/path/to/foobar -o qux -lfoo libbar.a buz.o Compared to the former, even though orthodox, linking in the latter is indirect. I like the former method because it's simple and error-free even though it somewh...
« Read More »