Actually my suggestion to use cl.exe is possibly valid, but simply based on the fact that IMHO it works better so I use it. With cl.exe come the header and library files you need to link apps under windows. These are of course the M$ versions. When you get BCC you get Borlands take on these files, which IME have issues. Windows has issues period, but you get less using the M$ native compiler, headers and libs.
*However* if you had read my post properly you would have noted that the minimum flags case includes -DWIN32 which you fail to do......if I leave it out it chokes as we will be trying to compile non win32 code (well skipping the kludges - or whatever). The errors are slightly different but I suggest it might work if you add that define.
C:\>cl.exe -DWIN32 -I"D:\Perl\lib\CORE" D:\Perl\lib\CORE\perl56.lib -o
+ interp.exe interp.c
Microsoft (R) 32-bit C/C++ Standard Compiler Version 13.00.9466 for 80
+x86
Copyright (C) Microsoft Corporation 1984-2001. All rights reserved.
interp.c
Microsoft (R) Incremental Linker Version 7.00.9466
Copyright (C) Microsoft Corporation. All rights reserved.
/out:interp.exe
/out:interp.exe
D:\Perl\lib\CORE\perl56.lib
interp.obj
# all is well but without the define......
C:\>cl.exe -I"D:\Perl\lib\CORE" D:\Perl\lib\CORE\perl56.lib -o interp.
+exe interp.c
Microsoft (R) 32-bit C/C++ Standard Compiler Version 13.00.9466 for 80
+x86
Copyright (C) Microsoft Corporation 1984-2001. All rights reserved.
interp.c
D:\Perl\lib\CORE\perl.h(803) : warning C4273: 'win32_strerror' : incon
+sistent dll linkage
d:\Perl\lib\CORE\dosish.h(111) : warning C4005: 'Stat' : macro redefin
+ition
d:\Perl\lib\CORE\win32.h(306) : see previous definition of 'St
+at'
D:\Perl\lib\CORE\perl.h(1754) : error C2061: syntax error : identifier
+ 'perl_os_thread'
D:\Perl\lib\CORE\perl.h(1754) : error C2059: syntax error : ';'
D:\Perl\lib\CORE\perl.h(1755) : error C2061: syntax error : identifier
+ 'perl_mutex'
D:\Perl\lib\CORE\perl.h(1755) : error C2059: syntax error : ';'
D:\Perl\lib\CORE\perl.h(1756) : error C2061: syntax error : identifier
+ 'perl_cond'
D:\Perl\lib\CORE\perl.h(1756) : error C2059: syntax error : ';'
D:\Perl\lib\CORE\perl.h(1757) : error C2061: syntax error : identifier
+ 'perl_key'
D:\Perl\lib\CORE\perl.h(1757) : error C2059: syntax error : ';'
d:\Perl\lib\CORE\perl.h(2245) : warning C4273: 'win32_crypt' : inconsi
+stent dll linkage
d:\Perl\lib\CORE\perl.h(2355) : warning C4273: 'win32_environ' : incon
+sistent dll linkage
d:\Perl\lib\CORE\perlvars.h(22) : error C2061: syntax error : identifi
+er 'PL_thr_key'
d:\Perl\lib\CORE\perlvars.h(22) : error C2059: syntax error : ';'
d:\Perl\lib\CORE\perlvars.h(39) : error C2061: syntax error : identifi
+er 'PL_op_mutex'
d:\Perl\lib\CORE\perlvars.h(39) : error C2059: syntax error : ';'
C:\>
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|