Announcement

Collapse

Maintenance

The forum could be offline for 30-60 minutes in the very near future for maintenance (said 3pm Pacific). I was behind on getting this notice. I do apologize.
See more
See less

rc errors?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • rc errors?

    can someone please explain this?

    #INCLUDE "resource.h" : when I type this in the resource compiler fails.
    #include "resource.h" : when I type this in it works fine.

    What I mean by "fails" is, when I run rc it reports back with the
    following error.

    fatal error RC1021: invalid preprocessor command 'INCLUDE'

    I am using PBDLL v6.0
    Cheers!



    [This message has been edited by mark smit (edited January 12, 2000).]

  • #2
    Rc.exe seems to be case sensitive - therefore you have to type include
    with small letters, otherwise it won't understand what you mean.

    A big problem, as I see it, is that if you have "Key words - Upper case"
    activated in the PB/DLL 6.0 editor and open up an RC file, it automatically
    converts 'include' to 'INCLUDE', which then of course causes this error when
    you try to create the .RES file.

    I now use another editor for .RC files to avoid this problem. Hopefully,
    the next version of the PB editor will sense what kind of file it is and
    exclude .RC files from this automatic conversion..

    Comment


    • #3
      As Borje says, RC.EXE is case sensitive.

      Of course, the IDE can have keyword capitalization switched off... check out the OPTIONS dialog box in the IDE. The IDE is likely to have this handled automatically (when an RC file opened) in a future edition.

      If you are using PowerGEN, please review the errata in the FAQ forum which corrects this exact error that was made in the PowerGEN help file.


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

      Comment


      • #4
        Thanks guys,

        I kinda figured it was a case sensitive issue.

        Cheers!

        Comment

        Working...
        X