Thank you,
Sorry for posting two times, I didn't see that it works the first time.
dpb <none@non.net> wrote in message <ko0d0b$f2$1@speranza.aioe.org>...
> On 5/27/2013 12:52 PM, Nia wrote:
> > Thank you for replying. I will continue to dig into it...
>
> DO _NOT_ TOPPOST!!! PLEASE!!!! Will quit responding if don't...
>
> ...
>
> >> help mex
> mex Compile mex-function
>
> Usage:
> mex [options ...] file [files ...]
>
> Description:
> ...
> mex accepts any combinations of source files, object files, and
> library files as arguments.
>
> from the doc file it adds...
>
> filenames can be any combination of source
> files, Simulink S-function files, object files, and library files.
> Include both the file name and the file extension in filenames.
> A non-source-code filenames parameter is passed
> to the linker without being compiled.
>
> Looks like you just need to pass the library name as well as that of the
> c source file
>
> --
Sorry for posting two times, I didn't see that it works the first time.
dpb <none@non.net> wrote in message <ko0d0b$f2$1@speranza.aioe.org>...
> On 5/27/2013 12:52 PM, Nia wrote:
> > Thank you for replying. I will continue to dig into it...
>
> DO _NOT_ TOPPOST!!! PLEASE!!!! Will quit responding if don't...
>
> ...
>
> >> help mex
> mex Compile mex-function
>
> Usage:
> mex [options ...] file [files ...]
>
> Description:
> ...
> mex accepts any combinations of source files, object files, and
> library files as arguments.
>
> from the doc file it adds...
>
> filenames can be any combination of source
> files, Simulink S-function files, object files, and library files.
> Include both the file name and the file extension in filenames.
> A non-source-code filenames parameter is passed
> to the linker without being compiled.
>
> Looks like you just need to pass the library name as well as that of the
> c source file
>
> --