Re:The Makefile I use with JavaScript projects
by theothershoe on Wednesday February 28, 2018 @12:10PM
(#16484553)
Good point - cross platform issues are a concern. I've noticed in the past that OS X machines tend to run older versions of Make (unless the owner has installed a newer version with Homebrew). It is a good idea to pay attention to the Make features that you use, understand which features were added in recent versions, and be aware of which features are specific to GNU Make. In my projects I recommend that users make sure that they are in fact using GNU Make.
Some systems might not support the `-p` flag in `mkdir -p`, or the `-rf` flags in `rm -rf`. There are scripts distributed on NPM called `mkdirp` and `rimraf` to work around such issues.
Re:The Makefile I use with JavaScript projects
by rmgraham on Wednesday February 28, 2018 @11:34AM
(#16484122)
You can use forward slashes for paths on Windows in your Makefile. They are actually required if you want to use wildcards.
Re:The Makefile I use with JavaScript projects
by dblotsky on Wednesday February 28, 2018 @02:13PM
(#16485784)
Make works on Windows. You can get it standalone, or as part of MinGW (and then even other Unix tools will work).
Re:The Makefile I use with JavaScript projects
by metalliqaz on Wednesday February 28, 2018 @11:28AM
(#16484073)
Ah yes, the horror of autoconf and automake...
Re:The Makefile I use with JavaScript projects
by wbkang on Wednesday February 28, 2018 @01:14PM
(#16485214)
Btw Windows has supported slashes forever. Just don't mix the two.
What is the best approach to make sure your Makefile will work as expected on every platform, meaning, windows included?
For example: Can we write file paths using forward-slashes, or is it still an issue? I imagine running it via git bash (bash provided by the git installer on windows).