RE: Epics base 7.0.2 Windows MSVC odd case change

["Engbretson, Mark S. via Tech-talk" <tech-talk@aps.anl.gov>]

Gnu make 4.1

-----Original Message-----
From: Michael Davidsaver <mdavidsaver@gmail.com> 
Sent: Friday, January 4, 2019 2:01 PM
To: Engbretson, Mark S. <engbretson@anl.gov>; tech-talk@aps.anl.gov
Subject: Re: Epics base 7.0.2 Windows MSVC odd case change

Which version of Make are you using?

In fact a makefile troubleshooting target was added PRINT.% which prints the
value of a make variable.  eg. PRINT.CPPFLAGS

This shouldn't cause problems as to my knowledge GNU make target names are
always case sensitive.

On 1/4/19 11:26 AM, Engbretson, Mark S. via Tech-talk wrote:
> I was just attempting a build on epics base 7.0.2 on windows with
Microsoft Visual Studio 2012 (windows 7) and 2017 (windows 10) and it
stalled on building the pvData json module print.cpp.
> 
>  
> 
> The odd part is that when it is being parsed by mkmf.pl, the print.d is
created with all references to print being upper case, i.e. PRINT, so
print.cpp never actually gets compiled, so the library does not have all the
elements that it needs to build.
> 
> If I were to change the file name to print1.cpp and modify the make file
to use that file name – everything works. As it does if I edit the print.d
file and flip the upper case PRINT back to lower case print.
> 
>  
> 
> This did not do this with epics base 7.0.1.  Not a big deal since I am
aware of a solution, but I was wondering if any of the build system expects
might know why “print” on at least 2 of my build systems is now being
treated  differently. Works as expected on linux.
>