It is nice to see the diversity. Also, the comparisons like these greatly help to understand the outcomes of underlying architecture of both projects much better. =)
On Tue, Jan 13, 2015 at 12:09 PM, Constantine <voi...@gmail.com> wrote: > - Each tool has own subset of options, for example CPPDEFINES is defined > only for C/C++ tool What if multiple tools has the same option? How the value is calculated in this case? > - Output build directory can be set to any place (even outside of project) > for the whole project or for specific nodes That's cool. Why SCons can not reach that and how Aqualid managed to overcome this problem? > - API is different from SCons Is it still possible to provide a conduit, so that Aqualid can still process SCons scripts and tools? Where are the principal differences in SCons APIs that make it incompatible with Aqualid? _______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
