On 2016-09-02 08:36, Martin Schreiber wrote:
> DIREXT has been defined, if DIREXT has not been defined then
> remove "${MAC_IFDEF(DIREXT)}" from expanded string.
Ah, now I understand. That could be useful.
> Could you manage to set the appropriate unit output directories?
Yes. Seeing as MSErun allows inheriting settings from higher level
entries, I didn't want to manually define the
"-FU<path_to_example>/units" for each project I add. I read the MSERun
readme file again and tried a couple of the File path macros. Eventually
I found that FILE_NONAME is the one I was after. This macro now extracts
the Path from the ${FILE} and then appends "unit" to the end.
FU${FILE_NONAME(${FILE})}units
Now it works perfectly. This tool will definitely be used from now
onwards. It just took a couple of attempts to get a basic understanding.
One more question, to try and clarify why "-FUunits" didn't work in the
first place. Not that I need to, I'm just curious. In the Edit Group
Item dialog there is a "Compile Directory" entry. Does that entry mean
MSErun makes that the current directory before executing the Compile
Command? Also, can all the edit boxes in that dialog accept macros?
Many thanks for all your help.
Regards,
Graeme
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/
My public PGP key: http://tinyurl.com/graeme-pgp
------------------------------------------------------------------------------
_______________________________________________
mseide-msegui-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
