--- Peter Kuhar <[EMAIL PROTECTED]> escribió:
> Is this a global variable???
>
> On 9/30/07, David Lucena <[EMAIL PROTECTED]> wrote:
> >
> > I am using SDCC to program a z80 machine. When I create this code:
> >
> > unsigned char test = 0;
> >
> > It is assembled as follows:
> >
> > ld
Is this a global variable???
On 9/30/07, David Lucena <[EMAIL PROTECTED]> wrote:
>
> I am using SDCC to program a z80 machine. When I create this code:
>
> unsigned char test = 0;
>
> It is assembled as follows:
>
> ld iy,#_test
> ld 0(iy),#0x00
>
> But I would like that
I am using SDCC to program a z80 machine. When I create this code:
unsigned char test = 0;
It is assembled as follows:
ld iy,#_test
ld 0(iy),#0x00
But I would like that it could be initialized as its done in assembler:
test:
.db 0
Is there any way of forcing this beh
On 9/30/07, Stanley Lee <[EMAIL PROTECTED]> wrote:
> Sorry for the additional spam, but I have a few more questions about the
> Makefile as I am on the way of switching away from using piklab ide
I think Piklab should work fine. If you have Piklab related problem,
try ask in gnupic mailing list. T
I salute the switch to the Makefile, even if it's a pain. It
makes a LOT of sense to keep all the details of a compilation
(commands, switches, command-line variables, etc.) in one text
file which can be controlled by a version control system.
Most IDEs keep that information in some proprietary p
Hi
Sadly makefiles are hard to read. I usually write generic makefiles so i
only need to do it once ;)
Stanley Lee wrote:
> PROG_NAME = LED_toggle.hex
> OBJS = main.o
> all: $(PROG_NAME)
>
> #for the .c.o directive below, do I need to replace it with the
> .c .o instead of .c.o? i.e. how would I
[EMAIL PROTECTED] wrote:
>I use "$< -o $@"
>where you have "$+ -o $(@)".
>
oops, I have confused my compile and link commands.
My link command uses "$^ -o $@"
$^ is like $+, but with no duplicates.
Randy
-
This SF.net em
> Sorry for the additional spam, but I have a few more questions about the
> Makefile as I am on the way of switching away from using piklab ide and
> more towards using the Makefile.
> [...]
Please do a simple Google search with "make tutorial", and read at least two
or three of them. It might he
Stanley Lee wrote:
> #for the .c.o directive below, do I need to replace it with the
> .c .o instead of .c.o? i.e. how would I know which
> source code to compile and build?
>
> .c.o:
>$(CC) $(CFLAGS) $(INC) -c $<
I'm no expert on makefiles, but perhaps you want to use
%.o : %.c
I thi
