Re: [Plib-users] Build error
Brought to you by:
sjbaker
From: mat t. p. <pr...@tt...> - 2003-05-09 21:11:22
|
John- Let me be the first to welcome to the painful world of plib and OSX. The good news is that I've done all the leg work to get this stuff to work usefully with ProjectBuilder. Here are the specifics: 1.) Sounds like you need to replace any files with a .m4 extension with the mac versions in /usr/share/autoconf/. Im pretty sure this is how you get the build script to operate correctly. 2.) once the stuff is built you'll have a second problem which is that gcc will not enjoy using the plib headers from /usr/include/plib/. For some crazy reason, gcc wont treat them as c++ files and will try to compile them as C which will miserably fail. I have two solutions for this: A.) add every plib header to your ProjectBuilder target (make sure they are located outside of /usr/include/ ) and compile away! B.) Compile a framework target for those headers and toss it into /System/Library/Frameworks and add it to the target. Ive compiled a framework for this stuff that handles all the header stuff but your products wont be cross platform <shrug>. I can make this public by early next week, or you can teach yourself how to make frameworks (which is pretty cool actually). 3.) For your targets, after you've dealt with the header fiasco, you'll need to add .a libs to the target also. Just go to "Add Frameworks...", type in /usr/include/plib/ as the path, and select the libs. Got all that? Its not as bad as it may sound, do it once and you'll be a pro. Email me with any questions you might have, Im happy to help. mat. On Friday, May 9, 2003, at 01:54 PM, John MacMullin wrote: > > Any suggestions to get the configure to run to completion? Again, > please understand that I am a complete novice with these things. Your > patience is greatly appreciated. > |