Frontend user code

• Midas Doc
• Feature Listing
• Application Listing
• Online Database
• FAQ
• Index

Links

• Frontend Operation
• Frontend Application
• Equipment List Parameters
• Slow Control System
• Equipment Flags
• Event Notification (Hot-Link)

Introduction

This section describes the features of the user-written part of a "C-style" Frontend, referred to here as frontend.c.

You can also write frontends using object-oriented C++ (TMFE) or Python.

The frontend system has evolved over the decades, and contains some legacy features that are not often used (e.g. interrupt handlers). For backwards-compatibility, these features are still present, but this does require a bit more boiler-plate code to be written for each frontend. We will first document every feature supported by the frontend system, then explain a slightly more user-friendly wrapper (mfed.cxx) that helps reduce the amount of boiler-plate needed for a new frontend.

Frontend Templates

To make a user-written or custom frontend, users will usually modify one of the templates provided in the MIDAS package under $MIDASSYS/examples/ for their particular hardware and other requirements. Make sure to pick the closest template, e.g. if writing a Slow Control frontend, pick a slow-control template. For each example frontend, a Makefile is also provided.

A partial list of the templates provided is shown below:

Hardware	Filename	Directory (MIDAS package)	Purpose	Language
VME	fevmemodules.c	$MIDASSYS/examples/Triumf/c/	Access to VME modules	C
VME	fevme.cxx	$MIDASSYS/examples/Triumf/c++/	Access to VME modules	C++
CAMAC	frontend.c	$MIDASSYS/examples/experiment/	Access to CAMAC modules	C
	mtfe.c	$MIDASSYS/examples/mtfe/	Multithreaded using ring buffer	C
Wiener CC-USB	feccusb.cxx	$MIDASSYS/examples/mtfe/	CAMAC/USB demo	C++
RS485 bus	mscb_fe.c	$MIDASSYS/examples/slowcont/	Slow control with MSCB	C
EPICS	frontend.c	$MIDASSYS/examples/epics/	Slow controls	C
Camac	ebfe.c	$MIDASSYS/examples/eventbuilder/	Event Builder (with mevb)	C
	frontend.cxx	$MIDASSYS/examples/experiment/	mfed (wrapper to simplify writing a frontend)	C++

The features of a typical frontend program are best explained by reference to examples of the user code provided in the Midas Package.

Frontend code

Note that there are several kinds of frontend used for different purposes, e.g.

• frontend to read VME or CAMAC hardware, using interrupt or polling (e.g. to read experimental data)
• multithreaded frontend where polling can be in a separate thread
• slow control frontend (can be multithreaded) see also Slow Control System
• etc.

