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
Create a MakeFile to simplify project setup and ease the development process.
It requires #161 to complete, so pickup that or wait for it to complete before start working on this.
Hi @GouravSardana !
I want to understand a bit more about Make files. What exact dependencies/ file names should we include in the Make file to compile them?
Also, in the make file resource provided, it is mentioned
Interpreted languages like Python, Ruby, and Javascript don't require an analogue to Makefiles.
oh okay, I just wanted to know what exact files should I include in the Make file to compile them?
Since, only C/C++, Java files need compiling and Python files don't need compiling is mentioned in https://makefiletutorial.com/
Makefile does lot more than just compiling, currently this repository has lot of commands that can be aggregated at one place.
Let me give you an example
all: setup lint test build
setup:
@echo SETUP
pip install -r requirements.txt
lint:
@echo LINT
# Linting it using linters like black, pylint etctest:
@echo TEST
pytest
build:
@echo BUILD
...
publish:
@echo PUBLISH
...
...
These all tasks and other similar tasks will get collected to one place. Currently we have to follow up the procedure to setup the development environment. After implementing Makefile, environment setup and package build will get done in one go, just have to type make.
Note: #161 is work in progress which add poetry as dependency manager, the procedure to setup the development environment requires some changes after that.
Restart triage: P3 — useful command wrappers, not a release prerequisite. No Makefile exists. As the earlier discussion explains, its purpose would be collecting setup/test/build commands, not compiling Python source.
Next step: stabilize those commands and the #161 packaging decision first. If still useful, add small wrappers while documenting equivalent direct commands so Windows contributors do not need Make. Keep publishing separate from ordinary setup/test targets.
Configuration review only. Keeping the issue open.
Activity
shreelakshmijoshi commentedon Mar 8, 2022
Hi @PradyumnaKrishna! Would you assign me this issue under GSSOC?
PradyumnaKrishna commentedon Mar 9, 2022
Done @shreelakshmijoshi
dhruti29 commentedon Mar 21, 2022
Hello, @PradyumnaKrishna I want work on this issue please assign me this issue under GSSOC...!!
GouravSardana commentedon Mar 21, 2022
@dhruti29 , Please go ahead
shreelakshmijoshi commentedon Mar 27, 2022
Hi @GouravSardana !
I want to understand a bit more about Make files. What exact dependencies/ file names should we include in the Make file to compile them?
Also, in the make file resource provided, it is mentioned
And dynamic-cli has all Python files.
GouravSardana commentedon Mar 27, 2022
@PradyumnaKrishna is leading the effort from this side. Can you please explain what we need from our side ?
shreelakshmijoshi commentedon Mar 27, 2022
oh okay, I just wanted to know what exact files should I include in the Make file to compile them?
Since, only C/C++, Java files need compiling and Python files don't need compiling is mentioned in https://makefiletutorial.com/
GouravSardana commentedon Mar 27, 2022
I agree with the point which you mentioned but let’s hear from @PradyumnaKrishna
PradyumnaKrishna commentedon Mar 27, 2022
Makefile does lot more than just compiling, currently this repository has lot of commands that can be aggregated at one place.
Let me give you an example
These all tasks and other similar tasks will get collected to one place. Currently we have to follow up the procedure to setup the development environment. After implementing Makefile, environment setup and package build will get done in one go, just have to type
make.Note: #161 is work in progress which add poetry as dependency manager, the procedure to setup the development environment requires some changes after that.
shreelakshmijoshi commentedon Mar 27, 2022
@PradyumnaKrishna, you're right.
harshsingh32 commentedon May 20, 2023
I would like to work on this issue, please assign this issue to me under GSSoC'23.
GouravSardana commentedon Oct 21, 2026
Restart triage: P3 — useful command wrappers, not a release prerequisite. No Makefile exists. As the earlier discussion explains, its purpose would be collecting setup/test/build commands, not compiling Python source.
Next step: stabilize those commands and the #161 packaging decision first. If still useful, add small wrappers while documenting equivalent direct commands so Windows contributors do not need Make. Keep publishing separate from ordinary setup/test targets.
Configuration review only. Keeping the issue open.