> 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 help to keep the spam level low here. ;-)
> #for the .c.o directive below, do I need to replace it with the
> <filename>.c <filename>.o instead of .c.o? i.e. how would I know which
> source code to compile and build?
No, you don't have to replace it, because there is a rule below
("$(PROG_NAME): $(OBJS)") that tells make which object files belong to the
program.
> prog: $(PROG_NAME)
> piklab-prog --programmer=direct --port=/dev/parport0
> --device=$(sdcc_PIC_TYPE) --command=program $(PROG_NAME)
>
> #would the prog directive be telling the makefile to flash the hexfile to
> the microcontroller? if I am using PICKIT2 programmer, would I be
> commanding the programmer to look in /dev/usbxxx, x being number?
It's the other way around: you tell make to produce the goal "prog". Make
finds the rule, checks that $(PROG_NAME) is up to date (if not, make builds
it!), and then "piklab-prog" is called with the arguments shown. If you need
another device, enter its name in the command line for "piklab-prog".
Hope that helps.
Bodo
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