Templates for many types of user frontend code are provided in the MIDAS packages (see #Frontend Templates).

The following sections refer to these templates. Most of the examples are taken from the largefe.cxx example. Documentation on the MIDAS library subroutines to access the ODB (some of which are used in the examples below) can be found in the ODB access page.

The user frontend code is then compiled and linked with the system part and the MIDAS library (see Frontend Task). Makefiles are provided with the templates that can be modified as needed.

Access to command line parameters

The function mfe_get_args gives access to the Frontend command line parameters.

This example shows how to use it in the frontend user code:

 int argc;
 char **argv;
 mfe_get_args(&argc, &argv);
 for (int i = 0; i < argc; i++) {
    // Use argv[i] 
 }

See Frontend Application Arguments for the arguments that are handled automatically by the frontend system.

Include files

The following example (from template frontend file $MIDASSYS/examples/basic/largefe.cxx) shows the standard include files needed for a frontend. The user may add any other include files as needed (e.g. those needed for VME access).

Some legacy frontends may include the experim.h file. This was an old way of accessing the ODB, but was not very user-friendly when the ODB structure needed to change.

The example below shows a typical list of include files for a frontend:

#include <stdio.h>
#include <stdlib.h>
#include "midas.h"
#include "mfe.h"

Global Declarations

The following example (from template frontend file fevmemodules.c - see #Frontend Templates) shows the global declaration. The declarations are system wide. Some may be changed to suit the user, but none should not be removed.

frontend_name

This value can be modified to reflect the purpose of the code

frontend_call_loop

If set to TRUE, the function frontend_loop() gets called very frequently. If FALSE, frontend_loop() does not run. The user can add suitable code to this routine if desired (e.g. to check for a condition).

display_period

The time interval (defined in milliseconds) between the refresh of a frontend status display. The value of zero disables the display. If the frontend is started in the background with the display enabled, the stdout should be redirected to the null device to prevent the process from hanging.

max_event_size

specifies the maximum size (in bytes) of the expected event.

event_buffer_size

specifies the maximum size (in bytes) of the buffer to be allocated by the system.

equipment_common_overwrite

whether the definitions in the EQUIPMENT struct override those in the /Equipment/largefe/Common section of the ODB. If FALSE, the values in the struct will be used the first time the program runs, then the ODB values will be used afterwards (e.g. allowing you to change the period of a periodic equipment via the ODB).

See below for an example of global declarations from a frontend.

/*-- Globals -------------------------------------------------------*/
/* The frontend name (client name) as seen by other MIDAS clients   */
const char *frontend_name = "largefe";

/* The frontend file name, don't change it */
const char *frontend_file_name = __FILE__;

/* frontend_loop is called periodically if this variable is TRUE    */
BOOL frontend_call_loop = TRUE;

/* a frontend status page is displayed with this frequency in ms */
INT display_period = 0;

/* maximum event size produced by this frontend */
INT max_event_size = 10000;

/* maximum event size for fragmented events (EQ_FRAGMENTED) */
INT max_event_size_frag = 5 * 1024 * 1024;

/* buffer size to hold events */
INT event_buffer_size = 10 * 10000;

/* whether the values in EQUIPMENT struct override ODB values */
BOOL equipment_common_overwrite = FALSE;

System Function Declarations

These lines declare the pre-defined system functions which should be present.

INT frontend_init();
INT frontend_exit();
INT begin_of_run(INT run_number, char *error);
INT end_of_run(INT run_number, char *error);
INT pause_run(INT run_number, char *error);
INT resume_run(INT run_number, char *error);
INT frontend_loop();

Readout Function Declarations

Following the previous group is a second group of declarations, which define the readout functions. These depend on the defined equipments, and run when the respective equipment is triggered. In this example, one equipment will be defined, so there is one declaration. The user functions will be described in detail in later sections.

INT read_large_event(char *pevent, INT off);

If using an interrupt, callback function prototypes are also included

extern void interrupt_routine(void);
void register_cnaf_callback(int debug);

Equipment List

This list of structs defines the behaviour of your frontend (e.g. periodic or polled equipment). See Equipment List for full documentation of the entries.

Note that these are the default values for each equipment (used the very first time a frontend is run). If equipment_common_overwrite is FALSE, then some of the values will subsequently be read from the ODB instead. If equipment_common_overwrite is TRUE, then the ODB will be updated with the coded values each time the program runs.

EQUIPMENT equipment[] = {

  {"large",                   /* equipment name */
    {3, 0,                    /* event ID, trigger mask */
     "SYSTEM",                /* event buffer */
     EQ_PERIODIC | EQ_FRAGMENTED,     /* equipment type */
     0,                       /* event source */
     "MIDAS",                 /* format */
     TRUE,                    /* enabled */
     RO_ALWAYS,               /* read when running and on transitions */
     2000,                    /* read every 2 sec */
     0,                       /* stop run after this event limit */
     0,                       /* number of sub events */
     0,                       /* log history */
     "", "", ""},
     read_large_event,        /* readout routine */
     NULL, NULL,              /* keep null */
     NULL,                    /* init string */
  },

  {""}
};

In the case of a polled equipment, the struct would be of the form:

   EQUIPMENT equipment[] = {
     { "Trigger",            // equipment name
       {
         ...
         EQ_POLLED,          // equipment type
         ...
         500,                // poll for 500ms 
         ...
         "", "", "",},
         read_my_event,    // readout routine 
      ...

In the case of a periodic equipment, the struct would be of the form:

   EQUIPMENT equipment[] = {
     { "Scaler",           // equipment name
        {    
           ...
           EQ_PERIODIC     // equipment type
           ...
           10000,          // period (read every 10s)
           ...
           "", "", "",},
      read_my_event,   // readout routine 
      ...

Sequence of Operations in the frontend

The following table shows the sequence of operations of the Frontend System functions. These functions must be implemented in the user's code (but may be as simple as just returning SUCCESS if the function is not relevant for your use case). These functions are called by mfe.cxx at the appropriate time. The System Transition functions are associated with a particular Run Transition as shown below:

System Function	System Transition Function	Associated Transition	Action
frontend_init()			Runs once after system initialization, before Equipment registration.
	begin_of_run()	TR_START	Runs after system statistics reset at each begin-of-run request.
	pause_run()	TR_PAUSE	Runs at each pause-run request.
	resume_run()	TR_RESUME	Runs at each resume-run request.
	end_of_run()	TR_STOP	Runs at each end-of-run request.
frontend_exit()			Runs once before any Slow Control Equipment exit

Each defined Equipment has the option to force itself to run at individual transition times (see Equipment ReadOn Flag), so that its equipment function will be called on a certain transition (or combination of transitions).

The system transition functions all run prior to the equipment functions. This gives the system the chance to take basic action on the transition request (e.g. enable/disable interrupt) before the equipment runs. All the transition routines run with a Transition Sequence number of 500 (the default). This allows users to add additional functions in the frontend that will run before or after any of the transitions (such as a prestart() or a poststop() function). See Run Transition Priority for more information.

Function frontend_init

No parameters.

This function runs once only at the application startup. Users may perform hardware checking, loading/setting of global variables, mapping of required ODB structures (see experim.h include file), setting up hot-links etc. in frontend_init(), e.g.

INT frontend_init()
{
  set_equipment_status(equipment[0].name, "Initializing...", "yellow");
  ....                  
  set_equipment_status(equipment[0].name, "OK", "green");

  return SUCCESS;
}

Reporting Equipment Status

If running with the webserver mhttpd, a frontend can send an update to the Status Page, to report on its progress, using the function set_equipment_status() (see above example). This is useful when hardware can take a long time to respond.

Function begin_of_run

Parameters:

• INT run number provides the number of the current run being started
• char * error can be used for returning a message to the system. This message string will be logged into the midas.log file (see Message System.

This function is called every time a run start transition occurs, i.e. at begin-of-run. It allows the updating of user parameters, and the loading/setup/clearing of hardware. At the exit of this function, the acquisition should be armed and ready to test the interrupt (if used), e.g.

INT begin_of_run (INT runnumber, char * error)
{
  // Read/validate some settings from the ODB (and return FE_ERR_ODB if there's a problem).
  // Apply them to the hardware (and return FE_ERR_HW if there's a problem).
  // etc...
  return SUCCESS;
}

Functions pause/resume_run

Parameters:

• INT run number provides the number of the current run being paused/resumed.
• char * error can be used for returning a message to the system. This message string will be logged into the midas.log file (see Message System.

These two functions are called upon "Pause" and "Resume" command respectively. Any code relevant to the upcoming run state can be included,e.g.

INT pause_run (INT run_number, char * error)
{
  disable_trigger();
  // Disable interrupt
  inRun = 0;
  mvme_write_value(myvme, VLAM_BASE+4, inRun);
  return SUCCESS;
}
                           //
INT resume_run (INT run_number, char * error)
{
  enable_trigger();
  inRun = 1;
  mvme_write_value(myvme, VLAM_BASE+4, inRun);
  return SUCCESS;
}

Function end_run

Parameters:

• INT run number provides the number of the current run being ended.
• char * error can be used for returning a message to the system. This message string will be logged into the midas.log file (see Message System.

This function is called at every "stop run" transition. It provides the opportunity to disable the hardware, e.g.

INT end_of_run(INT run_number, char *error)
{
  // Stop the hardware.
  // etc...
  return SUCCESS;
}

Function frontend_exit

Parameters: none

The function runs when the frontend program is shut down. Can be used to release any locked resources like memory, communications ports etc. e.g.

 function frontend_exit()
 {
    mvme_close(gVme);
    return;
 }

Function frontend_loop

Parameters: none

If frontend_call_loop is set to TRUE, this routine is called when the frontend is idle and at least once between every event. You could use it for example to check if there has been a timeout from hardware.

...
BOOL frontend_call_loop = TRUE;
...
                                
INT frontend_loop()
{
  // Implement any code that needs to be run very frequently
  return SUCCESS;
}

Event Types and Triggers

The frontend supports several different types of event trigger. The event trigger type is specified by the Equipment Flag in the Equipment Declaration. Common event types are "polled events" where the Equipment Flag is EQ_POLLED, "interrupts events" where the Flag is EQ_INTERRUPT, and "periodic events" where the Flag is EQ_PERIODIC. The name of the associated readout routine is specified in the Equipment Declaration for each event type.

Polled and interrupt events (see Event Types) require several extra functions to handle the hardware that periodic events do not require. These are described below.

Note that each frontend may contain:

• zero or one polled equipments
• zero or one interrupt equipments
• any number of periodic equipments

Function poll_event

Parameters:

• INT source
• INT count
• BOOL test

If the Equipment Type is EQ_POLLED, the poll_event() routine will be called as often as possible over the corresponding poll time (e.g. 500ms) given by each polling equipment.

The user must provide suitable code in the routine poll_event(), e.g. reading a register from a VME module to see if any data is available

INT poll_event(INT source, INT count, BOOL test)
{
   /* Polling routine for events. Returns TRUE if event  is available. If test equals TRUE, don't return. 
      The test flag is used to time the polling 
    */
    int i;
    int lam = 0;
                                //
    for (i = 0; i < count; i++, lam++) {
      lam = vmeio_CsrRead(myvme, VMEIO_BASE);
      if (lam)
        if (!test)
          return lam;
    }
    return 0;
 }

An event readout routine must also be provided by the user.

Function interrupt_configure

• INT cmd
• INT source
• PTYPE adr

If the Equipment Type is EQ_INTERRUPT, an interrupt configuration routine called interrupt_configure() must be provided by the user. The interrupt configuration routine has the following declaration:

/*-- Interrupt configuration --------------------------*/
INT interrupt_configure(INT cmd, INT source, PTYPE adr)
{
 int vec = 0;
 switch (cmd) 
 {
   case CMD_INTERRUPT_ENABLE:
     if (inRun) mvme_write_value(myvme, VLAM_BASE+4, 0x1);
     break;
                                     //
   case CMD_INTERRUPT_DISABLE:
     if (inRun) mvme_write_value(myvme, VLAM_BASE+4, 0x0);
     break;
                                     //
   case CMD_INTERRUPT_ATTACH:
     mvme_set_dmode(myvme, MVME_DMODE_D32);
     mvme_interrupt_attach(myvme, INT_LEVEL, INT_VECTOR, 
               (void *)adr, &myinfo);
     mvme_write_value(myvme, VLAM_BASE+0x10, INT_VECTOR);
     vec = mvme_read_value(myvme, VLAM_BASE+0x10);
     printf("Interrupt Attached to 0x%x for vector:0x%x\n",
                    adr, vec&0xFF);
     break;
                                     //
   case CMD_INTERRUPT_DETACH:
     printf("Interrupt Detach\n");
     break;
  }
  return SUCCESS;
}

Under the four commands listed above, the user must implement the hardware operation needed to perform the requested action. In the Midas drivers directory examples can be found of such an interrupt code for CAMAC. See source code such as hyt1331.c,ces8210.c

An event readout routine must also be provided by the user in the frontend.

Event Readout routine

An event readout routine is required for all equipment, and is responsible for sending the actual data to midas. The framework calls the event readout routine whenever an equipment has been triggered (e.g. periodicially, or because poll_event() returned TRUE for a polled equipment etc). The function is of the form

INT function_name ( char *pevent ... )
{
  INT event_size;
  ........  // read data from hardware
  ........  // pack into banks depending on format
  ........
  return (event_size);
}

where the first argument of the readout function (pevent) provides the pointer to the newly constructed event, and points to the first valid location for storing the data.

NOTE

• The return value is the event size, and must be the number of bytes collected in this function. This is different to almost every other function in midas (where the return value is a status code).
• You can return 0 if you've decided you don't actually want to write this event.
• The event serial number will be incremented by one for every call to the readout routine, as long as the returned size is non-zero.

General readout function

A readout function is needed to send out data. This is done using one of the supported event structures usually "MIDAS" format data banks. The bank format ("MIDAS" in the example above) is declared in the Equipment List Parameters Format field.

An example of a scaler readout routine read_scaler_event() where the data is read out into MIDAS data banks is shown below.

INT read_large_event(char *pevent, INT off)
{
  DWORD *pddata;

  /* init bank structure */
  bk_init32(pevent);

  /* create bank (bank names must be 4 chars long) */
  bk_create(pevent, "BIGG", TID_DWORD, (void **) &pddata);

  /* fill data (just dummy values in this case) */
  memset((char *) pddata, 0x0000, 100);
  pddata += 1000000;
  memset((char *) pddata - 100, 0xFFFF, 100);

  /* close the bank */
  bk_close(pevent, pddata);

  /* return the number of bytes we wrote */
  return bk_size(pevent);
}

Some other examples of event readout routines in this document are

• FIXED Format event construction
• Super Event construction
• Slow Control

Many other examples of readout routines can be found in the frontend templates in the MIDAS package.

Polled or Interrupt readout routine

In the case of a Polled or Interrupt event, the content of the memory location pointed to by pevent (see Event Readout routine) prior to its use in the readout function, contains the interrupt source bitwise register. This feature can be exploited in order to identify which hardware module has triggered the readout when multiple interrupts have been assigned to the same readout function.

The examples below show a VME interrupt source for a given equipment. Depending whether USE_INT is defined, the Equipment will either use a Polled or an Interrupt mechanism. The Equipment declaration is of the form:

EQUIPMENT equipment[] = {
              //
   {"Trigger",  /* equipment name */
      ...
#ifdef USE_INT
      EQ_INTERRUPT, /* equipment type */
#else
      EQ_POLLED,    /* equipment type */
#endif
  /* interrupt source: crate 0, all stations */
      LAM_SOURCE(0, 0x0),
      ....
      "", "", "",
    },
    read_trigger_event, /* readout routine */
    NULL, NULL,
    trigger_bank_list,
}
 

Note that the LAM_SOURCE macro simply codes the parameters into a bitwise register.

The readout routine would contains code such as

INT read_trigger_event(char *pevent, INT off)
{
#if defined VADC0_CODE
  DWORD  *pdata;
#endif
                       //
#if defined VADC0_CODE
  /* read ADC0 data */
  v792_EvtCntRead(myvme, VADC0_BASE, &evtcnt);
  ........
  /* Read Event */
  v792_EventRead(myvme, VADC0_BASE, pdata, &nentry);
  ........
  v792_DataClear(myvme, VADC0_BASE);
#endif
                      //
  ........
  return (size);
}

The data will be packed into banks as described for the general readout function above. The example $MIDASSYS/examples/Triumf/c/fevmemodules.c contains a complete example of read_trigger_event().

Manual Trigger

Another type of frontend event trigger supported is the "manual trigger", where the Equipment Flag is EQ_MANUAL_TRIGGER. This flag means that an event can be triggered through the URL ?cmd=Trigger/<equipment_name> (e.g. http://my.host:8080/?cmd=Trigger/MyEquipmentName). If you add this URL to the /Alias part of the ODB, then a link will appear on midas webpages that can be clicked to trigger an event.

In some cases, the same readout code may be used for two types of event: a manual trigger and (say) a poll event. It is possible to determine whether the readout of an event was triggered by a manual trigger or a regular trigger by adding a call to the event header Macro DATA_SIZE in the readout routine:

 flag = DATA_SIZE(pevent);

If the result is

 *  flag = 0 normal call
 *  flag = 1 manual trigger

It is also possible for a backend MIDAS client (such as an analyzer or custom data archiver) to trigger a manual trigger event. The client controls when an event is sent by means of a function that requests an event by triggering the event sending mechanism with a RPC call.

With a frontend Equipment declaration of a manually triggered event of the form:

   { "Histo",             /* equipment name */
      2, 0,                 /* event ID, trigger mask */
      "SYSTEM",             /* event buffer */
      EQ_MANUAL_TRIG,     /* equipment type */
      0,    
      .......
   }
   

the code fragment to manually trigger this event is:

 int main(unsigned int argc,char **argv)
 {
     .......
     bm_request_event(hBufEvent, 2, TRIGGER_ALL, GET_ALL, &request_id, process_event_TD);
     .......
 }

When it is time to save the data during the run, the function below is called:

BOOL trigger_histo_event(void)
{
  HNDLE hconn;
  BOOL event_triggered;
                           //
  event_triggered = FALSE;
  ...................
  if (run_state == STATE_RUNNING) {   // Check the frontend client exists
       if( cm_exist(ClientName,TRUE))  {    
           status = cm_connect_client (ClientName, &hconn);
           if(status != RPC_SUCCESS)
               cm_msg(MERROR,"trigger_histo_event","Cannot connect to frontend \"%s\" (%d)",
                      ClientName,status);
           else  {     // successfully connected to frontend client
               status = rpc_client_call(hconn, RPC_MANUAL_TRIG, 2); // trigger a histo event
               if (status != CM_SUCCESS)
                   cm_msg(MERROR,"trigger_histo_event","Error triggering event from frontend (%d)",status);
               else {  // successfully triggered event
                   event_triggered=TRUE;
                   status =cm_disconnect_client(hconn, FALSE);
                   if (status != CM_SUCCESS)
                       cm_msg(MERROR,"trigger_histo_event","Error disconnecting client (%d)",status);
               }
           }
       }
       else
           cm_msg(MERROR,"trigger_histo_event","Frontend client %s not running (%d)",
                  ClientName,status);
   } 
   return(event_triggered);
}

Deferred Transition

This option permits the user to postpone any transition issued by any requester until some condition is satisfied. For example:

• It may not be advisable to pause or stop a run until some hardware has turned off a particular valve.
• The start of the acquisition system should be postponed until the beam rate has been stable for a given period of time.
• While active, a particular acquisition system should not be interrupted until the "cycle" is completed.

In these examples, any application having access to the state of the hardware can register to be a "transition Deferred" client. The MIDAS system will then catch any transition request and postpone the trigger of such a transition until the condition is satisfied.

The Deferred transition requires 3 steps for setup

1. Register for the deferred transition
2. Provide a callback function to serve the deferred transition
3. Implement the condition code

Note that you should only have ONE frontend that defines a deferred transition (as this niche feature that was implemented with this assumption in mind...).

The following example demonstrates this process:

 BOOL transition_PS_requested=FALSE; // global
                                             //
 INT frontend_init()
 {
   // register for deferred transition
                                             //
   cm_register_deferred_transition(TR_STOP, wait_end_cycle);
   cm_register_deferred_transition(TR_PAUSE, wait_end_cycle);
   ...  
 }
/*
*/ 
 //-- Deferred transition callback
 BOOL wait_end_cycle(int transition, BOOL first)
 {
   if (first) {
     transition_PS_requested = TRUE;
     return FALSE;
   }
                       //
   if (end_of_mcs_cycle){
     transition_PS_requested = FALSE;
     end_of_mcs_cycle = FALSE;
     return TRUE;
   }
   else
     return FALSE;
 }
/*
*/
 INT read_mcs_event(char *pevent, INT offset)
 {  
     ...     // read out data at end of cycle
     ...
     end_of_mcs_cycle = TRUE; // end of cycle 
                              //
     if (!transition_PS_requested)
        start_cycle(); // start a new cycle 
     return bk_size(pevent);
  }

In the example above,

• The frontend code is registered for PAUSE and STOP using cm_register_deferred_transition(). The second argument wait_end_cycle is the declaration of the callback function.
• The callback function wait_end_cycle will be called as soon as the transition is requested with the Boolean flag first set to TRUE.
• By setting transition_PS_requested TRUE , the user will be provided with the acknowledgment of the transition request.
• By returning FALSE from the callback, the transition is prevented from occurring.
• As soon as the user condition is satisfied (end_of_mcs_cycle = TRUE), the return code in the callback will be set to TRUE and the requested transition will be issued.

While the transition is Deferred, the odb key /runinfo/Requested transition will contain the transition code, and the d mhttpd webserver main status page will indicate that a deferred transition is in progress.

Once in deferred state, an odbedit override command can be issued to force the transition to happen,

>odbedit
odb> stop now    (or "start now")

or /runinfo/Requested transition can be set to 0. The transition will then take place on the next stop or start command.

Compilation using CMake

Here is a "minimal" CMakeLists.txt file that can be used to compile a user-written frontend (called "myfe" in this case) that uses the mfe framework.

 cmake_minimum_required(VERSION 3.0)
 project(myfe)
 
 # Check for MIDASSYS environment variable
 if (NOT DEFINED ENV{MIDASSYS})
   message(SEND_ERROR "MIDASSYS environment variable not defined.")
 endif()
 
 set(CMAKE_CXX_STANDARD 11)
 set(MIDASSYS $ENV{MIDASSYS})
 
 if (${CMAKE_SYSTEM_NAME} MATCHES Linux)
   set(LIBS -lpthread -lutil -lrt)
 endif()
 
 # Define the executable to be built, and the source code files
 add_executable(myfe.exe myfe.cxx)
 
 # Directories to search for 
 target_include_directories(myfe.exe PRIVATE ${MIDASSYS}/include)
 
 # Libraries to link to
 target_link_libraries(myfe.exe ${MIDASSYS}/lib/libmfe.a ${MIDASSYS}/lib/libmidas.a ${LIBS})

One could then build the executable using the folllowing commands:

 mkdir build
 cd build
 cmake ..
 make

Some older operating systems may require the "cmake3" command to be used instead of "cmake".