OCaml Forge

Detail: [#1233] user-provided BUILDFLAGS in the Makefile should go into the _oasis file

Features: Browse | Download .csv | Monitor

[#1233] user-provided BUILDFLAGS in the Makefile should go into the _oasis file

Date:
2012-11-08 04:03
Priority:
3
State:
Open
Submitted by:
Francois Berenger (happycrow)
Assigned to:
Nobody (None)
Summary:
user-provided BUILDFLAGS in the Makefile should go into the _oasis file

Detailed description
Hello,

I think the BUILDFLAGS users have to put
before '# OASIS_START' in the Makefile
should be specified in the _oasis file.

It feels kind of strange that the build
description is spread in several files.

Also, it's kind of annoying that this Makefile
has to be put under version control just because
of these BUILDFLAGS.

Regards,
F.

Followup

Message
Date: 2012-11-19 01:03
Sender: Francois Berenger

From ocaml-beginners ML:

I somehow feel DOCFLAGS and BUILDFLAGS should be in the _oasis file, in some way.
Even if we have to pass an option to ocamlbuild, I feel it should
be done via the _oasis file.
Date: 2012-11-08 04:11
Sender: Francois Berenger

It would be nice to have some kind of "fake target"
in the _oasis file, where users can put some
custom commands to execute.
Date: 2012-11-08 04:06
Sender: Francois Berenger

Even additional Makefile targets should be
able to be specified in the _oasis file.

For example, I have in my Makefile:
[...]
# OASIS_STOP
TAGS: *.ml
otags -o TAGS `ls *.ml`

cleaner:
rm -f TAGS tags.ml myocamlbuild.ml setup.ml

And that's one more reason why my Makefile has to be put under
version control.

Regards,
F.

Attached Files:

Changes:

No Changes Have Been Made to This Item