On 30/11/2014 06:10, Marvin Humphrey wrote:
I was able to rebase my changes on top of your perl_build_with_make branch without too much trouble, so I've discarded my own refactoring of charmonizer.main and pushed a new branch go_bindings_2. All non-charmonizer changes were left intact, except for one trivial new commit modifying build.go.
OK, I can push all commits that change charmonizer.main to master anyway. They don't affect the Perl build yet. I'm not so sure about really making the switch for the Perl build system. Maybe the Makefile-based build should be optional for now. On the other hand, if we want to go forward with letting CFC build the static libraries, similar changes have to be made anyway.
We'll probably collide less often in build scripts once we move responsibility for building static archives from our charmonizer apps to CFC.
What do you have in mind regarding the build process? Based on Makefiles or a invoking the C compiler directly?
Nick
