I did try today with -l instead of using mylib.lib as an input file, and
the behavior is identical.
Happy Hacking,
David E. McMackins II
Associate, Free Software Foundation (#12889)
www.mcmackins.org www.delwink.com
www.gnu.org www.fsf.org
On 03/28/2016 02:15 AM, Maarten Brock wrote:
> Hello D
According to the SDCC manual, you don't use -l
I've been using: sdcc -mgbz80 -Lmydir main.c mylib.lib
and it does compile without problems, until I tried to add that extra
file. I'll see about -l later today.
Happy Hacking,
David E. McMackins II
Associate, Free Software Foundation (#12889)
ww
Hello David,
The -L option only sets a library search path. It's -l that adds a library.
Hope this helps,
Maarten
> I'm running Debian Sid, using SDCC 3.5.0 for the gbz80 architecture.
>
> In my statically-linked library, I have been using only one source file,
> but today I had a reason to add
I'm running Debian Sid, using SDCC 3.5.0 for the gbz80 architecture.
In my statically-linked library, I have been using only one source file,
but today I had a reason to add another. In this second source file, I
defined gb_memcpy which is a version of standard memcpy that uses an
8-bit length par
