[BBv2][msvc] assembler support - asmflags note (low priority)

From: Andrey Melnikov (melnikov_at_[hidden])
Date: 2005-09-19 15:54:51

Reece Dunn wrote:
> 
> I have now attached the resulting msvc assembler support patch.
> 
diff -u -r1.178 builtin.jam
--- tools/builtin.jam	14 Sep 2005 09:54:14 -0000	1.178
+++ tools/builtin.jam	19 Sep 2005 20:00:57 -0000
@@ -54,6 +54,7 @@
feature cflags : : free ;
feature cxxflags : : free ;
feature fflags : : free ;
+feature asmflags : : free ;
feature linkflags : : free ;
feature archiveflags : : free ;
feature version : : free ;

Are we going to have qbflags, rcflags, mocflags, doxflags etc? I dislike 
the idea to modify builtin.jam every time we add a new target type. For 
now it's ok, but in the feature we need to develop a more scalable 
framework. E.g. to put asmflags in types/asm.jam as it's unlikely that 
the feature will be used without the type.

IMO at some point in the feature we'll need to create an abstraction for 
tool types. For example, now we have:

- C compilers
- C++ compilers
- linkers/librarians
- fortran compilers
- ...

We'll have to separate tool type-specific and os-specific abstractions 
from builtin.jam. The file is very big. Also, builtin.jam and common.jam 
can be merged. Now it's unclear what should be done by common.jam and 
what - by builtin.jam

Also, can we just use <flags>?

Andrey