id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
222	Custom defined build variants are not working as expected	Md Abdur Rahim	somebody	"Have a new variant defined like this.

variant debug-ssl : debug : <define>UNICOMM_SSL ;

Evetything works perfectly ""inside"" current project (Jamroot) - every targets are built correctly. But if we try to use another project by declaring it with use-project rule

use-project smart : $(SMART_ROOT) ;

When we start building the ""first"" library which depends on smart and specify build variant debug everything is also fine. But if we try to use early defined debug-ssl variant bjam process just finishes when tries to unwind first target defined by smart project (e.g. smart//smart_debug_out) and used as source <library> by ""first"" library. 
BJam even says nothing. Process just exits and that's all.
I suppose if an error existed, it would say that error encountered.

The target looks like this:
lib smart_debug_out
		: debug_out.cpp # sources
                  /boost/iostreams//boost_iostreams
		: <link>static  # requirements
		; 

I tried to explicitly specify targets for every variant (debug, debug-ssl) but it makes no difference. 

Something like this.

lib smart_debug_out
		: debug_out.cpp # sources
                  /boost/iostreams//boost_iostreams
		: <link>static  # requirements
                  <variant>debug
		; 

lib smart_debug_out
		: debug_out.cpp # sources
                  /boost/iostreams//boost_iostreams
		: <link>static  # requirements
                  <variant>debug-ssl
		; 

And again debug works, but debug-ssl makes bjam exits on half of the way.

I also used 
--debug-configuration --debug-building options to monitor the build  
process. It is good seen if view attachments with any diff tool.


"	defect	closed	major		component1	2.0	invalid	variant rule