I DID read your post
Thanks :-) now I know -DWIN32 is important
C:\>bcc32 -tWD -DWIN32 -I"c:\perl\lib\CORE" -L"C:\borland\bcc55\lib"
lib\CORE\perl58.lib C:\borland\bcc55\lib\import32.lib C:\borland\bcc55
Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland
Warning W8070 perl_inc.c 14: Function should return a value in functio
Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland
But you didnt say anywhere in your post that this was a problem you just added it silently ;-)
# Essentially we pass all the same -D defines that perl was built with
# the include dir to find the perl headers and the perl56.lib binary w
# what where the real functions defined in the headers are found and w
# will be linking against........
And this is what I did. There is no -DWIN32 in:
perl -MExtUtils::Embed -e ccopts -e ldopts
Which is what everyone was saying Nalina
I personally dont think that it is possible for everyone to use cl.exe
ps Please stop down voting me now. I was only trying to help. There was no malice.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.