
Loading ...
Posted by jay on Feb 21st, 2006
If you ever need to get rid of lotus notes installed on OS X then you need to remove the following.
- The Notes directory
- The Notes Data directory
- The com.ibm.lotus.notes.plist file
- The Notes Preferences file
The plist and Notes Preferences file can be found in ~/Library/Preferences/ directory.

Loading ...
Posted by jason on Feb 21st, 2006
You are all readily familiar with the standard LD_LIBRARY_PATH for defining where an executable can find the libraries it requires to run. You can in addition to this define a default set of paths that all applications will search, this can save configuration problems. The standard paths to search is defined in the file /etc/ld.so.conf . This often just points to a directory under which several other configuration files are located. Each configuration file contains a list of paths for the dynamic linker/loader to search for libraries.
The dynamic linker/loader, ld.so or ld-linux.so is the program that finds shared libraries needed by the program you are running, and then run the actual program, that is assuming static libraries are not being used. The dynamic loader actually uses the file /etc/ld.so.cache which contains a compiled list of candidate libraries. The cache file is generated from the ld.so.conf file using ldconfig , which you must run to update the cache file.

Loading ...
Posted by chris on Feb 9th, 2006
I was looking to package a Java Swing Application as a proper Mac OS X application. I found some instructions on how to do it here (look towards the bottom of the page):
http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/
One slight issue is the fact that inside the Mac .app file is a special JavaApplicationStub which fires off the whole process. This must have its executable flag set or the thing will not fly. Ant does its best to mess everything up here as its copy command will not respect UNIX file permissions. Another possible problem is that if you build the .app on Windows the permissions will also be lost. The solution: use the tar task to build a tar.gz of the .app directly. You can then specify that the stub file should have mode 755. When it is expanded on a Mac it will have the right permissions regardless of what platform it was built on.