Re: [Mutsu-developers] Absird (long)

[Ben H. <bh...@al...>]

At 11:29 AM -0600 3/18/02, Laine Lee wrote:
>
>Here's the method that resulted in absird.c being compiled successfully when
>run from the terminal:
>
>Copy the malloc.h file that exists in
>System:Library:Frameworks:Kernel.framework:Versions:A:Headers:sys to
>/usr/includes, add the file libjpeg.62.0.0.dylib to /usr/lib and either
>rename it or make the symbolic link libjpeg.62.dylib, cd to where the
>absird.c source file exists and run this command in the Terminal: "cc
>-I/usr/include -L/usr/lib -ljpeg absird.c".


Juse change the "#include <malloc.h>" line in absird.c to #include 
<sys/malloc.h> and it will be found. That is a common problem when 
coming from other UNIXes i think.

No need to copy it from the kernel framework. (that's bad) Never 
touch anything in the Kernel framework unless yer writiing a kernel 
extension. :)

You want to use the "C++ Tool" project type for your absird tool. 
(command line app = tool). Just paste the stuff from absird.c into 
the main.c file, and add libjpeg.a to the project. Also, you might 
need to add a Header search path to find the libjpeg.h header, under 
Build Settings, Search Paths.

If you use libjpeg.a, not the libjpeg.dylib, you won't have to bother 
with including it in your project. The .a means it is a static 
library and the code gets included into the binary, instead of being 
loaded at runtime.

-Ben
-- 
http://homepage.mac.com/bhines/