• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 21 subscribers
  • Views 1604 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

Create library with batch-file

Oliver Enns

Dear experts!

I'm trying to create a simple batch-file, that generates a library:

SET lib_debug=debug_lib.lib
IF NOT EXIST %lib_debug% GOTO create_lib
DEL %lib_debug%
:create_lib
lib51 create %lib_debug%
FOR %%i IN (..\obj_dbg\*.obj) DO (
lib51 add %%i to %lib_debug%)

So the lib is going to be created (fine so far).
But the lib is almost empty (<1KB). I've about 120 object-files with a total size of 8,8MB.
Why the obj want not to be added? Do I have to take notice on the order of adding obj-files to the lib?

Thanks in advance!

Kind regards,
Oliver

Parents
  • 0 in reply to Oliver Enns

    I should read the manual more carefully,

    Well, in your defence some of the blame lies at the feet of the LIBx51 tools, for producing no diagnostic output whatsoever.

    Don't get me wrong: I'm completely in favor of tools producing no screen output at all if things went fine. I like a nice, blank window as the "all OK" indication --- it makes eventual error message stand out all the better. But since LIBx51 isn't completely quiet anyway (the banner always appears), it might as well report success while at it.

    But that set aside, if a tool decides to refuse the job given to it (like LIB51 does if you give it OMF2 files to add), it absolutely has to report that problem. Silent failure like that is an inexcusable omission.

Reply
  • 0 in reply to Oliver Enns

    I should read the manual more carefully,

    Well, in your defence some of the blame lies at the feet of the LIBx51 tools, for producing no diagnostic output whatsoever.

    Don't get me wrong: I'm completely in favor of tools producing no screen output at all if things went fine. I like a nice, blank window as the "all OK" indication --- it makes eventual error message stand out all the better. But since LIBx51 isn't completely quiet anyway (the banner always appears), it might as well report success while at it.

    But that set aside, if a tool decides to refuse the job given to it (like LIB51 does if you give it OMF2 files to add), it absolutely has to report that problem. Silent failure like that is an inexcusable omission.

Children