From 263224d5e217e54a4382309887728088dba23f7e Mon Sep 17 00:00:00 2001 From: Raul Torres <138264735+rauletorresc@users.noreply.github.com> Date: Thu, 12 Dec 2024 23:26:05 -0500 Subject: [PATCH] [NFC] Fix doc: 'make plugin' instead of 'make standalone-plugin' (#1378) **Context:** Updates related to the standalone plugin rule on the `Makefile `did not made it to the docs. **Description of the Change:** Instruct to use `make plugin` instead of `make standalone-plugin` --- doc/catalyst-cli/catalyst-cli.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/catalyst-cli/catalyst-cli.rst b/doc/catalyst-cli/catalyst-cli.rst index d3e4d4900e..b04c3aaf90 100644 --- a/doc/catalyst-cli/catalyst-cli.rst +++ b/doc/catalyst-cli/catalyst-cli.rst @@ -245,7 +245,7 @@ These plugins are shared objects that include dialects and passes written by thi This means that you can write dialects and passes that can be used with ``catalyst-cli`` and ``quantum-opt``. As an example, the `LLVM repository includes a very simple plugin `_. -To build it, simply run ``make standalone-plugin`` and the standalone plugin +To build it, simply run ``make plugin`` and the standalone plugin will be built in the root directory of the Catalyst project. With this, you can now run your own passes by using the following flags: