Mail Archives: djgpp/1997/01/09/05:50:40
Dim Zegebart wrote:
>
> After an hour of countless attempts i "DISCOVER" the right way
> of involving non statndart LIB into project.
> I have libGDBM.a and libSWORD.a, so in RHIDE i'm just type
> GDBM and SWORD in library option-window. It works fine !!!
>
> Unfortunately i'm can't understand such bihavior.
It's because of the GNU library linking syntax. When you instruct gcc
to link a library you do so like this:
gcc [blah blah] -lalleg
This translates into [lib]alleg[.a]. The reason this is done is to
force all library names to be standardized. If they were not, you could
call your library schmo.jnk, and your friend could call his 55ck858.44c,
and nobody would have the slightest idea what they were. But because of
the forced naming convention, all libraries have standard names (libc.a,
libgcc.a, liballeg.a, libsword.a), or they can't be easily linked.
RHIDE simply follows this convention, allowing you to enter the library
names in the same way that you would to link them with gcc. I can see
why this behavior might be annoying, but it's perfectly rational.
To Robert: Perhaps RHIDE could allow users to enter full library names
and translate them? Or just have a popup listing all available
libraries. Doesn't sound like it'd be too much work and it would help
the newbies. :)
--
---------------------------------------------------------------------
| John M. Aldrich, aka Fighteer I | fighteer AT cs DOT com |
| Proud owner of what might one | http://www.cs.com/fighteer |
| day be a spectacular MUD... | Plan: To make Bill Gates suffer |
---------------------------------------------------------------------
- Raw text -