Mac Os X
Get flash to fully experience Pearltrees
Environment Variables for MacOS X Applications
MacOS X native applications do not see unix environment variables defined in ~/.cshrc or any other of the standard unix configuration files. Normally this doesn't matter, but certain MacOS X applications can make good use of environment variables. These include the framework build of Python (which is used to write wxPython or aqua Tk applications) and BBEdit (which can directly run unix scripts, but without your environment variables unless you define them in this fashion). The trick is to define your environment variables in the file ~/.MacOSX/environment.plist .
____ __ __ _ _ / ___| ___ _ __ __ __ ___ _ __ | \/ | __ _ (_) _ __ | |_ ___ _ __ __ _ _ __ ___ ___ \___ \ / _ \| '__|\ \ / // _ \| '__| _____ | |\/| | / _` || || '_ \ | __|/ _ \| '_ \ / _` || '_ \ / __|/ _ \ ___) || __/| | \ V /| __/| | |_____|| | | || (_| || || | | || |_| __/| | | || (_| || | | || (__| __/ |____/ \___||_| \_/ \___||_| |_| |_| \__,_||_||_| |_| \__|\___||_| |_| \__,_||_| |_| \___|\___| _ (_) _ __ _ __ _ __ ___ __ _ _ __ ___ ___ ___ | || '_ \ | '_ \ | '__|/ _ \ / _` || '__|/ _ \/ __|/ __| | || | | | | |_) || | | (_) || (_| || | | __/\__ \\__ \ _ _ _ |_||_| |_| | .__/ |_| \___/ \__, ||_| \___||___/|___/ (_)(_)(_) |_| |___/ o o \|||/ (o o) +-------------------------oOO--(_)--OOo------------------------+ Sat, 29 Oct 2011 05:21:00 +0700 __ / \ /|oo \ (_| /_) _`@/_ \ _ | | \ \\ | (*) | \ )) ______ |__U__| / \// / FIDO \ _//|| _\ / (________) (_/(_|(____/
Variable d'environnement PATH sous Mac OS X et / ou Eclipse
ldd sous mac OS X
The "file" command will shown the architecture. by Jun 20
iphone - How do I determine the target architecture of static library (.a) on Mac OS X? - Stack Overflow
As an alternative, I've found objdump can work well. As an example, in my environment I build library archives with vxWorks and need to link those into other projects. To test whether the archive is the correct architecture, I could do something like the following (bash syntax): One nice benefit of this is that objdump , or a similarly named variant, is installed on most *nix operating systems, whereas tools suggested in other responses aren't.
There are essentially two problems to solve when dealing with environment variables in OS X. The first is when invoking programs from Spotlight (the magnifying glass icon on the right side of the Mac menu/status bar) and the second when invoking programs from the Dock. Invoking programs from a Terminal application/utility is trivial because it reads the environment from the standard shell locations ( ~/.profile , ~/.bash_profile , ~/.bashrc , etc.) To solve both problems simultaneously, I use a login item (set via the System Preferences tool) on my User account.
osx - Setting environment variables in OS X? - Stack Overflow
© Amit Singh. All Rights Reserved. Written in Early 2003
/proc on Mac OS X
Quick use :
create /proc folder
Go in /profs-2.0 folder
Become root ==> sudo su
lauch procfs ==> ./procfs /proc
Enjoy it by Jun 9
Free procfs - Utilities Tools For Mac
procfs - MacFUSE-Based Process File System for Mac OS X procfs is a free MacFUSE-Based Process File System for Mac OS X. The process file system ("procfs" for brevity, or simply "/proc", because that's where it is usually mounted) has become a common entity on Unix-like systems. For example, Solaris, Linux, and the various modern BSDs all have procfs. In general, procfs uses the file metaphor to provide both a view of currently running processes and perhaps an interface to control them. Mac OS X does not provide a process file system.
Making procfs Cooler
I earlier wrote and released as open source a MacFUSE-based process file system (procfs) for Mac OS X. This document describes some new features I added to procfs soon after its first release. The source code for all features discussed here is available. Process Names
Index of /FreeBSD-srctree/newsrc/miscfs/procfs
Parent Directory 14-Feb-2002 09:39 - procfs.h.html 14-Feb-2002 09:43 8k procfs_ctl.c.html 14-Feb-2002 09:43 9k procfs_dbregs.c.html 14-Feb-2002 09:43 4k procfs_fpregs.c.html 14-Feb-2002 09:43 4k procfs_map.c.html 14-Feb-2002 09:43 6k procfs_mem.c.html 14-Feb-2002 09:43 8k procfs_note.c.html 14-Feb-2002 09:43 3k procfs_regs.c.html 14-Feb-2002 09:43 4k procfs_rlimit.c.html 14-Feb-2002 09:43 4k procfs_status.c.html 14-Feb-2002 09:43 8k procfs_subr.c.html 14-Feb-2002 09:43 11k procfs_type.c.html 14-Feb-2002 09:43 4k procfs_vfsops.c.html 14-Feb-2002 09:43 6k procfs_vnops.c.html 14-Feb-2002 09:43 27k
macfuse - The Easiest and Fastest Way to Create File Systems for Mac OS X - Google Project Hosting
Please Note: This project is no longer being maintained. We cannot currently help with any lion (or any large feline) related bugs or issues. The MacFuse google group is a decent resource for finding forks/replacement projects.
Last week, we ran this hint about using MacFUSE to install sshfs , which lets you mount ssh-connected servers like regular folders in the Finder. I tried it last weekend, and while I was generally thrilled with it (it's amazingly handy being able to work in remote folders as if they're local), I had some issues. In particular, it seems not to interact well with Path Finder (sshfs connections don't show as mounted volumes, for instance, unless they're in /Volumes, but they will do so in the Finder). I also had two kernel panics when I tried to unmount a mounted file system, so I decided to remove MacFUSE for now. Unfortunately, there's no uninstaller included with the disk image distribution. After some rooting around on the MacFUSE site, I found these removal instructions on the Issues tab.
How to uninstall MacFUSE - Mac OS X Hints
Mac OS X is a descendant of both unix and previous Mac OS traditions, and has inherited different - and sometimes conflicting - ways of looking at things from both sides. One of these is the way the locations of files are described, generally referred to as file paths (i.e. the path to take to get to the file). The biggest difference is in how the two traditions think about volumes (i.e. disks, partitions, server volumes, etc). In the Mac OS tradition, each volume is thought of as an independent entity; it shows up on the desktop as a separate icon, which contains everything on that volume. The only exception to this is files on the desktop; each volume can have its own desktop, and what you see on your screen is actually all of the volumes' desktops merged together.