.. _How to handle Simulator and Command Line Macros:

How to handle Simulator and Command Line Macros
===============================================

Some simulators define proprietary pre-processing that might have some implications on the actual simulated code (see for example in OVM lib ``ifdef INCA`` occurrences).

Also, many times, compilation/run scripts take as arguments macro definitions.

See :ref:`Build Configurations` for enhanced support of simulator commands files.

Until we'll fully integrate with all simulators and/or we provide preferences for specifying macros and means for easily turning them on/off, we recommend to create a dummy \*.sv file that you set first in the top files project property as follows:

#.  Create a separate dummy \*.sv file (**eclipse_simulator_macros.sv**) where you'll define simulator macros guarded by **ifndefs**.
#.  Put the dummy macros file in your project.
#.  Configure the **Project Top Files** so that the dummy macros file will be the first one.
#.  Rebuild.

Dummy macros might look like: 

.. figure:: ../../images/vlogdt-dummy-macros.png
