Skip to content

Don't create an empty addons.make for a project without addons (#297) - #680

Closed
danoli3 wants to merge 1 commit into
openframeworks:masterfrom
danoli3:no-empty-addons-make
Closed

danoli3 wants to merge 1 commit into
openframeworks:masterfrom
danoli3:no-empty-addons-make

Conversation

@danoli3

@danoli3 danoli3 commented Oct 25, 2026

Copy link
Copy Markdown
Member

Fixes #297.

baseProject::save always wrote addons.make, so every new project without addons got an empty one. Now it's only written when the project has addons or already has an addons.make (still rewritten, so removing every addon still clears it).

Tested: new project with no addons on osx / linux64 / vs / vscode -> no addons.make; -aofxOsc -> ofxOsc; regenerate with no addons -> existing file emptied. The GUI only reads addons.make when it exists.

@danoli3

danoli3 commented Oct 25, 2026

Copy link
Copy Markdown
Member Author

Combined into #683.

@danoli3 danoli3 closed this Oct 25, 2026
@danoli3
danoli3 deleted the no-empty-addons-make branch October 25, 2026 12:00
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.

projectGenerator CLI creates an empty addons.make where it is not needed

1 participant