Re: extra .c file in .xs module building

Does specifying the object file in 'OBJECT' have the desired effect ?

OBJECT => 'module_name.$(OBJ_EXT) extra.$(OBJ_EXT)',
[download]

Update: The 2 stops (.) are wrong and it's probably better expressed as:

OBJECT => '$(BASEEXT)$(OBJ_EXT) extra$(OBJ_EXT)',
[download]

I gather that if you specify one object file, then you need to specify *all* object files that are going to be built. (And I don't know whether that's all that's required to get it to work.)

Cheers,
Rob

Comment on Re: extra .c file in .xs module building Select or Download Code

Replies are listed 'Best First'.
Re^2: extra .c file in .xs module building by cmac (Monk) on Jan 18, 2009 at 06:46 UTC
That did the trick. Many thanks!! Now I don't seem to have "memclr" in my library paths. The "helper" program that's used in Makefile.PM outputs "-L/usr/local/lib" which goes into the LIBS array. Do you (or anyone) know if memclr is deprecated in favor of memset? With an eye toward CPAN, I wouldn't want to use a library function that people don't have in standard libraries... Many thanks, cmac www.animalhead.com	[reply]
Re^3: extra .c file in .xs module building by chromatic (Archbishop) on Jan 18, 2009 at 07:34 UTC
Do you (or anyone) know if memclr is deprecated in favor of memset? I don't have `memclr` available on my Ubuntu system, while `memset` is part of the C89 and C99 standards.	[reply] [d/l] [select]
Re^4: extra .c file in .xs module building by cmac (Monk) on Jan 19, 2009 at 03:06 UTC
Found a online dialog from some years ago where a smart young programmer told an old programmer like me "There is no memclr! Where did you hear of such an thing?". memclr was so long ago that it was limited to 256 bytes. Who would need to clear more memory than that? ;-)	[reply]