Re^4: shared-obj linking in xs-module

Thank you, for your suggestion. It functions very well, but the problem is that you have collected all obj-files in the sh-obj file. My posted code is just a short example, but in the real case I have many sh-obj files, and some of these could be proprietary one, in this case I have only sh-obj files.

What I can do, in this generic case?

Comment on Re^4: shared-obj linking in xs-module

Replies are listed 'Best First'.
Re^5: shared-obj linking in xs-module by rafl (Friar) on Mar 16, 2006 at 14:32 UTC
Exactly what I did in the code example I posted. Linking the generated shared object against the libraries. In that example that libraries are also external (not proprietary, though) and I don't have built them myself. I built my code with the headers that are provided with those libraries and then link against their shared objects, which are more than one as well. Cheers, Flo	[reply]
Re^6: shared-obj linking in xs-module by warlock (Initiate) on Mar 16, 2006 at 14:52 UTC
Ok Cheers, but how con you do if you have only shared-objects? In C it would not be a problem.	[reply]
Re^7: shared-obj linking in xs-module by rafl (Friar) on Mar 16, 2006 at 15:00 UTC
You mean only shared-objects without header files? It'll work the same way as in C, so as almost everything concerning XS works the sam way as in C as it actually only is preprocessed C code that links against a library called libperl, which is written in C as well. Flo	[reply]
Re^8: shared-obj linking in xs-module by warlock (Initiate) on Mar 16, 2006 at 15:03 UTC
Re^9: shared-obj linking in xs-module by rafl (Friar) on Mar 16, 2006 at 15:07 UTC
Some notes below your chosen depth have not been shown here