Skip to content

Conversation

@veselink1
Copy link
Contributor

@veselink1 veselink1 commented Feb 26, 2025

Provides a different way of interacting with the container. Instead of having to drop into an interactive Docker session, one can just execute the desired command into the container by running in their native shell session:

  exec-builder cmake -GNinja ..

It lets me use my macOS shell:

dev/master-debug-linux/build via △ v3.30.2 took 4m9s
❯ exec-builder ninja
[27/983] Building CXX object couchstore/CMakeFiles/couchstore_view_objs.dir/Unity/unity_1_cxx.cxx.o

Provides a different way of interacting with the container. Instead of
having to drop into an interactive Docker session, one can just execute
the desired command into the container by running in their native shell
session:

```
  exec-builder cmake -GNinja ..
```
@veselink1
Copy link
Contributor Author

@ceejatec, I'm wondering, would it make sense to restructure the code such that there is one entry point?

cbbuilder create ...
cbbuilder enter ...
cbbuilder exec ...

Just an idea, curious to find out what you think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant