Skip to content

Update gitignore for macOS build artifacts - #22288

Open
draco892 wants to merge 5 commits into
darktable-org:masterfrom
draco892:Fix/Issue_22287_Ignore_macOS_build_artifacts_and_generated_application_files
Open

draco892 wants to merge 5 commits into
darktable-org:masterfrom
draco892:Fix/Issue_22287_Ignore_macOS_build_artifacts_and_generated_application_files

Conversation

@draco892

Copy link
Copy Markdown

This pull request updates .gitignore to ignore the files and directories generated during macOS compilation and application packaging.

It adds rules for the generated macOS binaries, libraries, support files, .app bundles, and packaging script backup files. Existing entries were also reorganized into clearer sections.

This keeps the working tree clean after a macOS build and prevents generated artifacts from being accidentally committed.

See: #22287

@zisoft

zisoft commented Sep 15, 2026

Copy link
Copy Markdown
Collaborator

This occurs when building with MacPorts. The homebrew based build process creates all files under ./build.

The better solution would be to update the package building script for MacPorts to use the build directory (@MStraeten ?)

@zisoft

zisoft commented Sep 15, 2026

Copy link
Copy Markdown
Collaborator

I think it would be sufficient to edit ./packaging/macosx/darktable.bundle and change the destination for the package:

<?xml version="1.0"?>
<app-bundle>
  <meta>
    <prefix name="default">/opt/local</prefix>
    <prefix name="dt">/usr/local</prefix>
    <destination overwrite="yes">../../build/macosx/package</destination>
    <run-install-name-tool/>
    <gtk>gtk+-3.0</gtk>
  </meta>
  ...

(this is untested, I don't use MacPorts)

@victoryforce

Copy link
Copy Markdown
Collaborator

@draco892 - Instead of merging master into your feature branch, use rebase to move your local commits on top of the latest master. This keeps a clean, straight line of history without extra merge nodes.

@zisoft

zisoft commented Sep 18, 2026

Copy link
Copy Markdown
Collaborator

@draco892 : I don't think that the .gitignore file needs to be updated.

Did you try my suggestion above?

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.

3 participants