Rc compiler

I would like to thank every one. I got it to work just right.
I got the errors in ms-dos and found that the rc compiler
couldn't find the included file. Thanks

[Troy King]

Originally posted by Curtis De Vries:
How do you use the rc.exe compiler in the ms-dos prompt?
I don't know much about using the dos prompt and I can't
find any help in any of my help files. Thanks Curtis

Basic steps:
1. Run the DOS command shell (Usually Start Menu->Programs->MS-DOS prompt)
2. Change to the drive the resource scrip tis on by typing drive letter:. For example, if the file was on your d: drive, type "D:" (without the quotes) and that will change you to the drive.
3. Change to the directory ("folder") the resource script is in. If it was D:\Docs\Myprogram in explorer, at the DOS prompt, do this: "cd \Docs\Myprogram" (without the quotes).
4. Run the resource compiler: "rc myfile" (without the quotes)
5. Use PBRES to convert the resource to the PB-compatible format: "pbres myfile" (without the quotes)

These steps assume that rc.exe and pbres.exe are in your system search path; if they're not you'll have to prefix the commands with the drive letter and path of the commands. Example:
"C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin\RC.EXE" myfile
and
"C:\PBDLL60\BIN\PBRES.EXE" myfile

In the case of the first command there, because the folder names have spaces in them, you must enclose the drive, path, and filename in quotes (unless you're using Windows NT), but not the argument to the commands. This is correct:
"C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin\RC.EXE" myfile
but this is not:
"C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin\RC.EXE myfile"

In the case of:
"C:\PBDLL60\BIN\PBRES.EXE" myfile
the quotes aren't really necessary because none of the directories have spaces in their name.

I hope this helps get you started.

Oh, to close the DOS window, type "exit" (minus the quotes)
------------------
Troy King
[email protected]

[This message has been edited by Troy King (edited June 13, 2000).]

[Semen Matusovski]

Curtis --
If you have enough experience of work in MS-DOS prompt, you can simply select in PB DLL menu File - DOS prompt.
If not, there is a lot of file managers similar well-known Norton Commander.
I recommend to download shareware ($25)
ftp://ftp.netlab.sk/public/rarsoft/far/Far163.exe
It works in text-mode and much comfortable than Windows Explorer (at least, for me).
One tip: after starting a program, switch panels off/on by Ctrl-O to view results.

------------------

How do you use the rc.exe compiler in the ms-dos prompt?
I don't know much about using the dos prompt and I can't
find any help in any of my help files. Thanks Curtis

[Lance Edmonds]

Additionally, post the error message that RC.EXE is giving you... the more info we have the better the answer we can give you.


------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

[Troy King]

Make sure besides Semen's suggestion that you're matching the #define with the implementation. If you call it VOS_WINDOWS32 in the #define, make sure you call it VOS_WINDOWS32 in the implementation.

------------------
Troy King
[email protected]

[Semen Matusovski]

It's important lower/upper case.
For example, on my PC I was able to compile following text

program icon far.ico
#include "c:\pbdll60\winapi\resource.h"
VS_VERSION_INFO Versioninfo
fileversion 1,0,0,0
productversion 1,0,0,0
fileos VOS_WINDOWS32
filetype VFT_APP
begin
block "Stringfileinfo"
begin
block "040904E4"
begin
value "Comments", "*******"
value "CompanyName", "******"
value "FileDescription", "*******"
value "FileVersion", "******"
value "InternalName", "******"
value "LegalCopyright", "******"
value "LegalTrakemarks", "******"
value "OriginalFilename", "******"
value "ProductName", "******"
END
END
END

To see RC's messages, it's necessary to start rc in console(DOS-prompt) window.

------------------

I tried putting include and added another underscores but it
still doesn't work. Do I nead to add somthing? What am I
missing. That was the entire code for the rc file. Thanks

[Troy King]

Curtis, it's choking on the VOS_WINDOWS32, which interestingly enough is noted as VOS__WINDOWS32 (note the two underscores) in MSDN. I tried that route too. Anyway, add

#include "resource.h"

to the top of the file and it will work just fine. Alternatively, you can add

#define VOS_WINDOWS32                   0x00000004L

to the file before the resource info and that should do it too.

Good luck.

------------------
Troy King
[email protected]

I am not having a good time with rc files. Does anyone
know what is wrong with this rc code. The Rc program
window shows up and quits but no Res file is made.

#INCLUDE "resource.h"
program icon ***.ico
VS_VERSION_INFO Versioninfo
fileversion 1,0,0,0
productversion 1,0,0,0
fileos vos__windows32
filetype vft_app
begin
block "Stringfileinfo"
begin
block "040904E4"
begin
value "Comments", "*******"
value "CompanyName", "******"
value "FileDescription", "*******"
value "FileVersion", "******"
value "InternalName", "******"
value "LegalCopyright", "******"
value "LegalTrakemarks", "******"
value "OriginalFilename", "******"
value "ProductName", "******"
END
END
END

Do I have to put the include "resorce.h" in the code?
Thanks


[This message has been edited by Curtis De Vries (edited June 12, 2000).]