• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 21 subscribers
  • Views 975 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RTX51-TINY application link process wants RTX51.LIB!

Bahri Okuroglu

Hi all,

I'm using RTX51-TINY in my application. I included rtx51tny.h in the files, and tried to link them with BL51 as follows:

bl51 module1.obj, module2.obj, module3.obj rtx51tiny

However, the linker complains about the rtx51.lib file:

MS-DOS BL51 BANKED LINKER/LOCATER V2.01
COPYRIGHT KEIL ELEKTRONIK GmbH 1987 - 1991

*** FATAL ERROR 210: I/O ERROR ON INPUT FILE:
EXCEPTION 0021H: PATH OR FILE NOT FOUND
FILE: C:\C51PROGR\LIB\RTX51.LIB

Can anyone tell me what I'm missing?

thanks for reading...

Parents
  • 0

    Shouldn't that be:

    bl51 module1.obj, module2.obj, module3.obj, rtx51tiny.lib
    Without the .lib, you haven't given the linker a valid library filename, so it'll go for its default - which is, presumably, C:\C51PROGR\LIB\RTX51.LIB

    And a comma between your last .obj and the .lib - as these all constitute the "input list"


Reply
  • 0

    Shouldn't that be:

    bl51 module1.obj, module2.obj, module3.obj, rtx51tiny.lib
    Without the .lib, you haven't given the linker a valid library filename, so it'll go for its default - which is, presumably, C:\C51PROGR\LIB\RTX51.LIB

    And a comma between your last .obj and the .lib - as these all constitute the "input list"


Children
  • 0 in reply to Andrew Neil

    Dear Neil,

    Thanks for the reply, but the documentation gaved me that syntax. It says:

    *******************************
    Generation Example:
    C51 BEISPIEL.c
    BL51 BEISPIEL.OBJ RTX51TINY
    *******************************

    I had too many modules to link and was doing the compile+link process in a batch file. I think that BL51 parameter line was too long to evaluate.

    The problem disappered when I used the linker as follows (where FILELIST.L51 is a text file containing the parameters):

    BL51 @FILELIST.L51