At 9:32 -0500 8/03/01, Kort, Eric wrote:
>
>
>
>a. Why can't you just cut and paste your existing source code into the perl
>scripts as inline'd C? You would still have two "versions" (one inline'd
>for Win32, one not for Mac) but the C source in the two versions would be
>identical. Or are you using Mac-specific code elements? In that case, you
>would have to recode anyway for the Windows API.
>
>Obviously, it's up to you. But for the moment I persist in my view that
>simply cutting and pasting your existing code Inline style will be a lot
>less of a headache than using SWIG or h2xs. But if you insist:
>
>b.
>perldoc h2xs
>perdoc perlapi
>perldoc perlxs
>perldoc perlxstut
>perldoc perlguts
>www.swig.org
>
>If neither a nor b are sufficient, please advise.
Some of these modules are automatically-generated C source code. Like 70000
lines of C !!!! I doubt I could seamlessly cut/paste that into an inline C
file...
But anyway, I could find a workaround.
The real problem is the fact that I need to link with an external library
(for which I don't have the source code). Of course, this library is
specific to Win32, and is different from the one I use on MacOS (even
though the API is the same).
Thanks for your help.
--------------------------------------------------------------
François LETELLIER - [EMAIL PROTECTED]
Directeur technique - CTO
ARKEM
20 bis, avenue des ARTS - 94100 Saint-Maur-des-Fossés - FRANCE
tel : + 33 (0)1 48 86 26 00 - fax : + 33 (0)1 48 86 57 00
http://www.arkem.com
