Jan,
It is possible to link MS VC++ libraries if they are compiled using the C
compiler and not the C++ compiler. The problem though is the Perl headers.
There are #ifdefs for the MS VC++ compiler but not the IBM VAC++ compiler
and I am not sure what is the correct combination to get it to work with the
IBM VA C++ compiler.
IBM VA C++ v4 most definitely supports commandline compilation using vacbld!
v5 recently announced also supports batch compilation as well as incremental
compilation.
Anyone have any other tips?
Stephen Kurlow
GSTPay Pty Ltd
Level 14, 99 Walker Street
North Sydney NSW, Australia
Phone: +61-2-8912-2209 Mobile: +61-403-060718 Fax: +61-2-8912-2233
> -----Original Message-----
> From: Jan Dubois [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, 29 April 2000 6:04
> To: Steve Dalton
> Cc: Perl-Win32-Users Mailing List; Stephen Kurlow
> Subject: Re: Using Perl C library from IBM VisualAge
>
>
> On Fri, 28 Apr 2000 12:09:09 +1000, "Steve Dalton"
> <[EMAIL PROTECTED]> wrote:
>
> >I have been using ActiveState Perl (v5.6) from my C++ programs
> in MS Visual
> >Studio successfully for some time now. However, some of my collegues are
> >also using the IBM VisualAge compiler (v4) and the perl calling
> component of
> >the code has been #ifdef'd out until now.
> >
> >I am now trying to get the the code to compile under the
> VisualAge compiler
> >and am having all sorts of problems with the perl header files.
>
> Is there a reason not to link int the Perl library compiled with VC++?
> With ActivePerl 5.6 this shouldn't be such a problem anymore as it is now
> compiled with plain C again and not with C++ anymore.
>
> At my previous job I had to mix VC++ 5 with VisualAge C++ 3.5 code and it
> worked reasonably well (you needed wrappers to set up the floating point
> masks if you were dealing with NaNs etc).
>
> >Firstly, I am getting a problem with threads with the following
> message from
> >perl.h:
> >
> >"The text "perl_os_thread" is unexpected. "pthread_t" may be
> undeclared or
> >ambiguous."
> >
> >I tracked this down to the fact that WIN32 is not defined in
> VisualAge and
> >so win32thread.h was not being included. On defining WIN32
> however I am now
> >seeing a problem with the read macro in istream(probably brought about by
> >defining WIN32 when I really shouldn't have!).
> >
> >Has anyone had any success with using the perl library with VisualAge? Is
> >there a proper way to do this???
>
> I tried this once a long time ago and it didn't seem trivial. I've never
> used version 4 at all but I heard that it doesn't even support commandline
> compilation anymore; everything needs to be imported into some code
> repository and be compiled by the IDE. This would be a real showstopper
> for the Perl build process.
>
> Sorry for not having more helpful information!
>
> -Jan
>
>
---
You are currently subscribed to perl-win32-users as: [[email protected]]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
