use Inline C => Config => LIBS => '-lparser';
[download]

use Inline C => Config => LIBS => '-lfoo';
[download]

use Inline C => Config => LIBS => '-L/path/to/lib -lfoo';
[download]

use Inline C => Config =>
    BUILD_NOISY => 1,
    LIBS => '-L/path/to/lib -lfoo';
[download]

use Inline C => <<END_C;
#include <stdio.h>
#include <stdlib.h>
#include <string.h>

// Wild guess follows:
int parser (char * url, char * page, char * pool, int lenx2) {
       // C code that does whatever
       // it is that parser()does.
}

char* MyParser(char *url, char* page)
{
        char *pool;
        int len;
        int ret;

        len = strlen(page);

//      page = (char*)malloc(len);

        pool = (char*)malloc(2*len+1);

        // parsing page
        ret = parser(url, page, pool, 2*len+1);


        if(ret > 0)
                return pool;
        free(pool);
}

END_C
[download]

and of course i supplied MyParser with 2 arguments :)

I have noticed that some quoted strings in my code "\r\n" are being translated to (to a return and newline) in the corresponding XS file. this is whats creating some errors- now i have some mis-formed lines! is there a way to avoid ths?

downer: 

I have noticed that some quoted strings in my code "\r\n" are being translated to (to a return and newline) in the corresponding XS file.

When I write Inline-C stuff, I have to add an extra escape to the backslashes:

 ...
 char string [] = "Hello World\\n";
 ...
[download]

Regards

mwa

now i have some mis-formed lines

I have not struck this problem before (though it seems mwah has). Do you mean that the following simple Inline::C function leads to a corrupted XS file:

void greet() {
     printf("Hello World\n");
}
[download]

If not, then can you provide a *small* complete script that demonstrates the issue.

Cheers,
Rob
Update:I hadn't noticed the OP's usage of <<END_C and wasn't aware of the gotcha (explained below by tye) associated with that usage.

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?

... 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

The '-lparser.c' is probably incorrect, as parser.c is likely a source file (i.e., not yet compiled), and the -l switch is used to indicate a library (i.e., compiled code).

...roboticus