Discussion:
ULINK (again)!
(too old to reply)
Shane Stump
2008-07-25 22:45:51 UTC
Permalink
I am trying to statically link a large application in C Builder 2007.
The application uses many 3rd party components including DevExpress and
NexusDB to name a few.

The C Builder 2007 linker runs out of memory. Linking with packages
causes other problems.

I have tried several times to get ULINK to work and I have never gotten
past 1st base with it.

Can somebody who uses it successfully inside of C Builder 2007 with
DevExpress please provide IDIOT PROOF instructions on how you did it?

Best Regards,

Shane
Dennis Jones
2008-07-29 21:02:19 UTC
Permalink
I am trying to statically link a large application in C Builder 2007. The
application uses many 3rd party components including DevExpress and NexusDB
to name a few.
The C Builder 2007 linker runs out of memory. Linking with packages causes
other problems.
I have tried several times to get ULINK to work and I have never gotten
past 1st base with it.
Same here. It never worked for me -- WAY too many problems.

When I asked the author about the problems I was having (on several
occasions), he gave (what were, in my opinion) excuses such as, there is a
bug in the compiler, or ilink32 doesn't write dictionary information
correctly, or name mangling was wrong, or AQtime has a bug (apps linked with
ulink would crash AQtime), or whatever. What the author didn't seem to
understand is that if he is going to produce something that is supposed to
be used with the Borland tools, then it needs to be plug-in compatible with
ilink32/tlink32 -- it should not require a bunch of work-arounds, or
re-compiling dozens of dependent projects with unusual switch settings, etc.
Even when he fixed a bug, another one would invariably come up. Then he
would ask for more information, I would have to re-compile using some
strange flag and send him the results -- and back and forth we would go for
days and days.

Fortunately, I have not run into any linker problems that couldn't be solved
by making some sort of change to the project, so it wasn't critical for me.
I was just hoping for a faster linker. But I will gladly wait a few extra
seconds for my apps to link rather than go through all the extra hassle of
trying to get ulink to work. Perhaps you (or others) need it bad enough
that you would be willing to work with him more to resolve the issues -- it
just wasn't worth the effort for me (and I don't have the time to be his
beta tester!).

I haven't even tried ulink for oer two years, so it may be better now, I
don't know. But until I absolutely need it, I'm staying away from it. Too
bad PocketSoft stopped building RTLink (it was for DOS, but they could have
added Windows support), and Blinker also seems to have aborted development
(both of which were commercial products, fully Borland-compatible).

- Dennis
Shane Stump
2008-07-30 02:01:15 UTC
Permalink
Dennis,

The funny thing I can't explain is that I have actually added several
more modules to my application and now ILINK32 works AGAIN!

I go through periods when the only way I can get my application to link
with ILINK32 is by linking with packages (which I really want to avoid)!

I emailed the author of ULINK and requested they make it a
"drop-in-replacement" and charged for it. If it worked, I would be
willing to pay. I never heard back.

Best Regards,

Shane

Continue reading on narkive:
Loading...