On Tue, Aug 30, 2011 at 8:57 AM, Rami Ojares / AMG <[email protected]>wrote:
> On 08/30/2011 03:39 PM, Rami Ojares / AMG wrote: > >> Q3: How do I use the --lzolibs option? >> It says that it is used only together with --compile option so - if I >> understand correctly - only when compiling lzo libraries, right? >> > The --lzolibs option was for a special case and should not normally be needed. If you have <include href="mylib.lzx"> in your app, the compiler will look for a .lzo with the same name and use it preferentially. The --lzolibs was to force linking with other libraries that were not explicitly <include>'ed in apps. > > --lzolibs help says that it takes comma separated list of external lzo > libraries. > > So are these absolute paths like > --lzolibs /a/b/c.lzo,/d/e/f.lzo > > Or relative paths like > --lzolibs c.lzo,f.lzo > I think they can be relative or absolute. I think they would be relative to the current working directory, similar to how lzc interprets filenames for .lzx files, but I'd need to look at the source to tell. > and if so then relative against what directory, LPS_HOME? > > - rami > -- Henry Minsky
