Return-Path: william@bourbon.usc.edu Delivery-Date: Mon Oct 6 21:43:49 2008 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75]) by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m974hntU031641 for ; Mon, 6 Oct 2008 21:43:49 -0700 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m974njhj001487 for ; Mon, 6 Oct 2008 21:49:45 -0700 Message-Id: <200810070449.m974njhj001487@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Linking iniparser Date: Mon, 06 Oct 2008 21:49:45 -0700 From: Bill Cheng SOmeone wrote: > I know we aren't supposed to ask about using the iniparser, but I can't even > get to that point, so this is really a more elementary "how to link stuff" > question. I compiled the library per the documentation, included > "iniparser.h" in my code, and added "-liniparser.a" to my compile line. If you have successfully created a "iniparser.a" file, instead of saying "-liniparser.a", you should just use "iniparser.a". You can use "-lXYZ" if you have a file named "libXYZ.a". > When > I attempt to compile, I get numerous errors anytime a function is used from > any of the header files (iniparser, dictionary, etc.), many of which say > "iniparser_xxx cannot be used as a function. I tried emulating your > instructions for linking openssl in CS531, but have still been unsuccessful. > Do you have any pointers for this? I've included this library in our spec because quite a few students have used it successfully before. I have never tried it myself because I would just write it from scratch myself using what's mentioned near the end of lecture 9. Sorry that I'm not very helpful here. -- Bill Cheng // bill.cheng@usc.edu