forks
/
dexed
mirror of https://gitlab.com/basile.b/dexed.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
dexed/docs/features_projects.md

4.9 KiB
Raw Permalink Blame History

title header-includes
Projects <script src="https://cdnjs.cloudflare.com/ajax/libs/anchor-js/4.2.2/anchor.min.js"></script>

Three project formats are supported. For all the formats a single widget is used to display the source files list and the configurations, the project inspector. Project properties are edited in specific widgets.

DUB

Dexed handles DUB projects.

DUB JSON format format is fully supported. DUB SDL format is supported in read-only mode.

The widget used to edit the properties is the DUB project editor.

The option editor exposes a category for DUB. The options specified in this category are applied each time a project is compiled.

Makefiles

Makefiles can be opened as projects.

The rules found in the makefile are interpreted as configurations.

Source files are detected using a list of prefixes. Files located in a sub folder and that start with one of the prefix is then displayed in the project inspector. Custom prefixes can be specified in the Options menu, category Makefile projects. Default prefixes are "src", "import", and "include".

While not very useful for D, Makefile projects allow to use dexed with other languages. Working IDE features are then limited to

  • Compile project
  • The messages reported by make can be clicked to open new files
  • Custom tools can use symbolic strings, allowing for example to setup a custom linter for all the sources detected using the prefixes
  • Searches in the whole project
  • Text completions (based on work-splitting)
  • Integration in project groups

Note that the dialog used to open a project will only recognize "Makefile" and files with the ".mak" extension.

DEXED format

The DEXED format (previously called native format then ce projects) is based on DMD command line interface. The widget used to edit the properties is the DEXED project editor (the format is detailed in this page).

Menu reference

  • "New project": Closes and creates a new project (either with the native format or a DUB project). A warning may be displayed if the current project is not yet saved.
  • "Open project": Opens a project from a dialog.
  • "Open recent": Displays the list of the most recently used projects.
  • "Close project": Closes the current project. A warning may be displayed if the current project is yet not saved.
  • "Save project": Saves the current project.
  • "Save project as": Saves the current project from a dialog.
  • "Add project to group": Adds this project to the project group. See also the page dedicated to the project groups.
  • "Project editor": Displays widget used to edit the project properties,in respect with the format (CE or DUB).
  • "Edit project file": Opens the project file in a new source editor. When saved from a source editor, a project file is directly reloaded.
  • "View project command line": Displays the list of switches and arguments, as they would be passed to the compiler (or the build tool) when compiling.
  • "View in mini explorer": Expands the mini-explorer tree on the folder that contains the project file.
  • "Verify project with Dscanner": Performs some static checks on each source of the project and using Dscanner.
  • "Compile project": Compiles the project using the current configuration.
  • "Compile and run project": Compiles the project using the current configuration and executes the output when the binary produced is executable.
  • "Compile and run project...": Ditto. Before the execution of the binary an input query dialog lets you pass options to the process.
  • "Check semantics": Like Compile project but only checks the program semantics and does not generate object files.
  • "Run project": Executes the project output when the binary produced is executable.
  • "Run project...": Ditto. Before the execution, an input query dialog lets you specify switches and arguments to the process.
  • "Test project": Only for DUB projects. Invoke dub test using the configuration selected in the project inspector.

Other build tools

It's possible to use the custom tools to call other build tools. For example to call make, add a new tool with make as executable and sets the workingDirectory to the folder that contains the makefile. To specify a special target, such as release, add release in the parameters editor. To get make output in the messages, check popUsesPipes in the tool options.