Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mruby
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Libraries
mruby
Commits
2a69f510
Unverified
Commit
2a69f510
authored
Feb 06, 2021
by
Yukihiro "Matz" Matsumoto
Committed by
GitHub
Feb 06, 2021
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #5324 from dearblue/c++-exc
Exclude `<build-dir>/mrbc/**/*` from rake target rules
parents
0bd01c54
5c3b5f42
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
lib/mruby/build/command.rb
lib/mruby/build/command.rb
+2
-2
No files found.
lib/mruby/build/command.rb
View file @
2a69f510
...
...
@@ -104,9 +104,9 @@ module MRuby
rakedep
=
File
.
exist?
(
gemrake
)
?
[
gemrake
]
:
[]
if
build_dir
.
include?
"mrbgems/"
generated_file_matcher
=
Regexp
.
new
(
"^
#{
Regexp
.
escape
build_dir
}
/(.*)
#{
Regexp
.
escape
out_ext
}
$"
)
generated_file_matcher
=
Regexp
.
new
(
"^
#{
Regexp
.
escape
build_dir
}
/(
?!mrbc/)(
.*)
#{
Regexp
.
escape
out_ext
}
$"
)
else
generated_file_matcher
=
Regexp
.
new
(
"^
#{
Regexp
.
escape
build_dir
}
/(?!mrbgems/.+/)(.*)
#{
Regexp
.
escape
out_ext
}
$"
)
generated_file_matcher
=
Regexp
.
new
(
"^
#{
Regexp
.
escape
build_dir
}
/(?!mrb
c/|mrb
gems/.+/)(.*)
#{
Regexp
.
escape
out_ext
}
$"
)
end
source_exts
.
each
do
|
ext
,
compile
|
rule
generated_file_matcher
=>
[
...
...
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