-
It looks like this functionality already exists as -o for both gpasm and gplink. The manual says this option is "Alternate name of hex output file", which is accurate but incomplete. It appears to affect the base name (and path if specified) of all output files, object, list, error and such like. As a new user, I didn't think to try it (generating object) and only discovered later by chance...
2009-05-18 21:25:17 UTC in gputils
-
It would be useful to be able to specify a path for output files as a command option to both gpasm and gplink. Occasionally it would also be useful to control the name of output files also through a command option.
This is particularly useful where a common set of sources is used to build multiple different but related targets. Different targets may need separate output directories to avoid...
2009-05-07 12:41:45 UTC in gputils
-
In the following example labels are defined using two occurences of the #v(expression) syntax in a single definition to create a "two dimensional" array of labels. Unfortunately gpasm reports "unknown opcode" errors.
broken.asm:
test MACRO n
LOCAL m=0
WHILE m
2009-05-07 10:47:18 UTC in gputils
-
gplink appears to ignore second and subsequent linker command files specified individually with -s command line options. For example,
gplink -s16f887.lkr -stest1.lkr test1.o utils.o
This is useful where, for example, a common set of sources is used to build multiple variants each of which uses a "standard" linker command file for the processor and also some variant-specific customisation...
2009-05-07 10:21:16 UTC in gputils
-
It appears that the names given to code sections and those used as regular code labels are created in the same namespace by gpasm. Thus the following example fails due to the use of "test" as both a code section name and code label.
broken.asm:
rstvec CODE
call test
test CODE
test nop ; do something here
nop
END
F:\>gpasm -c -p16f887...
2009-05-07 09:56:55 UTC in gputils
-
Under mpasm it's possible to use a command-line defined symbol in the #include statement to set the path to included files. Under gpasm this approach fails as shown in this example:
broken.asm:
#INCLUDE INC/message.inc
END
F:\>gpasm -DINC=src -p16f887 broken.asm
broken.asm:6:Error [179] Unable to open file "INC/message.inc" - No
such file or directory
gpasm has a -I command...
2009-05-07 09:21:49 UTC in gputils
