Shared build directory for CPP targets?

[BP]

Hey! I build lots of demos all the time, and pretty much always want to see if they work in CPP targets. 

I find that the first time I build any demo, it takes awhile, but the 2nd time it builds way faster.

I'd like to configure haxe to use a common build directory for all projects, so if a project uses NME, then NME only gets built once, and once it's built, building future CPP targets builds faster, since NME has already been compiled. This would be true of any lib I use. If it's already built for a CPP target, it doesn't need to be built again.

Is this possible? I'm on a mac, but am interested in *general* solutions if possible.....

[BP]

Also, I am familiar with the "haxe --wait" directive for connecting to a running haxe compiler instance, and allowing it to cache build results... I find it works of course, but I think that connecting to a shared, pre-built lib directory for commons libs would probably save more time, if possible... thanks!

[Richard Lee]

Hi...

My company has similar issues.  We have many libraries that we use in a variety of different executables, and would like to have a way of not recompiling the upstream source code each time for each target executable.  We've investigated shared build directories, but find that they don't really work correctly.  We've been thinking of ways of extending haxelib to support build byproducts in the CPP target.  We should talk further.  Currently, were at the WWX 2013 conference in Paris.  Are you here?

Richard

[BP]

Sadly I'm not at WWX... possibly someone there will have an idea on if this could be managed effectively with the existing toolset, or if it'd require an addition to haxe....

[AS3Boyan]

That is true, maybe copying already builded files will help? Maybe some utility will help, I should try that...

This feature is a must have, but sometimes, you will need to clear this build files.

[BP]

hey! i've been crazy busy at work, and haven't had anytime to look at this.... does *anyone* have any idea how to make a shared build directory work? I just tried to build 2 android samples back to back, and it took over 5 min each time.... i'd love to see this become a priority, or common knowledge if it's supported ;-) thanks!

[Richard Lee]

We've made some progress, but don't have anything to share yet.  It looks doable to make haxelibs support precompiled .a/.lib or .so/.dll binaries of the .hx files available for downstream usage *if* the compile flags exactly match.  If you are building the different modules yourself, that should be easy to ensure.

If you'd like to collaborate some on figuring out how to make this work in a more general way, drop me a note!

Richard

On Jun 12, 2013, at 6:20 PM, BP <brad...@gmail.com> wrote:

hey! i've been crazy busy at work, and haven't had anytime to look at this.... does *anyone* have any idea how to make a shared build directory work? I just tried to build 2 android samples back to back, and it took over 5 min each time.... i'd love to see this become a priority, or common knowledge if it's supported ;-) thanks!

--
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 a topic in the Google Groups "Haxe" group.
For more options, visit https://groups.google.com/groups/opt_out.