Skip to content
Snippets Groups Projects
Select Git revision
  • main default protected
  • b-mpi3
  • 2.1.16-patches protected
  • averbyts-main-patch-10254
  • 2.1.16.1-FastCaloSimExternal
  • powhegdependencies
  • rwang-main-patch-54603
  • 1.0 protected
  • ActsAthSimulation
  • emoyse-main-patch-02904
  • master_archived
  • bootstraps
  • master_1.0_bouquet_cpack_ForAnalysis
  • add_bootstrapgenerator
  • my-version-of-externals
  • ACTS-rebuild
  • rbianchi-master-patch-18042
  • 2.0.113-patches protected
  • fixFindPython
  • 1.0.48-patches protected
  • 2.1.45
  • 2.1.44
  • 2.1.43
  • 2.1.16.7
  • 2.1.16.6
  • 2.1.16.5
  • 2.1.16.4
  • 2.1.42
  • 2.1.41
  • 2.1.40
  • 2.1.39
  • 2.1.38
  • 2.1.37
  • 2.1.16.3
  • 2.1.36
  • 2.1.35
  • 2.1.34
  • 2.1.16.2
  • 2.1.33
  • 2.1.32
40 results
Blame Permalink
  • Frank Winklmeier's avatar
    be3ef593
    Add and execute script to clean stale files from build area · be3ef593
    Frank Winklmeier authored 
    For incremental builds, deleting python modules (or entire packages) can
lead to stale .pyc files in the binary directory, which will be used
by python despite the original source having been deleted. Make sure
during the cmake configuration that we do not have any such stale files
in the binary directory.
    be3ef593
    History
    Add and execute script to clean stale files from build area
    Frank Winklmeier authored 
    For incremental builds, deleting python modules (or entire packages) can
lead to stale .pyc files in the binary directory, which will be used
by python despite the original source having been deleted. Make sure
during the cmake configuration that we do not have any such stale files
in the binary directory.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.