[v2] como support

From: David Abrahams (dave_at_[hidden])
Date: 2005-05-23 10:26:22

What's up with como-win.jam? Apparently my copyright is on it, but
most of the work I did trying to figure out how to get that compiler
to work for BBv1 has been discarded. All of that setup code was
important at some point for me:

$(COMO_BACKEND_SETUP)
$(COMO_BACKEND_INCLUDE_SETUP)
$(COMO_BACKEND_LIB_SETUP)
$(COMO_PATH_SETUP)
$(COMO_BASE_SETUP)

I had a hard time getting this toolset to work for me in v2
:(. I had to do something like:

using como : 4.3.3 : 
"set PATH=c:/tools/como433/bin;%PATH% &&" 
"set COMO_MS_INCLUDE=\"c:/program files/microsoft visual studio .net 2003/vc7/include\" &&" 
como.exe ;

just to get started, from which I get

como-win.compile.c++ bin\copy.test\como-win-4.3.3\debug\copy.obj
Command-line error #595: too many arguments on command line

1 catastrophic error detected in the compilation of " --sys_include=c:/program".
Compilation terminated.

Yes, I need to have como433/bin in my PATH or como.exe complains that
it can't find cpfe433.exe.

Okay, so I eventually got past the line length issue like this:

using como : 4.3.3 : 
"set PATH=c:/tools/como433/bin;%PATH%
set COMO_MS_INCLUDE=\"c:/program files/microsoft visual studio .net 2003/vc7/include\"
"como.exe
;

But now:

como-win.compile.c++ ..\..\..\bin.v2\libs\bind\test\bind_test.test\como-win-4.3.3\debug\bind_test.obj
Cannot execute 'cl' process. OS says it failed because: No such file or directory
Failure while executing 'cl' compiler ...email Comeau for advice.

set PATH=c:/tools/como433/bin;%PATH%
set COMO_MS_INCLUDE="c:/program files/microsoft visual studio .net 2003/vc7/include"
como.exe -c -e5 --no_version --no_prelink_verbose --display_error_number --long_long --diag_suppress=9,21,161,748,940,962 -D__STL_LONG_LONG -DBOOST_ALL_NO_LIB=1 --no_inlining -D_WIN32 --exceptions -I"..\..\.." -o "..\..\..\bin.v2\libs\bind\test\bind_test.test\como-win-4.3.3\debug\bind_test.obj" "bind_test.cpp" 

This is a prime example where the promise that you can just write out
the command to execute and we'll figure out the rest just turns out to
be a confusing trap for the poor user.

Obviously if the user sets the path in one element and then calls
como.exe without qualification, if there's any validation code (as
with many toolsets) we'll fail to find como.exe, because it isn't in
the path yet. And if the como toolset tries to do any other
deduction, e.g. extracting the thing we need to put in the PATH,
something like:

using como : 4.3.3 : 
"set COMO_MS_INCLUDE=\"c:/program files/microsoft visual studio .net 2003/vc7/include\" && c:/tools/como433/bin/como.exe" ;

will fail.

We really need to settle on some new approach.
Thoughts?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com