topic-36078

Posts: 4840

Joined: Fri Nov 18, 2005 04:52 PM

Windows.h not found errors
Posted: Mon Sep 10, 2018 05:39 AM

I am having trouble with "windows.h" not found errors. It happens both with the BCC7 compiler and also with my resource editor. The path to windows.h is set both in the computer's path, and in the BCC32.cfg file. The windows.h file is located in:

C:\BCC7\inclcude\windows\sdk\

I have confirmed that it is there.

Any ideas?

FWH 18.05/xHarbour 1.2.3/BCC7/Windows 10

Rick Lipkin

Posts: 2706

Joined: Fri Oct 07, 2005 01:50 PM

Re: Windows.h not found errors
Posted: Tue Sep 11, 2018 01:22 PM

James

Here is my Borland.cfg contents:

Code (fw): Select all Collapse

-I"C:\BORLAND\BCC73\include";"C:\BORLAND\BCC73\include\windows\crtl"
;"C:\BORLAND\BCC73\include\dinkumware";"C:\BORLAND\BCC73\include\windows\rtl"
;"C:\BORLAND\BCC73\include\windows\sdk";"C:\BORLAND\BCC73\include\windows\sdk\atl"
-L"C:\BORLAND\BCC73\lib";"C:\BORLAND\BCC73\lib\psdk"

I am using Resedit for my resource compiler and here are the config paths ..

Rick Lipkin

James Bott

Posts: 4840

Joined: Fri Nov 18, 2005 04:52 PM

Re: Windows.h not found errors
Posted: Tue Sep 11, 2018 02:34 PM

Rick,

Our bcc32.cfg files seem to be identical. My default windows path also contains the path to the windows.h file. So, I still don't know why the compiler is not finding it. I have taking to putting a copy of windows.h in the current directory when needed, but I really don't like doing this.

I also use RESEDIT and I didn't know it had it's own paths. I will add them and see if that fixes the issue for RESEDIT.

Thanks for the response.

FWH 18.05/xHarbour 1.2.3/BCC7/Windows 10

dtussman

Posts: 102

Joined: Sat Jun 06, 2015 06:57 PM

Re: Windows.h not found errors
Posted: Tue Sep 11, 2018 06:39 PM

You misspelled the word include in your original post but I don't know if that's the explanation

James Bott

Posts: 4840

Joined: Fri Nov 18, 2005 04:52 PM

Re: Windows.h not found errors
Posted: Tue Sep 11, 2018 08:43 PM

Hi David,

Yes, I was hoping nobody would notice. Old Eagle-Eye Tussman they used to call you.

Actually, I typed that in and thus the typo. I did double-check it in all my paths and none of them are misspelled.

I think the resource editor is working now that I have entered the paths in it's own configuration setup.

However the compiler is still complaining that it can't find various *.h files. I know there is some logic in there somewhere.

James

FWH 18.05/xHarbour 1.2.3/BCC7/Windows 10

FiveTech Support Forums

Continue the discussion