Delete Percona-Server/CMakeCache.txt from the build-binary.sh script
Bug #1164699 reported by
Roel Van de Paar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.1 |
Invalid
|
Low
|
Unassigned | |||
5.5 |
Triaged
|
Medium
|
Unassigned | |||
5.6 |
Triaged
|
Medium
|
Unassigned | |||
5.7 |
Triaged
|
Medium
|
Unassigned |
Bug Description
When building various builds (./build/
This feature request to see if we can/should add 'rm Percona-
(hijack; at the same time, can we also make it so that if no options are passed, "." is assumed as default $1?)
tags: | added: pkg |
To post a comment you must log in.
RoelV <email address hidden> writes: build-binary. sh . ; ./build/build- build-binary. sh --debug --valgrind .) CMakeCache. txt CMakeCache. txt' into the build-binary.sh script so that it's a
> Public bug reported:
>
> When building various builds (./build/
> binary.sh --debug . ; ./build/
> it's easy to forget to include deletions of Percona-
> Server/
>
> This feature request to see if we can/should add 'rm Percona-
> Server/
> cleaner build automatically, each time.
This is probably a really good idea, CMake is fairly awful at doing such
things, and as a workaround we have the bzr clean-tree option enabled in
most Jenkins builds.
--
Stewart Smith