#EXPORT Directive with #DEFINE Filename

MotoDan · Joined: 30 Dec 2011 Posts: 55

Hello all,

I am trying to get the #EXPORT directive to work with portions of the filename to include the firmware version number like this:

gpsmikey · Joined: 16 Nov 2010 Posts: 588 Location: Kirkland, WA

I have not tried that, but in my experience, dots "." tend to be problematic (across multiple operating systems too). Try using an underscore "_" instead or another option would be to create a version string like "v1p3" should also work. Much less likely to run into problems - dots in a file name can have multiple "functions" including separating the file name from the file type and Murphy says that it will NOT be interpreted the way you intend it to.

mikey
_________________
mikey
-- you can't have too many gadgets or too much disk space !
old engineering saying: 1+1 = 3 for sufficiently large values of 1 or small values of 3

Ttelmah · Joined: 11 Mar 2010 Posts: 19539

It's more complex than this....

First, '+' is not the way to catenate.
Second, you have a problem, since you need to catenate without spaces (the default is to add spaces in front of numbers when catenated).
Third, you need to ensure that the macro expansion takes place at each level in the catenation. The default way of catenating without spaces, prevents macro expansion on the argument (this is covered in K&R), so you need to cheat and force an expansion before the catenation (this is the reason for 'xcat' in the code below).

The way to do this is to build the macro, a 'section at a time'.
So:

MotoDan · Joined: 30 Dec 2011 Posts: 55

Ttelmah,

Thanks for the reply and excellent solution to my problem! I had no clue how to do this. Being able to build the hex file based on the FW version names allows me to change the revision level in one place. I use the Major.Minor rev names in my code and having the output filename generated automatically is very handy. This macro will go at the top of everything I write from now on!

Thanks again!
MotoDan