Opening Files from the Command Line
You can call Sigasi Studio from the command line to open files. Just run
sigasi yourFile.vhd. You can also drag and drop files on the Sigasi Studio
icon to open them.
You can specify a linenumber by appending
+yourLineNumber to the
command line. For example:
sigasi test.vhd +10 will open
You can also specify the project location with the
-p <project path> parameter.
If the specified project was not open in the workspace yet, this will import
and open the project in the workspace.
Note that the VHDL file you specify on the command line has to be in an open Sigasi project to enjoy all of Sigasi Studio’s powerful editing and navigation features. If the file you open from the command line is not in a Sigasi Studio project, Sigasi Studio opens the file as an external file. This is nevertheless really handy for quick edits.
This feature enables you to configure Sigasi Studio as default editor for other EDA tools.
Note You could get a firewall warning when you start Sigasi Studio because Sigasi Studio opens and listens to a port (4444 by default). This is necessary for the communication between the running Sigasi Studio instance and the command line executable. Configure your firewall to allow Sigasi Studio access for opening this port.
Eclipse plugin users can also use this feature but need to specify a few
more command line options. You have to type
eclipse -application com.sigasi.runner.open instead of
eclipse -application com.sigasi.runner.open test.vhd +10 will
test.vhd at line 10.
Other command line options
You can add some extra parameters to Sigasi Studio to modify the behavior.
-help: show simple command line usage information
-data <location>: specifies the workspace location
-noSplash: do not show the splash screen at startup
-application org.eclipse.ui.ide.workbench: to use the default Eclipse workbench launcher instead of the Sigasi Studio workbench launcher
-consoleLog: log all debug information in the console (in addition to the regular log file)
-refresh: force refresh of workspace
-showLocation: show workspace location in title bar
Run Sigasi Studio with multiple users on the same server
If Sigasi Studio (>=3.8) is used on a server with multiple users concurrently, the following changes need to be made:
sigasi/sigasi.iniadd following lines between
You can edit VHDL files without setting up a project. When a file that doesn't belong to a project is opened in Sigasi Studio, this file is called an external file and it will be opened in single file mode.
Single file mode is a limited environment in which not all Sigasi Studio features are available. Navigation only works within a file. For that reason missing declaration are not flagged as errors.
There are several ways to open VHDL files:
- Drag the files to the editor window.
- Open the file from the command line
- Drag the files to the Sigasi Studio icon
- Click File > Open File…
If the file belongs to a project, Sigasi Studio will open the file as part of that project. If not Sigasi Studio opens the file as external file.
In general, if you want to benefit from all of the Sigasi Studio features, you should set up a proper project.
Setting up Sigasi Studio as Default Editor
To configure Sigasi Studio as default VHDL editor in Windows:
- Find a VHDL file in the File Explorer
- Right-click and select Open with > Choose default program…
- Next click the Browse button and select the Sigasi Studio executable (
<path to Sigasi Studio>/sigasi.exe)
- Next Sigasi Studio will appear in the list of programs
- Verify that "Always use the selected program to open this kind of file" is enabled
- Confirm with OK
Repeat this procedure for
*.vhd files and for
- Find a VHDL file in Dolpin or Konqueror
- Right-click and select Open with > Other…
- Enter the path of the Sigasi Studio executable (or use the browse button)
- Click the Remember application association for this type of file so that all other VHDL files will also get opened with Sigasi Studio.
- Click OK
- Find a VHDL file in Nautilus
- Right-click and select Open with > Other Application…
- In Use a custom command: Enter the path of the Sigasi Studio executable (or use the browse button)
- Click the Remember this appliation for "VHDL document" files so that all other VHDL files will also get opened with Sigasi Studio.
- Click Open
Mac OS X
When I double-click a VHDL file, I want it to open with my favorite VHDL editor. Sigasi Studio, obviously.
Here is how to set this up in Mac OS X:
- Find a VHDL file in the Finder
- Right-click and select Get Info
- Select Open with > Other… and find your Sigasi Studio application
- Click Change All… so that all other VHDL files will also get opened with Sigasi Studio.
Repeat this procedure for
*.vhd files and for
Altera Quartus II
In Altera Quartus II, open the preferences page in Tools > Options > General > Preferred Text Editor.
As command-line options, you should have
%f +%l -p %p. Optionally you
-noSplash to skip the splash dialog.
You can configure Sigasi Studio to be the preferred editor for Xilinx Vivado.
- In Xilinx Vivado, click Tools > Settings...
- Open the Tool Settings > Text Editor tab
- Locate the Current Editor drop down menu and instead of 'Vivado Text Editor (default)' select 'Custom Editor...'
- If needed click the ... button and in the pop-up dialog enter:
<path to Sigasi Studio>/sigasi.exe [file name] +[line number]
- Click OK to close the dialog and OK to close the Settings window.
To configure Sigasi Studio as default VHDL editor in Xilinx ISE:
- In Xilinx ISE, Click Edit > Preferences and ISE General > Editors
- Select Custom instead of ISE Text Editor
- If Sigasi Studio is on your path enter
sigasi.exe $1 +$2(Windows) or
sigasi $1 +$2(Linux). If Sigasi Studio is not on your path, use the absolute path instead. If there are spaces in this path, you need to enclose the path in curly braces . For example:
c:\\My\ Applications\sigasi\sigasi.exe $1 +$2.
If you now open any VHDL file in Xilinx ISE, Sigasi Studio will automatically open the selected file.
You can find more info on configuring Xilinx ISE to work with external editors in the Xilinx documentation.