lists@lowfrequency.or

I'd like to use some external video libraries in a jitter external. I'm not sure how to go bout packaging them inside the mxo object - are there any examples of this out there?

On a side note, I'd be very interested in speaking with a jitter externals developer who can work on a jit.qt.movie-like external for OS X jitter. There is money involved.

I'd like to use some external video libraries in a jitter external.  I'm not sure how to go bout packaging them inside the mxo object - are there any examples of this out there?

On a side note, I'd be very interested in speaking with a jitter externals developer who can work on a jit.qt.movie-like external for OS X jitter.  There is money involved.

external-libraries

there's a couple of options (referring to os x, windows is a bit different)

the non-mac way is to write a script that installs the necessary libraries in either /usr/local/lib (for static libs (.a) or dynamic libs (.dylib) or in /Library/Frameworks for frameworks.

the mac way is to install the libs in your_external.mxo/contents/Frameworks

the strange max-msp way might be to write a script to install the libs in MaxMsp.app/contents/Frameworks/ and max runtime/contents/frameworks/

the last one's a little weird and i would much prefer the second (mac way), but for a plugin (essentially what externals are) to load a framework requires some unorthodox methods.

see the following link for a more detailed explanation and possible solution:

http://www.far-blue.co.uk/hacks/plugin-frameworks.html

please let us know if you make any progress with this (i'll do the same).

i'm trying to figure this out as well.
there's a couple of options (referring to os x, windows is a bit different)

see the following link for a more detailed explanation and possible solution:
http://www.far-blue.co.uk/hacks/plugin-frameworks.html

Personally, I would put it in /Libary/Frameworks on OSX, especially if

it's a library you haven't modified and are just linking against. On

windows, things can go in Max/support folder if it's a dll. I would

only put highly specific and modified libraries within an external

itself. You can use otool on OSX to modifiy things about the library

> there's a couple of options (referring to os x, windows is a bit different)

> the non-mac way is to write a script that installs the necessary libraries in either /usr/local/lib (for static libs (.a) or dynamic libs (.dylib) or in /Library/Frameworks for frameworks.

> the mac way is to install the libs in your_external.mxo/contents/Frameworks

> the strange max-msp way might be to write a script to install the libs in MaxMsp.app/contents/Frameworks/ and max runtime/contents/frameworks/

> the last one's a little weird and i would much prefer the second (mac way), but for a plugin (essentially what externals are) to load a framework requires some unorthodox methods.

> see the following link for a more detailed explanation and possible solution:

> please let us know if you make any progress with this (i'll do the same).

Personally, I would put it in /Libary/Frameworks on OSX, especially if
it's a library you haven't modified and are just linking against.  On
windows, things can go in Max/support folder if it's a dll.  I would
only put highly specific and modified libraries within an external
itself.  You can use otool on OSX to modifiy things about the library
like loadpath etc.

On 10/13/07, Robert Ramirez  wrote:
>
> i'm trying to figure this out as well.
> there's a couple of options (referring to os x, windows is a bit different)
>
> the non-mac way is to write a script that installs the necessary libraries in either /usr/local/lib (for static libs (.a) or dynamic libs (.dylib) or in /Library/Frameworks for frameworks.
>
> the mac way is to install the libs in your_external.mxo/contents/Frameworks
>
> the strange max-msp way might be to write a script to install the libs in MaxMsp.app/contents/Frameworks/ and max runtime/contents/frameworks/
>
> the last one's a little weird and i would much prefer the second (mac way), but for a plugin (essentially what externals are) to load a framework requires some unorthodox methods.
>
> see the following link for a more detailed explanation and possible solution:
> http://www.far-blue.co.uk/hacks/plugin-frameworks.html
>
> please let us know if you make any progress with this (i'll do the same).
>
> -rob
>


looks like otool is just used to get information about a library, not change that information. am i missing something? did you mean install_name_tool?

looks like otool is just used to get information about a library, not change that information.  am i missing something?  did you mean install_name_tool?


actually, yes I meant install_name_tool. Here's an example from Qt.

@executable_path/../Frameworks/libqt.3.dylib 

actually, yes I meant install_name_tool.  Here's an example from Qt.

install_name_tool 
        -change libqt.3.dylib 
        @executable_path/../Frameworks/libqt.3.dylib 
        demo.app/Contents/MacOS/demo

external libraries?