[Clas_slow_control] error building hall b epics

[Mark M. Ito]

Stepan et al.,

I don't necessarily think that you need to get a capfast license. It 
would certainly not hurt, and I don't think it breaks the bank, but it 
might not be worth it; I don't know the answer to that question. Hall B 
would survive with or without it in my opinion.

But if you do _not_ get a license (as things stand now), the capfast 
build commands in the makefiles should be removed and the .db files 
checked directly into the CVS repository. That would then render the 
capfast .sch files obsolete and they might go out-of-date. But if you 
never get a capfast license again, it doesn't matter; you would then 
have said goodbye to .sch files.

   -- Mark

On 02/17/2010 06:18 PM, Stepan Stepanyan wrote:
> Nerses,
>
> What we need to get capfast license.
>
> Stepan
>
> nerses at jlab.org wrote:
>> Dear Mark,
>>
>> after upgrade of clon01 we lost capfast license which was bind to old
>> clon01 cpu id.
>> In EPICS software there is VDCT
>> http://www.aps.anl.gov/epics/wiki/index.php/VDCT_Status_Page
>> Which had claims about it's capability to convert capfast files VDCT xml
>> files.
>>
>> Nerses
>>
>>> No capfast? Hints?
>>>
>>> sch2edif -n analog_fcclassc8.sch
>>> gmake[2]: sch2edif: Command not found
>>> gmake[2]: *** [analog_fcclassc8.edf] Error 127
>>> gmake[2]: Leaving directory
>>> `/home/marki/epics/epicsBtest/app/analog_fc/db'
>>> gmake[1]: *** [all] Error 2
>>> gmake[1]: Leaving directory 
>>> `/home/marki/epics/epicsBtest/app/analog_fc'
>>> gmake: *** [analog_fc.dir] Error 2
>>>
>>> _______________________________________________
>>> Clas_slow_control mailing list
>>> Clas_slow_control at jlab.org
>>> https://mailman.jlab.org/mailman/listinfo/clas_slow_control
>>>
>>
>>
>> _______________________________________________
>> Clas_slow_control mailing list
>> Clas_slow_control at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/clas_slow_control