Re^4: Help with Inline C

that seems to help. now I am just having compilation errors, a step in the right direction. I am a C newbie, so the mechanics of why everything is so is at this point beyond me.

couldnt I also do something like gcc -c parser.c mycode.c then use Inline C => Config => LIBS => '-lparser.o';
is this totally different than what is required?

Comment on Re^4: Help with Inline C Select or Download Code

Replies are listed 'Best First'.
Re^5: Help with Inline C by syphilis (Archbishop) on Oct 15, 2007 at 22:54 UTC
... then `use Inline C => Config => LIBS => '-lparser.o';` I don't think that would work - but the following config option does: `use Config; use Inline C => Config => LDDLFLAGS => $Config::Config{lddlflags} . ' /full/path/to/parser.o';` [download] Alternatively, once you've got 'parser.o', you could just go that one extra step and create 'libparser.a' with: `ar cru libparser.a parser.o` [download] Then `LIBS => '-L/full/path/to/lib -lparser'` should also work fine. Cheers, Rob	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: Help with Inline C
by syphilis (Archbishop) on Oct 15, 2007 at 22:54 UTC

... then use Inline C => Config => LIBS => '-lparser.o';

use Config;
use Inline C => Config =>
 LDDLFLAGS => $Config::Config{lddlflags} . ' /full/path/to/parser.o';
[download]

ar cru libparser.a parser.o
[download]

LIBS => '-L/full/path/to/lib -lparser'

[reply]
[d/l]
[select]