Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

please reconsider from single brittle Big bang build to convenient accessible modular approach stepwise small builds that make each chapter really independent and avoids early unnecessary complex decluttering of all dependencies at once when something goes wrong #18

Open
Delli opened this issue Dec 13, 2023 · 0 comments

Comments

@Delli
Copy link

Delli commented Dec 13, 2023

Here's a recommended directory structure for managing multiple executables in a Stack project:

.
├── App1
│ ├── Main.hs
│ └── stack.yaml
├── App2
│ ├── Main.hs
│ └── stack.yaml
├── App3
│ ├── Main.hs
│ └── stack.yaml
└── stack.yaml
Each App# directory contains the Haskell source code and Stack configuration for a specific executable. This allows you to build and run each executable independently using the following commands:

stack build App1
stack build App2
stack build App3
You can also run each executable directly from the corresponding directory:

cd App1
stack exec Main
This approach promotes modularity and makes it easier to reuse code between different executables. You can also define shared libraries and dependencies using Stack's configuration files.

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

No branches or pull requests

1 participant