Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / podusowski/pake issues and pull requests
#24 - pake unusable on windows after includes are using absolute path.
Issue -
State: open - Opened by Quasek over 9 years ago
- 2 comments
Labels: bug
#24 - pake unusable on windows after includes are using absolute path.
Issue -
State: open - Opened by Quasek over 9 years ago
- 2 comments
Labels: bug
#23 - when giving source filename to the compiler, use absolute paths
Issue -
State: closed - Opened by podusowski over 9 years ago
Labels: inconvenience
#23 - when giving source filename to the compiler, use absolute paths
Issue -
State: closed - Opened by podusowski over 9 years ago
Labels: inconvenience
#22 - easier pake deployment
Issue -
State: open - Opened by podusowski over 9 years ago
Labels: inconvenience
#22 - easier pake deployment
Issue -
State: open - Opened by podusowski over 9 years ago
Labels: inconvenience
#21 - exclude system includes from dependency graph
Issue -
State: closed - Opened by podusowski over 9 years ago
- 1 comment
Labels: enhancement
#21 - exclude system includes from dependency graph
Issue -
State: closed - Opened by podusowski over 9 years ago
- 1 comment
Labels: enhancement
#20 - Checking modified file which has been moved 'crashes' pake with fatal error.
Issue -
State: closed - Opened by Quasek over 9 years ago
- 4 comments
Labels: bug
#20 - Checking modified file which has been moved 'crashes' pake with fatal error.
Issue -
State: closed - Opened by Quasek over 9 years ago
- 4 comments
Labels: bug
#19 - To not print traceback when run_before or run_after exits with error code.
Issue -
State: closed - Opened by Quasek over 9 years ago
- 1 comment
Labels: duplicate
#19 - To not print traceback when run_before or run_after exits with error code.
Issue -
State: closed - Opened by Quasek over 9 years ago
- 1 comment
Labels: duplicate
#18 - Building object directory is computed by using path to source given in .pake file
Issue -
State: open - Opened by Quasek over 9 years ago
Labels: bug
#18 - Building object directory is computed by using path to source given in .pake file
Issue -
State: open - Opened by Quasek over 9 years ago
Labels: bug
#17 - Variable printing output is not human readable.
Issue -
State: open - Opened by Quasek over 9 years ago
Labels: inconvenience
#17 - Variable printing output is not human readable.
Issue -
State: open - Opened by Quasek over 9 years ago
Labels: inconvenience
#16 - Fix to displaying variable which holds nothing.
Pull Request -
State: closed - Opened by Quasek over 9 years ago
- 1 comment
#16 - Fix to displaying variable which holds nothing.
Pull Request -
State: closed - Opened by Quasek over 9 years ago
- 1 comment
#15 - Parser rewrite
Issue -
State: closed - Opened by salwator over 9 years ago
- 2 comments
Labels: refactoring
#15 - Parser rewrite
Issue -
State: closed - Opened by salwator over 9 years ago
- 2 comments
Labels: refactoring
#14 - errors from run_* give ugly output
Issue -
State: open - Opened by podusowski over 9 years ago
Labels: inconvenience
#14 - errors from run_* give ugly output
Issue -
State: open - Opened by podusowski over 9 years ago
Labels: inconvenience
#13 - bash-complete module
Issue -
State: open - Opened by podusowski over 9 years ago
Labels: enhancement
#13 - bash-complete module
Issue -
State: open - Opened by podusowski over 9 years ago
Labels: enhancement
#12 - Port pake to python3
Issue -
State: open - Opened by salwator over 9 years ago
- 1 comment
Labels: brainstorm
#12 - Port pake to python3
Issue -
State: open - Opened by salwator over 9 years ago
- 1 comment
Labels: brainstorm
#11 - Additional info while parsing error.
Pull Request -
State: closed - Opened by Quasek over 9 years ago
- 1 comment
#11 - Additional info while parsing error.
Pull Request -
State: closed - Opened by Quasek over 9 years ago
- 1 comment
#10 - Pake parsing error does not indicate where error occurs
Issue -
State: open - Opened by Quasek over 9 years ago
- 2 comments
Labels: bug
#10 - Pake parsing error does not indicate where error occurs
Issue -
State: open - Opened by Quasek over 9 years ago
- 2 comments
Labels: bug
#9 - Added python-way creating a directories.
Pull Request -
State: closed - Opened by Quasek over 9 years ago
#9 - Added python-way creating a directories.
Pull Request -
State: closed - Opened by Quasek over 9 years ago
#8 - Unable to disable output coloring.
Issue -
State: open - Opened by Quasek over 9 years ago
- 4 comments
Labels: inconvenience
#8 - Unable to disable output coloring.
Issue -
State: open - Opened by Quasek over 9 years ago
- 4 comments
Labels: inconvenience
#7 - pake parser module is colliding with python's parser module
Issue -
State: closed - Opened by Quasek over 9 years ago
- 2 comments
Labels: bug, blocked
#7 - pake parser module is colliding with python's parser module
Issue -
State: closed - Opened by Quasek over 9 years ago
- 2 comments
Labels: bug, blocked
#6 - on windows, pake crashes with "bad marshal data (string size out of range)"
Issue -
State: closed - Opened by podusowski over 9 years ago
- 1 comment
Labels: bug
#6 - on windows, pake crashes with "bad marshal data (string size out of range)"
Issue -
State: closed - Opened by podusowski over 9 years ago
- 1 comment
Labels: bug
#5 - new token and variable: shell
Issue -
State: open - Opened by podusowski over 9 years ago
- 1 comment
Labels: enhancement
#4 - package downloading system
Issue -
State: open - Opened by podusowski over 9 years ago
Labels: enhancement, brainstorm
#3 - continous mode
Issue -
State: open - Opened by podusowski over 9 years ago
- 2 comments
Labels: enhancement, brainstorm
#2 - warning when link_with(x) is used without depends_on(x) if x is in local tree
Issue -
State: open - Opened by podusowski over 9 years ago
- 2 comments
Labels: enhancement, brainstorm
#1 - compiler commands generation
Issue -
State: open - Opened by podusowski over 9 years ago
Labels: enhancement