After the copying of the system files is finished, the lcc setup program will call the ‘dolibs.exe’ utility to build all the import libraries from their ASCII descriptions. This saves download time, since the megabytes of import libraries are not transmitted but generated at your machine.
Sometimes for various reasons[1],
the dolibs.exe utility does not work properly. In this case you can do the work
manually. Do the following:
cd \lcc\buildlib
this supposes
you installed in \lcc
make start building the libraries
copy *.lib \lcc\lib copy libraries to \lcc\lib directory
del *.lib erase all libs from the buildlib directory
The buildlib utility is called with each ASCII description of the import library, building the import lib. The newly created libraries should be moved to \lcc\lib so that the linker finds them when it needs them.
The registry keys that lcc-win32 uses are stored under the key HKEY_CURRENT_USER, i.e.; if you log in under another user ID after installing lcc-win32, you will be forced to install it again. If you install under the same directory, everything will work properly.
The lcc-win32 system assumes the software is under a directory called ‘lcc’. Please do not change this name.
Another possible problem are paths with spaces in them, for instance “Program Files”. I have tried to do my best to account for this, and the latest versions of the software should handle those paths without problems, I have installed my own copy of lcc in Program Files, but there could be still some problems in the utilities like lcclnk or lcclib. If you find path related problems, reinstal lcc in a directory without spaces in it.
[1]
In some systems, there is an old command.com present that gets called
instead of the correct win32 command interpreter. In this case, a DOS
session is opened and other things fail completely. The command can fail for
lack of disk space, or other reasons.