PBWin/PBCC Echo Server and Client combined (run twice)

[Jim Dunn]

Mike,

I noticed the following lines in your code from this post:

http://www.powerbasic.com/support/pb...ad.php?t=41648

The lines were:

%CCWIN = 1
#INCLUDE "win32api.inc"
'#INCLUDE "\pbwin90\winapi\WS2_32.INC"
#INCLUDE "\pbcc50\winapi\WS2_32.INC"

And it suddenly struck me... that maybe I'm the only one who copies PBWIN and PBCC into the same folder on my development machine?

I initially install PBWIN into C:\PBWIN90 and PBCC into C:\PBCC50, but then I do the following:

1) xcopy c:\pbwin90 c:\pb /d /e /c /y /h /i /r
2) xcopy c:\pbcc50 c:\pb /d /e /c /y /h /i /r
3) set path=%path%;c:\pb\bin

Then I run whichever compiler I need, using one source for WINAPI (the C:\PB\WINAPI folder).

So far this has worked, so I'm hoping the PowerBASIC think-tank will keep allowing this!!

<gulp>

[Michael Mattias]

that maybe I'm the only one who copies PBWIN and PBCC into the same folder on my development machine?

Well, no, I don't install the IDEs and compilers in the same folder, but you can change the IDE #INCLUDE paths for both to look for all your Windows' header files in ONE directory... in essence, ignoring the WInAPI folder installed and populated by the installer.

This gives you much better control over when those header files change. This is not a big deal any more, but for a couple of years WIN32API.INC was changing every couple of months, and the DWORD/LONG switchover combined with the change in signed/unsigned evaluation using IF or SELECT CASE would mean changing WIN32API.INC would break a working program.

I have a master folder I cleverly named "INCLUDE" and both IDEs are configured to look there.

D:\
    Software_Development 
          INCLUDE 
               WinAPI
               ODBC

MCM