RE: 3.14 build system doesn't cope with hyphens in IOC names

["Denison, PN \(Peter\)" <peter.denison@diamond.ac.uk>]

> -----Original Message-----
> From: Ernest L. Williams Jr. [mailto:ernesto@ornl.gov] 
> Subject: Re: 3.14 build system doesn't cope with hyphens in IOC names
> 
> We use hyphens in our IOC names under EPICS R3.14.7.
> I don't remember making any modifications to support this.
> 
> For example,
> 
> ==============================================================
> 
> [williams@lion test]$ makeBaseApp.pl -t example example 
> [williams@lion test]$ makeBaseApp.pl -i -t example my-new-ioc 
> The following target architectures are available in base:
>     vxWorks-mv2100_v6
>     vxWorks-mv5100_v6
>     vxWorks-ppc603_T2-2
>     vxWorks-ppc603_long
>     vxWorks-ppc603
>     linux-x86
>     vxWorks-ppc604_T2-2
> What architecture do you want to use? vxWorks-ppc603 
> [williams@lion test]$ ls configure/  exampleApp/  iocBoot/  Makefile 
> [williams@lion test]$ ls  iocBoot/ iocmy-new-ioc/  Makefile
nfsCommands 
> ==============================================================
> 
> Works perfect.

Sorry - I wasn't clear enough in my original explanation of the problem.
It is in the substitution of "APPNAME" that problems occur with hyphens.
In your example, the appname was "example", which doesn't contain
hyphens (so no problem) and you'd need to modify the st.cmd file by hand
to change to example_registerRecordDeviceDriver from
my-new-ioc_registerRecordDeviceDriver, also avoiding the problem.

If you use the same name for the app and the ioc, both with a hyphen in,
you'll see the problem.

Peter Denison, Senior Software Engineer
Diamond Light Source Ltd., Diamond House, Chilton, Didcot, Oxon, OX11
0DE
Tel: +44 1235 778511