Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
M
mkimage-profiles
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
2
Issues
2
List
Board
Labels
Milestones
Merge Requests
1
Merge Requests
1
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Ximper Linux
mkimage-profiles
Commits
2f357e44
Commit
2f357e44
authored
Sep 18, 2012
by
Michael Shigorin
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
clean.mk: skip if REPORT requested either
The problem would manifest itself like this: ..:..:.. cleaning up after build sed: can't read .../build.log: No such file or directory
parent
a2b89e66
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
3 deletions
+1
-3
clean.mk
lib/clean.mk
+1
-3
No files found.
lib/clean.mk
View file @
2f357e44
...
@@ -51,11 +51,9 @@ distclean: clean
...
@@ -51,11 +51,9 @@ distclean: clean
# builddir existing outside read-only metaprofile is less ephemeral
# builddir existing outside read-only metaprofile is less ephemeral
# than BUILDDIR variable is -- usually it's unneeded afterwards
# than BUILDDIR variable is -- usually it's unneeded afterwards
# so just zap it unless DEBUG has been requested (moreso for multi
# image builds, UI based ones, and readonly metaprofile; or CHECK)
postclean: build-image
postclean: build-image
@{ \
@{ \
if [ "0$(DEBUG)" -lt 2 -a -z "$(CHECK)" ] && \
if [ "0$(DEBUG)" -lt 2 -a -z "$(CHECK)
$(REPORT)
" ] && \
[ "$(NUM_TARGETS)" -gt 1 \
[ "$(NUM_TARGETS)" -gt 1 \
-o -n "$(__frontend)" \
-o -n "$(__frontend)" \
-o ! -L "$(SYMLINK)" ]; then \
-o ! -L "$(SYMLINK)" ]; then \
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment