Re: AXMakeProcessTrusted conflicts with dylib load by install_name_tool

2011-10-28 Thread Bill Cheeseman
t;http://pfiddlesoft.com/eventtapstestbench>. If you want help figuring out why it isn't working for you, you will have to provide more information. For example, the full text of the error message might be informative. And a more complete explanation of how you are using it with install_nam

AXMakeProcessTrusted conflicts with dylib load by install_name_tool

2011-10-28 Thread Shaguo
Hi I made my app trusted by AXMakeProcessTrusted to listen to the keyboard. But it failed to launch the dylib when it was launched. Reason: unsafe use of xxx with restricted binary Anyone has ideas on it? It makes me crazy. -- Thanks & Best Regards! Email:rasha...@gmail.com Yahoo:rasha.

Re: install_name_tool

2008-06-20 Thread Martin
r your answers but it's still not working here. Plus I don't really see why I should use "-id" option since what I really want to do is *change* one of the paths. Straight from "man install_name_tool": -change old new Changes the dependent shar

Re: install_name_tool

2008-06-20 Thread Sherm Pendley
On Fri, Jun 20, 2008 at 3:12 AM, Martin <[EMAIL PROTECTED]> wrote: > > Thanks for your answers but it's still not working here. Plus I don't really > see why I should use "-id" option since what I really want to do is *change* > one of the paths.

Re: install_name_tool

2008-06-20 Thread Sherm Pendley
the first line has certainly >>> not >>> been replaced by "bla". What am I doing wrong? >> >> Shouldn't you be using the -id flag, not -change? > > I usually do both of them (for framework embedding). E.g to make a framework > embeddable

Re: install_name_tool

2008-06-20 Thread Jean-Daniel Dupas
You don't want to change the path, you want to change the id of your library. -change is intended to be used to change the path of a dependent library in an other binary. install_name_tool -id @executable_path../../Frameworks/Foo.framework/ Versions/A/Foo Foo.framework/Foo But as I

Re: install_name_tool

2008-06-20 Thread Martin
ework/Versions/A/Foo (compatibility version 1.0.0, current version 1.0.0) ... $ install_name_tool -change /Users/martin/Library/Frameworks/ Foo.framework/Versions/A/Foo @executable_path../../Frameworks/ Foo.framework/Versions/A/Foo Foo.framework/Foo $ otool -L Foo.framework/Foo /

Re: install_name_tool

2008-06-19 Thread Laurent Cerveau
-id flag, not -change? I usually do both of them (for framework embedding). E.g to make a framework embeddable install_name_tool -change /Library/Frameworks/$EXECUTABLE_PATH @executable_path/../Frameworks/$EXECUTABLE_PATH $EXECUTABLE_NAME install_name_tool -id @executab

Re: install_name_tool

2008-06-19 Thread Jean-Daniel Dupas
Le 19 juin 08 à 23:02, Kyle Sluder a écrit : On Thu, Jun 19, 2008 at 4:40 PM, Martin <[EMAIL PROTECTED]> wrote: And as you can see, nothing has changed and the first line has certainly not been replaced by "bla". What am I doing wrong? Shouldn't you be using the -id flag, not -change? --

Re: install_name_tool

2008-06-19 Thread Kyle Sluder
On Thu, Jun 19, 2008 at 4:40 PM, Martin <[EMAIL PROTECTED]> wrote: > And as you can see, nothing has changed and the first line has certainly not > been replaced by "bla". What am I doing wrong? Shouldn't you be using the -id flag, not -change? --Kyle Sluder __

install_name_tool

2008-06-19 Thread Martin
Hi, I can't figure out how install_name_tool works. I've tried it with the simplest project ever: 1. I've created a blank "Foo" framework in Xcode 2. I've built it with the "-headerpad_max_install_names" linker flag (as man install_name_tool says) 3.