Pingpong's Profile

sidegame · Last edited by sidegame on Sat Jul 28, 2007 2:50 pm; edited 1 time in total

Greetings,

Using the search feature on this forum didn't yeild any obvious answers, but I will happily stand corrected as a generally oblivious person.

Using the FMOD 4.06.22, a project group of which I am a part has had difficulty including the .dylib's into XCode.

They can be placed in the project fine, and the project builds fine, but upon attempting to run it, we get the following error:

dyld: Library not loaded: /usr/local/lib/*.dylib

Referenced from: /Users/...etc. etc... /<application executablename>

Reason: image not found

Where *.dylib is whichever of the dylibs it first decides to encounter.

Upon running 'otool -L' on the executable, we noticed that despite adding all the dylibs to the project, the references all pointed to /usr/local/lib/. Upon running 'otool -L' on any of the dylibs, we discovered that these were also all pointing to /usr/local/lib/.

There exists a somewhat useful tool to change the location of dylibs for binary files, but not that I can find for existing dylibs. As such our inconvenient 'work around' is to run a script at the end of every build that does the following on all the fmod dylibs:

install_name_tool -change /usr/local/lib/libfmodex.dylib @executable_path/../Frameworks/libfmodex.dylib <name of executable>

This is incredibly inconvenient, and at present I'm trying to find a better solution, ideally changing the dylibs own statically stored path to themselves to be something more useful (if that is in fact what is the root of the problem). I opened the XCode examples, to find they compiled and ran... from XCode. Trying to run example app outside of XCode resulted in the same error. I then attempted the Makefile also provided with all the examples, but only to be faced with the same problem. It is however from the makefile that I devised the temporary solution using install_name_tool script. It may be worth considering that the use of install_name_tool in the makefile didn't actually run, as for instance with the 'effects', it has the following line:

install_name_tool -change libfmodex.dylib @executable_path/libfmodex.dylib effects

But when doing an 'otool -L' on the executable 'effects' both before and afterwards I get the same output, ie:

/usr/local/lib/libfmodex.dylib (compatibility version 1.0.0, current version 1.0.0)

/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0)

/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.9)

Modifying the install_name_tool command to the following:

install_name_tool -change /usr/local/lib/libfmodex.dylib @executable_path/libfmodex.dylib effects

results in 'otool -L effects' updating to:

@executable_path/libfmodex.dylib (compatibility version 1.0.0, current version 1.0.0)

/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0)

/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.9)

Which I believe is the desired output.

I would easily believe this to be an OSX only problem, but nevertheless it has been causing me a rather big headache so far, and I'm open to any suggestion or assistance (not to mention a hint as to why XCode can build+run fine, but if you try and run the executable outside of XCode it fails with the same original error).

Note - This is on an intel OSX machine, running 10.4.10, and has only been tested (and confirmed to have the same issue) on other 10.4.10 machines (intel and PPC).

Also note - That copying all the dylibs to /usr/local/lib resolves the problem, but is not feasible as access to all our machines for work have different privelages (and thus some we cannot copy to /usr/local/lib), and a release would need to be self contained.

Apologies for the first post being a long one, but I'm trying to get as much info as I think might help lead to a solution of this problem.

sidegame · Posted: Fri Jul 27, 2007 4:03 pm Post subject:

Ok, after a bit more investigation, it appears the PPC version of the dylibs, when running otool -L on them returns:

libfmodex.dylib:

libfmodex.dylib (compatibility version 0.0.0, current version 0.0.0)

/System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio (compatibility version 1.0.0, current version 1.0.0)

/System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit (compatibility version 1.0.0, current version 1.0.0)

/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 128.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.

Whereas the Intel version, using the same command returns:

libfmodex.dylib:

/usr/local/lib/libfmodex.dylib (compatibility version 1.0.0, current version 1.0.0)

/System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit (compatibility version 1.0.0, current version 1.0.0)

/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 128.0.0)

/System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio (compatibility version 1.0.0, current version 1.0.0)

/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0)

/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.3)

Running 'otool -R' on the two returns the following:

(PPC)

libfmodex.dylib:

libfmodex.dylib

(Intel)

libfmodex.dylib:

/usr/local/lib/libfmodex.dylib

If someone can direct me to a method of changing the install paths of dylibs (as install_name_tool does not seem to change the install paths of dylibs, only executables as far as I can tell), I'd appreciate it. Also if this problem is not unique to myself, it may be worth considering this a potential fix for the next release.

sidegame · Posted: Fri Jul 27, 2007 4:33 pm Post subject:

Ok.

I just did the same otool -L on the development build (4.07.19) and got the following results:

(PPC)

libfmodex.dylib:

libfmodex.dylib (compatibility version 0.0.0, current version 0.0.0)

/System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio (compatibility version 1.0.0, current version 1.0.0)

/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 128.0.0)

/System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit (compatibility version 1.0.0, current version 1.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.

(Intel)

libfmodex.dylib:

/Users/Mathew/Desktop/sound/fmod4/mac/build/Release/libfmodex.dylib (compatibility version 1.0.0, current version 1.0.0)

/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 128.0.0)

/System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio (compatibility version 1.0.0, current version 1.0.0)

/System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit (compatibility version 1.0.0, current version 1.0.0)

/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0)

/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.3)

I would like to make a request that when Mathew (guessing that is OSX Intel developer for FMOD) has a few spare moments that he modify the install path of the library to be consistent with the PPC versions. I apologise if listing the paths above is an unintended invasion of privacy, but they are publically available, and should the problem be solved feel free to remove the reference to the absolute path on your system where FMOD is being built.

sidegame · Posted: Fri Jul 27, 2007 5:01 pm Post subject:

Sorry to keep replying rather than modifying the above post, however this is not an edit of what I said before but rather something new:

Running 'otool -L' on all the dylibs (w/ 'head -n 2' for each of them), has shown some interesting results (as shown below).

Could I make the request that possibly the OSX builds be available as universal binaries (quite easy using the lipo command), and then possibly put together in a Framework?

sidegame · Posted: Sat Jul 28, 2007 2:49 pm Post subject: SOLVED :)

Good news. It appears there is functionality of the install_name_tool that I missed earlier.

if I go:

install_name_tool -id @executable_path/../Frameworks/<dylibname>.dylib <dylibname>.dylib

Then it updates their own local references to themselves that is used when compiled into a .app. It is still an issue as to what the defaults should be (I imagine just 'itself', or something similar to the above, as copying the dylibs to the .app/Conents/Frameworks/ is quite simple, given that's where most of your headers and other frameworks go anyway.

Neverthless, hopefully this can act as a reference for anyone else who stumbles into the same trap.

brett · God Joined: 03 May 2001 Posts: 8072

Thanks for the research we'll look at putting this in our mac specific tutorial section of the docs.

_________________

Brett Paterson

Firelight Technologies

FMOD SoundSystem

ssexton · Posted: Tue Jul 31, 2007 8:37 am Post subject:

As a long-time Mac programmer (but new to FMOD), I have a few comments on this, which might be helpful to you:

1. afaik, install_name_tool is the correct way to take care of this issue. Its not a problem with XCode because XCode does it for you. Do "man install_name_tool" for details, but as you've discovered, its -change for updating dependencies (must be an exact match) and -id for the object itself.

2. If you're not careful about the order in which you do things, it is *quite* easy to create situations where you need to create a symbolic link named @executable_path in order to link successfully. This is because the loader (dyld) knows how to resolve @executable_path, but the linker (ld) does not!

3. TO THE FMOD DEVS: A related issue, is that if you don't create the binary correctly, install_name_tool can fail. If you aren't already, please use -headerpad_max_install_names when you link to avoid the problem. Otherwise, install_name_tool can fail, if the old name is too much shorter than the new name.

Best regards,

Steve

mathew · Posted: Tue Jul 31, 2007 5:50 pm Post subject:

Okay then, wow!

I have been busy working on cleaning up the MacOSX code recently and have not been monitoring the forum as closely as I would have liked to. It would seem you have done a very good job of detailing what I have been working on.

The issue with the install_name_tool stuff should be all resolved now. I have set up the dylibs so that they use a relative path. So fmodevent will assume fmodex is in the same directory. I have also updated the examples to use relative paths for the accessing the library, eg. ../api/lib/libfmodex.dylib.

Another thing that was mentioned here was the use of universal binaries, well that has been implemented as well. Since the majority of people would benefit from having the libraries as universal, the minority can now use lipo to thin them back out to individual archs if needed. Notes have been added to the mac specific section of the docs explaining this.

All of these changes have been made to the development version of FMOD only, and should appear in the next release. Please stay tuned for the release and let me know if there is anything else we can tweak.

_________________

Mathew Block

Firelight Technologies

FMOD SoundSystem

Well, after trying a lot, and searching the forums, I got it working. I'd like to note that the examples did compile for me (with xcode) but didn't run. The instructions in the sticky about xcode 1.5 arn't really up to date, so I thought I'd post how I did it.

In an open project:

Supported QuickTime Read in Formats
Type	Developer	Windows		Mac	Unix	Suffix(s)
Type	Developer	32-bit	16-bit	Mac	Unix	Suffix(s)
Still Image Formats
3D Meta File	Apple	3.0	N/A	2.5	N/A	N/A
FlashPix	Macromedia	4.0		4.0	N/A	fpx,fpix
Graphics Interchange Format	Compuserve	3.0		2.5	XAnim	gif
JPEG File Interchange Format	C-Cube Microsystems/ Joint Photographic Experts Group				XAnim	jfif,jpg,jpeg,jpe
MacPaint	Apple/Claris				N/A	pntg,pnt,mac
Photoshop	Adobe					psd
Portable Network Graphics	W3 Consortium			3.0		png
QuickDraw Picture	Apple			All		pict,pic,pct
QuickTime Image Format	Apple			2.5		qti
Silicon Graphics Image	Silicon Graphics			2.5		sgi,rgb
Targa	TrueVision			3.0		targa,tga
Tagged Image File Format	Aldus/Adobe					tiff,tif
Windows BitMaP	Microsoft	Internal	Internal			bmp
Audio Formats
Audio Interchange File Format	Apple	All	All	All	Unknown	aif,aiff,aifc
Global System for Mobile Audio	ETSI	5.0	N/A	5.0	XAnim	gsm,gsd
MPEG-1 Audio/ ISO/IEC 11172-3 (Layers I/II)	Motion Picture Experts Group	5.0	N/A	2.0PPC	N/A	m1a,mpa,mp2, mpeg,mpg,mpm
MPEG-2 Audio/ ISO/IEC 13818-3 (Layers I/II)		Add-on		Add-on		m2a,mpa,mp2, mpeg,mpg,mpm
MPEG Audio (with ID3 for Layer III)		4.0		4.0PPC		mp3,mpeg,mpg
Musical Instrument Digitial Interface	Roland/Yamaha	3.0	2.0	2.0		midi,mid,rmi,smf,kar
QuickTime Audio	Apple	All	All	All	XAnim	mov,qt
QualCommPurevoice	Qualcomm	3.0	N/A	3.0	N/A	qcp
RIFF Waveform	Microsoft	Internal	Internal	2.0	XAnim	wav
Sound Designer 2	Digidesign	3.0	N/A	3.0	N/A	sd2
ULAW	Sun/NeXT	3.0	2.0	2.0	XAnim	au,snd,ulw
Video Formats
Animated Graphics Interchange Format	Compuserve	3.0	N/A	3.0	XAnim	gif
AutoDesk Animator	AutoDesk				XAnim	flc,fli
DigitalVideo Stream	Digital VCR Conference				N/A	dv,dif
Shockwave Flash 3	Macromedia	4.0		4.0		swf
Shockwave Flash 4		5.0		5.0
Shockwave Flash 5		6.0		6.0
MPEG-1 System/ ISO/IEC 11172-1	Motion Picture Experts Group	5.0		2.0PPC		mpeg,mpg,dat,m1s, mpgx,mpm,rtf
MPEG-2 System/ ISO/IEC 13818-1		Add-on		Add-on		mpeg,mpg,m2s
MPEG-4 System/ ISO/IEC 14496-1		6.0		6.0		m4s,mp4,mpg4
MPEG-1 Video/ ISO/IEC 11172-2		5.0		2.0PPC	XAnim	mpeg,mpg,mpv, m1v,m75,m15
MPEG-2 Video/ ISO/IEC 13818-2		Add-on		Add-on	N/A	mpeg,mpg,m2v
QuickDraw Picture Sequence	Apple	All	All	All	XAnim	pics
QuickTime Video	Apple	All	All	All	XAnim	mov,qt
RIFF Audio Video Interleave	Microsoft	Internal	Internal	3.0	XAnim	avi,vfw
Text Formats
Hyper Text Markup Lanuage Importer	W3 Consortium	4.0	N/A	4.0	N/A	(Import only)
QuickTime PreFlight Text Importer	Apple	5.0		5.0		(Import only)
Real Time Streaming Protocol		4.0		4.0		rtsp,rtp,mov
Session Description Protocol		4.0		4.0		sdp,mov
ShoutCast PlayLiSt	Nullsoft	5.0		5.0		pls
Synchronized Multimedia Integration Language	W3 Consortium	4.1		4.1PPC		smil,sml,smi,mov
Text Importer	Apple	3.0	2.0	1.5		txt,mov

Supported QuickTime Codecs
Type	QT type code	Windows		Mac	Unix	Purpose/Notes
Type	QT type code	32-bit	16-bit	Mac	Unix	Purpose/Notes
Audio Encoders/Decoders
Two's Complement - Big Endian PCM	'twos'	Internal	Internal	Internal	XAnim	8 & 16-bit 68k signed samples
Two's Complement - Little Endian PCM	'sowt'	Internal	Internal	Internal	XAnim	8 & 16-bit x86 signed samples
24-bit Integer PCM	'in24'	3.0	N/A	2.5	Unknown	Increasing samples beyond 16-bits
32-bit Floating Point PCM	'fl32'
32-bit Integer PCM	'in32'
64-bit Floating Point PCM	'fl64'
A-Law 2:1	'alaw'	Internal	Internal	3.0	XAnim	16 bit samples only
Apple GSM 10:1	'agsm'	4.0	N/A	4.0	XAnim	Decoder only
Digital Video audio	'dvca'	3.0		3.0	N/A	Decoder only
DVI IMA ADPCM 4:1	'dvi '	4.0		4.0		Streaming Decoder only
Linear Predictive Coding 23:1	'lpc '	3.0		3.0		Voice decoder only
Apple Interactive Multimedia Association 4:1	'ima4'	Internal	Internal	2.0	XAnim	16-bit samples only
MS IMA ADPCM 4:1	'ms$0002'			3.0		Microsoft's version of IMA for Waveform files
DVI IMA ADPCM 4:1	'ms$0011'			3.0		Intel's version of IMA for Waveform files
MPEG-4 Advanced Audio Coding/ ISO/IEC 14496-3 AAC	'mp4a'	6.0	N/A	6.0	N/A	Proprietary Replacement for MPEG layer III
MPEG Layer III Fixed Rate	'ms$0055'	Internal		4.0		Fraunhofer's low bps MPEG CBR layer III decoder
MPEG Layer III (with Xing VBR header)	'.mp3'	4.1		4.1		Fraunhofer's full VBR MPEG layer III decoder
Macintosh Audio Compression & Expansion 3:1	'MAC3'	All	All	Internal		8-bit samples only
Macintosh Audio Compression & Expansion 6:1	'MAC6'	All	All			8-bit samples only
Pulse Code Modulation 8-bit Offset Linear	'raw '	Internal	Internal		XAnim	8-bit unsigned samples
QDesign Music 1	'QDMC'	3.0	N/A	3.0	N/A	16-bit samples only
QDesign Music 2	'QDM2'	4.0		4.0
Qualcomm Purevoice(TM)	'Qclp'	3.0		3.0
(mu)-Law 2:1	'ulaw'	Internal	Internal	2.0	XAnim
Image or Key/Intra Frame Only Video Encoders/Decoders
Apple BMP/MS RLE (RGB)	'WRLE'	3.0	N/A	3.0	N/A	Used in Windows Bitmaps
Component Video (YUV)	'yuv2'		2.0	1.5	XAnim	Uses unsigned Y'CbCr 4:2:2 color space
Component Video - YUV	'yuv2'		2.0	1.5	XAnim	Uses unsigned Y'CbCr 4:2:2 color space
DV - NTSC (YUV)	'dvc '		N/A	3.0	N/A	Standard for DV/FireWire
DV - PAL (YUV)	'dvcp'			3.0		Standard for DV/FireWire
DV Pro - NTSC (YUV)	'dvpn'	4.0		4.0		Pro Standard for DV/FireWire
DV Pro - PAL (YUV)	'dvpp'	6.0		6.0		Pro Standard for DV/FireWire
Motion JPEG A (YUV)	'mjpa'	3.0		2.5	XAnim	Used for Video Capturing from M-JPEG cards
Motion JPEG B (YUV)	'mjpb'			2.5	N/A	Used for Video Capturing from M-JPEG cards
None/Plain RGB	'raw '		2.0	All	XAnim	Direct to video raw pixel map
Photo - JPEG/JFIF (YUV)	'jpeg'		2.0	1.5		Best for Still Images
Planar RGB/Photoshop	'8BPS'		N/A	2.5		Separates colors into channels
PNG/zlib (RGB)	'png '			3.0	N/A	Replacement for lossless GIF Images
TGA (RGB)	'tga '					Used for lossless Still Images
TIFF/PackBits (RGB)	'tiff'					Used for lossless Still Images
Key/Intra and Inter Frame Video Encoders/Decoders
Animation/RLE (RGB)	'rle '	3.0	2.0	1.5	XAnim	Designed for PC Graphics and Archiving
Cinepak/ Compact Video (YUV)	'cvid'					Designed for older PCs
Graphics (RGB)	'smc '					Designed for 8-bit/ 256 color PC Graphics
H.261 (YUV)	'h261'	4.0	N/A	4.0		ITU Standard for Video Conferencing
H.263 (YUV)	'h263'	3.0		3.0		ITU Standard for Video Conferencing
MPEG-4 Video/ ISO/IEC 14496-2 (YUV)	'mp4v'	6.0		6.0	N/A	ISO Standard for low bit rate video
Sorenson Video (YUV)	'SVQ1'	3.0	N/A	3.0		Designed for modern PCs
Sorenson Video 3 (YUV)	'SVQ3'	5.0	N/A	5.0		Designed for modern PCs
Video (YUV)	'rpza' road pizza	3.0	2.0	All	XAnim	Faster Compression than Cinepak

Introduction Legal Stuff: Copyright message SDL, C++ and QuickCG: Installing SDL and using QuickCG with your compiler, function reference QuickCG Examples: Examples of every function from QuickCG
Color and Image Arithmetic Light and Color: How humans see color, Color Model Conversions, and editing colors of images Image Arithmetic: Adding, Subtracting, ...
2D Drawing Painting: Painting with brushes of various colors, opacities and sizes Flood Fill: Filling areas with a new color Cohen Sutherland Clipping: Clipping 2D Lines
Fractals Recursion Trees: Make trees with fractals Sierpinski Fractals: Sierpinski Triangle and Sierpinski Carpet Julia and Mandelbrot Set: Those pretty fractals
Oldskool Effects Plasma: The plasma effect Fire Effect: The classic Tunnel Effect: It looks like a 3D tunnel
Raycasting Raycasting: Untextured and textured walls Raycasting II: Floor and Ceiling Raycasting III: Sprites
Filtering and FT Image Filtering: Blur, Find Edges, Emboss, ... Fourier Transform: Introduction to FT and frequency spectrum of signals an images, and using it on RGB color images
Texture Generation The XOR Texture: Not artistic, but handy Texture Generation using Random Noise: Turbulence, Clouds, Marble, Wood, ...

Pingpong Add pingpong as a contact

Pingpong's Profile

Pingpong's Groups

Related Tags

Pingpong's Recent Clips ( 269 )

Technical Note TN2062

Guide to Creating Kiosks on Mac OS X

[Feb 24 2003]

Introduction

Features of the SystemUIMode API

Available User Interface Modes

Available User Interface Options

Replacing the Finder

Enabling Open Firmware Password

Top 20 Commonly asked Kiosk questions

1) How do I disable Force Quit?

2) How do I disable/suppress the Dock?

3) How do I disable the Command-Tab or Command-Shift-Tab process switching keyboard equivalents?

4) How do I disable the Apple menu (or certain portions of it)?

5) How do I prevent my application from being Force Quit?

6) How do I disable single user mode (Command-S on boot)?

7) How do I disable the Eject Key?

8) How do I prevent users from booting off alternative media (bootable CDs, external hard drives, etc.)?

9) How do I prevent new media (CDs, DVDs, iPods, USB/Firewire hard drives, etc.) from becoming mounted?

10) How do I disable Command-Control-Power (force reboot)?

11) How do I make my application full screen so it takes over the screen?

12) How do I prevent users from clicking on the desktop to switch out of my application?

13) How do I disable Command-H (Hide) and Command-Q (Quit)?

14) How do I disable the window that pops up when Power key or the Control-Eject keyboard equivalent is pressed?

15) How do I disable Command-Option-Eject (sleep)?

16) How do I disable Command-Control-Option-Eject (normal shutdown)?

17) How do I disable Command-Control-Eject (normal reboot)?

18) How do I disable the screen capture keys: Command-Shift-3 and Command-Shift-4?

19) How do I disable the video brightness keys available on some keyboards?

20) How do I disable the sound volume keys available on some keyboards?

Summary

References

Downloadables

Sunday, February 12, 2006

Deploying App that use dylibs on Mac OS X

Supported Data Formats

Inside: QuickTime

Brief History

What's in QuickTime

QuickTime Hacks for the Mac OS

Lode's Computer Graphics Tutorial

Introduction

Color and Image Arithmetic

2D Drawing

Fractals

Oldskool Effects

Raycasting

Filtering and FT

Texture Generation