Experimental Physics and Industrial Control System
|
I apologize, I didn’t read carefully that you were running the makeSupport.pl to create the application. I get the same error as you when I try to run that script on Windows,
it seems that the Perl script does not understand Windows path syntax.
You can run the script on Linux and then just copy the tree to your Windows machine until we get that fixed.
Mark
From: Alireza Panna [mailto:[email protected]]
Sent: Tuesday, September 02, 2014 10:32 AM
To: Mark Rivers
Cc: Ralph Lange; EPICS Tech-Talk
Subject: Re: stream device get started?
Yes, it is true that EPICS_HOST_ARCH should be set in the environment which I do. Now correct me If I am wrong, but I was under the impression that the makeSupport perl
script in ../aysn-4-23/bin/<arch>/ creates the device support directories i.e the configure/release files and so on and then you run makeBase.pl to create the application. This is where my problem is, because when I run makeSupport.pl, I get the error mentioned
in the first email. I might be wrong since I am fairly new to the EPICS community.
------------------------------------------------------
University of Maryland, College Park
On Tue, Sep 2, 2014 at 7:15 AM, Mark Rivers <[email protected]> wrote:
Ralph is right, only ASYN should be defined in configure/RELEASE, EPICS_HOST_ARCH should be defined as an environment variable.
Mark
________________________________________
From: [email protected] [[email protected]] on behalf of Ralph Lange [[email protected]]
Sent: Tuesday, September 02, 2014 2:35 AM
To: EPICS Tech-Talk
Cc: Alireza Panna
Subject: Re: stream device get started?
On 01/09/2014 21:00, Mark Rivers wrote:
>> EPICS_HOST_ARCH env var is set and so is ASYN.
> These should not be set as environment variables, they should be defined in the configure/RELEASE file of your application.
Well...
While definitions of external modules like ASYN should always go into
the configure/RELEASE file (it is named RELEASE because it defines the
exact releases of external modules that you are using), EPICS_HOST_ARCH
is meant to be set in the environment.
While setting it in configure/RELEASE might work, the host architecture
is rather a property of the host than a definition of an external module.
As soon as you put your sources on a network drive and compile it for
multiple host architectures inside the same structure, setting the host
architecture in configure/RELEASE is obviously not a good idea.
~Ralph
|
- References:
- stream device get started? Alireza Panna
- RE: stream device get started? Mark Rivers
- Re: stream device get started? Ralph Lange
- RE: stream device get started? Mark Rivers
- Re: stream device get started? Alireza Panna
- Navigate by Date:
- Prev:
Re: stream device get started? Alireza Panna
- Next:
Re: motorApp R6.8 Mclennan PM600 opposite limit datum search mode on linux-arm Maren Purves
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: stream device get started? Alireza Panna
- Next:
Re: about caPutLog Benjamin Franksen
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 17 Dec 2015 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|