Lewis,
EPICS is advertised to build on Windows with only "make" and "perl"
(plus a MS compiler) required. Windows does not come with a shell that
will understand Dirk's script, right? So what shell would you point to?
Mark
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of J. Lewis Muir
Sent: Friday, March 12, 2010 9:39 AM
To: EPICS Tech-Talk
Subject: Re: Building StreamDevice 2-4 / SynApps / Win32
On 3/12/10 9:34 AM, John Dobbins wrote:
J. Lewis Muir wrote:
On 3/11/10 10:55 PM, Mark Rivers wrote:
I don't think shell is important on Windows, you can build EPICS in
a
Cygwin bash shell or a Windows cmd shell without having to worry
about
it.
Hi, Mark.
Note I'm not talking about the shell from which the make command is
executed; I'm talking about the shell that make uses to execute
commands
for a given target.
Lewis
Lewis, Mark, All,
It seems to me that an easy thing would be to write a Perl script that
replicates this code (which is just generating a test file):
# create stream.dbd from all RECORDS
$(COMMON_DIR)/$(LIBRARY_DEFAULT).dbd: ../CONFIG_STREAM
@for r in $(RECORDS); \
do echo "device($$r,INST_IO,dev$${r}Stream,\"stream\")"; \
done > $@
@echo "driver(stream)" >> $@
@echo "variable(streamDebug, int)" >> $@
@echo "registrar(streamRegistrar)" >> $@
endif
I can do that but am not sure about how to invoke the Perl script and
pass from $(RECORDS) to the Perl script.
It would be nice to not have this one part of EPICS dependent on
cygwin
when the rest it not.
Hi, John.
That would work, but I'm not convinced this one part is dependent on
Cygwin. I still think the problem is just that the target commands are
getting passed to either the wrong shell or a broken shell.
Lewis