| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
933
|
13 Nov 2013 |
Stefan Ritt | Forum | Installation problem | > got around to look at compile messages on
ubuntu: in addition to "variable 'error'
set but not used" we have these:
|
|
|
934
|
14 Nov 2013 |
Razvan Stefan Gornea | Forum | Installation problem | Hi, Thanks a lot for the response! Yes
to search packages and list their content
in Slackware it is pretty similar to your |
|
|
935
|
14 Nov 2013 |
Konstantin Olchanski | Forum | Installation problem | # slackpkg file-search sql.h
[ installed ] - libiodbc-3.52.7-x86_64-2
...
|
|
|
936
|
14 Nov 2013 |
Konstantin Olchanski | Forum | Installation problem | > #include "use.h"
> { USED int i=foo(); }
|
|
|
1383
|
24 Aug 2018 |
Lukas Gerritzen | Forum | Int64 datatype | I would like to store the address of 1-Wire
temperature sensors in a device
driver. However, the supportet data types |
|
|
1384
|
25 Aug 2018 |
Stefan Ritt | Forum | Int64 datatype | > I would like to store the address of 1-Wire
temperature sensors in a device
> driver. However, the supportet data types |
|
|
1389
|
28 Aug 2018 |
Konstantin Olchanski | Forum | Int64 datatype | > I would like to store the address of 1-Wire
temperature sensors in a device
> driver. However, the supportet data types |
|
|
368
|
10 Apr 2007 |
Dan Gastler | Forum | Interrupt code for VME? | Hello,
Is there any example code for using midas
for interrupt driven data
|
|
|
406
|
06 Sep 2007 |
Stefan Ritt | Info | Introduction of MIDAS_MAX_EVENT_SIZE | We had the problem that different experiments
used different MAX_EVENT_SIZE
values (the MEG experiment actually 10 MB!). |
|
|
16
|
09 Jul 2004 |
Stefan Ritt | | Introduction of environment variable MIDASSYS | Starting from midas version 1.9.4 on, the
environment variable 'MIDASSYS'
should be defined and point to the installation |
|
|
18
|
09 Jul 2004 |
Piotr Zolnierczuk | | Introduction of environment variable MIDASSYS | > Starting from midas version 1.9.4 on, the
environment variable 'MIDASSYS'
> should be defined and point to the installation |
|
|
19
|
09 Jul 2004 |
Stefan Ritt | | Introduction of environment variable MIDASSYS | > Here's my suggestion
> MIDASSYS=/opt/midas-1.9.4 (for example)
|
|
|
20
|
09 Jul 2004 |
Piotr Zolnierczuk | | Introduction of environment variable MIDASSYS | > I guess we should follow the "standard"
as much as possible. MIDASSYS was inspired
by
|
|
|
21
|
09 Jul 2004 |
John M O'Donnell | | Introduction of environment variable MIDASSYS | For a long time the "de facto" standard was
to spread a package around in many
directories under /usr/local. This proved |
|
|
22
|
12 Jul 2004 |
Stefan Ritt | | Introduction of environment variable MIDASSYS | > With POSIX there is a written standard,
which says that each pacakge goes in
> it's own
|
|
|
28
|
20 Jul 2004 |
Konstantin Olchanski | | Introduction of environment variable MIDASSYS | > > Starting from midas version 1.9.4 on,
the environment variable 'MIDASSYS' ...
> 2. What will the entire structure tree |
|
|
29
|
21 Jul 2004 |
Stefan Ritt | | Introduction of environment variable MIDASSYS | > Where should MIDAS be installed?
I personally don't have any preference, as |
|
|
148
|
03 Oct 2004 |
Stefan Ritt | Info | Introduction of new transition scheme | A new transition scheme has been implemented
and committed. Previously, one had the
possibility to register for PRE/POST transitions, |
|
|
2020
|
24 Nov 2020 |
Isaac Labrie Boulay | Forum | Invalid name "Analyzer/Tests" | Hi everyone,
I've recently took the analyzer template |
|
|
2027
|
27 Nov 2020 |
Konstantin Olchanski | Forum | Invalid name "Analyzer/Tests" | > I've recently took the analyzer template
from $MIDASSYS/examples/experiment and
> modified it to be able to use Roody on |
|