You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there is a single cmake job that populates build/bin/ with the executables for all Python commands present in the code base. However in a current context I want the ability to nominate only a subset of commands (some C++, some Python), and it would be preferable for the build/bin/ directory to be populated exclusively with only the set of commands I nominate. This would require construction of an individual target per Python command. Each of those targets should then depend on the API target, so that the API is created in the build directory only if at least one Python command is built.
The text was updated successfully, but these errors were encountered:
Extending this, for each command represented as a target, there are two separate underlying jobs: creation of the executable, and copying / softlinking of the source code. Those should ideally be represented as two independent tasks to be performed per command target.
Currently, there is a single
cmake
job that populatesbuild/bin/
with the executables for all Python commands present in the code base. However in a current context I want the ability to nominate only a subset of commands (some C++, some Python), and it would be preferable for thebuild/bin/
directory to be populated exclusively with only the set of commands I nominate. This would require construction of an individual target per Python command. Each of those targets should then depend on the API target, so that the API is created in the build directory only if at least one Python command is built.The text was updated successfully, but these errors were encountered: