| Age | Commit message (Collapse) | Author |
|---|
|
By defining the ERLANG_OTP or ERLANG_HIPE variable, you
can let Erlang.mk manage which version of Erlang/OTP will
be used for your project. It will build it if necessary,
and will activate it automatically when make is invoked.
|
|
Should act the same way as the Triq plugin, making switching
mostly painless, excluding the differences between the two
libraries.
|
|
Run erlydtl after compilation of project src. This accommodates erlydtl configs that include custom modules.
|
|
This allows all plugins to append to existing variables
and makes it easier to augment the functionality of the
core plugins.
|
|
Syntastic, an Erlang syntax checker plugin for Vim, uses the Erlang
compile application to get compilation errors and warnings. Therefore it
needs cooperation from the build system to get the appropriate compile
flags.
Currently it supports Rebar by parsing the configuration file. To add
support for Erlang.mk, we need new Make targets to return the compile
flags.
This plugin adds three targets:
o make show-ERL_LIBS
o make show-ERLC_OPTS
o make show-TEST_ERLC_OPTS
Separate patches for Syntastic's builtin checker and syntaxerl are
ready: they simply run those targets and parse the output.
|
|
This is a proof of concept at the moment. It only runs
the release in 'console' mode at the moment. I am expecting
users to want a mix of both self extracting (without removing
when done) and self running (with removal when done) archives.
There is currently no way to configure the behavior and so
the files get deleted when the release terminates (self running
use case).
The SFX archive will only be created when the SFX variable
is set (either in the Makefile or through the command-line).
There are currently no documentation. Just "make SFX=1".
|
|
.. to fetch and list deps recurvively.
Therefore, they work on direct dependencies, dependencies' dependencies,
and so on. Nothing is built with those targets.
The following targets are also available to work on other kinds of
dependencies:
make fetch-doc-deps
make fetch-rel-deps
make fetch-test-deps
make fetch-shell-deps
make list-doc-deps
make list-rel-deps
make list-test-deps
make list-shell-deps
In all cases, they include "normal" and eg. "test" dependencies of the
top-level project, then only "normal" dependencies' dependencies.
It's possible to include several kinds in one go:
make fetch-deps DEP_TYPES='doc test'
make list-deps DEP_TYPES='doc test'
As it may be difficult to use the output of `make list-*` because
the list could appear after other targets output (like dependencies
fetching), the list is available in files pointed by the following
variables:
$(ERLANG_MK_RECURSIVE_DEPS_LIST)
$(ERLANG_MK_RECURSIVE_DOC_DEPS_LIST)
$(ERLANG_MK_RECURSIVE_REL_DEPS_LIST)
$(ERLANG_MK_RECURSIVE_TEST_DEPS_LIST)
$(ERLANG_MK_RECURSIVE_SHELL_DEPS_LIST)
Internally, `list-deps` is simply implemented on top of `fetch-deps`:
the latter fills a sorted log with all the directories it traversed.
`list-deps` finally just prints the log file to stdout.
Fixes #560.
|
|
This is a breaking change for Elvis users, who should now
use the external plugin available at https://github.com/inaka/elvis.mk
|
|
We can now use 'make -j 32' again. All tests pass. There might
be some issues left with the areas that are not fully tested
yet (some plugins).
A few changes in behavior:
* 'make app' will also do 'make deps' unless SKIP_DEPS is set.
You can use 'make app-build' instead to just build the application.
* 'make rel' will also do 'make app' (and therefore deps). There
are no alternative target to keep the old behavior at this time.
|
|
|
|
This is a preliminary work, good enough to be used in some,
but not all, projects. Tests cover the current functionality.
Documentation has been written but will be committed at a
later stage, as it covers more than just this target (the
target is documented as part of a "Compatibility with other
build tools" chapter).
|
|
If you were using the index file as a "lock file",
bear with me for a moment, equivalent functionality
will soon be added. :-)
|
|
|
|
Rebased and moved ct.cover.spec into the test/ directory.
|
|
The ci plugin allows testing your Erlang project across
any number of Erlang versions.
|
|
|
|
|
|
|
|
|
|
|
|
The general idea is that erlang.mk now keeps track of what kind
of build it generated. A test build is valid for all subsequent
test target invocations. A normal build is only valid for itself
and releases.
This rework adds the ability to specify deps to eunit.
The EUNIT_DIR variable is gone in favor of a more global TEST_DIR.
The tests-ct target got renamed to ct and documented.
Many more minor changes were done during the course of testing
these changes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* The build.config says what gets into the generated erlang.mk.
* The default erlang.mk in the repository hasn't changed yet.
* Clean targets were separated into "clean" and "distclean".
* The "help" target was added to display some help message.
I probably broke a couple things...
|
