haxe build.hxml target

[Todor Angelov]

hi,

what about "haxe build.hxml target" ?

if build.hxml contain all targets definitions in "--next" sections

$haxe build.hxml

will compile all of them,but

$haxe build.hxml flash

will compile only flash

this in additions with init. macros will avoid writing building scripts and work only with pure haxe

:)

[Philippe Elsass]

That would work if we could "name" the --next sections:
--next client
-js index.js
-main ClientMain
--next server
-php www
-main ServerMain

And either you build all, or you choose 'haxe build.hxml client'.

--
To post to this group haxe...@googlegroups.com
http://groups.google.com/group/haxelang?hl=en
---
You received this message because you are subscribed to the Google Groups "Haxe" group.
For more options, visit https://groups.google.com/d/optout.

[Todor Angelov]

yes. the same thing :)
a way to point what you want to compile from all-in-one hxml file
and the "project cfg" can be saved in another json file for example

> You received this message because you are subscribed to a topic in the

[Andy Li]

You can have similar functionality by arranging the hxml like those of haxe's unit test.

See "compile.hxml" in https://github.com/HaxeFoundation/haxe/tree/development/tests/unit

compile.hxml compiles everything.

compile-js.hxml will only compile the js target.

Best regards,

Andy

[Todor Angelov]

yes, of course. currently i use that way. a lot of files around.
i can write shell script to build or neko app or combo linux-win
binary but why ...

[Brennan Kinney]

Why not just make a small build app, something like a GUI to enable/check the targets you want, and then save that to a shell script, followed by(or another button to trigger) running the script and building for those targets. Bit of work up front but would achieve the same thing without having to manually edit files and the support you're requesting? Could then make it available on github for others to use/contribute, HaxeRoundup and the like could spread the word.

[Aaron]

Here is a tool I created that lets you use haxe as the build script language:

https://github.com/Randonee/easybuild

It basically lets you call functions in the build script from the command line.

[Brennan Kinney]

Cool! looks useful :)

[Todor Angelov]

hi brennan,
it's a simple few line of code hack and because haxe is cross-platform
you will have it everywhere even there is no neko installed.
it's a not request but evolution of existing feature, "named next" as
pointed philippe.
i prefer to stay 90% of time with pure haxe and
shell-console/web-browser as gui.
right now i use js.hxml, cpp.hxml, etc ... but if want to change
appsize for example i have to edit all of them.
in all-in-one.hxml i have to edit only "each" section...

[Todor Angelov]

well, i see no interest from haxe team.
so i created hxmake to work with.
it mimics bash shell and allows scripting that shell from haxe program
and as side effect can build projects too.
it is pure haxe, only 2 dependencies: hscript and part of my abv
library. it no need neko to work. it use json or hxml as project
file.
i have worked prototype yet and i'll publish the code in next few days...